PlanDefinitionType

{
  "description" : "The type of PlanDefinition.",
  "date" : "2020-04-09T21:10:28+00:00",
  "meta" : {
    "lastUpdated" : "2020-04-09T21:10:28.568+00:00"
  },
  "publisher" : "HL7 (FHIR Project)",
  "content" : "complete",
  "property" : null,
  "name" : "PlanDefinitionType",
  "experimental" : false,
  "resourceType" : "CodeSystem",
  "title" : "PlanDefinitionType",
  "extension" : [ {
    "valueCode" : "cds",
    "url" : "http://hl7.org/fhir/StructureDefinition/structuredefinition-wg"
  }, {
    "valueCode" : "trial-use",
    "url" : "http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status"
  }, {
    "url" : "http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm",
    "valueInteger" : 2
  }, {
    "extension" : [ {
      "valueString" : "concept",
      "url" : "path"
    }, {
      "url" : "count",
      "valueInteger" : 4
    } ],
    "url" : "http://health-samurai.io/extensions/excised-data"
  }, {
    "url" : "http://health-samurai.io/extensions/source",
    "valueCode" : "db"
  } ],
  "status" : "draft",
  "id" : "f8235188-567b-4985-9923-d78d35a37e4b",
  "valueSet" : "http://terminology.hl7.org/ValueSet/plan-definition-type",
  "url" : "http://terminology.hl7.org/CodeSystem/plan-definition-type",
  "identifier" : [ {
    "system" : "urn:ietf:rfc:3986",
    "value" : "urn:oid:2.16.840.1.113883.4.642.1.1245"
  } ],
  "caseSensitive" : true,
  "version" : "0.1.0",
  "contact" : [ {
    "telecom" : [ {
      "system" : "url",
      "value" : "http://hl7.org/fhir"
    }, {
      "system" : "email",
      "value" : "fhir@lists.hl7.org"
    } ]
  } ],
  "text" : {
    "div" : "<div xmlns=\"http://www.w3.org/1999/xhtml\"><p>This code system <code>http://terminology.hl7.org/CodeSystem/plan-definition-type</code> defines the following codes:</p><table class=\"codes\"><tr><td style=\"white-space:nowrap\"><b>Code</b></td><td><b>Display</b></td><td><b>Definition</b></td></tr><tr><td style=\"white-space:nowrap\">order-set<a name=\"plan-definition-type-order-set\"> </a></td><td>Order Set</td><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></tr><tr><td style=\"white-space:nowrap\">clinical-protocol<a name=\"plan-definition-type-clinical-protocol\"> </a></td><td>Clinical Protocol</td><td>Defines a desired/typical sequence of clinical activities including preconditions, triggers and temporal relationships.</td></tr><tr><td style=\"white-space:nowrap\">eca-rule<a name=\"plan-definition-type-eca-rule\"> </a></td><td>ECA Rule</td><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></tr><tr><td style=\"white-space:nowrap\">workflow-definition<a name=\"plan-definition-type-workflow-definition\"> </a></td><td>Workflow Definition</td><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></tr></table></div>",
    "status" : "generated"
  }
}