Skip to content

NexusAutomation Naming system

Status: draft · 1.33.0 · JSON

Identifies first-party EMR automation acting as a Device actor (Task.requester, Task.owner where work is assigned back to the automation, Provenance.agent.who, and the author of a Task Note turn): rules and services the EMR itself runs on the state of work or of arriving data -- a referral waiting past a clinic's configured period, an action a report run was configured to take, an arriving result being matched to a chart. Its content is code and clinic configuration rather than authored clinical knowledge. References under this system are LOGICAL: Reference.identifier carries the name and Reference.type carries 'Device'; no Device resource need exist on the FHIR server. Reference.display SHOULD carry the human-readable name. Granularity is the rule or capability: the unit a clinician or auditor can recognize, never the run or the process that executed it. Third sibling of NamingSystem/nexus-harness-graph and NamingSystem/nexus-cds-rule; automation signs here rather than there because a consumer reads identifier.system for which KIND of producer acted, and asserting the decision-support rule registry issued an identifier it never saw is a false statement at exactly the point it is read. Unlike those two, one namespace serves all first-party automation: it is minted in a single repository under a single review process, so two capabilities choosing one name collide in review rather than in a FHIR store -- and if first-party automation is ever minted outside that repository, this namespace splits as the other two did. Values are opaque to consumers and MUST NOT be parsed.

Type Value Preferred
uri https://fhir.apps.health/NamingSystem/nexus-automation true