{
  "resourceType": "NamingSystem",
  "id": "NexusGeneratedScheduleNS",
  "name": "NexusGeneratedSchedule",
  "status": "draft",
  "kind": "identifier",
  "date": "2026-09-14",
  "publisher": "WELLSTAR Technologies Corp.",
  "responsible": "Nexus EMR (WELL Health) -- EMR-local identifier system",
  "description": "Marks a `Schedule` as one a Nexus EMR schedule-generation run authored. Carried as\n`Schedule.identifier.system`; the value is the identifier of the practitioner whose calendar it is.\n\n**Authorship, not a search key.** A run finds the calendar to work on by its `actor` association --\nthe schedule naming the practitioner, preferring one that also names the clinic -- and never by an\nidentifier or a resource id. Only a calendar the run CREATES is stamped. A calendar the run finds\nand adopts is corrected in place and does not gain the identifier, so on this resource presence\nmeans the generator wrote this schedule and absence means something else did.\n\n**One write turns on that distinction.** `Schedule.planningHorizon` is removed from a generated\ncalendar, which is open-ended by design, and left untouched on an adopted one. Writing this system\nonto a calendar you generated elsewhere is therefore a request to have that element dropped, not a\nneutral label.\n\n**The value is not unique and is not an identity.** It is the practitioner's identifier, repeated on\nevery calendar the generator writes for that practitioner, so it says who the calendar is for rather\nthan which calendar this is. Do not treat the system and value together as a key: correlate a\nschedule by its own resource identity.\n\nEMR-local: values are minted per deployment and imply no external governance.",
  "uniqueId": [
    {
      "type": "uri",
      "value": "https://fhir.apps.health/NamingSystem/nexus-generated-schedule",
      "preferred": true
    }
  ]
}