Release 5 Preview #1

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

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 with Details

id: example6

identifier: 20170201-001 (OFFICIAL)

basedOn: General Wellness Careplan

groupIdentifier: G20170201-001 (OFFICIAL)

status: completed

businessStatus: test completed and posted (Details )

intent: order

priority: routine

code: Lipid Panel (Details )

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: 31 Oct. 2016, 8:25:05 am --> 31 Oct. 2016, 6:45:05 pm

authoredOn: 31 Oct. 2016, 8:25:05 am

lastModified: 31 Oct. 2016, 6:45:05 pm

requester: Dr Adam Careful

performerType: Performer (Details : {http://terminology.hl7.org/CodeSystem/task-performer-type code 'performer' = 'performer', given as 'Performer'})

owner: Clinical Laboratory @ Acme Hospital

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 (Details )

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

Restrictions

-

Repetitions

Period

*

1

?? --> 2 Nov. 2016, 9:45:05 am

output
type: DiagnosticReport generated (Details )
value: DiagnosticReport/lipids

output
type: collected specimen (Details )
value: 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.