Why this version of a laboratory requisition was written -- saved, signed and printed, or printed
without a signature.
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.
May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Source of the definition for the extension code - a logical name or a URL.
Comments
The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension.
Why this version was written: saved | signed-printed | printed-unsigned
Definition
Which exit produced this version of the requisition. One of three codes:
- saved -- the requisition was saved without being printed.
- signed-printed -- the requisition was signed and printed.
- printed-unsigned -- the requisition was printed without a signature.
This element is not bound to a value set. A consumer must treat any other value the same way it
treats an absent one: render the version neutrally rather than failing or guessing, because a value
outside the three says nothing this guide defines.