A typical Healthcare Information Exchange (HIE) accepts data from an array of disparate sources. Often the data it accepts is semantically and syntactically altered by a providing system to satisfy interfacing requirements. However, there are also cases where data from different sources need to be properly merged before reaching the HIE's interface.
It’s been about a year and half since we first released Intel® SOA Expressway for Healthcare, which is a purpose-built, easy-to-deploy integration appliance for connecting islands of information together to enable a secure, high-performance, best-of-breed health information infrastructure. We have now begun shipping release 2.2, which contains a number of new feature enhancements.
Last April at HIMSS in Chicago, Intel participated in the IHE showcase , which is essentially a huge "plug fest" for healthcare vendors promoting interoperability in healthcare. Integrating the Healthcare Enterprise (IHE) is an initiative by healthcare professionals and industry to improve the way computer systems in healthcare share information. The IHE process delivers a set of interoperability "profiles", which are comprised of established standards to address specific clinical use cases.
I recently participated in a webinar with Ken Rubin from HP (formerly EDS) who is the Chief Architect for their Healthcare practice. The webinar was sponsored by the Healthcare Information Management Systems Society (HIMSS). You can access it on demand by registering here.
Hospitals and IDNs are increasingly looking for new ways to stay connected with their affiliated physicians to enable sharing of health information, streamline the referrals process, and provide seamless access to hospital, lab, PBMs and payer networks. Both hospitals and their affiliated physicians really get excited about the idea of having a consolidated view of patient information and a more integrated workflow, as it is an enabler for increased efficiency, reduced errors and improved outcomes.