Nexus EMR Consent Item CodeSystem Code system¶
| Canonical | ../CodeSystem/nexus-consent-item |
|---|---|
| Status | draft · 1.26.0 |
| Content | complete |
| Source | FSH · JSON |
The consent items a patient can be asked about, one Consent resource per (patient, item).
Content is complete for the standard, cross-clinic catalogue defined here (Email, SMS,
AI Scribe). Clinic-defined items are expected in a later phase and will be published in
tenant-scoped CodeSystems rather than added to this one, so consumers MUST NOT assume every
item coding they encounter on a NexusEmrCoreItemConsent comes from this system. The
NexusEmrCoreItemConsent category binding is extensible for exactly that reason.
Each concept's definition is the standard description shown to staff and patients when the item is presented for a decision.
| Code | Display | Definition |
|---|---|---|
email |
Whether the clinic may email the patient for any reason, including sending the patient's own health information (e.g., lab results, referral letters), as well as routine, non-clin… | |
sms |
SMS | Whether the clinic may text the patient for any reason, including the patient's own health information, as well as routine, non-clinical purposes like appointment reminders. |
ai-scribe |
AI Scribe | Whether an AI scribe tool may listen to, transcribe, or summarize the visit to help generate clinical notes. |