HL7 Terminology (THO)
5.5.0 - Continuous Process Integration (ci build) International flag

HL7 Terminology (THO), published by HL7 International - Vocabulary Work Group. This guide is not an authorized publication; it is the continuous build for version 5.5.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/UTG/ and changes regularly. See the Directory of published versions

ValueSet: PlanDefinitionType

Official URL: http://terminology.hl7.org/ValueSet/plan-definition-type Version: 1.0.0
Draft as of 2020-02-24 Maturity Level: 2 Responsible: Health Level Seven International Computable Name: PlanDefinitionType
Other Identifiers: urn:ietf:rfc:3986#Uniform Resource Identifier (URI)#urn: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

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

Expansion based on codesystem PlanDefinitionType v1.0.0 (CodeSystem)

This value set contains 4 concepts.

CodeSystemDisplayDefinition
  order-sethttp://terminology.hl7.org/CodeSystem/plan-definition-typeOrder 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-protocolhttp://terminology.hl7.org/CodeSystem/plan-definition-typeClinical Protocol

Defines a desired/typical sequence of clinical activities including preconditions, triggers and temporal relationships.

  eca-rulehttp://terminology.hl7.org/CodeSystem/plan-definition-typeECA 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-definitionhttp://terminology.hl7.org/CodeSystem/plan-definition-typeWorkflow 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

DateActionCustodianAuthorComment
2023-11-14reviseTSMGMarc DuteauAdd standard copyright and contact to internal content; up-476
2020-10-14reviseVocabulary WGGrahame GrieveReset Version after migration to UTG
2020-05-06reviseVocabulary WGTed KleinMigrated to the UTG maintenance environment and publishing tooling.