Hi Anthony,

In general we build features into OpenVPMS by request from users or integration partners.  In the case of Integrations we are also driven by customers wanting that integration.  

One of the core questions we ask for many of these features is this best done as a core inbuilt feature or as an Integration.  The answer often depended on the fetaure set involved,  our resources at the time, no and quality of available integrations, integration complexity etc.

In the case of Hospital Workflow, the decison was to integrate Smartflow in the core and  not try an replicate what was already a rich feature set that would divert our resources away from some of our other "core" development priorities at the time.

These days the only change to this decision would be not building this into the core but creating the necessary API services so any hospitalisation workflow provider, not just Smartflow,  could provide a plugin to implement this API.  I think this may happen in the future ..

Another example was Rostering, which we handled slightly differently,  we built some very base Rostering functionality in the core OpenVPMS , which could be extended via a plugin, and provided a plugin to Deputy.  

As it stands today we have no roadmap that includes adding Hospital Workflow functionality to the core OpenVPMS but we are always listening to our customers requests so maybe one day. :-)

Cheers

Tony