FHIR CI-Build

This is the Continuous Integration Build of FHIR (will be incorrect/inconsistent at times).
See the Directory of published versions

Example Task/example6 (Narrative)

Orders and Observations Work GroupMaturity Level: N/AStandards Status: InformativeCompartments: 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: Task

Resource Task "example6"

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: Fulfill the focal request (Task Codes#fulfill)

description: Create order for getting specimen, Set up inhouse testing, generate order for any sendouts and submit with specimen

focus: ServiceRequest/lipid: Lipid Panel Request

for: Patient/example: Peter James Chalmers "Peter CHALMERS"

encounter: Encounter/example: Example In-Patient Encounter

executionPeriod: 2016-10-31T08:25:05+10:00 --> 2016-10-31T18:45:05+10:00

authoredOn: 2016-10-31T08:25:05+10:00

lastModified: 2016-10-31T18:45:05+10:00

requester: Practitioner/example: Dr Adam Careful "Adam CAREFUL"

RequestedPerformers

-Reference
*PractitionerRole/f202

owner: Organization/1832473e-2fe0-452d-abe9-3cdb9879522f: Clinical Laboratory @ Acme Hospital "Clinical Lab"

Reasons

-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

Restrictions

-RepetitionsPeriod
*1?? --> 2016-11-02T09:45:05+10:00

output

type: DiagnosticReport generated ()

value: DiagnosticReport/lipids

output

type: collected specimen ()

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.