Release 4B R5 Final QA

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

Using Codes Code Systems Value Sets Concept Maps Identifier Systems

4.3.14.60 4.3.2.61 Code System CodeSystem http://hl7.org/fhir/request-intent

Clinical Decision Support icon Work Group   Maturity Level : 3 Trial Use Use Context : Country: World, Not yet ready for Production use
This is a code system defined by the FHIR project. Committee:
Official URL : Title: http://hl7.org/fhir/request-intent RequestIntent Definition: Codes indicating the degree of authority/intentionality associated with a request. Version : 5.0.0-draft-final
draft as of 2023-03-01 Clinical Decision Support Computable Name : RequestIntent Work Group
OID: 2.16.840.1.113883.4.642.1.114 (for OID based terminology systems) Flags : Experimental, CaseSensitive, Complete. All codes ValueSet: RequestIntent Source Resource XML / JSON OID : 2.16.840.1.113883.4.642.4.114

This Code system is used in the following value sets:

  • ValueSet: Care Plan Intent (Codes indicating the degree of authority/intentionality associated with a care plan.)
  • ValueSet: TaskIntent Task Intent (Distinguishes whether the task is a proposal, plan or full order.)
  • ValueSet: Transport Intent (Distinguishes whether the transport is a proposal, plan or full order.)
  • ValueSet: RequestIntent (Codes indicating the degree of authority/intentionality associated with a request.)
    • ValueSet: Care Plan Intent
(Codes

4.3.2.61.1 Definition

Codes indicating the degree of authority/intentionality associated with a care plan.) request.

4.3.14.60.1 4.3.2.61.2 Content

This code system http://hl7.org/fhir/request-intent defines the following codes:

Lvl Code Display Definition Copy
1 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. btn   btn
1 plan Plan The request represents an intention to ensure something occurs without providing an authorization for others to act. btn   btn
1 directive Directive The request represents a legally binding instruction authored by a Patient or RelatedPerson. btn   btn
1 order Order The request represents a request/demand and authorization for action by a Practitioner. the requestor. btn   btn
2   original-order Original Order The request represents an original authorization for action. btn   btn
2   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. btn   btn
2   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. btn   btn
3     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. btn   btn
1 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. btn   btn

 

See the full registry of code systems 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. 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