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

← WHO Reference Architecture 0.2.0-draft.1

Metamodel in use

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

✓ Every relationship follows a pattern ArchiMate allows. 2 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
ValueMotivation
79
Business ProcessBusiness
78
StakeholderMotivation
75
GoalMotivation
67
OutcomeMotivation
59
Business FunctionBusiness
58
Application ComponentApplication
48
Application ServiceApplication
41
CapabilityStrategy
39
Value StreamStrategy
21
Application FunctionApplication
15
Data ObjectApplication
8
DriverMotivation
8
GroupingOther
7
Work PackageImplementation & Migration
4
Business ActorBusiness
1
ProductBusiness
1

Relationship patterns

SourceRelationshipTargetCountArchiMate 3.2Relationships
Stakeholderassociated withValue99✓ allowed1 2 3 4 5 6 7 8 +91 more
ValueinfluencesOutcome92✓ allowed1 2 3 4 5 6 7 8 +84 more
OutcomerealisesGoal64✓ allowed1 2 3 4 5 6 7 8 +56 more
Business Functioncomposed ofBusiness Process62✓ allowed1 2 3 4 5 6 7 8 +54 more
Application Componentflows toApplication Component42✓ allowed1 2 3 4 5 6 7 8 +34 more
Application ServicerealisesCapability30✓ allowed1 2 3 4 5 6 7 8 +22 more
Goalcomposed ofGoal29✓ allowed1 2 3 4 5 6 7 8 +21 more
Application ComponentrealisesApplication Service22✓ allowed1 2 3 4 5 6 7 8 +14 more
CapabilityrealisesOutcome21✓ allowed1 2 3 4 5 6 7 8 +13 more
Groupingcomposed ofGoal20✓ allowed1 2 3 4 5 6 7 8 +12 more
Application Serviceflows toApplication Component17✓ allowed1 2 3 4 5 6 7 8 +9 more
CapabilityrealisesGrouping13✓ allowed1 2 3 4 5 6 7 8 +5 more
Value StreamtriggersValue Stream13✓ allowed1 2 3 4 5 6 7 8 +5 more
Application ServiceservesApplication Function12✓ allowed1 2 3 4 5 6 7 8 +4 more
Business Functionassociated withBusiness Function9✓ allowed1 2 3 4 5 6 7 8 +1 more
Value StreamrealisesGoal9✓ allowed1 2 3 4 5 6 7 8 +1 more
Business Functionassociated withCapability8✓ allowed1 2 3 4 5 6 7 8
DriverinfluencesGoal8✓ allowed1 2 3 4 5 6 7 8
GoalinfluencesValue8✓ allowed1 2 3 4 5 6 7 8
Valueassociated withStakeholder8✓ allowed1 2 3 4 5 6 7 8
Value Streamassociated withBusiness Function8✓ allowed1 2 3 4 5 6 7 8
Work PackagerealisesGoal8✓ allowed1 2 3 4 5 6 7 8
Application FunctionservesApplication Component6✓ allowed1 2 3 4 5 6
Business FunctionrealisesCapability6✓ allowed1 2 3 4 5 6
Business FunctionservesApplication Service6✓ allowed1 2 3 4 5 6
Capabilityassociated withValue Stream6✓ allowed1 2 3 4 5 6
Stakeholdercomposed ofStakeholder6✓ allowed1 2 3 4 5 6
Valueassociated withGrouping6✓ allowed1 2 3 4 5 6
Application ComponentaccessesData Object5✓ allowed1 2 3 4 5
Application Componentassigned toApplication Function5✓ allowed1 2 3 4 5
Application Componentflows toApplication Service5✓ allowed1 2 3 4 5
Capabilityassociated withBusiness Function5✓ allowed1 2 3 4 5
Application ComponentrealisesApplication Function4✓ allowed1 2 3 4
Capabilitycomposed ofCapability4✓ allowed1 2 3 4
GroupingaggregatesDriver4✓ allowed1 2 3 4
Outcomeassociated withOutcome4✓ allowed1 2 3 4
Valueassociated withDriver4✓ allowed1 2 3 4
Application ComponentaccessesGrouping3✓ allowed1 2 3
Application FunctionrealisesApplication Service3✓ allowed1 2 3
Application ServiceservesProduct3✓ allowed1 2 3
CapabilityinfluencesGoal3✓ allowed1 2 3
CapabilityservesCapability3✓ allowed1 2 3
GoalinfluencesGoal3✓ allowed1 2 3
OutcomeaggregatesOutcome3✓ allowed1 2 3
ProductrealisesCapability3✓ allowed1 2 3
Valueassociated withOutcome3✓ allowed1 2 3
Application Componentflows toApplication Function2✓ allowed1 2
Application ComponentservesApplication Component2✓ allowed1 2
Application Functionflows toApplication Component2✓ allowed1 2
Application Serviceflows toApplication Service2✓ allowed1 2
Application ServiceservesApplication Component2✓ allowed1 2
Goalcomposed ofGrouping2✓ allowed1 2
StakeholderinfluencesDriver2✓ allowed1 2
Value Streamcomposed ofValue Stream2✓ allowed1 2
Application FunctionrealisesCapability1✓ allowed1
Business Actorassigned toStakeholder1✓ allowed1
Business Processassociated withBusiness Function1✓ allowed1
Business ProcessrealisesCapability1✓ allowed1
Business ProcessservesApplication Service1✓ allowed1
GoalaggregatesGoal1✓ allowed1
GroupingaggregatesOutcome1✓ allowed1
GroupinginfluencesGrouping1✓ allowed1
GroupingrealisesGrouping1✓ allowed1
OutcomeaggregatesGrouping1✓ allowed1
Outcomeassociated withCapability1✓ allowed1
Outcomecomposed ofOutcome1✓ allowed1
OutcomeinfluencesOutcome1✓ allowed1
Stakeholderassociated withBusiness Actor1✓ allowed1
StakeholderinfluencesGoal1✓ allowed1
StakeholderinfluencesStakeholder1✓ allowed1
ValueinfluencesStakeholder1✓ allowed1
Value Streamassociated withBusiness Process1✓ 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 1 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 (14 sequence diagram(s)): PlantUML, Mermaid sequence diagrams, and JSON.

SequenceSourceParticipantsSteps
HRH Application Communication Diagram (horizontal)viewFinancial Analytics & BI, DPI-F Information Mediator, Provider Registry & Payment System, Claims & Reimbursement System, Health Facility Portal, Health Worker Self Service Portal, DPI-F: Security & Consent, DPI-H National Health Workforce Directory/Registry8
SUB-GOAL 1. Central Health Workforce RegistryviewDPI-F Security & Consent Module, DPI-F Information Mediator, DPI-H: Facility Registry, Reporting Module, DPI-H National Health Workforce Directory/Registry, Health Worker, Terminology, Facility9
0.2 Application Structure Viewpoint (All Sub-goals)viewProvider Registry & Payment System, DPI-F Information Mediator, Financial Analytics & BI, Claims & Reimbursement System, Health Facility Portal, Health Worker Self Service Portal, DPI-H National Health Workforce Directory/Registry, DPI-H: Facility Registry, Terminology Service, DPI-F: Security & Consent, Reporting Module, Learning Management & Training Tracking Systems, Verification & Validation Service, Profile Management Service, Digital Payroll Services26
1.2 Application Structure ViewpointviewFinancial Analytics & BI, DPI-F Information Mediator, Provider Registry & Payment System, Claims & Reimbursement System, Health Facility Portal, Health Worker Self Service Portal, DPI-H National Health Workforce Directory/Registry, DPI-H: Facility Registry, Terminology Service, DPI-F: Security & Consent, Reporting Module, Verification & Validation Service, Registry Management Service, Identity Management Service24
1.3 Layered ViewpointviewDPI-H National Health Workforce Directory/Registry, DPI-F Information Mediator, DPI-F Security & Consent Module, DPI-H: Facility Registry, Reporting Module, Terminology Service9
1. Central Health Workforce RegistryviewDPI-F Security & Consent Module, DPI-F Information Mediator, DPI-H: Facility Registry, Reporting Module, DPI-H National Health Workforce Directory/Registry, Health Worker, Terminology, Facility9
2.2 Application Structure ViewpointviewFinancial Analytics & BI, DPI-F Information Mediator, Provider Registry & Payment System, Claims & Reimbursement System, Health Facility Portal, Health Worker Self Service Portal, DPI-H National Health Workforce Directory/Registry, DPI-H: Facility Registry, Terminology Service, DPI-F: Security & Consent, Digital Payroll Services, Reporting Module20
2.3 Layered ViewpointviewTerminology Service, DPI-F Information Mediator, DPI-H National Health Workforce Directory/Registry, DPI-H: Facility Registry, DPI-F Payments, Payroll Scheduling & Execution, Reporting Module11
3.2 Application Structure ViewpointviewFinancial Analytics & BI, DPI-F Information Mediator, Provider Registry & Payment System, Claims & Reimbursement System, Health Facility Portal, Health Worker Self Service Portal, DPI-H National Health Workforce Directory/Registry, DPI-H: Facility Registry, Terminology Service, DPI-F: Security & Consent, Profile Management Service, Reporting Module, Verification & Validation Service22
3.3 Layed ViewpointviewTerminology Service, DPI-F Information Mediator, DPI-H National Health Workforce Directory/Registry, DPI-F Security & Consent Module, Reporting Module, DPI-H: Facility Registry, Validating Credentials11
4.2 Application Structure ViewpointviewProvider Registry & Payment System, DPI-F Information Mediator, Health Facility Portal, Health Worker Self Service Portal, DPI-H National Health Workforce Directory/Registry, DPI-H: Facility Registry, Terminology Service, DPI-F: Security & Consent, Reporting Module, Learning Management & Training Tracking Systems, Verification & Validation Service, Profile Management Service21
4.3 Layered ViewpointviewDPI-H National Health Workforce Directory/Registry, DPI-F Information Mediator, Learning Management & Training Tracking Systems4
Application Structure ViewpointviewMaster Data / Registries, API Gateway & Messaging Adapters, Matching / Settlement Engine, Fraud & Security Monitoring, Authentication & Authorization System, Financial Data Exchange, Policy & Eligibility Management, Provider Registry & Payment System, Audit & Open Data System, Data Ingestion & Analytics, Financial Analytics & BI, Provider Payments & Claims Management, Identity & Security Management, Workflow & Operational Automation, Workflow / RPA Engine, Audit, Compliance & Reporting, Insurance & Eligibility Management20
WHO Models — Cross-Component FlowsflowDPI-H National Health Workforce Directory/Registry, Reporting Module, DPI-H: Facility Registry, Financial Analytics & BI, Master Data / Registries, Financial Data Exchange, Workflow & Operational Automation, API Gateway & Messaging Adapters, Claims & Reimbursement System, Matching / Settlement Engine, Fraud & Security Monitoring, Authentication & Authorization System, Workflow / RPA Engine, Data Ingestion & Analytics12

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