Release 4 5 Preview #3
This page is part of the FHIR Specification (v4.0.1: R4 - Mixed Normative and STU ). This is the current published version in it's permanent home (it will always be available at this URL). For a full list of available versions, see the Directory of published versions

Task-example6.xml

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 )

Jump past Narrative

Example of completed task for a lipid panel order (id = "example6")

<?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 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"/> 
  : 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

  <text> <status value="generated"/> <div xmlns="http://www.w3.org/1999/xhtml"><p> <b> Generated Narrative</b> </p> <p> <b> id</b> : example6</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> : completed</p> <p> <b> businessStatus</b> : <span> test completed and posted</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: id: lipid; Placer: 2345234234234; status: active;
           intent: original-order; <span> Lipid Panel</span> ; occurrence: May 2, 2013 4:16:00 PM; <span> Fam hx-ischem heart dis</span> ; patient is afraid of needles</a> </p> <p> <b> for</b> : <a> Peter James Chalmers. Generated Summary: id: example; Medical record number: 12345 (USUAL);
           active; Peter James Chalmers (OFFICIAL), Jim , Peter James Windsor (MAIDEN); -unknown-(HOME),
           ph: (03) 5555 6473(WORK), ph: (03) 3410 5613(MOBILE), ph: (03) 5555 8834(OLD); gender:
           male; birthDate: 1974-12-25; </a> </p> <p> <b> encounter</b> : <a> Example In-Patient Encounter. Generated Summary: id: example; status: in-progress; <span> inpatient encounter</span> </a> </p> <p> <b> executionPeriod</b> : Oct 31, 2016 8:25:05 AM --&gt; Oct 31, 2016 6:45:05 PM</p> <p> <b> authoredOn</b> : Oct 31, 2016 8:25:05 AM</p> <p> <b> lastModified</b> : Oct 31, 2016 6:45:05 PM</p> <p> <b> requester</b> : <a> Dr Adam Careful. Generated Summary: id: example; 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: 1832473e-2fe0-452d-abe9-3cdb9879522f;
           id: ClinLab; name: Clinical Lab; ph: +1 555 234 1234(WORK), contact@labs.acme.org(WORK)</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 

         into subtask to grab the specimen and a sendout lab test </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> ?? --&gt; Nov 2, 2016 9:45:05 AM</td> </tr> </table> <blockquote> <p> <b> output</b> </p> <p> <b> type</b> : <span> DiagnosticReport generated</span> </p> <p> <b> value</b> : <a> Generated Summary: id: lipids</a> </p> </blockquote> <blockquote> <p> <b> output</b> </p> <p> <b> type</b> : <span> collected specimen</span> </p> <p> <b> value</b> : <a> Generated Summary: id: 101; id: 23234352356; id: X352356; status: available; <span> Venous blood specimen</span> ; receivedTime: Mar 4, 2011 7:03:00 AM; Specimen is grossly lipemic</a> </p> </blockquote> </div> </text> <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> 
    <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"/> 
    <!--   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> 
  <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
   -->
  <!--     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.