This page is part of the FHIR Specification (v0.4.0: DSTU 2 Draft). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions
This is an example form generated from the questionnaire. See also the XML or JSON format.
This is an example form generated from the questionnaire. See also the XML or JSON format
Logical id of this artefact |
Metadata about the resource
A set of rules under which this content was created |
language |
Text summary of the resource, for human interpretation
Contained, inline Resources
Who and/or what test is about
type |
Patient |
|
Group |
|
Location |
|
Device |
|
Who ordered the test |
|
Identifiers assigned to this order
label: | |
system: | |
value: |
The encounter that this diagnostic order is associated with |
|
Explanation/Justification for test |
Additional clinical information
type |
Observation |
|
Condition |
|
DocumentReference |
|
If the whole order relates to specific specimens |
|
status |
priority |
This is not the same as an audit trail - it is a view of the important things that happened in the past. Typically, there would only be one entry for any given status, and systems may not record all the status events.
xml:id (or equivalent in JSON) |
status |
More information about the event and its context
code: | |
text: |
The date at which the event happened |
Who recorded or did this
type |
Practitioner |
|
Device |
|
There would always be at least one item in normal usage, but this is optional so that a workflow can quote order details without having to list the items.
xml:id (or equivalent in JSON) |
Code to indicate the item (test or panel) being ordered
code: | |
text: |
If this item relates to specific specimens |
|
Location of requested test (if applicable)
type |
CodeableConcept
code: | |
text: |
BodySite |
|
status |