{
  "resourceType": "CodeSystem",
  "status": "draft",
  "content": "complete",
  "name": "NexusConsentItemCS",
  "id": "nexus-consent-item",
  "title": "Nexus EMR Consent Item CodeSystem",
  "description": "The consent items a patient can be asked about, one Consent resource per (patient, item).\n\nContent is `complete` for the standard, cross-clinic catalogue defined here (Email, SMS,\nAI Scribe). Clinic-defined items are expected in a later phase and will be published in\ntenant-scoped CodeSystems rather than added to this one, so consumers MUST NOT assume every\nitem coding they encounter on a NexusEmrCoreItemConsent comes from this system. The\nNexusEmrCoreItemConsent `category` binding is extensible for exactly that reason.\n\nEach concept's definition is the standard description shown to staff and patients when the\nitem is presented for a decision.",
  "url": "https://fhir.apps.health/CodeSystem/nexus-consent-item",
  "concept": [
    {
      "code": "email",
      "display": "Email",
      "definition": "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-clinical purposes like appointment reminders."
    },
    {
      "code": "sms",
      "display": "SMS",
      "definition": "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."
    },
    {
      "code": "ai-scribe",
      "display": "AI Scribe",
      "definition": "Whether an AI scribe tool may listen to, transcribe, or summarize the visit to help generate clinical notes."
    }
  ],
  "experimental": false,
  "caseSensitive": true,
  "count": 3
}