Release 5 Preview #3

This page is part of the FHIR Specification (v4.5.0: R5 Preview #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

Task-example6.json

Orders and Observations Work GroupMaturity Level: N/AStandards Status: InformativeCompartments: Not linked to any defined compartments

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

Example of completed task for a lipid panel order

{
  "resourceType": "Task",
  "id": "example6",
  "text": {
    "status": "generated",
    "div": "<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: 03/05/2013 9:16:00 AM; <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>: 31/10/2016 9:25:05 AM --&gt; 31/10/2016 7:45:05 PM</p><p><b>authoredOn</b>: 31/10/2016 9:25:05 AM</p><p><b>lastModified</b>: 31/10/2016 7: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 </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; 02/11/2016 10: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: 04/03/2011 6:03:00 PM; Specimen is grossly lipemic</a></p></blockquote></div>"
  },
  "identifier": [
    {
      "use": "official",
      "system": "http:/goodhealth.org/identifiers",
      "value": "20170201-001"
    }
  ],
  "basedOn": [
    {
      "display": "General Wellness Careplan"
    }
  ],
  "groupIdentifier": {
    "use": "official",
    "system": "http:/goodhealth.org/accession/identifiers",
    "value": "G20170201-001"
  },
  "status": "completed",
  "businessStatus": {
    "text": "test completed and posted"
  },
  "intent": "order",
  "priority": "routine",
  "code": {
    "text": "Lipid Panel"
  },
  "description": "Create order for getting specimen, Set up inhouse testing,  generate order for any sendouts and submit with specimen",
  "focus": {
    "reference": "ServiceRequest/lipid",
    "display": "Lipid Panel Request"
  },
  "for": {
    "reference": "Patient/example",
    "display": "Peter James Chalmers"
  },
  "encounter": {
    "reference": "Encounter/example",
    "display": "Example In-Patient Encounter"
  },
  "executionPeriod": {
    "start": "2016-10-31T08:25:05+10:00",
    "end": "2016-10-31T18:45:05+10:00"
  },
  "authoredOn": "2016-10-31T08:25:05+10:00",
  "lastModified": "2016-10-31T18:45:05+10:00",
  "requester": {
    "reference": "Practitioner/example",
    "display": "Dr Adam Careful"
  },
  "performerType": [
    {
      "coding": [
        {
          "system": "http://terminology.hl7.org/CodeSystem/task-performer-type",
          "code": "performer",
          "display": "Performer"
        }
      ],
      "text": "Performer"
    }
  ],
  "owner": {
    "reference": "Organization/1832473e-2fe0-452d-abe9-3cdb9879522f",
    "display": "Clinical Laboratory @ Acme Hospital"
  },
  "reasonCode": {
    "text": "The Task.reason should only be included if there is no Task.focus or if it differs from the reason indicated on the focus"
  },
  "note": [
    {
      "text": "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 "
    }
  ],
  "restriction": {
    "repetitions": 1,
    "period": {
      "end": "2016-11-02T09:45:05+10:00"
    }
  },
  "output": [
    {
      "type": {
        "text": "DiagnosticReport generated"
      },
      "valueReference": {
        "reference": "DiagnosticReport/lipids"
      }
    },
    {
      "type": {
        "text": "collected specimen"
      },
      "valueReference": {
        "reference": "Specimen/101"
      }
    }
  ]
}

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.