NexusEmrPreventionResult Naming system

Status: draft · 1.26.0 · JSON

Identifies the screening-result values recorded by the Nexus EMR prevention form. A recorded result is written as a coding on the screening Observation's valueCodeableConcept, beside a text carrying the same label, and this is that coding's system. NOTE THE ELEMENT: unlike its two siblings for administration site and route, which ride Immunization, this system rides Observation.value -- the three are one family because the prevention panel writes all three, not because they share an element. Codes are not enumerated here; the values recorded today are normal, abnormal and other, with the coding's display and the concept's text carrying 'Normal', 'Abnormal' and 'Other'. PENDING IS NOT A VALUE UNDER THIS SYSTEM: a pending result writes no value[x] at all and sets dataAbsentReason to temp-unknown instead, because a pending result is a missing value rather than a recorded one, and because result availability is independent of the prevention's own status. A reader must not expect to find 'pending' here. For normal and abnormal a governed interpretation travels beside the value -- the v3 ObservationInterpretation code N or A on Observation.interpretation -- and other writes none; prefer the interpretation where it is present, and read this system to know which recorded value produced it. The writer clears every value[x] variant, the interpretation and dataAbsentReason before writing, so a value and an absence reason are mutually exclusive on a stored Observation. EMR-LOCAL: this system implies no external governance, and consumers should treat values under it as local/raw codes per the raw-code pattern; no standard terminology slicing is claimed by the profiles today. The URI is stable and is pinned in stored Coding.system values.

Type	Value	Preferred
uri	../NamingSystem/nexus-emr-prevention-result	true