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: completed
businessStatus: test completed and posted
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: Oct 30, 2016 10:25:05 PM --> Oct 31, 2016 8:45:05 AM
authoredOn: Oct 30, 2016 10:25:05 PM
lastModified: Oct 31, 2016 8:45:05 AM
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 | ?? --> Nov 1, 2016 11:45:05 PM |
output
type: DiagnosticReport generated
value: Generated Summary:
output
type: collected specimen
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.