Generated from processes/content/j4-1-vhl-point-of-care.bpmn by gen-processes-viz.ts — do not edit here. All processes · smart-trust-demo processes

J4.1 Read a family member’s records at the point of care abroad

Process_J41VhlFetch · advisory · 8 step(s)

J4.1. Abroad, a child of the family needs care. The caregiver, the VHL Holder (IHE ITI VHL; Holder in SMART Trust and smart-trust-phw, requirement provide-a-vhl-to-a-receiver), opens her QR on the family phone and tells the passcode. The hospital system, a VHL Receiver (Receiver in SMART Trust and smart-trust-phw), verifies the HCERT against the GDHCN trust list, requests the manifest by ITI-YY5 with an HTTP Message Signature (STT-VHL-005, STT-VHL-006, STT-VHL-008) and decrypts the documents (STT-VHL-007). Country B’s portal checks the passcode, returns the manifest and logs every request, granted or refused, as an AuditEvent at home (IHE BALP). If the HCERT does not verify, there is no digital verification: the VHL is not followed and the records are treated like paper. As in J3, loading the DID documents is a PRECONDITION of this visit, not a step in it: the hospital verifies against its cached copy of the trust list and needs no connection to do so. It refreshes that cache nightly or hourly, where an offline site such as the J3 clinic refreshes about weekly.

BPMN diagram: J4.1 Read a family member's records at the point of care abroad

How it connects

  • Called by: no call activity names this process
  • Calls: none
  • Presented on: no docs page section shows this diagram
  • Running instances: none recorded

Lanes — who acts

lane role what it does here
Caregiver caregiver —
Family phone family-phone —
Point-of-care provider poc-provider —
Point-of-care receiver poc-receiver —
National health portal national-portal —

Steps

3 of 8 step(s) carry no documentation — activity-documented lists them.

step lane skill / sub-process what it does
Show the child’s VHL QR
Task_Open
Family phone wallet-hold-vhl —
Scan the QR and enter the passcode the caregiver says
Task_Scan
Point-of-care provider receiver-scan-credential —
Verify the HCERT and read the VHL at key 5
Task_Verify
Point-of-care receiver hcert-verify STT-VER-001 against Country B’s DSC on the trust list the preconditions establish; VHL expiry (STT-VHL-009). A DSC Country B published after the hospital’s last refresh is not in its copy, so the HCERT fails at the trust-list step (STT-VER-006), naming that reason.
Not verified: treat records as paper
Task_Unverified
Point-of-care provider review-client-history No digital verification: treat the records like paper. The HCERT failed verification. The typed result names the step and the reason (STT-VER-008), for example a DSC missing from the cached trust list (STT-VER-006). Nothing is digitally verified, so the VHL is not followed and no manifest is requested. Whatever the family can show, such as the paper DVCs or a QR read unverified (STT-VER-011), carries the same weight as a paper record: the clinician decides on it by clinical judgement and local policy, and records why it was not verified.
Request the manifest (ITI-YY5), signed
Task_Fetch
Point-of-care receiver vhl-receive STT-VHL-005, STT-VHL-006, STT-VHL-008; the host does the HTTP, the library builds and reads (STT-VHL-010).
Check passcode, log access, return manifest
Task_Release
National health portal portal-serve-manifest Check the passcode, return the manifest and log the access. The home country’s portal hosts the manifest (ITI-YY5). It checks the passcode and the link’s expiry and the consent the holder gave when sharing (IHE PCF), returns the manifest of encrypted files on success, and records every request, granted or refused, as an AuditEvent (IHE BALP) in the home country. A wrong passcode is refused and still logged. The records stay hosted at home: the receiver views them and nothing is copied into a registry abroad.
Decrypt the IPS and DVCs
Task_Decrypt
Point-of-care receiver vhl-receive JWE dir/A256GCM (STT-VHL-007).
Review history, allergies and vaccinations
Task_Review
Point-of-care provider review-client-history —

Decisions

1 of 1 decision(s) carry no documentation — gateway-documented lists them.

decision what decides it branches
HCERT verified?
Gateway_Verified
— yes → Request the manifest (ITI-YY5), signed
no → Not verified: treat records as paper

SMART Trust demonstrator: journeys J1 to J4 — built with folio-assistant.

deployed dev