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

Business layer - examples

This page presents the Business Architecture for a national or regional Client Registry, a foundational capability for integrated, person-centered healthcare.

It defines the key business goals, capabilities, processes, roles, and concepts using terminology aligned with ArchiMate, while remaining accessible to business audiences.

This model supports alignment with enterprise architecture frameworks such as TOGAF and reference models such as OpenHIE.

---

This page serves as a business-readable entry point to the Client Registry Business architecture.

---

Methodology Note

The example Client Registry architecture is documented using:

• Business-readable concepts (Goals, Outcomes, Capabilities…)
• Narrative descriptions
• ArchiMate notation for illustration (but based on structured, machine-readable internal format)
• Standards alignment (e.g. FHIR Patient, Identifier, Merge Operation)

This enables:

• Shared understanding across stakeholders of different levels.
• Integration with digital health reference models and the overall Reference Architecture.
• Traceability from strategic goals to technical specifications.

---

Overview

Business overview:

• Business Goal "Ensure unique patient identification" (G001)
  is realized by Business Capability "Patient Identity Management" (C001)

• Business Capability "Patient Identity Management" (C001)
  is realized by → Business Function "Client Registration and Search" (F001)

• Business Function "Client Registration and Search" (F001)
  is composed of → Business Process "Query by Identifier" (BP003)
  is composed of → Business Process "Query by Demographics" (BP004)

• Business Process "Register New Client" (BP001)
  → uses → Business Object "Client Identity" (BO001)
  is assigned to → Business Role "Administrative Health Worker" (BR001)

• Business Process "Update Client Demographics" (BP002)
  → uses → Business Object "Demographic Data" (BO002)
  is assigned to → Business Role "Administrative Health Worker" (BR001)

Goals

Long-term strategic aims that guide the health system’s direction.

       Examples:
        - "Goal001: Ensure unique and consistent identification of patients across all health services."
        - "Goal002: Enable person-centered care by linking data across health encounters."

---

Outcomes

Measurable results aligned with the stated goals.

       Examples:
        - "Out001 % of patient records correctly matched across systems"
        - "Out002 Number of duplicate IDs merged per quarter"

---

Capabilities

High-level organizational abilities supported by people, processes, and technology.

       Examples:
        - "Cap001 Patient Identity Management"
        - "Cap002 Record Matching and Deduplication"

---

Business Processes (Functions)

Coherent sets of business behavior that fulfill a capability.

       Examples:
        - "BP001 Register New Client"
        - "BP002 Update Client Demographics"

---

Roles

Responsibilities assigned to actors in the business.

       Examples:
        - "BR001 Administrative Health Worker"

---

Business Concepts

Information objects important to the domain.

       Examples:

• Client / Patient
• Unique Identifier
• Person Name
• Date of Birth
• Record Match Status
  

---

Business View Diagram

This diagram shows the key business functions and roles in the Client Registry context using ArchiMate notation.

---