Skip to content

Nexus EMR Item Consent Profile Core Profile

Canonical../StructureDefinition/nexus-emr-core-item-consent
Statusdraft · 1.26.0
BaseConsent (constraint)
SourceFSH · JSON

Patient-level consent for one catalogue item — whether the clinic may email the patient, text the patient, or use an AI scribe during their visit. Recorded manually by clinic staff from what the patient tells them, not captured through a patient-facing flow.

TypedFhir API / TypeScript

The typed accessor surface Consent exposes for Consent — generated from this IG's compiled profile; each typed accessor has a validating raw-FHIR twin (xRaw) where marked. The three ports are parity-enforced.

class Consent extends ClinicalResourcegenerated source

Accessor Type Access Notes
$effectiveDate FuzzyDate | undefined read-only The resource's effective date — the first present of this profile's date elements (precedence), normalized to the canonical FuzzyDatetime f…
$display string | undefined read-only The resource's human headline — a coded concept's label, else a title / name, else undefined.
status string | undefined read/write active | draft | inactive | entered-in-error
scope Concept | undefined read/write · raw twin patient-privacy - Privacy consent
category Concepts read/write · raw twin Fixed: this Consent is an app consent
patient Reference | undefined read/write · raw twin The patient (Patient X)
dateTime FuzzyDate | undefined read/write When consent was given/withdrawn
policy Json[] | undefined read/write The policy this consent is given under
policyRule Concept | undefined read/write · raw twin Regulation that this consents to
provision Json | undefined read/write The decision, and the app it is about