This
page
is
part
of
the
FHIR
Specification
(v4.0.1:
R4
-
Mixed
Normative
and
STU
)
in
it's
permanent
home
(it
will
always
be
available
at
this
URL).
(v4.2.0:
R5
Preview
#1).
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
Patient
Care
Work
Group
|
Maturity Level : 2 | Trial Use | Use Context : Any |
This
is
a
value
set
defined
at
http://www.hl7.org/Special/committees/patientcare/
.
Summary
| Defining URL: | http://hl7.org/fhir/ValueSet/care-plan-intent |
| Version: |
|
| Name: | CarePlanIntent |
| Title: | Care Plan Intent |
| Definition: |
Codes indicating the degree of authority/intentionality associated with a care plan. |
| Committee: |
Patient
Care
Work
Group
|
| OID: | 2.16.840.1.113883.4.642.3.150 (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:
http://hl7.org/fhir/request-intent
| Code | Display | |
| 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 a Practitioner. |
| option | Option | The request represents a component or option for a RequestGroup that establishes timing, conditionality and/or other constraints among a set of requests. Refer to [[[RequestGroup]]] for additional information on how this status is used. |
| directive | Directive | The request represents a legally binding instruction authored by a Patient or RelatedPerson. |
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 |