Example Bundle/bundle-transaction (Narrative)

Clinical Decision Support FHIR Infrastructure Work Group

Maturity Level : N/A

Standards Status : Informative

Compartments : Not linked to any defined compartments

Raw XML ( canonical form

• Narrative + also see
• XML Format Specification ) Definition for Code System PlanDefinitionType <?xml version="1.0" encoding="UTF-8"?> This code system http://terminology.hl7.org/CodeSystem/plan-definition-type defines the following codes: order-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-protocol Defines a desired/typical sequence of clinical activities including preconditions, triggers and temporal relationships. eca-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-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. 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. Defines a desired/typical sequence of clinical activities including preconditions, triggers and temporal relationships. 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. 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. </ CodeSystem
• JSON >
• TTL

This is the narrative for the resource. See also the XML , JSON or Turtle format. This example conforms to the profile Bundle .

---

---

 

 

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.