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 . Page versions: R4 R3
Clinical Decision Support Work Group | Maturity Level: 1 | Draft | Use Context: Not Intended for Production use |
This is a value set defined by the FHIR project.
Summary
Defining URL: | http://hl7.org/fhir/ValueSet/action-participant-role |
Version: | 3.5.0 |
Name: | ActionParticipantRole |
Title: | Action participant role |
Definition: | Either a practitioner role or a relationship type. |
Committee: | Clinical Decision Support Work Group |
OID: | 2.16.840.1.113883.4.642.3.796 (for OID based terminology systems) |
Source Resource | XML / 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 0 concepts
Expansion based on http://terminology.hl7.org/CodeSystem/v3-RoleCode version 2018-08-12, http://terminology.hl7.org/CodeSystem/v2-0131 version 2.9, http://hl7.org/fhir/ValueSet/relatedperson-relationshiptype version 3.5.0, http://terminology.hl7.org/CodeSystem/practitioner-role version 3.5.0, http://hl7.org/fhir/ValueSet/practitioner-role version 3.5.0
Code | System | Display |
See the full registry of value sets defined as part of FHIR.
Explanation of the columns that may appear on this page:
Lvl | A 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 |
Source | The source of the definition of the code (when the value set draws in codes defined elsewhere) |
Code | The code (used as the code in the resource instance). If the code is in italics, this indicates that the code is not selectable ('Abstract') |
Display | The 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 |
Definition | An explanation of the meaning of the concept |
Comments | Additional notes about how to use the code |