Un marco basado en la aplicación en el mundo real.

Nuestros estándares y recomendaciones sobre mejores prácticas funcionan juntos a fin de formar una base para los sistemas de intercambio de información de salud integrales.

  • Basado en estándares

    Basado en estándares

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

  • Implementable

    Implementable

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

  • Modular

    Modular

    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.

| Capa 1 |
Componentes de arquitectura

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.

Vea los componentes
Servicios de Dominio Empresarial
  • 135
    Sistema de gestión logística
    Sistema de gestión logística
  • 139
    Registros de salud compartidos
    Registros de salud compartidos
  • 132
    Sistema de Información de Gestión de la Salud
    Sistema de Información de Gestión de la Salud
  • 131
    Servicio de Finanzas y Seguros
    Servicio de Finanzas y Seguros
Servicios de Registro
  • 140
    Servicios de terminología
    Servicios de terminología
  • 128
    Registro de clientes
    Registro de clientes
  • 130
    Registro del centro
    Registro del centro
  • 133
    Registro de Trabajadores de la Salud
    Registro de Trabajadores de la Salud
  • 138
    Catálogo de productos
    Catálogo de productos
| Capa 2 |
Capa de interoperabilidad

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.

| Capa 3 |
Punto de servicio

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.

Consulte los puntos de servicio
Puntos de servicio
  • 136
    Sistema de información de salud comunitaria
    Sistema de información de salud comunitaria
  • 129
    Registros médicos electrónicos
    Registros médicos electrónicos
  • 132
    Sistema de Información de Gestión de la Salud
    Sistema de Información de Gestión de la Salud
  • 134
    Sistema de laboratorio
    Sistema de laboratorio
  • 137
    Sistema de farmacia
    Sistema de farmacia
  • 135
    Sistema de gestión logística
    Sistema de gestión logística
  • 131
    Servicio de Finanzas y Seguros
    Servicio de Finanzas y Seguros

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.