Current Build


Orders and Observations Work GroupMaturity Level: N/ABallot 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 with Details

id: example1


identifier: 20170201-001 (OFFICIAL)

basedOn: General Wellness Careplan

groupIdentifier: G20170201-001 (OFFICIAL)

status: in-progress

businessStatus: waiting for specimen (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: Oct 31, 2016 8:25:05 AM --> (ongoing)

authoredOn: Oct 31, 2016 8:25:05 AM

lastModified: Oct 31, 2016 9:45:05 AM

requester: Dr Adam Careful

performerType: Performer (Details : { 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

relevantHistory: Author's Signature. Generated Summary: id: signature; recorded: Oct 31, 2016 8:25:05 AM;

Exception generating Narrative: Unknown Content who @ START_TAG seen ...<when value="2016-10-31T08:25:05+10:00"/>\n\t\t\t\t<who>... @8:10


Other examples that reference this example:

  • Task/Accepted Specimen Collection Task
  • Task/Completed Specimen Collection Task

    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.