This is the Continuous Integration Build of FHIR (will be incorrect/inconsistent at times).
See the Directory of published versions
Orders and Observations Work Group | Maturity Level: N/A | Standards Status: Informative | Compartments: Patient |
This is the narrative for the resource. See also the XML, JSON or Turtle format. This example conforms to the profile Task.
Generated Narrative: Task example1
identifier: http:/goodhealth.org/identifiers
/20170201-001 (use: official, )
basedOn: General Wellness Careplan
groupIdentifier: http:/goodhealth.org/accession/identifiers
/G20170201-001 (use: official, )
status: in-progress
businessStatus: waiting for specimen
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: Lipid Panel Request
for: Peter James Chalmers
encounter: Example In-Patient Encounter
executionPeriod: 2016-10-31T08:25:05+10:00 --> (ongoing)
authoredOn: 2016-10-31T08:25:05+10:00
lastModified: 2016-10-31T09:45:05+10:00
requester: Dr Adam Careful
Concept |
Performer |
owner: Clinical Laboratory @ Acme Hospital
Concept |
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
relevantHistory: Author's Signature
Repetitions | Period |
1 | ?? --> 2016-11-02T09:45:05+10:00 |
Generated Narrative: Provenance #signature
Provenance for ServiceRequest Physiotherapy of chest (regime/therapy)
Summary
Recorded 2016-10-31T08:25:05+10:00 Agents
Role who Luigi Maas
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.