This page is part of the FHIR Specification (v4.1.0: Release 4B Ballot #1). 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 an accepted, filler generated specimen collection subtask (id = "example2")
<?xml version="1.0" encoding="UTF-8"?> <Task xmlns="http://hl7.org/fhir"> <!-- This is an example to demonstrate using task for actioning a filler generated servicerequest and to illustrate how to populate many of the task elements - this is the child task from task example1 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 with output Specimen => example 6 action lipid panel - completed with output Specimen and DiagnosticReport --> <id value="example2"/> <text> <status value="generated"/> <div xmlns="http://www.w3.org/1999/xhtml"><p> <b> Generated Narrative</b> </p> <p> <b> identifier</b> : id: 20170201-002 (OFFICIAL)</p> <p> <b> groupIdentifier</b> : id: G20170201-001 (OFFICIAL)</p> <p> <b> partOf</b> : <a> Lipid Panel. Generated Summary: id: 20170201-001 (OFFICIAL); id: G20170201-001 (OFFICIAL); status: in-progress; <span> waiting for specimen</span> ; intent: order; priority: routine; <span> Lipid Panel</span> ; description: Create order for getting specimen, Set up inhouse testing, generate order for any sendouts and submit with specimen; executionPeriod: 31 Oct. 2016, 9:25:05 am --> (ongoing); authoredOn: 31 Oct. 2016, 9:25:05 am; lastModified: 31 Oct. 2016, 10:45:05 am; <span> Performer</span> ; <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> ; 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 </a> </p> <p> <b> status</b> : accepted</p> <p> <b> businessStatus</b> : <span> waiting for patient</span> </p> <p> <b> intent</b> : filler-order</p> <p> <b> priority</b> : routine</p> <p> <b> code</b> : <span> Specimen Collection</span> </p> <p> <b> focus</b> : <span> BloodDraw ServiceRequest</span> </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:45:05 am --> (ongoing)</p> <p> <b> authoredOn</b> : 31 Oct. 2016, 9:45:05 am</p> <p> <b> lastModified</b> : 31 Oct. 2016, 10:45:05 am</p> <p> <b> requester</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> 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> <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> ?? --> 1 Nov. 2016, 10:45:05 am</td> </tr> </table> </div> </text> <identifier> <use value="official"/> <system value="http:/goodhealth.org/identifiers"/> <value value="20170201-002"/> </identifier> <groupIdentifier> <use value="official"/> <system value="http:/goodhealth.org/accession/identifiers"/> <value value="G20170201-001"/> </groupIdentifier> <!-- This Task is a child task of the submitted lipid panel requet --> <partOf> <reference value="Task/example1"/> <display value="Lipid Panel"/> </partOf> <status value="accepted"/> <!-- fictive business status populated for this example --> <businessStatus> <text value="waiting for patient"/> </businessStatus> <intent value="filler-order"/> <priority value="routine"/> <!-- fictive code and description elements populated for this example --> <code> <text value="Specimen Collection"/> </code> <!-- Filler generated order using a fictive servicerequest to complete the loop --> <focus> <display value="BloodDraw ServiceRequest"/> </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:45:05+10:00"/> </executionPeriod> <authoredOn value="2016-10-31T08:45:05+10:00"/> <lastModified value="2016-10-31T09:45:05+10:00"/> <!-- requester is filler --> <requester> <reference value="Organization/1832473e-2fe0-452d-abe9-3cdb9879522f"/> <display value="Clinical Laboratory @ Acme Hospital"/> </requester> <performerType> <coding> <system value="http://terminology.hl7.org/CodeSystem/task-performer-type"/> <code value="performer"/> <display value="Performer"/> </coding> <text value="Performer"/> </performerType> <!-- assume at draw station --> <owner> <reference value="Organization/1832473e-2fe0-452d-abe9-3cdb9879522f"/> <display value="Clinical Laboratory @ Acme Hospital"/> </owner> <restriction> <repetitions value="1"/> <period> <end value="2016-11-01T09:45:05+10:00"/> </period> </restriction> <!-- The expected output of this task is a Specimen and will generated once the task is completed --> </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.