This
page
is
part
of
the
FHIR
Specification
(v4.3.0:
R4B
(v5.0.0-draft-final:
Final
QA
Preview
for
R5
-
STU
see
ballot
notes
).
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
Clinical
Decision
Support
Work
Group
|
Maturity Level : 3 | Trial Use |
Use
Context
:
|
Official
URL
:
http://hl7.org/fhir/ValueSet/action-selection-behavior
|
|
|||
| draft as of 2020-12-28 |
|
|||
|
|
|
|||
This value set is used in the following places:
Defines selection behavior of a group.
http://hl7.org/fhir/action-selection-behavior
This
expansion
generated
28
May
2022
01
Mar
2023
This value set contains 6 concepts
Expansion
based
on
ActionSelectionBehavior
v4.3.0
Action
Selection
Behavior
v5.0.0-draft-final
(CodeSystem)
| Code | System | Display | Definition |
| any | http://hl7.org/fhir/action-selection-behavior | Any |
Any number of the actions in the group may be chosen, from zero to all. |
| all | http://hl7.org/fhir/action-selection-behavior | All |
All the actions in the group must be selected as a single unit. |
| all-or-none | http://hl7.org/fhir/action-selection-behavior | All Or None |
All the actions in the group are meant to be chosen as a single unit: either all must be selected by the end user, or none may be selected. |
| exactly-one | http://hl7.org/fhir/action-selection-behavior | Exactly One |
The end user must choose one and only one of the selectable actions in the group. The user SHALL NOT choose none of the actions in the group. |
| at-most-one | http://hl7.org/fhir/action-selection-behavior | At Most One |
The end user may choose zero or at most one of the actions in the group. |
| one-or-more | http://hl7.org/fhir/action-selection-behavior | One Or More |
The end user must choose a minimum of one, and as many additional as desired. |
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 |