Release 4 FHIR CI-Build

This page is part of the Continuous Integration Build of FHIR Specification (v4.0.1: R4 - Mixed Normative and STU ) in it's permanent home (it will always (will be available incorrect/inconsistent at this URL). The current version which supercedes this version is 5.0.0 . For a full list of available versions, see times).
See the Directory of published versions . Page versions: R5 R4B R4 R3

Task-example1

Example Task/example1 (Narrative)

Maturity Level : N/A
Responsible Owner: Orders and Observations Work Group Standards Status : Informative Compartments : Not linked to any defined compartments Group , 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 with Details Narrative: Task example1

id : example1 contained :

identifier : 20170201-001 (OFFICIAL) http:/goodhealth.org/identifiers /20170201-001 (use: official, )

basedOn : General Wellness Careplan

groupIdentifier : G20170201-001 (OFFICIAL) http:/goodhealth.org/accession/identifiers /G20170201-001 (use: official, )

status : in-progress In Progress

businessStatus : waiting for specimen (Details )

intent : order

priority : routine Routine

code : Lipid Panel (Details ) Fulfill the focal request

description :

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

Focus

- focus : Value[x]
* Lipid Panel Request

for : Peter James Chalmers

encounter : Example In-Patient Encounter

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

authoredOn : 31/10/2016 8:25:05 AM 2016-10-31T08:25:05+10:00

lastModified : 31/10/2016 9:45:05 AM 2016-10-31T09:45:05+10:00

requester : Dr Adam Careful

RequestedPerformers

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

owner : Clinical Laboratory @ Acme Hospital

Reasons

- reasonCode : 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 (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: 31/10/2016 8:25:05 AM; Signature

Restrictions

- Repetitions Period
* 1 ?? --> 02/11/2016 9:45:05 AM 2016-11-02T09:45:05+10:00

Generated Narrative: Provenance #signature

  Provenance for ServiceRequest Physiotherapy of chest (regime/therapy)

Other examples that reference this example: Summary

Task/Accepted Specimen Collection Task Task/Completed Specimen Collection Task
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.