This page is part of the FHIR Specification (v4.3.0: R4B - STU). 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
Orders and Observations Work Group | Maturity Level: N/A | Standards Status: Informative | Compartments: Not linked to any defined compartments |
This is the narrative for the resource. See also the XML, JSON or Turtle format. This example conforms to the profile Task.
Generated Narrative
Resource "example5"
identifier: id: 20170201-001 (OFFICIAL)
basedOn: : General Wellness Careplan
groupIdentifier: id: G20170201-001 (OFFICIAL)
status: in-progress
businessStatus: specimen received, test in progress ()
intent: order
priority: routine
code: Lipid Panel ()
description: Create order for getting specimen, Set up inhouse testing, generate order for any sendouts and submit with specimen
focus: ServiceRequest/lipid: Lipid Panel Request
for: Patient/example: Peter James Chalmers "Peter CHALMERS"
encounter: Encounter/example: Example In-Patient Encounter
executionPeriod: 2016-10-31T08:25:05+10:00 --> (ongoing)
authoredOn: 2016-10-31T08:25:05+10:00
lastModified: 2016-10-31T16:45:05+10:00
requester: Practitioner/example: Dr Adam Careful "Adam CAREFUL"
performerType: Performer (task-performer-type#performer)
owner: Organization/1832473e-2fe0-452d-abe9-3cdb9879522f: Clinical Laboratory @ Acme Hospital "Clinical Lab"
reasonCode: 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: 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
- | Repetitions | Period |
* | 1 | ?? --> 2016-11-02T09:45:05+10:00 |
- | Type | Value[x] |
* | collected specimen () | 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.