NexusGeneratedSchedule Naming system

Status: draft · 1.26.0 · JSON

Marks a Schedule as one a Nexus EMR schedule-generation run authored. Carried as Schedule.identifier.system; the value is the identifier of the practitioner whose calendar it is.

Authorship, not a search key. A run finds the calendar to work on by its actor association -- the schedule naming the practitioner, preferring one that also names the clinic -- and never by an identifier or a resource id. Only a calendar the run CREATES is stamped. A calendar the run finds and adopts is corrected in place and does not gain the identifier, so on this resource presence means the generator wrote this schedule and absence means something else did.

One write turns on that distinction. Schedule.planningHorizon is removed from a generated calendar, which is open-ended by design, and left untouched on an adopted one. Writing this system onto a calendar you generated elsewhere is therefore a request to have that element dropped, not a neutral label.

The value is not unique and is not an identity. It is the practitioner's identifier, repeated on every calendar the generator writes for that practitioner, so it says who the calendar is for rather than which calendar this is. Do not treat the system and value together as a key: correlate a schedule by its own resource identity.

EMR-local: values are minted per deployment and imply no external governance.

Type	Value	Preferred
uri	../NamingSystem/nexus-generated-schedule	true