Community-Based Information Exchange

December 28, 2010 by Mark R. Anderson
| Share | Print
Community-Based HIEs are a Model of Interoperability Among Clinical Information Systems

  • Does not enable advanced community reporting of clinical outcomes.

  • Does not track community disease management protocol.

  • Designed for a single hospital or a hospital exchange that wants to seamlessly provide hospital specific data to its providers in one common view.

  • Traditionally, the data is viewed within the HIE.

  • Data is not transferable into a provider's specific EHR product as discrete data.

    • Type 2

    • Facilitates data sharing between different practices utilizing the same EHR product.

    • Through a specific vendor's data exchange protocols, specific patient data can be exchanged between multiple provider organizations.

    • Can receive data from hospitals and laboratory facilities.

    • Traditionally does not exchange data with other EHR vendor products.

    • Can provide PHR capabilities, but only among practices using the same EHR product.

    • Is usually governed by one hospital organization, or by a smaller local provider community.

    Type 3

    • Provides data sharing between different practices that are utilizing a short list of different EHR products.

    • Traditionally distributed by an EHR vendor claiming it can connect other EHR vendors with its product.

    • Exchanges data using one specific vendor's data exchange protocols.

    • Generally built from the ground-up, and utilizes multiple point-to-point interfaces.

    • Can receive data from hospitals and laboratory facilities and provide PHR capabilities, but only with other organizations using the same EHR product.

    Type 4

    • Has the ability to exchange discrete patient data, following CCD methodology, between multiple practices with selected EHR products, hospitals, radiology centers and laboratory facilities, even if they are on separate healthcare products.

    • Provides a community master patient index (MPI) and a community patient portal for patient communications with each care provider.

    • Data is able to be transmitted seamlessly into each provider's EHR as discrete data.

    • Provides e-prescribing capabilities for those providers that have not embraced EHR technology.

    • Often governed by a community of competing hospitals and provider organizations throughout a region.

    Type 5

    • Has the ability to exchange discrete patient data, following HITSP C32 version 2.5 or higher CCD record format, between multiple practices with different EHR products and with hospitals, radiology centers and laboratory facilities, even if they are on separate vendor systems.

    • Provides a community MPI and a community patient portal for patient communications with each care provider.

    • The data is able to be transmitted seamlessly into each provider's EHR as discrete data.

    • Should possess a community PHR capability, designed to provide each patient with a centralized location for demographics and clinical history.

    • Provides e-prescribing applications for those providers that have not embraced EHR technologies and offers extensive disease management and outcomes measurement data capture and reporting.

    • Is governed by a community of competing hospitals and provider organizations throughout a region.

    • The goal is to improve the quality of healthcare in the community while reducing costs via patient data coordination.

    Vendors Categorized Within Five HIE Types

    HIE

    Federated

    Non-Federated

    Type 1

    Medicity

    Quest HIE

    Microsoft HIE

    Oracle HIE

    		  

    Type 2

    HIEweb

    Noteworthy Medical

    NextGen

    eClinicalworks

    Medical Communication Systems

    Type 3

    PreviousPage
    of 4Next