Reference Architecture
0.1.0 - release
This page is part of the Reference Architecture (v0.1.0: Releases Draft) based on FHIR (HL7® FHIR® Standard) R4. This is the current published version. For a full list of available versions, see the Directory of published versions
Contents:
This page provides a list of the FHIR artifacts defined as part of this implementation guide.
The following artifacts define the types of individuals and/or systems that will interact as part of the use cases covered by this implementation guide.
Client Registry |
The Client Registry assists in uniquely identifying individuals who receive health care services by:
Maintaining a central registry of all patients and their demographics and assigning a unique identifier to each patient. |
Facility Registry |
A registry that stores and manages standardized information about health facilities, serving as a central authority for facility data. |
Health Management Information System |
A system that collects, analyzes, and reports health data for monitoring and decision-making purposes. |
Health Worker Registry |
A registry that maintains information about health workers, including their identifiers, roles, and affiliations.
|
Interoperability Layer |
A component that facilitates the exchange of health information between systems by routing, translating, and orchestrating messages. |
Logistics Management Information System |
A system that manages the supply chain operations, including tracking and distribution of health commodities. |
Point-of-Service System |
A system used at the point of care, such as electronic medical records (EMRs), to capture and manage patient encounters and clinical data. |
Shared Health Record |
A centralized repository that stores and manages longitudinal patient health records, enabling access to clinical data across systems. |
Terminology Service |
A service that provides access to standardized code systems, value sets, and mappings to ensure consistent use of terminology across systems. |