This
page
is
part
of
the
FHIR
Specification
(v4.3.0:
R4B
(v5.0.0:
R5
-
STU
).
The
This
is
the
current
published
version
which
supercedes
in
it's
permanent
home
(it
will
always
be
available
at
this
version
is
5.0.0
.
URL).
For
a
full
list
of
available
versions,
see
the
Directory
of
published
versions
.
Page
versions:
R5
R4B
R5
R4B
R4
Orders
and
Observations
Work
Group
|
Maturity
Level
:
|
Trial Use |
Use
Context
:
|
Official
URL
:
http://hl7.org/fhir/ValueSet/task-intent
|
|
|||
| draft as of 2020-12-28 |
|
|||
|
|
|
|||
This value set is used in the following places:
Distinguishes whether the task is a proposal, plan or full order.
This value set includes codes based on the following rules:
http://hl7.org/fhir/task-intent
http://hl7.org/fhir/request-intent
| Code | Display | Definition |
| proposal | Proposal | The request is a suggestion made by someone/something that does not have an intention to ensure it occurs and without providing an authorization to act. |
| plan | Plan | The request represents an intention to ensure something occurs without providing an authorization for others to act. |
| order | Order |
The
request
represents
a
request/demand
and
authorization
for
action
by
|
| original-order | Original Order | The request represents an original authorization for action. |
| reflex-order | Reflex Order | The request represents an automatically generated supplemental authorization for action based on a parent authorization together with initial results of the action taken against that parent authorization. |
| filler-order | Filler Order | The request represents the view of an authorization instantiated by a fulfilling system representing the details of the fulfiller's intention to act upon a submitted order. |
| instance-order | Instance Order | An order created in fulfillment of a broader order that represents the authorization for a single activity occurrence. E.g. The administration of a single dose of a drug. |
| option | Option |
The
request
represents
a
component
or
option
for
a
|
This
expansion
generated
28
May
2022
26
Mar
2023
This value set contains 9 concepts
Expansion based on:
| Code | System | Display | Definition |
| unknown | http://hl7.org/fhir/task-intent | Unknown |
The intent is not known. When dealing with Task, it's not always known (or relevant) how the task was initiated - i.e. whether it was proposed, planned, ordered or just done spontaneously. |
| proposal | http://hl7.org/fhir/request-intent | Proposal |
The request is a suggestion made by someone/something that does not have an intention to ensure it occurs and without providing an authorization to act. |
| plan | http://hl7.org/fhir/request-intent | Plan |
The request represents an intention to ensure something occurs without providing an authorization for others to act. |
| order | http://hl7.org/fhir/request-intent | Order |
The
request
represents
a
request/demand
and
authorization
for
action
by
|
| original-order | http://hl7.org/fhir/request-intent | Original Order |
The request represents an original authorization for action. |
| reflex-order | http://hl7.org/fhir/request-intent | Reflex Order |
The request represents an automatically generated supplemental authorization for action based on a parent authorization together with initial results of the action taken against that parent authorization. |
| filler-order | http://hl7.org/fhir/request-intent | Filler Order |
The request represents the view of an authorization instantiated by a fulfilling system representing the details of the fulfiller's intention to act upon a submitted order. |
| instance-order | http://hl7.org/fhir/request-intent | Instance Order |
An order created in fulfillment of a broader order that represents the authorization for a single activity occurrence. E.g. The administration of a single dose of a drug. |
| option | http://hl7.org/fhir/request-intent | Option |
The
request
represents
a
component
or
option
for
a
|
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 |