Release 4 5

This page is part of the FHIR Specification (v4.0.1: R4 (v5.0.0: R5 - Mixed Normative and STU ) ). This is the current published version in it's permanent home (it will always be available at this URL). 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

Using Codes Code Systems Value Sets Concept Maps Identifier Systems

4.4.1.623 4.4.1.745 Value Set ValueSet http://hl7.org/fhir/ValueSet/care-plan-intent

Patient Care icon Work Group   Maturity Level : 2 Trial Use Use Context : Any Country: World
This is a value set defined at http://www.hl7.org/Special/committees/patientcare/ Committee:
Official URL : Title: http://hl7.org/fhir/ValueSet/care-plan-intent Care Plan Intent Definition: Codes indicating the degree of authority/intentionality associated with a care plan. Version : 5.0.0
draft as of 2023-03-26 Patient Care Computable Name : CarePlanIntent Work Group
OID: Flags : 2.16.840.1.113883.4.642.3.150 (for OID based terminology systems) Source Resource XML / JSON : 2.16.840.1.113883.4.642.3.150

This value set is used in the following places:

This value set includes codes from Codes indicating the following code systems: degree of authority/intentionality associated with a care plan.


  • Include these codes as defined in 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 a Practitioner. the requestor.
    option Option The request represents a component or option for a RequestGroup RequestOrchestration that establishes timing, conditionality and/or other constraints among a set of requests. Refer to [[[RequestGroup]]] [[[RequestOrchestration]]] for additional information on how this status is used.
    directive Directive The request represents a legally binding instruction authored by a Patient or RelatedPerson.

 

This expansion generated 26 Mar 2023


This value set contains 5 concepts

Expansion based on RequestIntent v5.0.0 (CodeSystem)

Code System Display Definition
   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 the requestor.

   option http://hl7.org/fhir/request-intent Option

The request represents a component or option for a RequestOrchestration that establishes timing, conditionality and/or other constraints among a set of requests. Refer to RequestOrchestration for additional information on how this status is used.

   directive http://hl7.org/fhir/request-intent 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