The journeys walkthrough (first told in the VaxLink workshop, source) shows sample FHIR payloads in its payload drawer and on its device screens S1 to S8. This page maps each of them to the example in this guide that materializes it.

Every example is published twice: as a page, and as raw JSON at a stable URL the walkthrough can fetch (https://worldhealthorganization.github.io/smart-trust-demo/<Type>-<id>.json). They are FHIR R4 (4.0.1), as this guide is, like smart-base and the Personal Health Wallet guide.

By device screen

Screen Moment Country, device Shows Examples
S1 J1 Taifafeki, tablet Birth doses with their product codes; two printed DVCs signed with XXR’s DEV key (kid 916ffa567c0f44a2) the Taifafeki records behind the cards: TrustDemoTaifafekiSomsak, TrustDemoJ1HepB, TrustDemoJ1Bcg; the doses as later verified in Onesa: TrustDemoJ3HepB (json), TrustDemoJ3Bcg (json); TrustDemoKesaroHospital (json), TrustDemoAnan (json)
S2 J2a Onesa, mobile Offline QR scan of the two cards: read, not verified, nothing saved yet the Taifafeki records on the cards: TrustDemoJ1HepB, TrustDemoJ1Bcg
S3 J2b Onesa, mobile Offline registration of Somsak into the household through a form; the doses saved as reported (primarySource false), and a referral TrustDemoHousehold (json), TrustDemoHouseholdRegistration (json), TrustDemoJ2Registration (json), TrustDemoSomsak (json), TrustDemoKhamla (json), TrustDemoBounmy (json), TrustDemoJ2HepBReported (json), TrustDemoJ2BcgReported (json), TrustDemoJ2Referral (json)
S4 J3a Onesa, tablet Signature verified against the cached GDHCN trust list; provenance attached TrustDemoJ3Verification (json), TrustDemoJ3HepB (json), TrustDemoJ3Bcg (json)
S5 J3b Onesa, tablet Product code mapped to the national schedule (nurse adjudicates the Hep B product); 6-week doses calculated; reminder TrustDemoProductToOnesaEpi (json), TrustDemoJ3Adjudication (json), TrustDemoOnesaInfantSchedule (json), TrustDemoJ3Recommendation (json), TrustDemoJ3Reminder (json)
S6 J4.0a Onesa, mobile Family wallet on one phone; Somsak’s IPS with six doses TrustDemoJ4Ips (json), TrustDemoOnesaPenta1 (json), TrustDemoOnesaBopv1 (json), TrustDemoOnesaPcv1 (json), TrustDemoOnesaMr1 (json), TrustDemoFamilyPhone (json)
S7 J4.0b Onesa, mobile VHL QR with a 4-digit passcode and a 14-day expiry; consent TrustDemoJ4Consent (json)
S8 J4.1 Taifafeki, tablet VHL viewer: passcode unlock, wrong-passcode test, access logged in Onesa TrustDemoJ41Received (json), TrustDemoJ41Access (json), TrustDemoJ41WrongPasscode (json)

Country profiles

Each country records only what its own step needs, so the guide has a small profile per country where the two differ. Each profile’s description says how it is used in the journey and why its constraints are there. These are demonstrator profiles: they show what each step relies on and are not a ministry’s national specification.

Country Moment Profile Why it is there Examples
Taifafeki J1 TrustDemoTaifafekiPatient The birth hospital’s newborn: a hospital number, since a baby of parents from Onesa has no Taifafeki citizen id. TrustDemoTaifafekiSomsak
Taifafeki J1 TrustDemoTaifafekiImmunization A birth dose with every field the signed DVC (HCERT) carries: product, date, lot, dose number, performer. TrustDemoJ1HepB, TrustDemoJ1Bcg
Taifafeki J4.1 TrustDemoTaifafekiVhlReceipt What the Taifafeki clinic keeps when it views a summary from Onesa through a VHL: viewed, not copied. TrustDemoJ41Received
Onesa J2 TrustDemoOnesaPatient The child the CHW registers, under a temporary id until civil registration catches up. TrustDemoSomsak
Onesa J2b TrustDemoOnesaHousehold The household roster, which is how a CHW notices a missing newborn. TrustDemoHousehold
Onesa J2b TrustDemoOnesaRegistration The answers on the offline registration form (Structured Data Capture), kept so the extracted records trace back to them. TrustDemoJ2Registration
Onesa J2b TrustDemoOnesaReportedImmunization A foreign dose read without verification: primarySource false, the family as source, not counted by the schedule. TrustDemoJ2HepBReported, TrustDemoJ2BcgReported
Onesa J2b TrustDemoOnesaReferral The CHW’s referral to the clinic, pointing at the reported doses to verify. TrustDemoJ2Referral
Onesa J3a TrustDemoOnesaDvcVerification Who verified which DVC against the GDHCN trust list, and which reported doses it replaced. TrustDemoJ3Verification
Onesa J3 TrustDemoOnesaImmunization A dose on the national schedule: the Onesa EPI code is required, and a foreign product code is kept beside it. TrustDemoJ3HepB, TrustDemoJ3Bcg, TrustDemoOnesaPenta1
Onesa J4.1 TrustDemoOnesaVhlAccess Every VHL access logged at home, refusals included (IHE BALP pattern). TrustDemoJ41Access, TrustDemoJ41WrongPasscode

The payload drawer

The keys of the walkthrough’s MOCK_FHIR_RESOURCES (src/data/storylineData.ts) and the example that replaces each one:

Key Type Example What changed
patient Patient TrustDemoSomsak (json) Temporary-id system is this guide’s (http://smart.who.int/trust-demo/sid/onesa-temporary-id), not a ministry URL.
group Group TrustDemoHousehold (json) actual = true; the members are Patients (FHIR R4 Group lists Patients, so each parent is a Patient beside their RelatedPerson role); the household code is FAMMEMB with the text “Household”.
immunizationHepB Immunization TrustDemoJ3HepB (json) Both codings, as on the walkthrough’s payload; plus CVX 08. The product and schedule code systems are this guide’s illustrative stand-ins.
serviceRequest ServiceRequest TrustDemoJ2Referral (json) Code is SNOMED CT 3457005 (patient referral) with the walkthrough’s text; the verification reason stays in reasonCode.
provenance Provenance TrustDemoJ3Verification (json) Verifier, enterer and author agents; the DVCs as source entities and the reported doses as removed. The COSE signature stays in the DVC rather than in Provenance.signature.
auditEvent AuditEvent TrustDemoJ41Access (json) R4 shape: type, subtype, outcome, outcomeDesc; the receiver is the requestor, the Onesa gateway the custodian and observer. The passcode is never logged.
cborPayload (not FHIR) — The DVC payload is an HCERT (CBOR/COSE), not a FHIR resource; its logical model is smart-trust-phw’s DVCMinPreQual. It waits for bean ig01 before it is an example here.

What the examples change from the walkthrough’s copies

Edit this page on GitHub