Release 4 FHIR CI-Build

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

Task-example2.xml

Example Task/example2 (XML)

Maturity Level : N/A
Responsible Owner: Orders and Observations Work Group Standards Status : Informative Compartments : Not linked to any defined compartments Group , Patient

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

Jump past Narrative

Example of an accepted, filler generated specimen collection subtask (id = "example2")

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


  <!--   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    -->
  
  (Details : {http://terminology.hl7.org/CodeSystem/task-performer-type code 'performer'
           = 'performer', given as 'Performer'})
    
    
    
  
  
    
    
    
  
  <!--     This Task is a child task of the submitted lipid panel requet
   -->
  
    
    
  
  
  
  
    
  
  
  
  
  
    
  
  
  
    
  
  <!--     who the task is for
   -->
  
    
    
  
  
    
    
  
  
  
    
  
  
  
  
  
      
      
  
  
    
      
      
      
    
    
  
  
  
    
    
  
  
    
    
      
    
  
  <!--   The expected output of this task is a Specimen and will generated once the task is completed
      -->

<!--  The expected output of this task is a Specimen and will generated once the task
 is completed   --><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"/>   <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>     <coding>       <system value="http://hl7.org/fhir/CodeSystem/task-code"/>       <code value="fulfill"/>     </coding>   </code>   <!--    Filler generated order using a fictive  servicerequest to complete the loop  -->  <focus>     <valueCanonical value="http://hl7.org/fhir/ServiceRequest/BloodDrawf201"/>   </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>   <requestedPerformer>     <concept>       <coding>         <system value="http://snomed.info/sct"/>         <code value="18850004"/>         <display value="Laboratory hematologist"/>       </coding>       <text value="Performer"/>     </concept>   </requestedPerformer>   <!--  assume at draw station  -->  <owner>     <reference value="Organization/1832473e-2fe0-452d-abe9-3cdb9879522f"/>     <display value="Clinical Laboratory @ Acme Hospital"/>   </owner> 


</

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.