This page is part of the FHIR Specification (v4.6.0: R5 Draft Ballot). 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
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
encounter: Example In-Patient Encounter. Generated Summary: status: in-progress; inpatient encounter
executionPeriod: 31 Oct. 2016, 9:25:05 am --> (ongoing)
authoredOn: 31 Oct. 2016, 9:25:05 am
lastModified: 31 Oct. 2016, 5:45:05 pm
requester: Dr Adam Careful. Generated Summary: id: 23; active; Adam Careful
performerType: Performer
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 | ?? --> 2 Nov. 2016, 10:45:05 am |
- | Type | Value[x] |
* | collected specimen | Generated Summary: id: 23234352356; id: X352356; status: available; Venous blood specimen; receivedTime: 4 Mar. 2011, 6:03:00 pm; Specimen is grossly lipemic |
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.