← WHO Reference Architecture 0.2.0
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.
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.
| Source | Relationship | Target | Count | ArchiMate 3.2 | Relationships |
|---|---|---|---|---|---|
| Capability | influences | Goal | 21 | ✓ allowed | 1 2 3 4 5 6 7 8 +13 more |
| Application Component | realises | Capability | 15 | ✓ allowed | 1 2 3 4 5 6 7 8 +7 more |
| Goal | aggregates | Goal | 13 | ✓ allowed | 1 2 3 4 5 6 7 8 +5 more |
| Capability | serves | Capability | 11 | ✓ allowed | 1 2 3 4 5 6 7 8 +3 more |
| Application Component | accesses | Data Object | 10 | ✓ allowed | 1 2 3 4 5 6 7 8 +2 more |
| Application Component | serves | Application Component | 10 | ✓ allowed | 1 2 3 4 5 6 7 8 +2 more |
| Stakeholder | associated with | Value | 10 | ✓ allowed | 1 2 3 4 5 6 7 8 +2 more |
| Business Function | composed of | Business Process | 9 | ✓ allowed | 1 2 3 4 5 6 7 8 +1 more |
| Application Component | flows to | Application Component | 7 | ✓ allowed | 1 2 3 4 5 6 7 |
| Business Function | realises | Capability | 6 | ✓ allowed | 1 2 3 4 5 6 |
| Business Function | serves | Application Service | 6 | ✓ allowed | 1 2 3 4 5 6 |
| Capability | realises | Outcome | 6 | ✓ allowed | 1 2 3 4 5 6 |
| Value | associated with | Stakeholder | 6 | ✓ allowed | 1 2 3 4 5 6 |
| Application Component | realises | Application Component | 5 | ✓ allowed | 1 2 3 4 5 |
| Application Process | realises | Capability | 5 | ✓ allowed | 1 2 3 4 5 |
| Value | influences | Outcome | 5 | ✓ allowed | 1 2 3 4 5 |
| Application Component | assigned to | Application Function | 4 | ✓ allowed | 1 2 3 4 |
| Application Component | assigned to | Application Interaction | 4 | ✓ allowed | 1 2 3 4 |
| Application Function | realises | Application Service | 4 | ✓ allowed | 1 2 3 4 |
| Artifact | realises | Data Object | 4 | ✓ allowed | 1 2 3 4 |
| Data Object | realises | Business Object | 4 | ✓ allowed | 1 2 3 4 |
| Goal | composed of | Goal | 4 | ✓ allowed | 1 2 3 4 |
| Outcome | associated with | Outcome | 4 | ✓ allowed | 1 2 3 4 |
| Application Component | realises | Application Service | 3 | ✓ allowed | 1 2 3 |
| Capability | associated with | Business Object | 3 | ✓ allowed | 1 2 3 |
| Data Object | associated with | Application Component | 3 | ✓ allowed | 1 2 3 |
| Application Service | aggregates | Application Service | 2 | ✓ allowed | 1 2 |
| Application Service | realises | Capability | 2 | ✓ allowed | 1 2 |
| Application Service | serves | Application Component | 2 | ✓ allowed | 1 2 |
| Application Service | specialises | Application Service | 2 | ✓ allowed | 1 2 |
| Artifact | realises | Artifact | 2 | ✓ allowed | 1 2 |
| Artifact | specialises | Artifact | 2 | ✓ allowed | 1 2 |
| Business Object | associated with | Capability | 2 | ✓ allowed | 1 2 |
| Business Object | specialises | Business Object | 2 | ✓ allowed | 1 2 |
| Business Role | associated with | Application Process | 2 | ✓ allowed | 1 2 |
| Business Role | associated with | Capability | 2 | ✓ allowed | 1 2 |
| Data Object | specialises | Data Object | 2 | ✓ allowed | 1 2 |
| Application Component | associated with | Application Component | 1 | ✓ allowed | 1 |
| Application Component | associated with | Application Service | 1 | ✓ allowed | 1 |
| Application Component | associated with | Artifact | 1 | ✓ allowed | 1 |
| Application Component | associated with | Data Object | 1 | ✓ allowed | 1 |
| Application Component | composed of | Application Component | 1 | ✓ allowed | 1 |
| Application Component | composed of | Application Interface | 1 | ✓ allowed | 1 |
| Application Component | serves | Business Role | 1 | ✓ allowed | 1 |
| Application Interface | serves | Business Role | 1 | ✓ allowed | 1 |
| Application Process | accesses | Data Object | 1 | ✓ allowed | 1 |
| Application Process | aggregates | Application Process | 1 | ✓ allowed | 1 |
| Application Process | composed of | Application Process | 1 | ✓ allowed | 1 |
| Artifact | associated with | Data Object | 1 | ✓ allowed | 1 |
| Business Function | serves | Application Function | 1 | ✓ allowed | 1 |
| Business Object | associated with | Business Role | 1 | ✓ allowed | 1 |
| Business Object | associated with | Product | 1 | ✓ allowed | 1 |
| Business Process | triggers | Application Interaction | 1 | ✓ allowed | 1 |
| Business Role | assigned to | Business Process | 1 | ✓ allowed | 1 |
| Capability | associated with | Application Component | 1 | ✓ allowed | 1 |
| Capability | associated with | Business Role | 1 | ✓ allowed | 1 |
| Capability | associated with | Capability | 1 | ✓ allowed | 1 |
| Capability | associated with | Data Object | 1 | ✓ allowed | 1 |
| Capability | associated with | Product | 1 | ✓ allowed | 1 |
| Capability | flows to | Capability | 1 | ✓ allowed | 1 |
| Data Object | aggregates | Data Object | 1 | ✓ allowed | 1 |
| Outcome | associated with | Capability | 1 | ✓ allowed | 1 |
| Outcome | composed of | Outcome | 1 | ✓ allowed | 1 |
| Outcome | influences | Outcome | 1 | ✓ allowed | 1 |
| Product | aggregates | Artifact | 1 | ✓ allowed | 1 |
| Product | aggregates | Business Object | 1 | ✓ allowed | 1 |
| Product | aggregates | Data Object | 1 | ✓ allowed | 1 |
| Product | associated with | Business Role | 1 | ✓ allowed | 1 |
| Product | flows to | Application Component | 1 | ✓ allowed | 1 |
| Value Stream | triggers | Value Stream | 1 | ✓ allowed | 1 |
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.
Derived from the model's DataObject and BusinessObject elements (10 class(es), 9 relationship(s)): PlantUML, Mermaid class diagram, Graphviz DOT, and JSON.
| Class | Type | Logical model | Attributes | Accessed / governed by |
|---|---|---|---|---|
| Adapted SMART Guidelines L1 | Business Object | — | — | — |
| Adapted SMART Guidelines L2 (DAK) | Data Object | — | — | — |
| Approved Terminology Content | Data Object | — | — | — |
| Clinical Guidelines | Business Object | — | — | — |
| Patient-level Data | Data Object | — | — | SHR Repository (readwrite) |
| Reference data models | Data Object | — | — | Harmonize and reconcile models for national context (read), Logical Information Model Registry (readwrite) |
| Shared Health Record | Business Object | — | — | — |
| SMART Guidelines L1 | Business Object | — | — | — |
| SMART Guidelines L2 (DAK) | Data Object | — | — | — |
| Structured Guidelines content | Data Object | — | — | — |
Derived from the model's ApplicationInteractions and cross-component Flow / Triggering chains (5 sequence diagram(s)): PlantUML, Mermaid sequence diagrams, and JSON.
Relationship table: ArchiMate 3.2 Appendix B as Archi holds it (MIT).