HL7 Terminology (THO)
6.0.2 - Publication
This page is part of the HL7 Terminology (v6.0.2: Release) based on FHIR (HL7® FHIR® Standard) v5.0.0. This is the current published version. For a full list of available versions, see the Directory of published versions
Official URL: http://terminology.hl7.org/ValueSet/plan-definition-type | Version: 1.0.1 | |||
Active as of 2024-04-24 | Maturity Level: 2 | Responsible: Health Level Seven International | Computable Name: PlanDefinitionType | |
Other Identifiers: OID:2.16.840.1.113883.4.642.3.797 | ||||
Copyright/Legal: This material derives from the HL7 Terminology THO. THO is copyright ©1989+ Health Level Seven International and is made available under the CC0 designation. For more licensing information see: https://terminology.hl7.org/license.html |
The type of PlanDefinition.
References
This value set is not used here; it may be used elsewhere (e.g. specifications and/or implementations that use this content)
Generated Narrative: ValueSet plan-definition-type
Last updated: 2024-04-24 00:00:00+0000
Profile: Shareable ValueSet
http://terminology.hl7.org/CodeSystem/plan-definition-type
Generated Narrative: ValueSet
Last updated: 2024-04-24 00:00:00+0000
Profile: Shareable ValueSet
Expansion based on codesystem PlanDefinitionType v1.0.1 (CodeSystem)
This value set contains 4 concepts
Code | System | Display | Definition |
order-set | http://terminology.hl7.org/CodeSystem/plan-definition-type | 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 | http://terminology.hl7.org/CodeSystem/plan-definition-type | Clinical Protocol | Defines a desired/typical sequence of clinical activities including preconditions, triggers and temporal relationships. |
eca-rule | http://terminology.hl7.org/CodeSystem/plan-definition-type | 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 | http://terminology.hl7.org/CodeSystem/plan-definition-type | 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. |
Explanation of the columns that may appear on this page:
Level | A few code lists that FHIR defines are hierarchical - each code is assigned a level. In this scheme, some codes are under other codes, and imply that the code they are under also applies |
System | 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) |
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 |
History
Date | Action | Author | Custodian | Comment |
2023-11-14 | revise | Marc Duteau | TSMG | Add standard copyright and contact to internal content; up-476 |
2020-10-14 | revise | Grahame Grieve | Vocabulary WG | Reset Version after migration to UTG |
2020-05-06 | revise | Ted Klein | Vocabulary WG | Migrated to the UTG maintenance environment and publishing tooling. |