Reference Architecture and Guidance for Digital Public Infrastructure for the Health Sector

← WHO Reference Architecture 0.3.0-draft.1

Metamodel in use

Derived from the model on every build (Tool archimate-metamodel), never drawn: 24 element type(s) and 105 relationship pattern(s), each checked against ArchiMate 3.2's relationship table.

✗ 2 relationship(s) follow 1 pattern(s) ArchiMate does not allow (red below). 34 placeholder element(s), named after their own type, are left out (listed at the end).

Click a box to see its elements, or a line to see its relationships.

Relationships:
Layers:

To keep the picture readable, relationships between the same two types share one line, a type's relationships to itself are written in its box, and associated with (which says nothing about how two things relate), groupings and junctions are left out. The tables below list everything.

The same diagram as Graphviz DOT, a Mermaid class diagram, and JSON.

Element types

TypeLayerElements
Application ComponentApplication
91
CapabilityStrategy
51
GroupingOther
44
GoalMotivation
38
Application ServiceApplication
36
Business RoleBusiness
26
Data ObjectApplication
25
PrincipleMotivation
16
Business FunctionBusiness
13
Business ObjectBusiness
13
StakeholderMotivation
13
ValueMotivation
12
Application FunctionApplication
11
Business ProcessBusiness
11
ArtifactTechnology
10
OutcomeMotivation
10
Business ServiceBusiness
6
Application ProcessApplication
5
NodeTechnology
5
Application InteractionApplication
3
ProductBusiness
3
Value StreamStrategy
3
Application InterfaceApplication
1
Business CollaborationBusiness
1

Relationship patterns

SourceRelationshipTargetCountArchiMate 3.2Relationships
GroupingaggregatesApplication Component66✓ allowed1 2 3 4 5 6 7 8 +58 more
GroupingaggregatesCapability27✓ allowed1 2 3 4 5 6 7 8 +19 more
CapabilityinfluencesGoal21✓ allowed1 2 3 4 5 6 7 8 +13 more
GroupingaggregatesBusiness Role21✓ allowed1 2 3 4 5 6 7 8 +13 more
Application ComponentrealisesApplication Service20✓ allowed1 2 3 4 5 6 7 8 +12 more
Application Componentflows toApplication Component18✓ allowed1 2 3 4 5 6 7 8 +10 more
GroupingaggregatesPrinciple17✓ allowed1 2 3 4 5 6 7 8 +9 more
Application ComponentrealisesCapability16✓ allowed1 2 3 4 5 6 7 8 +8 more
Application ServicerealisesCapability16✓ allowed1 2 3 4 5 6 7 8 +8 more
CapabilityrealisesOutcome14✓ allowed1 2 3 4 5 6 7 8 +6 more
GroupingaggregatesGrouping14✓ allowed1 2 3 4 5 6 7 8 +6 more
CapabilityrealisesGrouping13✓ allowed1 2 3 4 5 6 7 8 +5 more
GoalaggregatesGoal13✓ allowed1 2 3 4 5 6 7 8 +5 more
Application ComponentaccessesData Object11✓ allowed1 2 3 4 5 6 7 8 +3 more
CapabilityservesCapability11✓ allowed1 2 3 4 5 6 7 8 +3 more
GroupingaggregatesStakeholder11✓ allowed1 2 3 4 5 6 7 8 +3 more
Application ComponentservesApplication Component10✓ allowed1 2 3 4 5 6 7 8 +2 more
Stakeholderassociated withValue10✓ allowed1 2 3 4 5 6 7 8 +2 more
Application ComponentaccessesGrouping9✓ allowed1 2 3 4 5 6 7 8 +1 more
Business Functioncomposed ofBusiness Process9✓ allowed1 2 3 4 5 6 7 8 +1 more
Goalcomposed ofGoal8✓ allowed1 2 3 4 5 6 7 8
ProductrealisesCapability8✓ allowed1 2 3 4 5 6 7 8
Application ServiceservesProduct7✓ allowed1 2 3 4 5 6 7
GroupingaggregatesGoal7✓ allowed1 2 3 4 5 6 7
Business FunctionrealisesCapability6✓ allowed1 2 3 4 5 6
Business FunctionservesApplication Service6✓ allowed1 2 3 4 5 6
GroupingaggregatesApplication Function6✓ allowed1 2 3 4 5 6
Valueassociated withStakeholder6✓ allowed1 2 3 4 5 6
Application ComponentrealisesApplication Component5✓ allowed1 2 3 4 5
Application FunctionrealisesApplication Service5✓ allowed1 2 3 4 5
Application ProcessrealisesCapability5✓ allowed1 2 3 4 5
GroupingaggregatesData Object5✓ allowed1 2 3 4 5
GroupingaggregatesNode5✓ allowed1 2 3 4 5
Groupingcomposed ofGoal5✓ allowed1 2 3 4 5
ValueinfluencesOutcome5✓ allowed1 2 3 4 5
Application Componentassigned toApplication Function4✓ allowed1 2 3 4
Application Componentassigned toApplication Interaction4✓ allowed1 2 3 4
ArtifactrealisesData Object4✓ allowed1 2 3 4
Business Objectassociated withBusiness Object4✓ allowed1 2 3 4
Business Objectcomposed ofBusiness Object4✓ allowed1 2 3 4
Business Roleassociated withBusiness Object4✓ allowed1 2 3 4
Data ObjectrealisesBusiness Object4✓ allowed1 2 3 4
Outcomeassociated withOutcome4✓ allowed1 2 3 4
Application ComponentservesApplication Service3✓ allowed1 2 3
Application ServiceservesBusiness Role3✓ allowed1 2 3
Business Objectassociated withCapability3✓ allowed1 2 3
Business RolespecialisesBusiness Role3✓ allowed1 2 3
Capabilityassociated withBusiness Object3✓ allowed1 2 3
Data Objectassociated withApplication Component3✓ allowed1 2 3
GroupingaggregatesApplication Service3✓ allowed1 2 3
GroupingaggregatesArtifact3✓ allowed1 2 3
Application ComponentservesCapability2✗ not allowed1 2
Application ServiceaccessesData Object2✓ allowed1 2
Application ServiceaggregatesApplication Service2✓ allowed1 2
Application ServiceservesApplication Component2✓ allowed1 2
Application ServicespecialisesApplication Service2✓ allowed1 2
ArtifactrealisesArtifact2✓ allowed1 2
ArtifactspecialisesArtifact2✓ allowed1 2
Business ObjectspecialisesBusiness Object2✓ allowed1 2
Business Roleassociated withApplication Process2✓ allowed1 2
Business Roleassociated withCapability2✓ allowed1 2
Data ObjectspecialisesData Object2✓ allowed1 2
OutcomerealisesGoal2✓ allowed1 2
Application ComponentaccessesBusiness Object1✓ allowed1
Application Componentassociated withApplication Component1✓ allowed1
Application Componentassociated withApplication Service1✓ allowed1
Application Componentassociated withArtifact1✓ allowed1
Application Componentassociated withBusiness Object1✓ allowed1
Application Componentassociated withData Object1✓ allowed1
Application Componentcomposed ofApplication Component1✓ allowed1
Application Componentcomposed ofApplication Interface1✓ allowed1
Application ComponentrealisesApplication Function1✓ allowed1
Application ComponentservesBusiness Role1✓ allowed1
Application InterfaceservesBusiness Role1✓ allowed1
Application ProcessaccessesData Object1✓ allowed1
Application ProcessaggregatesApplication Process1✓ allowed1
Application Processcomposed ofApplication Process1✓ allowed1
Artifactassociated withData Object1✓ allowed1
Business Collaborationassociated withBusiness Object1✓ allowed1
Business FunctionservesApplication Function1✓ allowed1
Business Objectassociated withBusiness Role1✓ allowed1
Business Objectassociated withProduct1✓ allowed1
Business ProcesstriggersApplication Interaction1✓ allowed1
Business Roleassigned toBusiness Process1✓ allowed1
Business Roleassociated withApplication Component1✓ allowed1
Capabilityassociated withApplication Component1✓ allowed1
Capabilityassociated withBusiness Role1✓ allowed1
Capabilityassociated withCapability1✓ allowed1
Capabilityassociated withData Object1✓ allowed1
Capabilityassociated withProduct1✓ allowed1
Capabilityflows toCapability1✓ allowed1
Data ObjectaggregatesData Object1✓ allowed1
GroupingaggregatesBusiness Collaboration1✓ allowed1
GroupingaggregatesOutcome1✓ allowed1
GroupingrealisesGrouping1✓ allowed1
OutcomeaggregatesGrouping1✓ allowed1
Outcomeassociated withCapability1✓ allowed1
Outcomecomposed ofOutcome1✓ allowed1
OutcomeinfluencesOutcome1✓ allowed1
ProductaggregatesArtifact1✓ allowed1
ProductaggregatesBusiness Object1✓ allowed1
ProductaggregatesData Object1✓ allowed1
Productassociated withBusiness Role1✓ allowed1
Productflows toApplication Component1✓ allowed1
Value StreamtriggersValue Stream1✓ allowed1

Placeholder elements

Named after their own type, so they stand for the type rather than for a thing in the architecture: how a metamodel gets drawn by hand inside a model. They and their 40 relationship(s) are left out of the patterns above. Removing them is the model authors' call.

Data class diagram

Derived from the model's DataObject and BusinessObject elements (15 class(es), 17 relationship(s)): PlantUML, Mermaid class diagram, Graphviz DOT, and JSON.

ClassTypeLogical modelAttributesAccessed / governed by
Adapted SMART Guidelines L1Business Object———
Adapted SMART Guidelines L2 (DAK)Data Object———
Approved Terminology ContentData Object———
Clinical GuidelinesBusiness Object———
Generic ProductBusiness Object———
Patient-level DataData Object——Lifelong Health Record (readwrite)
Product ClassificationBusiness Object———
Product Master DataBusiness Object——National Product Catalogue (readwrite), Manufacturer / Distributor (source of truth), Data Owner (approves changes), Data Custodian (technical management and security), Data Steward (day-to-day management and quality control), Master Data Governance Group (leadership on additions and changes)
Reference data modelsData Object——Harmonize and reconcile models for national context (read), Logical Information Model Repository (readwrite)
Regulated Trade ItemBusiness Object———
Shared Health RecordBusiness Object———
SMART Guidelines L1Business Object———
SMART Guidelines L2 (DAK)Data Object———
Structured Guidelines contentData Object———
Trade ItemBusiness Object———

Sequence diagrams

Derived from the model's ApplicationInteractions and cross-component Flow / Triggering chains (7 sequence diagram(s)): PlantUML, Mermaid sequence diagrams, and JSON.

SequenceSourceParticipantsSteps
Semantic Governance Infrastructure (Fig. 3.4.1)viewGovernance TMS, Runtime TS, Global content sources3
1. Central Health Workforce RegistryviewHealth Workforce Registry, DPI-F Information Mediator, DPI-F Security & Consent Module, Health Facility Registry, Reporting Module, Health worker record, Terminology, Facility11
SUB-GOAL 1. Central Health Workforce RegistryviewHealth Workforce Registry, DPI-F Information Mediator, DPI-F Security & Consent Module, Reporting Module, Terminology, Health worker record7
Track and Trace through DHSC Components (DTH SC Fig. 24)viewManufacturer Systems, Interoperability Component, Data Repositories, Global Platforms, Warehouse Management System, Transportation Management System, Health Facility Logistics Management System, Dispensing System, Data Warehouse, Traceability Event, Product Verification, Individual, National Regulatory Authority, Track and Trace14
CDSviewClinical Guideline package, Computable Decision Support Engine1
BinteractionDocument Source, Document Repository2
DinteractionTest Operator, Create and submit document, Document Source, Document Repository3

Relationship table: ArchiMate 3.2 Appendix B as Archi holds it (MIT).