Author: Terry Bazemore
Sometimes, the business functionality that an organization needs to systematically improve patient care and outcomes, is just not available in the systems that they use on a daily basis. Every day, some health care business executive or IT leader, faces the pain of asking a health care systems vendor to change their "flagship" solution, in order to add some capability, that they know will improve patient care. The response of long timelines and prohibitively high development costs is routinely disheartening. The fact is that rapid changes to health care systems are risky to patient care and the requested changes may not match the direction of the system vendor's product. As a result, rapid enhancements requests never happen fast. The cost of forward progress is often exorbitant and usually associated with long turnaround times that include rounds and rounds of regression testing. (Diagrams and images included inside)
With the advent of modern APIs and now MicroServices, the delivery landscape is changing. Enhancing existing, and delivering new and valued capabilities may be accomplished without vast changes to flagship systems. This can be done by leveraging MicroServices in combination with well-known interface engine technologies and already familiar web and mobile delivery patterns. Because you have access to information in flight, extending capabilities may begin to seem like a do-it-yourself (DIY) pattern. Here we provide an example of how to accomplish this with a walkthrough of a real-world health care scenario.