Official URL: http://smart.who.int/trust-demo/ImplementationGuide/smart.who.int.trust-demo | Version: 0.1.0 |
| Draft as of 2026-10-23 | Computable Name: TrustDemo |
Somsak is born in Taifafeki and grows up in Onesa. A year later, a doctor in Taifafeki sees every vaccine he has ever had, and no record is copied across the border.
This guide is that story, told as the journeys J1 to J4, written down as a WHO SMART Guidelines digital adaptation kit (L2) and a FHIR implementation guide (L3). It is built on the SMART Trust HCERT libraries and WHO GDHCN.
Walk through the journeys Read the journeys See the FHIR examplesFour moments that matter
Each moment is one business process (BPMN), played by fictional people. Each one is linked to the user scenario, the process and the FHIR records it creates. Click a picture to walk through that moment in the journeys walkthrough.
A baby from Onesa gets his first vaccines in Taifafeki. The hospital signs each dose as a Digital Vaccination Certificate, and the family leaves with two paper QR cards.
A health worker registers him offline and reads the cards. She records them as "reported, not yet verified" and refers him to the clinic.
A nurse checks the signatures against the GDHCN trust list, offline. She maps the Taifafeki vaccine codes to the schedule of Onesa and gives the overdue 6-week doses.
What is in this guide
| What | Where | |
|---|---|---|
| People | Five fictional adults and a baby; the generic personas and system actors who play each process lane | Personas, system actors |
| Journeys | The story moment by moment, with the user scenarios and what each person needs | Journeys J1–J4, user scenarios |
| Workflows | One BPMN process per journey: every lane a role, every task a skill | Business processes |
| Requirements | Where the journeys’ requirements are defined, in smart-trust-tools | Functional requirements |
| Taifafeki profiles | The birth hospital’s patient and dose (the source of each DVC), and the record a clinic in Taifafeki keeps when it reads a VHL | Country profiles |
| Onesa profiles | The child and household the CHW registers, reported and verified doses, the referral, DVC verification, and the access log | Country profiles |
| Terminology and logic | Vaccine products, the schedule codes of Onesa, the ConceptMap between them, and the infant schedule as a PlanDefinition | Journey examples |
| Examples | Every screen and payload of the journeys walkthrough as a FHIR example, Taifafeki and Onesa | Journey examples |
How trust works here
Taifafeki and Onesa never connect to each other. Both build on WHO GDHCN. Taifafeki publishes the key it signs certificates with, and Onesa caches the trust list, so its clinics can verify a card from Taifafeki with no signal. A year later the same trust list lets a clinic in Taifafeki verify the VHL from Onesa. Data crosses the border in only two ways: as a signed QR card the family carries, or as a link the family chooses to share. The journeys walkthrough’s “How it works” view lays out both countries’ components on the DPI-H reference architecture, with GDHCN as the foundation; the same picture as an ArchiMate overlay on the RA’s own model is on the architecture page.
The journeys run the HCERT and VHL libraries of smart-trust-tools against WHO SMART Trust and WHO SMART Trust PHW.
The project
The plan, the app-platform proposal and the dependency register. Source: litlfred/smart-trust-demo.
Every person and record here is fictional, and every key is a test key. This guide is a demonstrator, not WHO guidance.