This is the third of a three-part article looking at the area of interoperability and health information exchange (HIE) in the healthcare industry. In the first part, I intended to clearly articulate the key challenges and barriers to adoption faced by those looking to engage in HIE.
Given the acronym soup of the IT industry I am not surprised to get that question and expect to for some time to come. The simple answer is that:
- Service Oriented Architecture (SOA) is a means of designing and building software. It is a manufacturing model.
Going forward for a while, I plan on posting on the deployment architectures and usages of a SOA "soft appliance" platform like Intel SOA Expressway.
A few years ago, we were facing some challenging scalability and costs issues with a key aspect of our enterprise infrastructure. Like many companies we dove head first in the use of XML and web services as a means to refresh a major enterprise application using the latest design patterns of n-tier distributed systems and SOA. Diligent development resulted in an architecture that worked as advertised; it was flexible, far easier to re-configure and re-purpose than its predecessor. That’s the good news and the usage followed.