SMART Trust demonstrator (WorldHealthOrganization/smart-trust-demo), 16 November 2026. It follows the owner’s decisions on the narrative review cards (A–E), the updated deck and the Country Canvas.
Status key: Done = merged to main (PR #16 or #20). Needs work = a change to a demo application, BPMN process, decision table, FHIR example or the viewer that someone has to make. Decide = needs an owner call first.
1. The technical track (T1–T7): what changed
Update, 16 November 2026: T1–T7 are no longer placeholders. They are drafted from the technical track schedule (draft for the team to confirm; names and times are proposals): each has its sessions, leads, outcomes, the journey steps it teaches from and technical questions, and T7 has the four Day 2 teams. See the technical track in the journeys viewer and the technical track on the module × journey map. The rows below record the state before that.
| What | Where | Status |
|---|---|---|
| Seven technical modules, T1–T7, created as placeholders, each paired with the policy module of the same number and day (T1 ↔ M1 … T7 ↔ M7) | workshops/technical-track.json |
Done |
| A page per technical module, with a switch to its policy pair and a strip of both tracks; each placeholder is seeded with its pair’s technical points at every journey step, as starting material | workshop-t1.html … workshop-t7.html, generated by tools/workshop/module-pages.ts |
Done |
| The hub lists both tracks by day | workshop.html |
Done |
| The technical column of the module × journey map: for every meeting point, what is technical (DSC signing, read-unverified, trust-list caching, terminology map, wallet, VHL, AuditEvent…) and four technical threads that cross modules | module-journey-map.html |
Done |
| The glossary uses the DPI-H RA’s definitions where it has the concept (18 terms, many technical: Client Registry, Terminology Service, Computable Decision Support Engine, HL7 FHIR, LOINC, SNOMED CT…) | glossary.html |
Done |
Still needed to write the technical track
- For each T module: the question it carries, objectives, timings and the journey steps it teaches from. Today only the pairing exists. (Needs work: content from the technical-track owners.)
- A technical canvas or not. The Country Canvas has six policy sheets and no technical sheet. Decide whether T modules fill their own sheets, share the policy sheets, or have none. (Decide.)
- The journeys viewer shows one workshop.
dpi-h-policy-track.workshop.jsonis the policy track. The technical track needs its own workshop file (dpi-h-technical-track.workshop.json) for the viewer to teach it with walkthrough questions, a Discussion lab and sheets. (Needs work, once 1 is written.) - Technical terms the handout lacks (E3): DVC, HCERT, VHL, DSC, Trust Network Participant, provenance, CWT, COSE, DID document. Add them, ideally as a technical glossary for the T track, linked to the SMART Trust guide. (Needs work.)
- The 13 RA concepts with no definition yet (E9): API, PHR, HIE, CRVS, DAK, IG, IPS, ICVP, IHR, PKI, GDHCN, DIIG, TWG keep the handout’s wording until the RA defines them. (Needs work upstream in smart-ra.)
2. Story changes that reach the technical layer
| Decision | Story change | Artefacts affected | Change needed | Status |
|---|---|---|---|---|
| A1, B1–B3, D1 | Journey titles: Vaccinated and recorded, Found and registered, A foreign record used for the next vaccine, Continuity across a border | user scenarios J1–J4, docs/journeys.md, the workshop’s chapter titles, viewer chapter names, device-screen headings, translations | Retitle | Done, #20 |
| C2 (discuss) | Clean up the J numbering (J2a, J2b, J3a, J3b, J4.0a, J4.0b, J4.1) to match the deck’s four journeys | step ids in scenarios, workshop, glossary-use, module map, module pages, FHIR example names, BPMN file names, viewer URLs (walkthrough/J2a/) |
Recommended: keep the step ids (stable links, example names) and show them as Journey 1–4 with parts (2a, 2b…); merge J4.0 and J4.1 into “Journey 4, parts 1 and 2” in titles | Decide |
| A2 | Khamla works in Taifafeki and brings Somsak home to Onesa after the birth | actor khamla-sengmany, J1 and J2 narratives |
Description and narrative text | Done, #20 |
| A4 | Somsak has no national ID; the hospital gives him an identifier at birth, linked to his mother | J1 FHIR example (Patient), S1 device screen | Add a Kesaro Provincial Hospital identifier to Somsak’s J1 Patient and a link to Khamla; S1 shows “registered with hospital ID, linked to mother”. The DVC payload is unchanged (no identity document, STT-PAY-005) | Needs work |
| A6 | Journey 2 happens at 7 weeks (was 3) | J2 scenario when, J2 FHIR examples (TrustDemoJ2Referral.authoredOn 2025-11-18 → 2025-12-16), S3 screen |
Dates and labels | Done, #20 |
| A7 | Journey 3 happens at 10 weeks (was about 7) | J3 scenario, J3 FHIR examples (verification and recommendation 2025-11-25 → 2026-01-06), S4 “Age: 4 Weeks”, S5 “4 Weeks Old” | Dates and labels. Also logic: at 10 weeks pentavalent 1, bOPV 1 and PCV 1 (due at 6 weeks, 2025-12-09) are overdue, so J3b becomes a catch-up: give them that day, and the next doses 4 weeks later | Done, #20 (dates); Needs work (logic, below) |
| A7 → logic | The national schedule must handle a late visit | processes/content/decisions/dose-due.dmn, dose-counts.dmn, TrustDemoJ3Recommendation (forecast status overdue), S5 schedule panel |
A catch-up rule: a dose past its due date is due now; the minimum interval sets the next | Needs work |
| A8 | Khamla’s village is named (the deck says “Khamla’s village”; the site calls it Village 04) | narratives, actor vilay, S3 |
Say “Khamla’s village (Village 04)” once, keep Village 04 | Done, #20 |
| A9 | Vilay finds Khamla in the client registry by her national ID and registers Somsak as her child | J2 BPMN (j2-chw-discovery-referral.bpmn), CHW app (S3), J2 FHIR examples, requirements |
New task “search client registry by caregiver’s national ID” before registration; Khamla’s Patient gets a national ID from Onesa; Somsak linked to her (RelatedPerson or Patient.link). Design point: Vilay is offline for weeks, so the lookup needs a cached extract of the catchment’s registry on the phone, or the match is queued until sync |
Needs work (+ Decide on offline lookup) |
| A10 | Registration notifies the civil registry of a birth abroad (late birth registration) | J2 BPMN, a new actor (Onesa civil registry, CRVS), J2 FHIR examples, S3 | New message flow to CRVS, queued offline and sent on sync; a FHIR Task or message Bundle as the example | Needs work |
| A11 | The CHW app schedules a reminder to bring Somsak to the clinic | J2 BPMN, S3, J2 FHIR examples (J3 already has TrustDemoJ3Reminder) |
A reminder step after the referral; a CommunicationRequest in J2 | Needs work |
| A12, A13 | “Reported, not verified” happens in J2; the family’s one phone is Bounmy’s | — | Already how the site and app work; deck changed | Done |
| A14 | The unmapped Taifafeki Hep B product and the nurse’s clinical call stay | — | No change | Done |
| A15 | The deck now names the passcode-protected link and the access log | — | Already in the site and examples | Done |
| A16 | In Journey 4, Dr. Anan is a paediatrician (the site said primary care clinic) | actor kesaro-clinic-viewer, S8 (“Kesaro Primary Care Clinic”), J4 FHIR examples (Organization, PractitionerRole) |
“Kesaro paediatric clinic”; PractitionerRole specialty paediatrics | Done, #20 |
| A17 | Onesa keeps a national FHIR health portal (the deck now says so) | — | No change | Done |
| B11 | HMIS counts a child registered at home (J2) in the coverage denominator | indicators TrustDemoIND01…04, J2 |
Check the denominator definition includes children registered at J2 who were born abroad; say so in the indicator | Needs work |
| D2–D10 | Canvas fixes (fifth touchpoint, “[Dates]”, capitalisation, cost-driver wording, notifications and consent capabilities) | the Word canvas | Edit the .docx (not the site) | Needs work |
3. Demo applications and tests
| Component | Change needed | Driven by |
|---|---|---|
OHS app (app/, Kotlin Multiplatform: Journeys.kt, JourneyScreen.kt, ImmunizationImport.kt) |
Journey titles where shown; the CHW flow gains a national-ID search, a CRVS notification and a reminder; the clinic flow’s schedule shows catch-up doses at 10 weeks; the J1 hospital flow carries a hospital identifier. AndroidHcertJourneys.feature scenarios updated to match |
A1, A4, A7, A9–A11 |
Android emulator test (android-test/) |
None: it tests the HCERT library against the WHO guide’s vectors, which the story changes do not touch | — |
Device screens (scenarios/device-screens/) |
S1 hospital identifier; S3 national-ID search, CRVS notice, reminder, 7 weeks; S4 and S5 “10 weeks”, catch-up schedule; S8 paediatric clinic | A4, A6, A7, A9–A11, A16 |
BPMN processes (processes/content/) |
j2-chw-discovery-referral: search by national ID, CRVS message, reminder; j3-clinic-verification-schedule: catch-up branch; j4-1-vhl-point-of-care: lane name (paediatric clinic). Re-render the SVGs and checklists (render:bpmn, bpmn:checklist) |
A7, A9–A11, A16 |
Decision tables (processes/content/decisions/) |
dose-due.dmn / dose-counts.dmn catch-up rule |
A7 |
FHIR examples (input/fsh/examples/) |
Dates (J2 +4 weeks, J3 +6 weeks), J1 hospital identifier, Khamla’s national ID, CRVS Task, J2 reminder, J4 paediatric PractitionerRole; regenerate the journey-examples page | A4, A6, A7, A9–A11, A16 |
| Journeys viewer | The canvas in the Table sheets tab and the matrix in Discussion are built (litlfred/cat-harness-tools#2354) and wired up downstream in PR #17. They wait on #2354 merging and a cat-harness-tools re-pin here. A second workshop file when the T track is written | JV-05, JV-06, T track |
| Translations (ar, es, fr, ru, zh) | Every changed English string leaves the five locales’ catalogues behind (reported, not failing). Run a translation refresh after the site PR merges | All text changes |
4. Suggested order
Site PRDone in #20: titles, timings and dates, place names, Khamla, the paediatric clinic, and the FHIR example dates.- Decide C2 (J numbering) and the offline national-ID lookup (A9).
- Logic PR: the catch-up rule (DMN, J3 recommendation, S5).
- J2 process PR: national-ID search, CRVS notification, reminder, across BPMN, FHIR examples, S3 and the app.
Re-pin cat-harness-tools after #2354, then merge the viewer wiring.Done in #21.- Translation refresh.
- Technical track content, then its workshop file and glossary.