The skill
receiver-scan-credentialas its source filesmart-trust-tools/skills/wallet/receiver-scan-credential.mdwrites it, rendered bygen-processes-viz.tsbecause it has no instruction page on this site — do not edit here. All processes
Scan a health credential
Skill receiver-scan-credential: The health worker at a receiving system scans the QR a holder shows (an HCERT, a VHL carried in an HCERT, or a SMART Health Link) and, for a passcode-protected health link, enters the passcode the holder says. Input is the QR as shown; output is its text (and passcode) handed to the receiving system, which verifies it or follows the link. Performed by a person; never judges authenticity.
Named by: J2 Discover and refer an unregistered infant in Country B, J3 Verify, import and schedule at the home clinic, J4.1 Read a family member’s records at the point of care abroad
Performed by a person: the health worker operating a receiving system
(a CHW app, a clinic EHR, a point-of-care viewer). Role
receiving-health-worker. What happens to the scan is the system’s:
hcert-verify (or its unverified triage read) and vhl-receive; for a
SMART Health Link, the SHL receiver’s manifest request.
Input and output
The contract is input.schema.json
and output.schema.json.
- In: the
shownQR, itsmedium(paper or a screen), and, for a VHL, thepasscodethe holder says. - Out: the
qrtext read, one per QR, and thepasscodewhen one was entered.
What the health worker does
- Scan each QR once, with the receiving system’s camera.
- For a passcode-protected health link, type the passcode the holder says; never ask to see it written.
- Hand over to the system, which verifies. The health worker does not decide whether a credential is genuine: the system’s result says so.
Success criteria
- Each QR’s text reaches the receiving system unchanged (
HC1:…orshlink:/…). - A QR that will not scan is reported as such, and the records are treated like paper.
Input and output contracts
What this skill takes and gives, as a class diagram drawn from its JSON Schema contracts by the schemas viewer’s own renderer. Each box links to its definition; each type to its specification.