FHIR Release 3 (STU) 5 Ballot

This page is part of the FHIR Specification (v3.0.2: STU (v5.0.0-ballot: R5 Ballot - see ballot notes 3). ). 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 R2

Content Detailed Descriptions Mappings XML JSON

Example Task/example6 (XML)

Extension: Data Absent Reason URL for this extension: http://hl7.org/fhir/StructureDefinition/data-absent-reason
FHIR Infrastructure Orders and Observations Work Group   Maturity Level : 1 N/A Standards Status : Informative Use Context Compartments : Any Not linked to any defined compartments
    Status: draft. Extension maintained by: Health Level Seven International (FHIR Infrastructure) Provides a reason why the expected value or elements in the element that is extended are missing. Context of Use: Use on data type: * usage info: insert a list of places where this extension is used Extension Content
  • Summary Narrative
    • Full Structure
  • XML
  • JSON
  • All TTL

Summary Name Flags Card. Type Description & Constraints extension 0..1 code URL = http://hl7.org/fhir/StructureDefinition/data-absent-reason Data Absent Reason: Provides a reason why the expected value or elements in the element that is extended are missing. Binding: DataAbsentReason Raw XML ( required canonical form ) Use on data type: * Documentation for this format + also see XML Format Specification Full Structure )

Name Flags Card. Type Description & Constraints extension 0..1 Extension URL = http://hl7.org/fhir/StructureDefinition/data-absent-reason Data Absent Reason: Provides a reason why the expected value or elements in the element that is extended are missing. Use on data type: * url 1..1 uri "http://hl7.org/fhir/StructureDefinition/data-absent-reason" valueCode 0..1

code Jump past Narrative Value

Example of extension Binding: DataAbsentReason ( required ) Documentation completed task for this format XML Template a lipid panel order (id = "example6")

<!-- Data Absent Reason --> 
<?xml version="1.0" encoding="UTF-8"?>


< xmlns="http://hl7.org/fhir"
     url="" >
  <!-- from Element: 
 <
</extension>
JSON
Template
  
{ // 
  // from Element: 
    "
    ],
    " 
    "
  }
Summary

<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"/> 
  <text> <status value="generated"/> <div xmlns="http://www.w3.org/1999/xhtml"><p> <b> Generated Narrative: Task</b> <a name="example6"> </a> </p> <div style="display: inline-block; background-color: #d9e0e7; padding: 6px; margin: 4px; border:

       1px solid #8da1b4; border-radius: 5px; line-height: 60%"><p style="margin-bottom: 0px">Resource Task &quot;example6&quot; </p> </div> <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 title=" fictive business status populated for this example  ">test completed and posted <span style="background: LightGoldenRodYellow; margin: 4px; border: 1px solid khaki"> ()</span> </span> </p> <p> <b> intent</b> : order</p> <p> <b> priority</b> : routine</p> <p> <b> code</b> : <span title=" fictive code and description elements populated for this example  ">Fulfill the focal request <span style="background: LightGoldenRodYellow; margin: 4px; border: 1px solid khaki"> (<a href="codesystem-task-code.html">Task Codes</a> #fulfill)</span> </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> : <span title="   Use the lipid servicerequest example  "><a href="servicerequest-example-lipid.html">ServiceRequest/lipid: Lipid Panel Request</a> </span> </p> <p> <b> for</b> : <span title="   who the task is for
 "><a href="patient-example.html">Patient/example: Peter James Chalmers</a>  &quot;Peter CHALMERS&quot;</span> </p> <p> <b> encounter</b> : <a href="encounter-example.html">Encounter/example: Example In-Patient Encounter</a> </p> <p> <b> executionPeriod</b> : <span title="   Lots of dates  ">2016-10-31T08:25:05+10:00 --&gt; 2016-10-31T18:45:05+10:00</span> </p> <p> <b> authoredOn</b> : 2016-10-31T08:25:05+10:00</p> <p> <b> lastModified</b> : <span title="   updated last modified date to track task activity ">2016-10-31T18:45:05+10:00</span> </p> <p> <b> requester</b> : <a href="practitioner-example.html">Practitioner/example: Dr Adam Careful</a>  &quot;Adam CAREFUL&quot;</p> <h3> RequestedPerformers</h3> <table class="grid"><tr> <td> -</td> <td> <b> Reference</b> </td> </tr> <tr> <td> *</td> <td> <a href="broken-link.html">PractitionerRole/f202</a> </td> </tr> </table> <p> <b> owner</b> : <a href="organization-example-lab.html">Organization/1832473e-2fe0-452d-abe9-3cdb9879522f: Clinical Laboratory @ Acme Hospital</a>  &quot;Clinical Lab&quot;</p> <h3> Reasons</h3> <table class="grid"><tr> <td> -</td> <td> <b> Concept</b> </td> </tr> <tr> <td> *</td> <td> 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 style="background: LightGoldenRodYellow; margin: 4px; border: 1px solid khaki"> ()</span> </td> </tr> </table> <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> <h3> Restrictions</h3> <table class="grid"><tr> <td> -</td> <td> <b> Repetitions</b> </td> <td> <b> Period</b> </td> </tr> <tr> <td> *</td> <td> 1</td> <td> ?? --&gt; 2016-11-02T09:45:05+10:00</td> </tr> </table> <blockquote> <p> <b> output</b> </p> <p> <b> type</b> : DiagnosticReport generated <span style="background: LightGoldenRodYellow; margin: 4px; border: 1px solid khaki"> ()</span> </p> <p> <b> value</b> : <a href="bundle-lipids.html">DiagnosticReport/lipids</a> </p> </blockquote> <blockquote> <p> <b> output</b> </p> <p> <b> type</b> : collected specimen <span style="background: LightGoldenRodYellow; margin: 4px; border: 1px solid khaki"> ()</span> </p> <p> <b> value</b> : <a href="specimen-example.html">Specimen/101</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> 
    <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> 
    <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> 
  <requestedPerformer> 
    <reference> 
      <reference value="PractitionerRole/f202"/> 
    </reference> 
  </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

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

   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> 

Name
Flags
Card.
Type
Description
&
Constraints
extension
0..1
code


</

Task


URL
=
http://hl7.org/fhir/StructureDefinition/data-absent-reason
Data
Absent
Reason:
Provides
a
reason
why
the
expected
value
or
elements
in
the
element
that
is
extended
are
missing.
Binding:

>


DataAbsentReason
(
required
)
Use
on
data
type:
*
Documentation
for
this
format

Full Structure Name Flags Card. Type Description & Constraints extension 0..1 Extension URL = http://hl7.org/fhir/StructureDefinition/data-absent-reason Data Absent Reason: Provides a reason why the expected value or elements in the element Usage note: every effort has been made to ensure that is extended the examples are missing. Use on data type: * url 1..1 uri "http://hl7.org/fhir/StructureDefinition/data-absent-reason" valueCode 0..1 code Value correct and useful, but they are not a normative part of extension Binding: DataAbsentReason ( required ) Documentation for this format XML Template <!-- Data Absent Reason --> < xmlns="http://hl7.org/fhir" url="" > <!-- from Element: < </extension> JSON Template the specification.

{ // // from Element: " ], " " }
  Constraints ele-1 : All FHIR elements must have a @value or children (xpath: @value|f:*|h:div ) ext-1 : Must have either extensions or value[x], not both (xpath: exists(f:extension)!=exists(f:*[starts-with(local-name(.), 'value')]) )