Each module of the policy-maker track asks one question of the same story. This page shows where each policy module (M1 to M7), and then each technical module (T1 to T7), meets a step of the journeys (J1 to J4.1), and, at each meeting point, what the system does there and the policy question the table answers about it, for its own country. The same map is the Modules × journey step of the journeys viewer’s Discussion tab.

● = the policy module’s question is asked at this step in the walkthrough. ○ = the policy module draws on this step without asking there. ◆ = the technical module works with this step (its technical question and what the system does there are under The technical track below).

The map

Module Sheet J1 J2a J2b J3a J3b J4.0a J4.0b J4.1
Policy track                  
M1 From journey to capabilities Sheet 1 ● ○ ○ ● ○   ○ ○
M2 The reference architecture (DPI-H) and where you stand Sheet 2 ○   ● ○     ○  
M3 Standards, specifications and the core data set Sheet 3 ○ ●     ●   ○  
M4 Trust, credentials and wallets Sheet 4 ● ●   ●   ●   ○
M5 Governance, decision rights and the legal basis Sheet 4 ●   ●     ● ● ●
M6 Doing it together Sheet 5       ○ ●   ● ●
M7 First move and the investment required Sheet 6 ○     ○       ●
Technical track                  
T1 Building with FHIR and the Open Health Stack serves M1 ◆       ◆   ◆  
T2 Offline data capture serves M3   ◆ ◆          
T3 Trust between countries: SMART Trust and the GDHCN serves M4 ◆     ◆       ◆
T4 Workflows, sync and who sees what serves M5     ◆   ◆   ◆ ◆
T5 From records to charts serves M2     ◆   ◆     ◆
T6 Verifying a card, sharing a link serves M6       ◆     ◆ ◆
T7 Team build, showcase and the journey together serves M7     ◆ ◆   ◆   ◆

Where they meet

M1 · From journey to capabilities

What had to exist for this moment to work — and where does our version of the journey break?

Step   What the system does Policy question for the table
J1 ● Hospital immunization record; one DVC per birth dose, signed by the document signer of Taifafeki. Which child, which record and which border would your country’s use case cover?
J2a ○ Offline CHW app reads the cards without verifying them. Where does your own journey break first: is there a stage where no national system knows the child exists?
J2b ○ Client registry holds a child with no birth record; referral to the clinic. For a child born abroad, does each touchpoint in your country work, partly work, or break today?
J3a ● Signature checked offline against the cached GDHCN trust list. What must be true before a nurse trusts a vaccination record she did not create?
J3b ○ Product code mapping and the computable national schedule. Does a dose given abroad count toward your national schedule?
J4.0b ○ National portal issues a passcode-protected link to the IPS and DVCs. Should the family or the state decide when a child’s record is shared?
J4.1 ○ Point-of-care viewer reads the whole first year from Onesa. Is continuity of the record across a border the end point of your use case?

M2 · The reference architecture (DPI-H) and where you stand

Which system do we use today for each block — and is it there, partly there, or absent?

Step   What the system does Policy question for the table
J1 ○ Facility EMR, product registry, immunization registry, trust services. Which block of your national architecture does each of these systems map to, and does it exist today?
J2b ● Client registry, CRVS link, offline CHW app, facility registry for the catchment. Which block gives a child their first identifier, and how does a birth abroad enter your registries and your coverage denominator?
J3a ○ Clinic EHR as a verifier; trust store loaded from the national trust anchor. Should a foreign record be verified in each clinic, or by one national service?
J4.0b ○ National FHIR server behind a gateway; IPS assembled from the lifelong record. Is there a national record for a shared link to point to?

M3 · Standards, specifications and the core data set

Which standards do we adopt rather than author — and who owns the national core data set?

Step   What the system does Policy question for the table
J1 ○ Birth-dose data elements: vaccine, product code, batch, date, giver (immunization DAK core data dictionary). Will you adopt the immunization core data set, or design your own national form?
J2a ● A core data element that tells a reported dose from a verified one. Who in your country defines the data element that tells a reported dose from a verified one?
J3b ● Terminology service: the product code of Taifafeki kept, the schedule code of Onesa added beside it; schedule logic over every dose. Who owns your national core data set and the code maps to other countries, and is vaccine code licensing settled?
J4.0b ○ IPS plus an immunization core as the part of the record that crosses borders. Will you adopt the IPS and the VHL specification as they are, and author only national extensions?

M4 · Trust, credentials and wallets

Who signs, who verifies, and who would hold the national trust anchor? Name it; do not decide it.

Step   What the system does Policy question for the table
J1 ● Document signer certificate (DSC) and its key; HCERT/CWT signing of each DVC. Who signs a vaccination record on behalf of your health sector: the hospital, the ministry, or a national trust service?
J2a ● Read-unverified: the CHW device decodes but does not verify. Who is allowed to verify a foreign credential: a health worker’s phone, a clinic, or only a national service?
J3a ● GDHCN trust list (DID documents), cached for offline verification; kid lookup. Who would hold your national trust anchor and accept a foreign signature, and what must be decided before you join the GDHCN?
J4.0a ● Family wallet on one shared phone, one profile and one VHL per member. Is a family wallet a national service, a private app or both, and who approves the apps that may hold a record?
J4.1 ○ Viewer verifies the VHL’s HCERT against the DSC of Onesa from the trust list. Who verifies your citizens’ records abroad, and what may that verifier see?

Who holds each decision — and what legal basis lets the record cross a border and be shared for a child?

Step   What the system does Policy question for the table
J1 ● Credential issued to a child with no national ID. What legal basis lets a facility issue a health credential to a child who is not a citizen and has no national ID?
J2b ● Temporary id created at a home visit, offline. Who may create a health identity for a newborn at a home visit, and on whose consent?
J4.0a ● Parent holds the child’s record on a shared device. Who may hold and share a child’s record, and what does your law say about dependants?
J4.0b ● Consent resource recorded; 4-digit passcode; 14-day expiry. What legal basis lets a clinician abroad open a record held at home on the family’s consent, and who sets how the link is protected?
J4.1 ● AuditEvent logged in Onesa on every access, including failed passcodes. What agreement makes every view abroad leave an entry in your home log, and who reads it?

M6 · Doing it together

Would your neighbour need this too? If yes, why would you each build it?

Step   What the system does Policy question for the table
J3a ○ One trust network for every programme that signs credentials. Should the trust network be built once for the region and every programme, not for immunization alone?
J3b ● Code map between neighbours’ vaccine products. Should neighbouring countries build one vaccine code map together instead of each building their own?
J4.0b ● Regional IPS + immunization profile with national extensions. Should the part of the record that crosses borders be profiled once for the region, with national extensions left sovereign?
J4.1 ● Connectathon test of issuer, gateway and viewer. What would your country bring to a regional connectathon within twelve months?

M7 · First move and the investment required

What is realistic in twelve months with the people and money we have — and who owns it?

Step   What the system does Policy question for the table
J1 ○ Issuing to the WHO certificate specification. If your country cannot issue a signed record yet, is that your first move?
J3a ○ GDHCN onboarding and a clinic verifier. If your clinics cannot verify a foreign record yet, is that your first move, and who pays for key management year after year?
J4.1 ● Whichever moment breaks hardest for the country. What is your twelve-month first move, who owns it, and which cost dominates it?

The technical track

The technical track’s modules (T1 to T7, from the draft schedule) teach from the same journey. ● = the module works with this step; each meeting point has what the system does there and a technical question for the room.

Module Day Serves J1 J2a J2b J3a J3b J4.0a J4.0b J4.1
T1 Building with FHIR and the Open Health Stack 1 M1 ●       ●   ●  
T2 Offline data capture 1 M3   ● ●          
T3 Trust between countries: SMART Trust and the GDHCN 1 M4 ●     ●       ●
T4 Workflows, sync and who sees what 1 M5     ●   ●   ● ●
T5 From records to charts 1 M2     ●   ●     ●
T6 Verifying a card, sharing a link 2 M6       ●     ● ●
T7 Team build, showcase and the journey together 2 M7     ● ●   ●   ●

T1 · Building with FHIR and the Open Health Stack

Which FHIR resources, terminologies and tools carry this journey, and where does each lab use them?

Step What the system does Technical question for the room
J1 Patient and Immunization in the hospital record; each dose signed as a DVC (HCERT). Which FHIR resources does the hospital write for a birth dose, and which of their fields end up in the signed card?
J3b ConceptMap from the product codes of Taifafeki to the schedule codes of Onesa; the schedule as a PlanDefinition. How does an implementation guide let two countries keep their own vaccine codes and still count each other’s doses?
J4.0b The IPS as a FHIR document Bundle assembled from the national record. What makes the IPS readable in another country’s system without a bilateral agreement?

T2 · Offline data capture

How does a form on a health worker’s phone become a patient record, with no signal?

Step What the system does Technical question for the room
J2a The CHW app decodes the paper cards (read-unverified) and fills the form from them, without checking signatures. Which data elements can the form take from a scanned card, and how does it mark them as reported, not verified?
J2b The household registration Questionnaire; answers become Patient, Group (household) and reported Immunization, queued offline. Which validation or skip rule stops a duplicate child being registered in the same household?

T3 · Trust between countries: SMART Trust and the GDHCN

How can a clinic in one country trust a vaccination record from another, and when is a card better than a link?

Step What the system does Technical question for the room
J1 The document signer key of Taifafeki (DSC of XXR) signs each DVC as a CWT in COSE. What does the DVC carry, and what does it deliberately leave out, so a card is enough without an identity document?
J3a The clinic verifies each card offline against its cached copy of the GDHCN trust list, by kid. How fresh does the cached trust list have to be, and what should the app show when a signature fails?
J4.1 The viewer verifies the VHL’s HCERT against the DSC of Onesa (XXU) before it fetches anything. Why is the health data not in the QR, and what does the viewer check before it opens the link?

T4 · Workflows, sync and who sees what

What should happen next for this child, how does the record reach the server, and who is allowed to see it?

Step What the system does Technical question for the room
J2b Everything Vilay records stays queued on the phone, for up to 28 days, and syncs when a signal returns. What happens to a queued registration if the clinic registers the same child before the phone syncs?
J3b The Onesa schedule (PlanDefinition) runs over every dose; at 10 weeks the 6-week doses come out overdue. How does the plan definition decide a dose is overdue, and what sets the date of the next one?
J4.0b The family’s consent is recorded before the portal issues the link; the gateway enforces passcode, expiry and consent on every request. Where does the gateway read the consent from, and what does it do when the link has expired?
J4.1 Each view is logged as an AuditEvent in Onesa, including failed passcode attempts. Which AuditEvent fields let Onesa tell the family who looked at the record, and when?

T5 · From records to charts

How does a FHIR record become a row, a chart and a coverage number, and who accessed what?

Step What the system does Technical question for the room
J2b A child born abroad and registered at home enters the coverage denominator here. Which flattened table and which column put Somsak in the coverage denominator, and when?
J3b Verified doses, including those given abroad, count toward coverage indicators. How does the indicator count a dose given abroad without counting it twice?
J4.1 AuditEvents become an access log you can chart. What would a ‘who looked at this child’s record abroad’ chart need from the AuditEvent rows?

How does an app go from a scanned QR to a verified result, and from a shared link to the records behind it?

Step What the system does Technical question for the room
J3a Scan, Base45 and zlib decode, COSE signature check against the trust list, then import with provenance. At which step of decoding does a tampered card fail, and what does the nurse see?
J4.0b The portal encrypts the IPS and DVCs, publishes a manifest and signs the link as an HCERT. What is inside the link QR, and why can a 4-digit passcode be enough?
J4.1 The viewer fetches the manifest with an HTTP Message Signature, sends the passcode, and decrypts the documents. What does the viewer need from the trust list, and what does it need from the gateway of Onesa?

T7 · Team build, showcase and the journey together

Can each team change one app in the journey and then run the whole journey live, from a birth abroad to a clinic back home to the family travelling again?

Step What the system does Technical question for the room
J2b CHW app team: the registration form, the household, the referral. Which one configuration change would make the CHW app fit your country’s household register?
J3a Clinic app team: the verifier and its trust store. How would your clinic app load your country’s trust list, and how often would it refresh it?
J4.0a Family app team: one phone, one profile and one link per member. How should the family app separate each member’s records on a shared phone?
J4.1 Viewer app team: open the link, enter the passcode, read the records. What must the viewer show the clinician about where the records came from?

Technical overlaps

Components that more than one module and more than one step depend on: build or test them once.

Thread Modules Steps How it crosses
Client registry and identifiers M2, M5 J1, J2b, J4.0a The same registry that gives Somsak a temporary id at home (J2b) is the one his IPS is assembled against (J4.0b). M2 asks whether it exists; M5 asks who may write to it.
Signing and the trust list M4, M6, M7 J1, J3a, J4.1 One PKI carries three moments: Taifafeki signs the DVCs (J1), Onesa verifies them offline (J3a), and Onesa signs, with its own key, the VHL a viewer in Taifafeki checks (J4.1). Built once, for every credential.
Core data set and terminology M3, M6 J2a, J3b, J4.0b The reported/verified element (J2a), the product code map (J3b) and the cross-border IPS profile (J4.0b) are one core data set, read at three points.
Lifelong record and the share link M2, M4, M5 J4.0a, J4.0b, J4.1 The national record, the wallet and the gateway’s audit log are one service seen from the family, the clinician and the ministry.

Policy overlaps

Decisions and legal bases that more than one module and step force: decide them once, with one holder.

Thread Modules Steps How it crosses
Trust anchor (decision right) M4, M5 J1, J3a, J4.1 Who signs at home and who accepts a foreign signature is one decision; M4 names the holder, M5 asks under what mandate.
Consent for dependants (legal basis) M5, M4 J1, J2b, J4.0a, J4.0b The child acts through his parents from birth to the clinic abroad; the same rule decides who registers him, who holds his record and who may share it.
Cross-border legal basis M5, M6 J4.0b, J4.1 Opening a home record abroad and logging the view at home need one agreement, which is cheaper to reach regionally than pair by pair.
Core data set custody (decision right) M3, M6 J2a, J3b Whoever owns the core data set owns the code maps to neighbours; the room decides whether that is a country, a region or WHO.

Sources

The steps and the questions asked at them are the workshop’s (workshops/dpi-h-policy-track.workshop.json); the journeys are j1-born-abroad, j2-found-at-home, j3-made-official, j4-0-one-family-one-phone, j4-1-full-history-abroad. The cell text and the overlaps are its matrix; the technical track is workshops/technical-track.json.

Edit this page on GitHub