This page is part of the FHIR Specification (v4.6.0: R5 Draft Ballot). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions . Page versions: R5 R4B R4 R3
Orders and Observations Work Group | Maturity Level: N/A | Standards Status: Informative | Compartments: Not linked to any defined compartments |
Raw XML (canonical form + also see XML Format Specification)
Example of in-progress/awaiting specimen task for a lipid panel order (id = "example1")
<?xml version="1.0" encoding="UTF-8"?> <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 parent task that will be broken into subtask to grab the specimen 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 => example 6 action lipid panel - completed with output DiagnosticReport --> <id value="example1"/> <text> <status value="generated"/> <div xmlns="http://www.w3.org/1999/xhtml"><p> <b> Generated Narrative</b> </p> <p> <b> identifier</b> : id: 20170201-001 (OFFICIAL)</p> <p> <b> basedOn</b> : <span> General Wellness Careplan</span> </p> <p> <b> groupIdentifier</b> : id: G20170201-001 (OFFICIAL)</p> <p> <b> status</b> : in-progress</p> <p> <b> businessStatus</b> : <span> waiting for specimen</span> </p> <p> <b> intent</b> : order</p> <p> <b> priority</b> : routine</p> <p> <b> code</b> : <span> Lipid Panel</span> </p> <p> <b> description</b> : Create order for getting specimen, Set up inhouse testing, generate order for any sendouts and submit with specimen</p> <p> <b> focus</b> : <a> Lipid Panel Request. Generated Summary: Placer: 2345234234234; status: active; intent: original-order; <span> Lipid Panel</span> ; occurrence: 3 May 2013, 9:16:00 am; patient is afraid of needles</a> </p> <p> <b> for</b> : <a> Peter James Chalmers. Generated Summary: Medical record number: 12345 (USUAL); active; Peter James Chalmers (OFFICIAL), Jim , Peter James Windsor (MAIDEN); , Phone: (03) 5555 6473, Phone: (03) 3410 5613, Phone: (03) 5555 8834; gender: male; birthDate: 1974-12-25; </a> </p> <p> <b> encounter</b> : <a> Example In-Patient Encounter. Generated Summary: status: in-progress; <span> inpatient encounter</span> </a> </p> <p> <b> executionPeriod</b> : 31 Oct. 2016, 9:25:05 am --> (ongoing)</p> <p> <b> authoredOn</b> : 31 Oct. 2016, 9:25:05 am</p> <p> <b> lastModified</b> : 31 Oct. 2016, 10:45:05 am</p> <p> <b> requester</b> : <a> Dr Adam Careful. Generated Summary: id: 23; active; Adam Careful </a> </p> <p> <b> performerType</b> : <span> Performer</span> </p> <p> <b> owner</b> : <a> Clinical Laboratory @ Acme Hospital. Generated Summary: id: ClinLab; name: Clinical Lab; Phone: +1 555 234 1234, contact@labs.acme.org</a> </p> <p> <b> reasonCode</b> : <span> The Task.reason should only be included if there is no Task.focus or if it differs from the reason indicated on the focus</span> </p> <p> <b> note</b> : 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 </p> <p> <b> relevantHistory</b> : <a> </a> </p> <blockquote> <p> <b> target</b> : <a> ServiceRequest/physiotherapy/_history/1</a> </p> <p> <b> recorded</b> : 31 Oct. 2016, 9:25:05 am</p> <h3> Agents</h3> <table> <tr> <td> -</td> <td> <b> Role</b> </td> <td> <b> Who</b> </td> </tr> <tr> <td> *</td> <td> <span> author (originator)</span> </td> <td> <a> Luigi Maas. Generated Summary: UZI-nummer: 12345678902 (OFFICIAL), BIG-nummer: 12345678902 (OFFICIAL); active; Luigi Maas(OFFICIAL); Phone: +31715269111; gender: male; birthDate: 1960-06-12</a> </td> </tr> </table> <h3> Signatures</h3> <table> <tr> <td> -</td> </tr> <tr> <td> *</td> </tr> </table> </blockquote> <h3> Restrictions</h3> <table> <tr> <td> -</td> <td> <b> Repetitions</b> </td> <td> <b> Period</b> </td> </tr> <tr> <td> *</td> <td> 1</td> <td> ?? --> 2 Nov. 2016, 10:45:05 am</td> </tr> </table> </div> </text> <contained> <!-- using contained resource for the purpose of this example only typically this would be a separate independent resource --> <Provenance> <id value="signature"/> <target> <reference value="ServiceRequest/physiotherapy/_history/1"/> </target> <recorded value="2016-10-31T08:25:05+10:00"/> <agent> <role> <coding> <system value="http://terminology.hl7.org/CodeSystem/v3-ParticipationType"/> <code value="AUT"/> </coding> </role> <who> <reference value="Practitioner/f202"/> <display value="Luigi Maas"/> </who> </agent> <signature> <type> <system value="urn:iso-astm:E1762-95:2013"/> <code value="1.2.840.10065.1.12.1.1"/> <display value="Author's Signature"/> </type> <when value="2016-10-31T08:25:05+10:00"/> <who> <reference value="Practitioner/example"/> <display value="Dr Adam Careful"/> </who> <targetFormat value="application/fhir+xml"/> <sigFormat value="application/signature+xml"/> <data value="dGhpcyBibG9iIGlzIHNuaXBwZWQ="/> </signature> </Provenance> </contained> <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="in-progress"/> <!-- fictive business status populated for this example --> <businessStatus> <text value="waiting for specimen"/> </businessStatus> <intent value="order"/> <priority value="routine"/> <!-- fictive code and description elements populated for this example --> <code> <text value="Lipid Panel"/> </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> <reference value="ServiceRequest/lipid"/> <display value="Lipid Panel Request"/> </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"/> </executionPeriod> <authoredOn value="2016-10-31T08:25:05+10:00"/> <lastModified value="2016-10-31T09:45:05+10:00"/> <requester> <reference value="Practitioner/example"/> <display value="Dr Adam Careful"/> </requester> <performerType> <coding> <system value="http://terminology.hl7.org/CodeSystem/task-performer-type"/> <code value="performer"/> <display value="Performer"/> </coding> <text value="Performer"/> </performerType> <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 --> <reasonCode> <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"/> </reasonCode> <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 --> <relevantHistory> <reference value="#signature"/> <display value="Author's Signature"/> </relevantHistory> <!-- 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 DiagnosticRequest and will generated once the task is near completion --> </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.