NexusClinicalRoleAssignment Naming system

Status: draft · 1.26.0 · JSON

Marks a PractitionerRole as the clinical-role assignment Nexus EMR maintains for a person, carried on PractitionerRole.identifier. A practitioner may hold PractitionerRoles from several writers at once, so an assignment must be recognizable before it is read or rewritten: a reader selects the PractitionerRole bearing an identifier under this system and leaves every other one for that practitioner untouched, and a writer replaces only the resource it marked. The VALUE is the id of the Practitioner the assignment is for, which the resource already states in practitioner -- the fact a consumer needs is the presence of an identifier under this system, not its value, so do not parse it and do not join on it. Nexus EMR maintains at most one such assignment per practitioner and replaces its role codes in place; a practitioner left with no roles has the assignment deleted rather than stored with an empty code. This system names the assignment, never the roles: those are codes on PractitionerRole.code, bound extensibly to CodeSystem/nexus-clinical-roles. MIGRATION: Nexus EMR writes this system today at http://services.well.com/fhir/NamingSystem/user-clinical-role-assignment (FHIR-379), an address this specification does not publish: it is live in stored PractitionerRole.identifier.system values and in code, and is under migration to the URI declared here. Write the URI declared here; expect both until the migration completes.

Type	Value	Preferred
uri	../NamingSystem/nexus-clinical-role-assignment	true
uri	http://services.well.com/fhir/NamingSystem/user-clinical-role-assignment	false