The skill holder-consent-to-share as its source file smart-trust-tools/skills/wallet/holder-consent-to-share.md writes it, rendered by gen-processes-viz.ts because it has no instruction page on this site — do not edit here. All processes

Consent to share a health link

Skill holder-consent-to-share: The holder decides what a health link (a Verifiable Health Link or a SMART Health Link) shares: which members’ records, protected by which passcode, until when. That choice is the holder’s consent, and the sharer issues nothing beyond it. Input is the records the sharer offers; output is the share request. Performed by a person.

Named by: J1 Issue the newborn’s birth-dose DVCs in Country A, J2 Discover and refer an unregistered infant in Country B, J3 Verify, import and schedule at the home clinic, 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

Performed by a person: the holder (IHE ITI VHL VHL Holder). Role vhl-holder. The sharer that acts on the answer is vhl-share for a VHL; for a SMART Health Link it is the SHL sharer, which sets the link’s P flag and exp from the same answer. Which kind of link is the sharer’s, not the holder’s, choice.

Input and output

The contract is input.schema.json and output.schema.json.

  • In: the offer: the members whose records the sharer holds and may share, with the documents each has (an IPS, vaccination certificates), and the longest maxExpiry the sharer allows.
  • Out: the share request: the members (and documents) chosen, the passcode the holder sets, and the expiry.

What the holder does

  1. Choose who is shared: one member, several, or none. Nothing is chosen by default.
  2. Set a passcode the holder can say aloud, and an expiry no later than the trip or visit needs.
  3. Confirm. Declining at any step shares nothing.

Success criteria

  • The share request names only what the holder chose; the sharer issues nothing else (vhl-share encrypts exactly those documents).
  • The passcode is handed to the sharer once, to protect the manifest, and is not printed on the QR.
  • With nothing chosen, no link is issued.

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.

input [1..1]output [1..1]documents [0..*]members [0..*]offer [1..1]members [0..*]share [1..1]holder-consent-to-share«skill»holder-consent-to-shareinput : HolderConsentToShareInput [1..1]output : HolderConsentToShareOutput [1..1]HolderConsentToShareInput«json-schema»HolderConsentToShareInputoffer : HolderConsentToShareInput.offer [1..1]HolderConsentToShareInput.offer.members.documents«json-schema»HolderConsentToShareInput.offer.members.documentstype : string [1..1]reference : string [1..1]HolderConsentToShareInput.offer.members«json-schema»HolderConsentToShareInput.offer.membersmember : string [1..1]documents : HolderConsentToShareInput.offer.members.docu… [0..*]HolderConsentToShareInput.offer«json-schema»HolderConsentToShareInput.offermembers : HolderConsentToShareInput.offer.members[] [0..*]maxExpiry : string [0..1]HolderConsentToShareOutput«json-schema»HolderConsentToShareOutputshare : HolderConsentToShareOutput.share [1..1]HolderConsentToShareOutput.share.members«json-schema»HolderConsentToShareOutput.share.membersmember : string [1..1]documents : string[] [0..*]HolderConsentToShareOutput.share«json-schema»HolderConsentToShareOutput.sharemembers : HolderConsentToShareOutput.share.members[] [0..*]passcode : string [0..1]expiry : string [1..1]

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

deployed dev