This
page
is
part
of
the
Continuous
Integration
Build
of
FHIR
Specification
(v4.0.1:
R4
-
Mixed
Normative
and
STU
)
in
it's
permanent
home
(it
will
always
(will
be
available
incorrect/inconsistent
at
this
URL).
The
current
version
which
supercedes
this
version
is
5.0.0
.
For
a
full
list
of
available
versions,
see
times).
See
the
Directory
of
published
versions
.
Page
versions:
R5
R4B
R4
R3
| Responsible Owner: Orders and Observations Work Group | Standards Status : Informative |
Compartments
:
|
Raw XML ( canonical form + also see XML Format Specification )
Example of completed task for a lipid panel order (id = "example6")
<?xml version="1.0" encoding="UTF-8"?><!-- This is an example to demonstrate using task for actioning a servicerequest and to illustrate how to populate many of the task elements this is the first in a series of related Task examples: example1 action lipid panel -in progress =>. example2 specimen collection subtask -accepted => example4 specimen collection subtask - completed with output Specimen=>example 5 action lipid panel -in progress specimen collected with output Specimen => example 6 action lipid panel - completed with output Specimen and DiagnosticReport --> : Create order for getting specimen, Set up inhouse testing, generate order for any sendouts and submit with specimen(Details : {http://terminology.hl7.org/CodeSystem/task-performer-type code 'performer' = 'performer', given as 'Performer'}): The Task.reason should only be included if there is no Task.focus or if it differs from the reason indicated on the focus : This is an example to demonstrate using task for actioning a servicerequest and to illustrate how to populate many of the task elements - this is the parent task that will be broken into subtask to grab the specimen and a sendout lab test Create order for getting specimen, Set up inhouse testing, generate order for any sendouts and submit with specimen <!-- who the task is for --> <!-- populate the reason just to demonstrate it use in this example --> The Task.reason should only be included if there is no Task.focus or if it differs from the reason indicated on the focus This is an example to demonstrate using task for actioning a servicerequest and to illustrate how to populate many of the task elements - this is the parent task that will be broken into subtask to grab the specimen and a sendout lab test <!-- add the link to the signature on the task to show how this element is usedemonstrating in this example the relevant history element using a contained resource for the purpose of this example only typically would reference an external resource --> <!-- complete the request within 48 hrs --><Task xmlns="http://hl7.org/fhir"> <!-- This is an example to demonstrate using task for actioning a servicerequest and to illustrate how to populate many of the task elements this is the first in a series of related Task examples: example1 action lipid panel -in progress =>. example2 specimen collection subtask -accepted => example4 specimen collection subtask - completed with output Specimen=>example 5 action lipid panel -in progress specimen collected with output Specimen => example 6 action lipid panel - completed with output Specimen and DiagnosticReport --> <id value="example6"/> <identifier> <use value="official"/> <system value="http:/goodhealth.org/identifiers"/> <value value="20170201-001"/> </identifier> <basedOn> <display value="General Wellness Careplan"/> </basedOn> <groupIdentifier> <use value="official"/> <system value="http:/goodhealth.org/accession/identifiers"/> <value value="G20170201-001"/> </groupIdentifier> <status value="completed"/> <!-- fictive business status populated for this example --> <businessStatus> <text value="test completed and posted"/> </businessStatus> <intent value="order"/> <priority value="routine"/> <!-- fictive code and description elements populated for this example --> <code> <coding> <system value="http://hl7.org/fhir/CodeSystem/task-code"/> <code value="fulfill"/> </coding> </code> <description value="Create order for getting specimen, Set up inhouse testing, generate order for any sendouts and submit with specimen"/> <!-- Use the lipid servicerequest example --> <focus> <valueReference> <reference value="ServiceRequest/lipid"/> <display value="Lipid Panel Request"/> </valueReference> </focus> <!-- who the task is for --> <for> <reference value="Patient/example"/> <display value="Peter James Chalmers"/> </for> <encounter> <reference value="Encounter/example"/> <display value="Example In-Patient Encounter"/> </encounter> <!-- Lots of dates --> <executionPeriod> <start value="2016-10-31T08:25:05+10:00"/> <!-- added completion date --> <end value="2016-10-31T18:45:05+10:00"/> </executionPeriod> <authoredOn value="2016-10-31T08:25:05+10:00"/> <!-- updated last modified date to track task activity --> <lastModified value="2016-10-31T18:45:05+10:00"/> <requester> <reference value="Practitioner/example"/> <display value="Dr Adam Careful"/> </requester> <requestedPerformer> <reference> <reference value="PractitionerRole/f202"/> </reference> </requestedPerformer> <owner> <reference value="Organization/1832473e-2fe0-452d-abe9-3cdb9879522f"/> <display value="Clinical Laboratory @ Acme Hospital"/> </owner> <!-- populate the reason just to demonstrate it use in this example --> <reason> <concept> <text value="The Task.reason should only be included if there is no Task.focus or if it differs from the reason indicated on the focus"/> </concept> </reason> <note> <text value="This is an example to demonstrate using task for actioning a servicerequest and to illustrate how to populate many of the task elements - this is the parent task that will be broken into subtask to grab the specimen and a sendout lab test"/> </note> <!-- add the link to the signature on the task to show how this element is usedemonstrating in this example the relevant history element using a contained resource for the purpose of this example only typically would reference an external resource --> <!-- complete the request within 48 hrs --> <restriction> <repetitions value="1"/> <period> <end value="2016-11-02T09:45:05+10:00"/> </period> </restriction> <!-- The expected output of this task is a DiagnosticReport and Specimen --> <output> <type> <text value="DiagnosticReport generated"/> </type> <valueReference> <reference value="DiagnosticReport/lipids"/> </valueReference> </output> <output> <type> <text value="collected specimen"/> </type> <valueReference> <reference value="Specimen/101"/> </valueReference> </output> </ Task >
Usage note: every effort has been made to ensure that the examples are correct and useful, but they are not a normative part of the specification.
FHIR
®©
HL7.org
2011+.
FHIR
Release
4
(Technical
Correction
#1)
(v4.0.1)
R6
hl7.fhir.core#6.0.0-ballot3
generated
on
Fri,
Nov
1,
2019
09:37+1100.
QA
Page
7,
2025
19:00+0000.
Links:
Search
|
Version
History
|
Table
of
Contents
|
Credits
Glossary
|
QA
|
Compare
to
R3
R4
|
Compare
to
R5
|
Compare
to
Last
Ballot
|
|
Propose
a
change