Reference Architecture
0.2.0 - ci-build
Reference Architecture
0.2.0 - ci-build
Reference Architecture, published by WHO. This guide is not an authorized publication; it is the continuous build for version 0.2.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/costateixeira/smart-ra/tree/glossary and changes regularly. See the Directory of published versions
These are the core terms used in this specification. These are largely inspired by TOGAF/ArchiMate, and OpenHIE. The glossary is grouped into layers, with examples from Healthcare Supply Chain and Client Registry.
A normative statement that guides design or decision-making within an architecture. Principles are high-level rules or guidelines that are enduring and tied to the organization's mission, reflecting values, governance expectations, or desired outcomes.
Examples:
- "Ordering systems SHOULD be able to function offline and synchronize when reconnected."
- "Essential product data SHALL conform to international coding standards (e.g., GS1, WHO ATC)."
- "Client identity resolution SHOULD support both deterministic and probabilistic matching."
- "Interoperability between systems SHALL be achieved using standards such as HL7 FHIR and IHE profiles where available."
A long-term strategic aim that guides the organization’s direction.
Examples:
- "Ensure uninterrupted availability of essential medicines." (No Stock-Out)
- "Ensure unique and consistent identification of patients across all health services."
A measurable result aligned with a goal, often as a result or effect of a change.
Examples:
- "% of health facilities reporting zero essential stock-outs quarterly."
- "% of patient records correctly matched across systems."
A high-level ability of the organization to perform a specific task or achieve an outcome, supported by people, process, and tools.
Examples:
- "Supply Chain Management"
- "Patient Identity Management"
A unit of business capability at any level of granularity; a high-level grouping of business behavior performed to fulfill a capability.
Examples:
- "Inventory Monitoring"; "Traceability"
- "Client Record Matching"; "Demographic Updates"
A sequence of application-supported steps that automate or enable a business process.
Examples:
_
- _"Submit Stock Report"; "Reorder Workflow"; "Order Fulfillment"
- "Register New Client"; "Update Demographics"; "Client Matching / De-duplication"
A business responsibility assigned to actors.
Examples:
- "Warehouse Manager"; "Supply Chain Officer"
- "Patient Registrar"; "Health Information Clerk"
A key concept or entity relevant to business operations.
Examples:
- "Order"; "Facility"; "Stock Level"
- "Client Identifier"; "Person"; "Patient Record"
A functional or non-functional condition the application must satisfy to support business needs.
Examples:
- "Track and report real-time stock levels per facility."; "Enable SMS-based order submission where internet is unavailable."
- "Support identity deduplication and merge of duplicate client records."; "Expose patient search and match via FHIR Patient resource."
A modular software unit that provides specific functionality.
Examples:
- "Logistics Management Information System (LMIS)"; "Product Catalog Service"; "Patient Demographics Query (PDQ) Service"
- "Health Worker Registry"; "Client Registry (OpenCR)"
A structured representation of domain concepts used by application components.
Examples:
- _StockLevelReport; SupplyRequest; ProductCatalogItem; ShipmentNotice
- PatientIdentifier; PersonName PatientDemographics_
A constraint or need on infrastructure to support applications and interoperability.
Examples:
- "Support IHE PHARM-110 transaction", "Ensure end-to-end TLS 1.3 encryption"
- "Support HL7 FHIR R4 Patient resource", "Enable matching via IHE PIXm/PDQm transactions"
A technical specification for data exchange.
Examples (FHIR Profiles and Interop Specs):
- InventoryReport; SupplyRequest (for stock requisition); Location (facility registry); Organization (supplier info); Bundle
- IHE mCSD (for facility registry sync); IHE PIXm / PDQm (for client registry interoperability)
Code systems and value sets used to ensure semantic interoperability.
Examples:
- GS1 Product Codes; WHO ATC Classification; ISO 3166 Country Codes
- HL7 v3 NullFlavor (for unknown/masked data); Custom value sets for: Gender, Marital Status, Occupation, National Person Identifier formats