FHIR Release 3 (STU) Current Build
This page is part of FHIR STU 3 (v3.0.1) in it's permanent home (it will always be available at this URL). It has been superceded by R4 . For a full list of available versions, see the Directory of published versions .

4.2.12.105 4.3.14.228 Code System http://hl7.org/fhir/request-intent

Vocabulary Clinical Decision Support Work Group   Maturity Level : 3 2 Informative Trial Use Use Context : Any

This is a code system defined by the FHIR project.

Summary

Defining URL: http://hl7.org/fhir/request-intent
Version: 4.1.0
Name: RequestIntent
Title: RequestIntent
Definition:

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

Committee: FHIR Infrastructure Clinical Decision Support Work Group
OID: 2.16.840.1.113883.4.642.1.105 2.16.840.1.113883.4.642.1.114 (for OID based terminology systems)
Source Resource XML / JSON

This Code system is used in the following value sets:

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

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

This code system http://hl7.org/fhir/request-intent defines the following codes:
Lvl Code Display Definition
1 proposal Proposal The request is a suggestion made by someone/something that doesn't does not have an intention to ensure it occurs and without providing an authorization to act act.
1 plan Plan The request represents an intension intention to ensure something occurs without providing an authorization for others to act act.
1 directive Directive The request represents a legally binding instruction authored by a Patient or RelatedPerson.
1 order Order The request represents a request/demand and authorization for action by a Practitioner.
2   original-order Original Order The request represents an original authorization for action action.
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 authorization.
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 order.
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.
1 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 used.

 

See the full registry of value sets 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. In this scheme, some codes are under other codes, and imply that the code they are under also applies 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