Release 4B 5 Ballot

This page is part of the FHIR Specification (v4.3.0: R4B (v5.0.0-ballot: R5 Ballot - 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.4.1.345 4.4.1.204 Value Set ValueSet http://hl7.org/fhir/ValueSet/request-intent

FHIR Infrastructure icon Work Group   Maturity Level : 3 Trial Use Use Context : Not yet ready for Production use, Not yet ready for Production use

This is a value set defined by the FHIR project.

Summary

Defining URL: http://hl7.org/fhir/ValueSet/request-intent
Version: 4.3.0 5.0.0-ballot
Name: RequestIntent
Title: RequestIntent
Status: draft
Definition:

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

Committee: FHIR Infrastructure icon Work Group
OID: 2.16.840.1.113883.4.642.3.113 (for OID based terminology systems)
Source Resource Flags: XML / JSON Experimental, Immutable

This value set is used in the following places:

4.4.1.345.1 4.4.1.204.1 Content Logical Definition

 

4.4.1.345.2 4.4.1.204.2 Expansion

This expansion generated 28 May 10 Sep 2022

This value set contains 9 concepts

Expansion based on RequestIntent v4.3.0 v5.0.0-ballot (CodeSystem)

All codes in this table are from the system http://hl7.org/fhir/request-intent
Level Code System Display Definition
1    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.

1    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.

1    directive http://hl7.org/fhir/request-intent Directive

The request represents a legally binding instruction authored by a Patient or RelatedPerson.

1    order http://hl7.org/fhir/request-intent Order

The request represents a request/demand and authorization for action by a Practitioner.

2      original-order http://hl7.org/fhir/request-intent Original Order

The request represents an original authorization for action.

2      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.

2      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.

3        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.

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

 

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