HL7 Terminology (THO)
3.1.0 - Publication International flag

This page is part of the HL7 Terminology (v3.1.0: Release) based on FHIR R4. The current version which supercedes this version is 5.2.0. For a full list of available versions, see the Directory of published versions

ValueSet: PlanDefinitionType

Official URL: http://terminology.hl7.org/ValueSet/plan-definition-type Version: 0.2.0
Standards status: Trial-use Maturity Level: 2 Responsible: HL7 (FHIR Project) Computable Name: PlanDefinitionType
Other Identifiers: : urn:oid:2.16.840.1.113883.4.642.3.797

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)

Logical Definition (CLD)

 

Expansion

This value set contains 4 concepts

Expansion based on PlanDefinitionType v0.1.0 (CodeSystem)

All codes in this table are from the system http://terminology.hl7.org/CodeSystem/plan-definition-type

CodeDisplayDefinition
order-setOrder 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-protocolClinical ProtocolDefines a desired/typical sequence of clinical activities including preconditions, triggers and temporal relationships.
eca-ruleECA 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-definitionWorkflow 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.

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

DateActionAuthorCustodianComment
2020-10-14reviseGrahame GrieveVocabulary WGReset Version after migration to UTG
2020-05-06reviseTed KleinVocabulary WGMigrated to the UTG maintenance environment and publishing tooling.