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

← WHO Reference Architecture 0.2.0

Metamodel in use

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

✓ Every relationship follows a pattern ArchiMate allows. 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
37
CapabilityStrategy
28
GoalMotivation
27
Application ServiceApplication
16
Data ObjectApplication
16
Business FunctionBusiness
13
ValueMotivation
12
Business ProcessBusiness
11
Business RoleBusiness
10
StakeholderMotivation
10
Business ObjectBusiness
8
ArtifactTechnology
7
Business ServiceBusiness
6
Application ProcessApplication
5
Application FunctionApplication
4
OutcomeMotivation
4
Application InteractionApplication
3
Value StreamStrategy
3
GroupingOther
2
Application InterfaceApplication
1
ProductBusiness
1

Relationship patterns

SourceRelationshipTargetCountArchiMate 3.2Relationships
CapabilityinfluencesGoal21✓ allowed1 2 3 4 5 6 7 8 +13 more
Application ComponentrealisesCapability15✓ allowed1 2 3 4 5 6 7 8 +7 more
GoalaggregatesGoal13✓ allowed1 2 3 4 5 6 7 8 +5 more
CapabilityservesCapability11✓ allowed1 2 3 4 5 6 7 8 +3 more
Application ComponentaccessesData Object10✓ allowed1 2 3 4 5 6 7 8 +2 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
Business Functioncomposed ofBusiness Process9✓ allowed1 2 3 4 5 6 7 8 +1 more
Application Componentflows toApplication Component7✓ allowed1 2 3 4 5 6 7
Business FunctionrealisesCapability6✓ allowed1 2 3 4 5 6
Business FunctionservesApplication Service6✓ allowed1 2 3 4 5 6
CapabilityrealisesOutcome6✓ allowed1 2 3 4 5 6
Valueassociated withStakeholder6✓ allowed1 2 3 4 5 6
Application ComponentrealisesApplication Component5✓ allowed1 2 3 4 5
Application ProcessrealisesCapability5✓ 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
Application FunctionrealisesApplication Service4✓ allowed1 2 3 4
ArtifactrealisesData Object4✓ allowed1 2 3 4
Data ObjectrealisesBusiness Object4✓ allowed1 2 3 4
Goalcomposed ofGoal4✓ allowed1 2 3 4
Outcomeassociated withOutcome4✓ allowed1 2 3 4
Application ComponentrealisesApplication Service3✓ allowed1 2 3
Capabilityassociated withBusiness Object3✓ allowed1 2 3
Data Objectassociated withApplication Component3✓ allowed1 2 3
Application ServiceaggregatesApplication Service2✓ allowed1 2
Application ServicerealisesCapability2✓ allowed1 2
Application ServiceservesApplication Component2✓ allowed1 2
Application ServicespecialisesApplication Service2✓ allowed1 2
ArtifactrealisesArtifact2✓ allowed1 2
ArtifactspecialisesArtifact2✓ allowed1 2
Business Objectassociated withCapability2✓ allowed1 2
Business ObjectspecialisesBusiness Object2✓ allowed1 2
Business Roleassociated withApplication Process2✓ allowed1 2
Business Roleassociated withCapability2✓ allowed1 2
Data ObjectspecialisesData Object2✓ allowed1 2
Application Componentassociated withApplication Component1✓ allowed1
Application Componentassociated withApplication Service1✓ allowed1
Application Componentassociated withArtifact1✓ allowed1
Application Componentassociated withData Object1✓ allowed1
Application Componentcomposed ofApplication Component1✓ allowed1
Application Componentcomposed ofApplication Interface1✓ 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 FunctionservesApplication Function1✓ allowed1
Business Objectassociated withBusiness Role1✓ allowed1
Business Objectassociated withProduct1✓ allowed1
Business ProcesstriggersApplication Interaction1✓ allowed1
Business Roleassigned toBusiness Process1✓ 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
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 (10 class(es), 9 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———
Patient-level DataData Object——SHR Repository (readwrite)
Reference data modelsData Object——Harmonize and reconcile models for national context (read), Logical Information Model Registry (readwrite)
Shared Health RecordBusiness Object———
SMART Guidelines L1Business Object———
SMART Guidelines L2 (DAK)Data Object———
Structured Guidelines contentData Object———

Sequence diagrams

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

SequenceSourceParticipantsSteps
1. Central Health Workforce RegistryviewDPI-H National Health Workforce Directory/Registry, DPI-F Information Mediator, DPI-F Security & Consent Module, DPI-H: Facility Registry, Reporting Module, Health Worker, Terminology, Facility11
SUB-GOAL 1. Central Health Workforce RegistryviewDPI-H National Health Workforce Directory/Registry, DPI-F Information Mediator, DPI-F Security & Consent Module, Reporting Module, Terminology, Health Worker7
CDSviewClinical Guideline package, 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).