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

← WHO Reference Architecture 0.2.0-draft.2

Metamodel in use

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

✓ Every relationship follows a pattern ArchiMate allows. 1 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
109
Application ServiceApplication
106
CapabilityStrategy
100
OutcomeMotivation
88
GroupingOther
49
GoalMotivation
35
Value StreamStrategy
21
ProductBusiness
13
Data ObjectApplication
8
ValueMotivation
3
StakeholderMotivation
2

Relationship patterns

SourceRelationshipTargetCountArchiMate 3.2Relationships
Application ComponentrealisesApplication Service127✓ allowed1 2 3 4 5 6 7 8 +119 more
Groupingcomposed ofOutcome61✓ allowed1 2 3 4 5 6 7 8 +53 more
CapabilityrealisesGrouping60✓ allowed1 2 3 4 5 6 7 8 +52 more
Groupingcomposed ofApplication Service57✓ allowed1 2 3 4 5 6 7 8 +49 more
Groupingcomposed ofData Object53✓ allowed1 2 3 4 5 6 7 8 +45 more
Application ComponentaccessesGrouping45✓ allowed1 2 3 4 5 6 7 8 +37 more
CapabilityrealisesOutcome42✓ allowed1 2 3 4 5 6 7 8 +34 more
GroupingrealisesCapability42✓ allowed1 2 3 4 5 6 7 8 +34 more
Application ServicerealisesCapability30✓ allowed1 2 3 4 5 6 7 8 +22 more
Application ServiceservesProduct30✓ allowed1 2 3 4 5 6 7 8 +22 more
Goalcomposed ofGoal22✓ allowed1 2 3 4 5 6 7 8 +14 more
OutcomerealisesGoal22✓ allowed1 2 3 4 5 6 7 8 +14 more
Groupingassociated withApplication Component19✓ allowed1 2 3 4 5 6 7 8 +11 more
Groupingcomposed ofGoal19✓ allowed1 2 3 4 5 6 7 8 +11 more
ProductrealisesCapability19✓ allowed1 2 3 4 5 6 7 8 +11 more
Application Componentflows toApplication Component15✓ allowed1 2 3 4 5 6 7 8 +7 more
GroupingrealisesGoal13✓ allowed1 2 3 4 5 6 7 8 +5 more
Value StreamtriggersValue Stream13✓ allowed1 2 3 4 5 6 7 8 +5 more
Application Componentassociated withGrouping12✓ allowed1 2 3 4 5 6 7 8 +4 more
Application ComponentservesApplication Service11✓ allowed1 2 3 4 5 6 7 8 +3 more
Application ServiceservesGrouping6✓ allowed1 2 3 4 5 6
Capabilityassociated withValue Stream6✓ allowed1 2 3 4 5 6
ValueinfluencesOutcome6✓ allowed1 2 3 4 5 6
Application Componentflows toApplication Service5✓ allowed1 2 3 4 5
Application Serviceflows toApplication Component5✓ allowed1 2 3 4 5
Value StreamrealisesGoal5✓ allowed1 2 3 4 5
Application ComponentrealisesGrouping4✓ allowed1 2 3 4
Capabilitycomposed ofCapability4✓ allowed1 2 3 4
GroupingaggregatesProduct4✓ allowed1 2 3 4
GroupingservesProduct4✓ allowed1 2 3 4
Outcomeassociated withOutcome4✓ allowed1 2 3 4
Stakeholderassociated withValue4✓ allowed1 2 3 4
CapabilityservesCapability3✓ allowed1 2 3
OutcomeaggregatesOutcome3✓ allowed1 2 3
OutcomerealisesGrouping3✓ allowed1 2 3
Application ComponentservesApplication Component2✓ allowed1 2
Goalcomposed ofGrouping2✓ allowed1 2
Value Streamcomposed ofValue Stream2✓ allowed1 2
Application ComponentrealisesCapability1✓ allowed1
Application ServiceservesApplication Component1✓ allowed1
GoalinfluencesValue1✓ allowed1
GroupingaggregatesOutcome1✓ allowed1
GroupinginfluencesGrouping1✓ allowed1
GroupingrealisesGrouping1✓ allowed1
OutcomeaggregatesGrouping1✓ allowed1
Outcomeassociated withCapability1✓ allowed1
Outcomecomposed ofOutcome1✓ allowed1
OutcomeinfluencesOutcome1✓ allowed1
Valueassociated withOutcome1✓ 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 0 relationship(s) are left out of the patterns above. Removing them is the model authors' call.

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
Sub-goal #1 Layered ViewviewDPI-H National Health Workforce Directory/Registry, DPI-F Information Mediator, DPI-F Security & Consent Module, DPI-H: Facility Registry, Reporting Module, Terminology Service9
Sub-goal #2 Layered ViewviewTerminology Service, DPI-F Information Mediator, DPI-H National Health Workforce Directory/Registry, DPI-H: Facility Registry, DPI-F Payments, Reporting Module9
Sub-goal #3 Layered ViewviewTerminology Service, DPI-F Information Mediator, DPI-H National Health Workforce Directory/Registry, DPI-F Security & Consent Module, Reporting Module, DPI-H: Facility Registry9
Sub-goal #4 Layered ViewviewDPI-H National Health Workforce Directory/Registry, DPI-F Information Mediator, Learning Management & Training Tracking Systems4
WHO Reference Architecture — Cross-Component FlowsflowDPI-H National Health Workforce Directory/Registry, Reporting Module, DPI-H: Facility Registry, Digital Payroll Services, DPI-F Information Mediator, Profile Management Service, Verification & Validation Service, Identity Management Service, Registry Management Service12

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