This page is part of the FHIR Specification v4.3.0-snapshot1: R4B Snapshot to support the Jan 2022 Connectathon. About the R4B version of FHIR. The current officially released version is 4.3.0. For a full list of available versions, see the Directory of published versions . Page versions: R5 R4B R4 R3
Clinical Decision Support Work Group | Maturity Level: 3 | Trial Use | Use Context: Any |
This is a value set defined by the FHIR project.
Summary
Defining URL: | http://hl7.org/fhir/ValueSet/plan-definition-type |
Version: | 4.3.0-snapshot1 |
Name: | PlanDefinitionType |
Title: | PlanDefinitionType |
Definition: | The type of PlanDefinition. |
Committee: | Clinical Decision Support Work Group |
OID: | 2.16.840.1.113883.4.642.3.797 (for OID based terminology systems) |
Source Resource | XML / JSON |
This value set is used in the following places:
http://terminology.hl7.org/CodeSystem/plan-definition-type
This expansion generated 20 Dec 2021
This value set contains 4 concepts
Expansion based on PlanDefinitionType v4.3.0-snapshot1 (CodeSystem)
All codes in this table are from the system http://terminology.hl7.org/CodeSystem/plan-definition-type
Code | Display | Definition |
order-set | Order Set | A pre-defined and approved group of orders related to a particular clinical condition (e.g. hypertension treatment and monitoring) or stage of care (e.g. hospital admission to Coronary Care Unit). An order set is used as a checklist for the clinician when managing a patient with a specific condition. It is a structured collection of orders relevant to that condition and presented to the clinician in a computerized provider order entry (CPOE) system. |
clinical-protocol | Clinical Protocol | Defines a desired/typical sequence of clinical activities including preconditions, triggers and temporal relationships. |
eca-rule | ECA Rule | A decision support rule of the form [on Event] if Condition then Action. It is intended to be a shareable, computable definition of actions that should be taken whenever some condition is met in response to a particular event or events. |
workflow-definition | Workflow Definition | Defines the steps for a group of one or more systems in an event flow process along with the step constraints, sequence, pre-conditions and decision points to complete a particular objective. |
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 |