health.hats.institution.sharingGrant

A patient-signed pre-authorization of a sharing class: a FHIR R4 Consent (scope patient-privacy) under the HATS profile. Stored in the patient's health.hats.audit.log space; read by the coordinator when it answers checkUserAccess.

Repository @hats.health did:plc:uvvhtareovj2oaregs7vsibv not from the namespace authority
Details · record, key tid
Kindrecord
Record keytid
Authorityinstitution.hats.health
Indexed

Record

record · key tid

Properties

resourceType

requiredstring

FHIR resource type.

  • const: "Consent"

Similar lexicons

semantic match

Lexicons whose schemas describe something close to this one. Check them before publishing a new one that overlaps.

  • A provider grant: a FHIR R4 Consent under the HATS profile (one flat provision: actor, class, code, securityLabel, action, purpose, period). Stored in the patient's health.hats.audit.log space. Counts only with an attestation from the patient or an act circle member; a grant carrying V counts only with the patient's own.

  • health.hats.fhir.consent

    record not from the namespace authority

    A FHIR R4 Consent resource. The record is the resource itself: its JSON fields as FHIR defines them, plus $type and the HATS integrity fields. Decimals are strings, since atproto has no floats; codes keep their code system's case.

  • Clinical consents (to treatment, to procedures). Access and sharing grants live in health.hats.audit.log, not here. The skey is the HL7 confidentiality code, lowercase (n, r, v), or 42cfrpart2 for 42 CFR Part 2 records.

  • health.hats.audit.breakGlass

    record not from the namespace authority

    A break-glass record: clinician DID, institution, reason, sections, and window. Written by the institution node that requested emergency access, into its own repo in the patient's health.hats.audit.log space; signed by the clinician, with a transparency receipt. The coordinator logs the same decision before granting and never writes into spaces.

  • A FHIR R4 Patient resource. The record is the resource itself: its JSON fields as FHIR defines them, plus $type and the HATS integrity fields. Decimals are strings, since atproto has no floats; codes keep their code system's case.