Release 5 FHIR CI-Build

This page is part of the Continuous Integration Build of FHIR Specification (v5.0.0: R5 - STU ). This is the current published version in it's permanent home (it will always (will be available incorrect/inconsistent at this URL). For a full list of available versions, see times).
See the Directory of published versions . Page versions: R5 R4B R4 R3

Example Task/example1 (XML)

Maturity Level : N/A
Responsible Owner: Orders and Observations Work Group Standards Status : Informative Compartments : Group , Patient

Raw XML ( canonical form + also see XML Format Specification )

Jump past Narrative

Example of in-progress/awaiting specimen task for a lipid panel order (id = "example1")

<?xml version="1.0" encoding="UTF-8"?>

      <!--   This is an example to demonstrate using task for actioning a servicerequest and

<!--  The expected output of this task is a DiagnosticRequest and will generated once
 the task is near completion   --><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    -->

   panel - completed with output DiagnosticReport   -->

  <id value="example1"/> 
  display: inline-block; background-color: #d9e0e7; padding: 6px; margin: 4px; border:
       1px solid #8da1b4; border-radius: 5px; line-height: 60%: Create order for getting specimen, Set up inhouse testing,  generate order for
         any sendouts and submit with specimen   who the task is for
 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
 Author's Signature (Details: urn:iso-astm:E1762-95:2013 code 1.2.840.10065.1.12.1.1
               = 'Author's Signature', stated as 'Author's Signature')
        <!--    using contained resource for the purpose of this example only typically this
     would be a separate independent resource    -->

  <!--   using contained resource for the purpose of this example only typically this
   would be a separate independent resource   -->
  <contained> 
    <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> 
    <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
   -->

  <!--    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> 
  <requestedPerformer> 
    <concept> 
      <coding> 
        <system value="http://snomed.info/sct"/> 
        <code value="18850004"/> 
        <display value="Laboratory hematologist"/> 
      </coding> 
      <text value="Performer"/> 
    </concept> 
  </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
   -->

  <!--    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

  <!--    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
   -->

  <!--    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.