Un cadre basé sur l'application dans le monde réel.

Nos normes et nos recommandations en matière de meilleures pratiques s’associent pour former la base de systèmes complets d’échange d’informations relatives à la santé.

  • Conforme aux normes

    Conforme aux normes

    We adopt best practices and influence international health information sharing standards to keep our recommendations up-to-date.

  • Applicable

    Applicable

    The OpenHIE Architecture provides patterns that can be used as foundations to support complex, interoperable systems for information exchange.

  • Modulaire

    Modulaire

    Our architecture recommendations are not one-size-fits-all. The components are modular to make the system work for your community’s needs.

The Architecture

A Health Information Exchange (HIE) makes sharing health data across information systems possible. It enables data to be shared between databases, facilities, and across regions or countries.

OpenHIE’s Architecture is made up of patterns that ensure that health information from various external systems is gathered into a single, unified HIE. To accomplish this, the exchange normalizes the context in which health information is used by focusing on the “for whom”, ”by whom”, “where”, and “what” of a patient’s health visit, bringing relevant information through a layer of interoperability and directly to the point of service. Additionally, OpenHIE also integrates medical supply data. This supports enhanced decision-making, improves the quality, safety, and continuity of care, and facilitates the appropriate use of information to improve health in a population.

| Couche 1 |
Composants de l'architecture

Business Domain Services & Registry Services

The first layer of the architecture consists of business domain services and registry services. Business domain components are designed to support specific health system business domains and would have the potential to combine data from multiple point-of-service and point-of-care systems. Registry services are designed to uniquely identify and track unique patients, facilities, healthcare products and terminology that are used throughout the health information exchange.

Se référer aux composants
Services de domaines d'activité
  • 109
    Système de gestion de la logistique
    Système de gestion de la logistique
  • 113
    Dossiers médicaux partagés
    Dossiers médicaux partagés
  • 106
    Système d'information sur la gestion de la santé
    Système d'information sur la gestion de la santé
  • 105
    Service des finances et des assurances
    Service des finances et des assurances
Services de registre
  • 114
    Services de terminologie
    Services de terminologie
  • 102
    Registre client
    Registre client
  • 104
    Registre de l'établissement
    Registre de l'établissement
  • 107
    Registre du personnel de soins de santé
    Registre du personnel de soins de santé
  • 112
    Catalogue des produits
    Catalogue des produits
| Couche 2 |
Couche d'interopérabilité

Interoperability Services Layer

The second layer of the architecture acts as a gateway between the business domain and registry services and the points of service, keeping data secure and consistent.

| Couche 3 |
Point de service

Point of Service Layer

Points of service , including those such as OpenMRS electronic medical records (EMR) system and the RapidSMS mHealth application, are used by clinicians and by community health workers to access and update a patient’s person-centric shared health information and to record healthcare transactions.

Se référer aux points de service
Points de service
  • 110
    Système d'information sur la santé communautaire
    Système d'information sur la santé communautaire
  • 103
    Dossier médical électronique
    Dossier médical électronique
  • 106
    Système d'information sur la gestion de la santé
    Système d'information sur la gestion de la santé
  • 108
    Système de laboratoire
    Système de laboratoire
  • 111
    Système de pharmacie
    Système de pharmacie
  • 109
    Système de gestion de la logistique
    Système de gestion de la logistique
  • 105
    Service des finances et des assurances
    Service des finances et des assurances

OpenHIE Architecture Specification

This specification documents the OpenHIE Architecture components and the requirements for each OpenHIE component. In addition, the specification documents the OpenHIE workflows (data exchanges) and the underlying standards that support the workflows.

This is a living document created by the OpenHIE Community and based upon real-world implementations and needs. You are encouraged to provide comments, proposed edits, and other suggestions for future versions on our Discourse forum site. If you have questions or need help unrelated to this guide, please contact us.

View Specification

OHIE In Action

Take a look at how the OpenHIE Community is helping to solve health problems and improve outcomes for resource emerging communities across the globe.