Release 5 Preview #1

This page is part of the FHIR Specification (v4.2.0: R5 Preview #1). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions . Page versions: R4B R4 R3

Codesystem-plan-definition-type.json

Clinical Decision Support Work GroupMaturity Level: N/AStandards Status: Informative

Raw JSON (canonical form + also see JSON Format Specification)

Definition for Code System PlanDefinitionType

{
  "resourceType" : "CodeSystem",
  "id" : "plan-definition-type",
  "meta" : {
    "lastUpdated" : "2019-12-31T21:03:40.621+11:00"
  },
  "text" : {
    "status" : "generated",
    "div" : "<div>!-- Snipped for Brevity --></div>"
  },
  "extension" : [{
    "url" : "http://hl7.org/fhir/StructureDefinition/structuredefinition-wg",
    "valueCode" : "cds"
  },
  {
    "url" : "http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status",
    "valueCode" : "trial-use"
  },
  {
    "url" : "http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm",
    "valueInteger" : 2
  }],
  "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"
  }],
  "version" : "4.2.0",
  "name" : "PlanDefinitionType",
  "title" : "PlanDefinitionType",
  "status" : "draft",
  "experimental" : false,
  "date" : "2019-12-31T21:03:40+11:00",
  "publisher" : "HL7 (FHIR Project)",
  "contact" : [{
    "telecom" : [{
      "system" : "url",
      "value" : "http://hl7.org/fhir"
    },
    {
      "system" : "email",
      "value" : "fhir@lists.hl7.org"
    }]
  }],
  "description" : "The type of PlanDefinition.",
  "caseSensitive" : true,
  "valueSet" : "http://hl7.org/fhir/ValueSet/plan-definition-type",
  "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."
  }]
}

Usage note: every effort has been made to ensure that the examples are correct and useful, but they are not a normative part of the specification.