Requisition Version Reason Extension¶
| Canonical | ../StructureDefinition/nexus-requisition-version-reason |
|---|---|
| Status | draft · 1.26.0 |
| Base | Extension (constraint) |
| Context | ServiceRequest (element) |
| Source | FSH · JSON |
Why this version of a laboratory requisition was written -- saved, signed and printed, or printed without a signature.
Overview
It describes the write, not the resource. A resource's version history records who changed the requisition and when, but not what they did; against the same author and timestamp, a save and a print are very different events. Each stored version carries its own reason, describing the write that produced that version. Reading the current version tells you only how the requisition last changed -- read the version history for the sequence.
A code, not a sentence. The history is rendered in more than one language, so only the code is stored and the wording belongs with the surface that renders it.
Absence is ordinary. Versions written before this was recorded carry no reason. A consumer must render an absent reason neutrally and must not treat it as an error, or infer any particular one of the three.
Not a status, and not a signature. ServiceRequest.status is the state of the order. Whether a
version is signed is read from the requisition's signature extension, not inferred from
signed-printed here.
At most one per version.