FHIR Release 3 (STU)

This page is part of the FHIR Specification (v3.0.2: STU 3). 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-example5

Orders and Observations Work Group

Maturity Level: N/A

Ballot Status: Informative

Compartments: Not linked to any defined compartments

This is the narrative for the resource. See also the XML or JSON format. This example conforms to the profile Task.

Generated Narrative with Details

id: example5

identifier: 20170201-001 (OFFICIAL)

basedOn: General Wellness Careplan

groupIdentifier: G20170201-001 (OFFICIAL)

status: in-progress

businessStatus: specimen received, test in progress (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

context: Example In-Patient Encounter

executionPeriod: 31/10/2016 8:25:05 AM --> (ongoing)

authoredOn: 31/10/2016 8:25:05 AM

lastModified: 31/10/2016 4:45:05 PM

Requesters

-

Agent

OnBehalfOf

*

Dr Adam Careful

Good Health Clinic

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

owner: Clinical Laboratory @ Acme Hospital

reason: 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 procedurerequest 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

?? --> 02/11/2016 9:45:05 AM

Outputs

-

Type

Value[x]

*

collected specimen (Details )

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.