NexusHarnessRun Naming system

Status: draft · 1.26.0 · JSON

Identifies the AI-harness run that produced a machine-written resource. On the wire it is the system of a Coding in meta.tag, with the run identifier in Coding.code -- carried on meta so that any plain FHIR read of the resource holds the lineage without first asking the harness. Values are OPAQUE run identifiers minted once per execution: there is no concept list and none is possible, which is why this is an identifier namespace rather than a terminology, and consumers MUST NOT parse a run id. Distinct from NamingSystem/nexus-harness-key, which identifies the WORK and must never contain a run id -- a key that changed on every execution would defeat the duplicate suppression it exists to provide -- and from NamingSystem/nexus-harness-graph, which identifies the ACTOR. Run identity belongs here instead, on meta, where it may change freely: a regenerated summary keeps its identifier and its resource and acquires a new run tag on the new version. A resource with no tag under this system is ordinary and conformant: treat the absence as 'not recorded', never as an error, and do not infer the graph tag from it or it from the graph tag. MIGRATION: Nexus EMR writes this system today as https://nexus.awaremd.com/summary-id/run-id (FHIR-377), an address this specification does not publish: it is live in stored meta.tag codings 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-harness-run	true
uri	https://nexus.awaremd.com/summary-id/run-id	false