ReportingRun Naming system

Status: draft · 1.26.0 · JSON

Identifies a report run: one evaluation of one report definition at one anchor, producing one patient membership. It appears on Bundle.identifier of an identified reporting extract -- a collection Bundle of patient stubs handed to a requester as a file rather than stored on a FHIR server -- so it is not a searchable identifier but the way a recipient says which run a file is of, and recognizes two files as the same run. It names the RUN, not the export event: the export event is kept out of the bytes deliberately, so that two exports of one run at one anchor are byte-identical and a recipient can verify a file against a checksum without the export it arrived by. Values are opaque, MUST NOT be parsed, do not resolve to anything fetchable, and do not yield the report definition (an edited definition is a new version, and a run names the version it executed). It names an analytic run and nothing about any individual in the membership, so it belongs on the artefact and never on a chart resource. MIGRATION: Nexus EMR writes this system today as https://well.company/reporting/export (tracked as FHIR-381), an address this specification does not publish. It is live in issued extracts and in code, and is under migration to the URI declared here. Write the URI declared here; expect both until the migration completes. That same pre-migration address is also written as the system of the extract's meta.tag codings, which is a second artifact under one address; that half is published as the Reporting Export Stamp extension, StructureDefinition/reporting-export-stamp, which carries the stamp's fields as typed values on Bundle.meta.

Type	Value	Preferred
uri	../NamingSystem/reporting-run	true
uri	https://well.company/reporting/export	false