agile EHR architectures
See the following -
The Postmodern EHR: What are the Enablers?
Traditional monolithic EHR architectures focus on stability and standardization at the expense of agility. Along with innovation, cloud based deployment and integration of things, agility is the main differentiator when describing the requirements of application architecture for the Postmodern EHR. Achieving agility is impossible for the vast majority of healthcare applications today as they are an inseparable mix of code for user interface, decision logic, workflows and data definitions. New architectures promote agility and reuse by turning the applications inside out and layering the four types of programming into portals, rule engines, process engines and XML data. Let’s look at some examples, layer by layer:
- Login to post comments
The Postmodern EHR: The Data Layer
This second approach entails defining a data layer, which is the most important aspect of the Postmodern EHR architecture from my previous post. Why is this the most important layer? Most healthcare organizations are beginning to realize that their data is more valuable than their applications. Data has become a key asset, since good data is key to improving outcomes, managing chronic disease and enabling population health management. And it needs to be managed for the lifetime of the patient. Which application is going to last that long? What happens to health data when we switch applications?
- Login to post comments