This page is part of the FHIR Specification (v1.8.0: STU 3 Draft). 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: R5 R4B R4 R3
This is a value set defined by the FHIR project.
Summary
Defining URL: | http://hl7.org/fhir/ValueSet/action-required-behavior |
Name: | PlanActionRequiredBehavior |
Definition: | Defines requiredness behavior for selecting an action or an action group |
Committee: | Clinical Decision Support Work Group |
OID: | 2.16.840.1.113883.4.642.2.990 (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 06 Dec 2016
This value set contains 3 concepts
Expansion based on http://hl7.org/fhir/action-required-behavior version 1.8.0
All codes from system http://hl7.org/fhir/action-required-behavior
Code | Display | Definition |
must | Must | An action with this behavior must be included in the actions processed by the end user; the end user may not choose not to include this action |
could | Could | An action with this behavior may be included in the set of actions processed by the end user |
must-unless-documented | Must Unless Documented | An action with this behavior must be included in the set of actions processed by the end user, unless the end user provides documentation as to why the action was not included |
See the full registry of value sets defined as part of FHIR.
Explanation of the columns that may appear on this page:
Level | A few code lists that FHIR defines are hierarchical - each code is assigned a level. In this scheme, some codes are under other codes, and imply that the code they are under also applies |
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) |
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 |