Nexus EMR Item Consent Profile Core Profile¶
| Canonical | ../StructureDefinition/nexus-emr-core-item-consent |
|---|---|
| Status | draft · 1.26.0 |
| Base | Consent (constraint) |
| Source | FSH · 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 / C#
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 : ClinicalResource — generated source
| Accessor | Type | Access | Notes |
|---|---|---|---|
| EffectiveDate | FuzzyDate? |
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? |
read-only | The resource's human headline — a coded concept's label, else a title / name, else undefined. |
| Status | string? |
read/write | active | draft | inactive | entered-in-error |
| Scope | Concept? |
read/write · raw twin | patient-privacy - Privacy consent |
| Category | Concepts |
read/write · raw twin | Fixed: this Consent is an app consent |
| Patient | Reference? |
read/write · raw twin | The patient (Patient X) |
| DateTime | FuzzyDate? |
read/write | When consent was given/withdrawn |
| Policy | Json[]? |
read/write | The policy this consent is given under |
| PolicyRule | Concept? |
read/write · raw twin | Regulation that this consents to |
| Provision | JsonNode? |
read/write | The decision, and the app it is about |