Technology Overview
One Patient, One Record - Accelerating Healthcare Innovation
Technology Overview
McKesson.  Cerner. Meditech.  GE/IDX. Siemens.  Eclypsis. Epic. NextGen.  GE Logician... we know them all.

Data Integration

The problem of integrating heterogeneous clinical data sources across multiple organizations is one of the core challenges to effective health information exchange. Clinical data sources can vary from widely-used, standards-compliant products to custom data formats particular to an organization. HIEBus™ addresses this problem with an architecture that hosts reusable, modular drivers that - like the data sources they integrate - can be standards-based, product-based, or completely customized. Hosting these drivers within this architecture allows the HIEBus™ to provide unified administration, configuration, and monitoring tools for an organization's various systems and interfaces. By providing "out-of-box" integration solutions when possible and customized integration solutions when necessary, all within a unified architecture, the HIEBus™ can effectively address the range of integration challenges with maximum reuse and manageability.

Example Implementation

Let's get specific. Here is an example of one of our clients that had a mature application infrastructure and wished to enable data sharing with other providers in their community. Specficially, the customer has the following systems they wish to include in the initial data exchange:

  • McKesson Horizon Lab System
  • McKesson STAR Registration System
  • ADAC QuadRIS RIS System
  • SeeBeyond eGate Integration Server

HIEBus™ CDIS architecture was able accommodate all these data sources seamlessly using a combination of approaches it supports. Since the McKesson Horizon and STAR systems had been previously integrated into the CareEvolution RHIO Technology Platform, they were implemented as specific configurations of our standard HL7Driver. These configurations were reused "out-of-the-box". The ADAC QuadRIS system supports a well-established and standards-compliant HL7Interface so this merely required a new configuration of an HL7Driver.

Like most real-world needs, the customer also wished to integrate historical information from their Star, Lab and QuadRIS systems. Because of the modular CDIS approach, these historical loads required minimal development. Data extract scripts supported by Horizon Lab and QuadRIS systems were used but their output was anything but standards based. Our implementation team authored drivers for this historical load. For historical ADT information, a standard STAR extract utility was used to stream historical ADT transactions to a file in an HL7 format.

One Patient, One Record - Accelerating Healthcare Innovation
privacy | site map | contact us | site credits   All Content ©2006 CareEvolution. All Rights Reserved.