FHIR CI-Build

This is the Continuous Integration Build of FHIR (will be incorrect/inconsistent at times).
See the Directory of published versions icon

4.4.1.84 ValueSet http://hl7.org/fhir/ValueSet/task-intent

Orders and Observations icon Work Group Maturity Level: 3Trial Use Use Context: Country: World
Official URL: http://hl7.org/fhir/ValueSet/task-intent Version: 6.0.0-cibuild
draft as of 2020-12-28 Computable Name: TaskIntent
Flags: Immutable OID: 2.16.840.1.113883.4.642.3.1240

This value set is used in the following places:

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


This value set includes codes based on the following rules:

  • Include all codes defined in http://hl7.org/fhir/task-intent
  • Include these codes as defined in http://hl7.org/fhir/request-intent
    CodeDisplayDefinition
    proposalProposalThe 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.
    planPlanThe request represents an intention to ensure something occurs without providing an authorization for others to act.
    orderOrderThe request represents a request/demand and authorization for action by the requestor.
    original-orderOriginal OrderThe request represents an original authorization for action.
    reflex-orderReflex OrderThe 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-orderFiller OrderThe 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-orderInstance OrderAn 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.
    optionOptionThe 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.

 

This expansion generated 11 Apr 2024


This value set contains 9 concepts.

CodeSystemDisplayDefinition
  unknownhttp://hl7.org/fhir/task-intentUnknown

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.

  proposalhttp://hl7.org/fhir/request-intentProposal

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.

  planhttp://hl7.org/fhir/request-intentPlan

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

  orderhttp://hl7.org/fhir/request-intentOrder

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

  original-orderhttp://hl7.org/fhir/request-intentOriginal Order

The request represents an original authorization for action.

  reflex-orderhttp://hl7.org/fhir/request-intentReflex 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-orderhttp://hl7.org/fhir/request-intentFiller 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-orderhttp://hl7.org/fhir/request-intentInstance 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.

  optionhttp://hl7.org/fhir/request-intentOption

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.

 

See the full registry of value sets defined as part of FHIR.


Explanation of the columns that may appear on this page:

LvlA 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
SourceThe source of the definition of the code (when the value set draws in codes defined elsewhere)
CodeThe code (used as the code in the resource instance). If the code is in italics, this indicates that the code is not selectable ('Abstract')
DisplayThe 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
DefinitionAn explanation of the meaning of the concept
CommentsAdditional notes about how to use the code