Difference between revisions of "DecisionSupportRule FHIR Resource Proposal"
Bryn rhodes (talk | contribs) |
Bryn rhodes (talk | contribs) |
||
| Line 1: | Line 1: | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
=DecisionSupportRule= | =DecisionSupportRule= | ||
| Line 27: | Line 13: | ||
--> | --> | ||
| − | The DecisionSupportRule resource represents the definition of a decision support rule of the form [on Event] if Condition then Action. | + | The DecisionSupportRule resource represents the definition of a decision support rule of the form [on Event] if Condition then Action. Event-Condition-Action rules are a common and flexible mechanism of dynamically affecting clinical workflow by intercepting established points within the workflow, evaluating conditions based on the relevant context, and returning guidance in the form of actions to be taken, either by the system directly, or as part of a recommended intervention with the involvement of clinicians at the point-of-care. |
| + | |||
| + | The intent of the resource is to establish a standard mechanism to enable automated sharing of the knowledge defined by the ECA rule. The resource is a concrete realization of the logical model defined by the [http://www.hl7.org/implement/standards/product_brief.cfm?product_id=337 HL7 Standard: Clinical Decision Support Knowledge Artifact Specification]. | ||
==Owning committee name== | ==Owning committee name== | ||
| Line 57: | Line 45: | ||
As a rule, resources should encompass all of these aspects. | As a rule, resources should encompass all of these aspects. | ||
--> | --> | ||
| + | |||
| + | A DecisionSupportRule is a knowledge artifact that enables automated sharing of a certain common pattern of clinical knowledge. Because it is definitional in nature, it is not a patient-specific resource. The resource captures the structure of an Event-Condition-Action rule and is flexible enough to be used to describe behaviors for any discipline and locale. It is intended to be used by decision support content vendors as a means of distributing knowledge artifacts, as well as by decision support service vendors and health care delivery systems as a means of automatically integrating decision support behavior. | ||
| + | |||
==RIM scope== | ==RIM scope== | ||
<!-- Identify the formal RIM mapping for the root concept of the resource. The expectation is that the RIM mapping will be sufficiently precise so as to not overlap with any other resource definition. --> | <!-- Identify the formal RIM mapping for the root concept of the resource. The expectation is that the RIM mapping will be sufficiently precise so as to not overlap with any other resource definition. --> | ||
| + | |||
| + | Because the DecisionSupportRule is definitional in nature, it has no direct counterpart in the RIM. | ||
==Resource appropriateness== | ==Resource appropriateness== | ||
| Line 76: | Line 69: | ||
* Have the characteristics of high cohesion & low coupling – need to explore whether coupling is good some places, not elsewhere – layers from Bo’s document | * Have the characteristics of high cohesion & low coupling – need to explore whether coupling is good some places, not elsewhere – layers from Bo’s document | ||
--> | --> | ||
| + | |||
| + | Decision support interventions are a critial aspect of health care delivery, but they are often implemented as custom logic, either within an EHR directly, or as part of a decision support service that is exposed via a proprietary interface. Increasingly, decision support content vendors are making these types of rules available, but each vendor uses a proprietary format to enable the distribution of their content. | ||
| + | |||
| + | The Clinical Decision Support Knowledge Artifact Specification provides a standard mechanism for sharing ECA rules, and enabling that content to be represented as a FHIR resource will extend the reach of that content. In addition, defining the content as a FHIR resource will allow implementers to use the FHIR stack and all its associated tooling and specifications to expose the content, effectively enabling another potential role of a FHIR server as a Knowledge Artifact Repository. | ||
| + | |||
==Expected implementations== | ==Expected implementations== | ||
<!--Key resources are justified by CCDA, for resources not deemed "key", what interest is there by implementers in using this particular resource. Provide named implementations if possible - ideally provide multiple independent implementations. --> | <!--Key resources are justified by CCDA, for resources not deemed "key", what interest is there by implementers in using this particular resource. Provide named implementations if possible - ideally provide multiple independent implementations. --> | ||
| + | |||
| + | Multiple decision support vendors have expressed interest in using the DecisionSupportRule resource to enable standards-based distribution of their content. | ||
| + | |||
| + | <!-- I'd have to get permission to post names publicly, but ask me (Bryn Rhodes) for details. --> | ||
==Content sources== | ==Content sources== | ||
| Line 100: | Line 102: | ||
<!-- Provide a listing of the types of scenarios to be represented in the examples produced for this resource. They should demonstrate the full scope of the resource and allow exercising of the resources capabilities (full element coverage, inclusion & omission of optional elements, repeating and singleton repeating elements, etc.) --> | <!-- Provide a listing of the types of scenarios to be represented in the examples produced for this resource. They should demonstrate the full scope of the resource and allow exercising of the resources capabilities (full element coverage, inclusion & omission of optional elements, repeating and singleton repeating elements, etc.) --> | ||
| + | |||
| + | ===Chlamydia Screening=== | ||
| + | When seeing a patient that meets the criteria defined by Chlamydia Screening guidelines, clinicians should ensure that the appropriate testing has been performed. The logic to capture this intervention can be represented as a DecisionSupportRule. | ||
| + | |||
| + | ===Exclusive Breastfeeding=== | ||
| + | When admitting a new mother for delivery, appropriate interventions to ensure the mother receives education regarding exclusive breastfeeding can be represented as a DecisionSupportRule. | ||
==Resource Relationships== | ==Resource Relationships== | ||
| Line 111: | Line 119: | ||
Reference to resources is really only relevant at the "same or higher level" (Bo – fix this wording) | Reference to resources is really only relevant at the "same or higher level" (Bo – fix this wording) | ||
--> | --> | ||
| + | |||
| + | This resource will make use of the [https://hl7-fhir.github.io/library.html Library] resource to represent any logic involved in the ECA rule. | ||
==Timelines== | ==Timelines== | ||
<!-- Indicate the target date for having the resource complete from a committee perspective and ready for vetting and voting --> | <!-- Indicate the target date for having the resource complete from a committee perspective and ready for vetting and voting --> | ||
| + | |||
| + | May 2016 Ballot Cycle | ||
==gForge Users== | ==gForge Users== | ||
Revision as of 09:58, 4 April 2016
Contents
- 1 DecisionSupportRule
- 1.1 Owning committee name
- 1.2 Committee Approval Date:
- 1.3 Contributing or Reviewing Work Groups
- 1.4 FHIR Resource Development Project Insight ID
- 1.5 Scope of coverage
- 1.6 RIM scope
- 1.7 Resource appropriateness
- 1.8 Expected implementations
- 1.9 Content sources
- 1.10 Example Scenarios
- 1.11 Resource Relationships
- 1.12 Timelines
- 1.13 gForge Users
DecisionSupportRule
The DecisionSupportRule resource represents the definition of a decision support rule of the form [on Event] if Condition then Action. Event-Condition-Action rules are a common and flexible mechanism of dynamically affecting clinical workflow by intercepting established points within the workflow, evaluating conditions based on the relevant context, and returning guidance in the form of actions to be taken, either by the system directly, or as part of a recommended intervention with the involvement of clinicians at the point-of-care.
The intent of the resource is to establish a standard mechanism to enable automated sharing of the knowledge defined by the ECA rule. The resource is a concrete realization of the logical model defined by the HL7 Standard: Clinical Decision Support Knowledge Artifact Specification.
Owning committee name
Clinical Decision Support Work Group
Committee Approval Date:
2016-02-24 - Meeting Minutes
Contributing or Reviewing Work Groups
FHIR Resource Development Project Insight ID
1234: FHIR-Based Clinical Quality Framework (CQF-on-FHIR)
Scope of coverage
A DecisionSupportRule is a knowledge artifact that enables automated sharing of a certain common pattern of clinical knowledge. Because it is definitional in nature, it is not a patient-specific resource. The resource captures the structure of an Event-Condition-Action rule and is flexible enough to be used to describe behaviors for any discipline and locale. It is intended to be used by decision support content vendors as a means of distributing knowledge artifacts, as well as by decision support service vendors and health care delivery systems as a means of automatically integrating decision support behavior.
RIM scope
Because the DecisionSupportRule is definitional in nature, it has no direct counterpart in the RIM.
Resource appropriateness
Decision support interventions are a critial aspect of health care delivery, but they are often implemented as custom logic, either within an EHR directly, or as part of a decision support service that is exposed via a proprietary interface. Increasingly, decision support content vendors are making these types of rules available, but each vendor uses a proprietary format to enable the distribution of their content.
The Clinical Decision Support Knowledge Artifact Specification provides a standard mechanism for sharing ECA rules, and enabling that content to be represented as a FHIR resource will extend the reach of that content. In addition, defining the content as a FHIR resource will allow implementers to use the FHIR stack and all its associated tooling and specifications to expose the content, effectively enabling another potential role of a FHIR server as a Knowledge Artifact Repository.
Expected implementations
Multiple decision support vendors have expressed interest in using the DecisionSupportRule resource to enable standards-based distribution of their content.
Content sources
Are there any source specifications that you wish to consult but are concerned about access to or expertise to consider? -->
- Clinical Quality Common Metadata Conceptual Model
- Clinical Decision Support Knowledge Artifact Specification
- Health Quality Measure Format
- Decision Support Service
- Decision Support Service Implementation Guide
- Infobutton Specification
- Infobutton Implementation Guide
- SOA Infobutton Implementation Guide
Example Scenarios
Chlamydia Screening
When seeing a patient that meets the criteria defined by Chlamydia Screening guidelines, clinicians should ensure that the appropriate testing has been performed. The logic to capture this intervention can be represented as a DecisionSupportRule.
Exclusive Breastfeeding
When admitting a new mother for delivery, appropriate interventions to ensure the mother receives education regarding exclusive breastfeeding can be represented as a DecisionSupportRule.
Resource Relationships
This resource will make use of the Library resource to represent any logic involved in the ECA rule.
Timelines
May 2016 Ballot Cycle
gForge Users
brynrhodes
