R4 Ballot #2 (Mixed Normative/Trial use)

This page is part of the FHIR Specification (v3.5.0: R4 Ballot #2). 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: R4B R4 R3

4.3.13.281 Code System http://terminology.hl7.org/CodeSystem/plan-definition-type

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

This is a code system defined by the FHIR project.

Summary

Defining URL:http://terminology.hl7.org/CodeSystem/plan-definition-type
Version:3.5.0
Name:PlanDefinitionType
Title:PlanDefinitionType
Definition:

The type of PlanDefinition.

Committee:Clinical Decision Support Work Group
OID:2.16.840.1.113883.4.642.1.1245 (for OID based terminology systems)
Source ResourceXML / JSON

This Code system is used in the following value sets:

4.3.13.281.1 Content

4.3.13.281.2 PlanDefinitionType

The type of PlanDefinition.

This code system http://terminology.hl7.org/CodeSystem/plan-definition-type defines the following codes:

CodeDisplayDefinition
order-set Order SetA 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 ProtocolDefines a desired/typical sequence of clinical activities including preconditions, triggers and temporal relationships.
eca-rule ECA RuleA 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 DefinitionDefines 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 code systems 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. 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