NexusCdsRule Naming system

Status: draft · 1.26.0 · JSON

Identifies decision-support rules acting as Device actors in the EMR (Task.requester, Task.owner where work is assigned to an agent, Provenance.agent.who). References under this system are LOGICAL: Reference.identifier carries the rule id and Reference.type carries 'Device'; no Device resource need exist on the FHIR server -- the identifier points into the decision-support engine's rule registry. Reference.display SHOULD carry the human-readable rule name. Granularity is the rule: the unit a clinician or auditor can recognize and a governance process can approve. Sibling of NamingSystem/nexus-harness-graph, which names harness graphs. These are separate authorities because separate registries mint them and nothing prevents both from minting the same value, which would make two producers indistinguishable and, for the same reason the business keys are split between NamingSystem/nexus-cds-key and NamingSystem/nexus-harness-key, would let one producer's re-run find and overwrite another producer's task. The system names the registry that issued the identifier and asserts nothing about which process executed the rule, so a rule invoked as a tool from elsewhere keeps its identifier. Values are opaque to consumers and MUST NOT be parsed. A consumer asking whether a resource was machine-produced reads the AIAST security label, not this system.

Type	Value	Preferred
uri	../NamingSystem/nexus-cds-rule	true