NexusAutomationKey Naming system¶
Status: draft · 1.33.0 · JSON
Identifies the business key carried by resources first-party EMR automation writes on its own behalf, so that re-evaluating a rule updates the existing resource rather than creating a duplicate. Every value begins with the producing rule's own name, which is what keeps two rules apart inside this one key space. The value is derived from what the resource is ABOUT -- the referral being chased, the patient and gap being addressed -- and never from the run that produced it: a key containing a run id or a sweep timestamp defeats the purpose, because it changes on every execution. Nor does it carry the clinic configuration that decided the gap was open, which would mint a second Task the moment an administrator changed a setting. Patient-scoped keys MUST include the subject, since two patients can present the same gap; a key scoped to a resource belonging to exactly one patient already carries the subject transitively. Values are opaque to consumers and MUST NOT be parsed. Producers find prior work with a search on this identifier before writing, and resolve the Task they find when the gap it addresses no longer holds. This namespace is first-party automation's alone: the AI harness keys under NamingSystem/nexus-harness-key and a decision-support rule under NamingSystem/nexus-cds-key, because the three are parallel producers and a shared key space would let one producer's re-run find and overwrite another producer's task. Sibling of NamingSystem/nexus-automation, which names the actor rather than the work.
| Type | Value | Preferred |
|---|---|---|
| uri | https://fhir.apps.health/NamingSystem/nexus-automation-key |
true |