Extensions for Using Data Elements from FHIR R4B in FHIR R5 - Downloaded Version null See the Directory of published versions
| Page standards status: Trial-use | Maturity Level: 3 |
{
"resourceType" : "CodeSystem",
"id" : "plan-definition-type",
"text" : {
"status" : "generated",
"div" : "<div xmlns=\"http://www.w3.org/1999/xhtml\">\n \n \n <p>This code system http://terminology.hl7.org/CodeSystem/plan-definition-type defines the following codes:</p>\n \n \n <table class=\"codes\">\n \n \n <tr>\n \n \n <td style=\"white-space:nowrap\">\n \n \n <b>Code</b>\n \n \n </td>\n \n \n <td>\n \n \n <b>Display</b>\n \n \n </td>\n \n \n <td>\n \n \n <b>Definition</b>\n \n \n </td>\n \n \n </tr>\n \n \n <tr>\n \n \n <td style=\"white-space:nowrap\">order-set\n \n \n <a name=\"plan-definition-type-order-set\"> </a>\n \n \n </td>\n \n \n <td>Order Set</td>\n \n \n <td>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.</td>\n \n \n </tr>\n \n \n <tr>\n \n \n <td style=\"white-space:nowrap\">clinical-protocol\n \n \n <a name=\"plan-definition-type-clinical-protocol\"> </a>\n \n \n </td>\n \n \n <td>Clinical Protocol</td>\n \n \n <td>Defines a desired/typical sequence of clinical activities including preconditions, triggers and temporal relationships.</td>\n \n \n </tr>\n \n \n <tr>\n \n \n <td style=\"white-space:nowrap\">eca-rule\n \n \n <a name=\"plan-definition-type-eca-rule\"> </a>\n \n \n </td>\n \n \n <td>ECA Rule</td>\n \n \n <td>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.</td>\n \n \n </tr>\n \n \n <tr>\n \n \n <td style=\"white-space:nowrap\">workflow-definition\n \n \n <a name=\"plan-definition-type-workflow-definition\"> </a>\n \n \n </td>\n \n \n <td>Workflow Definition</td>\n \n \n <td>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.</td>\n \n \n </tr>\n \n \n </table>\n \n \n </div>"
},
"extension" : [
{
"url" : "http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status",
"valueCode" : "trial-use"
},
{
"url" : "http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm",
"valueInteger" : 3
},
{
"extension" : [
{
"url" : "packageId",
"valueId" : "hl7.fhir.uv.xver-r4b.r5"
},
{
"url" : "version",
"valueString" : "0.1.0"
},
{
"url" : "uri",
"valueUri" : "http://hl7.org/fhir/uv/xver/ImplementationGuide/hl7.fhir.uv.xver-r4b.r5"
}
],
"url" : "http://hl7.org/fhir/StructureDefinition/package-source"
},
{
"url" : "http://hl7.org/fhir/StructureDefinition/structuredefinition-wg",
"valueCode" : "cds"
}
],
"url" : "http://terminology.hl7.org/CodeSystem/plan-definition-type",
"version" : "4.3.0",
"name" : "PlanDefinitionType",
"title" : "PlanDefinitionType",
"status" : "draft",
"experimental" : false,
"date" : "2020-12-27T23:55:11-06:00",
"publisher" : "Clinical Decision Support",
"contact" : [
{
"name" : "Clinical Decision Support",
"telecom" : [
{
"system" : "url",
"value" : "http://www.hl7.org/Special/committees/dss"
}
]
}
],
"description" : "The type of PlanDefinition.",
"jurisdiction" : [
{
"coding" : [
{
"system" : "http://unstats.un.org/unsd/methods/m49/m49.htm",
"code" : "001",
"display" : "World"
}
]
}
],
"caseSensitive" : true,
"valueSet" : "http://hl7.org/fhir/ValueSet/plan-definition-type|5.0.0",
"content" : "complete",
"concept" : [
{
"code" : "order-set",
"display" : "Order Set",
"definition" : "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."
},
{
"code" : "clinical-protocol",
"display" : "Clinical Protocol",
"definition" : "Defines a desired/typical sequence of clinical activities including preconditions, triggers and temporal relationships."
},
{
"code" : "eca-rule",
"display" : "ECA Rule",
"definition" : "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."
},
{
"code" : "workflow-definition",
"display" : "Workflow Definition",
"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."
}
]
}