Release 4 R6 Ballot (1st Full Ballot)

This page is part of the FHIR Specification (v4.0.1: R4 - Mixed Normative and STU v6.0.0-ballot4: Release 6 Ballot (1st Full Ballot) (see Ballot Notes ) 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 for published versions icon . Page versions: R5 R4B R4

Using Codes Code Systems Value Sets Concept Maps Identifier Systems

4.4.1.150 4.4.1.180 Value Set ValueSet http://hl7.org/fhir/ValueSet/task-intent

  Maturity Level : 2
Responsible Owner: Orders and Observations icon Work Group Trial Use Normative Use Context : Any Country: World
This is a value set defined by the FHIR project. Summary Committee:
Official URL : Title: http://hl7.org/fhir/ValueSet/task-intent TaskIntent Definition: Distinguishes whether the task is a proposal, plan or full order. Version : 6.0.0-ballot4
active as of 2020-12-28 Orders and Observations Computable Name : TaskIntent Work Group
OID: Flags : Immutable 2.16.840.1.113883.4.642.3.1240 (for OID based terminology systems) Source Resource XML / JSON : 2.16.840.1.113883.4.642.3.1240

This value set is used in the following places:

4.4.1.150.1 4.4.1.180.1 Definition

Distinguishes whether the task is a proposal, plan or full order.

4.4.1.180.2 Content Logical Definition

Generated Narrative: ValueSet task-intent

Last updated: 2025-12-18T07:07:42.17+11:00

This value set includes codes from based on the following code systems: rules:

  • Include all codes defined in http://hl7.org/fhir/task-intent version 📦6.0.0-ballot4
  • Include these codes as defined in http://hl7.org/fhir/request-intent version 📦6.0.0-ballot4
    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.
    original-order Original Order The request represents an original authorization for action.
    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.
    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.
    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.
    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.

 

4.4.1.150.2 4.4.1.180.3 Expansion

This expansion generated 01 Nov 2019 18 Dec 2025

ValueSet

This value set contains 9 concepts

Expansion based on http://hl7.org/fhir/request-intent version 4.0.1, http://hl7.org/fhir/task-intent version 4.0.1 http://hl7.org/fhir/task-intent http://hl7.org/fhir/request-intent http://hl7.org/fhir/request-intent http://hl7.org/fhir/request-intent http://hl7.org/fhir/request-intent http://hl7.org/fhir/request-intent http://hl7.org/fhir/request-intent http://hl7.org/fhir/request-intent http://hl7.org/fhir/request-intent
Code System System Code Display Definition
http://hl7.org/fhir/task-intent    unknown Unknown The intent is not known. When dealing with Task, it's not always known (or relevant) how the task was initiated - i.e. whether it was proposed, planned, ordered or just done spontaneously.
http://hl7.org/fhir/request-intent    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.

http://hl7.org/fhir/request-intent    plan Plan

The request represents an intention to ensure something occurs without providing an authorization for others to act.

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

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

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

The request represents an original authorization for action.

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

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

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

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

 

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