R4 Ballot #2 (Mixed Normative/Trial use)

This page is part of the FHIR Specification (v3.5.0: R4 Ballot #2). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions

4.4.1.14 Value Set http://hl7.org/fhir/ValueSet/task-performer-type

Orders and Observations Work Group Maturity Level: 0Informative Use Context: Any

This is a value set defined by the FHIR project.

Summary

Defining URL:http://hl7.org/fhir/ValueSet/task-performer-type
Version:3.5.0
Name:TaskPerformerType
Title:TaskPerformerType
Definition:

The type(s) of task performers allowed.

Committee:Orders and Observations Work Group
OID:2.16.840.1.113883.4.642.3.788 (for OID based terminology systems)
Source ResourceXML / JSON

This value set is used in the following places:


This value set includes codes from the following code systems:

 

This expansion generated 19 Aug 2018


This value set contains 8 concepts

Expansion based on http://terminology.hl7.org/CodeSystem/task-performer-type version 3.5.0

All codes from system http://terminology.hl7.org/CodeSystem/task-performer-type

LvlCodeDisplayDefinition
0requesterRequesterA workflow participant that requests services.
0dispatcherDispatcherA workflow participant that dispatches services (assigns another task to a participant).
1  schedulerSchedulerA workflow participant that schedules (dispatches and sets the time or date for performance of) services.
0performerPerformerA workflow participant that performs services.
0monitorMonitorA workflow participant that monitors task activity.
0managerManagerA workflow participant that manages task activity.
0acquirerAcquirerA workflow participant that acquires resources (specimens, images, etc.) necessary to perform the task.
0reviewerReviewerA workflow participant that reviews task inputs or outputs.

 

See the full registry of value sets defined as part of FHIR.


Explanation of the columns that may appear on this page:

LvlA few code lists that FHIR defines are hierarchical - each code is assigned a level. For value sets, levels are mostly used to organize codes for user convenience, but may follow code system hierarchy - see Code System for further information
SourceThe source of the definition of the code (when the value set draws in codes defined elsewhere)
CodeThe code (used as the code in the resource instance). If the code is in italics, this indicates that the code is not selectable ('Abstract')
DisplayThe display (used in the display element of a Coding). If there is no display, implementers should not simply display the code, but map the concept into their application
DefinitionAn explanation of the meaning of the concept
CommentsAdditional notes about how to use the code