The skill
vhl-shareas its source filesmart-trust-tools/skills/vhl/vhl-share.mdwrites it, rendered bygen-processes-viz.tsbecause it has no instruction page on this site — do not edit here. All processes
Issue a VHL
Skill vhl-share: Issue a VHL: a key, documents encrypted as JWE dir / A256GCM, and the payload as a CBOR map at HCERT key 5 (journey J4.0). A plain SMART Health Link is issued by the same steps with its own carrier.
Named by: J4.0 Issue the family’s records to one phone as VHLs, J4.1 Read a family member’s records at the point of care abroad
Issue a VHL: a key, documents encrypted as JWE dir / A256GCM, and the payload as a CBOR map at HCERT key 5 (journey J4.0).
Library operations
In the WIT contract (api/wit/):
vhl.vhl-payloadpayloads.raw-payloadvhl.to-vhlinkvhl.new-keyvhl.decryptvhl.build-manifest-request
Requirements
This skill satisfies 6 requirement(s), listed in satisfies above; each is a req: node in skills/requirements/.
A SMART Health Link is the same issue, with another carrier
A VHL is a SMART Health Link payload carried, signed, in an HCERT
(what smart-ips-pilgrimage calls a “Verifiable SHL”). A plain SHL is issued
by the same steps (the key, each document encrypted, the manifest, the
passcode flag P and exp from the holder’s consent,
holder-consent-to-share) with the payload as shlink:/ and base64url JSON
instead of HCERT key 5, so it is not signed and the hcert steps are skipped.
This skill covers both; the requirements above are the VHL’s.