Difference between revisions of "PDDI-CDS FHIR IG Proposal"

From HL7Wiki
Jump to navigation Jump to search
 
(29 intermediate revisions by 3 users not shown)
Line 3: Line 3:
 
<div style="float: left;">[[Image:OpenHotTopic.GIF|35px| ]]</div>
 
<div style="float: left;">[[Image:OpenHotTopic.GIF|35px| ]]</div>
 
<div style="background:#F0F0F0">
 
<div style="background:#F0F0F0">
This page documents a [[:category:Pending FHIR IGProposal|Pending]] [[:category:FHIR IG Proposal|FHIR IG Proposal]]
+
This page documents a [[:category:Approved FHIR IG Proposal|Approved]] [[:category:FHIR IG Proposal|FHIR IG Proposal]]
 
</div>
 
</div>
 
</div>
 
</div>
 
[[Category:FHIR IG Proposal]]
 
[[Category:FHIR IG Proposal]]
[[Category:Pending FHIR IG Proposal]]
+
[[Category:Approved FHIR IG Proposal]]
 +
 
 +
Approved 2018-08-08
  
  
Line 32: Line 34:
  
 
==Committee Approval Date:==
 
==Committee Approval Date:==
<i> **TODO** Please enter the date that the committee approved this IGproposal</i>
+
<i>Aug 8th 2018</i>
  
 
==Contributing or Reviewing Work Groups==
 
==Contributing or Reviewing Work Groups==
  
 
<!-- Additional work groups that may have an interest in contributing to, or reviewing  the content of the IG (optional) -->
 
<!-- Additional work groups that may have an interest in contributing to, or reviewing  the content of the IG (optional) -->
* Clinical Decision Support
+
* Pharmacy
 +
* Clinical Quality Information
  
 
==FHIR Development Project Insight ID==
 
==FHIR Development Project Insight ID==
Line 43: Line 46:
 
<!-- Please specify the id of your work group’s PSS for doing FHIR work that covers the development and maintenance of this IG.  (If submitted but not yet approved, just write “pending”.) The link to the PSS template can be found here: http://gforge.hl7.org/gf/download/docmanfileversion/6832/9398/HL7FHIR_DSTUballotPSS-20120529.doc -->
 
<!-- Please specify the id of your work group’s PSS for doing FHIR work that covers the development and maintenance of this IG.  (If submitted but not yet approved, just write “pending”.) The link to the PSS template can be found here: http://gforge.hl7.org/gf/download/docmanfileversion/6832/9398/HL7FHIR_DSTUballotPSS-20120529.doc -->
  
PSS ID?
+
1405
  
 
==Scope of coverage==
 
==Scope of coverage==
Line 101: Line 104:
 
<!-- What is the realm code (2-character country code or 'uv') and IG code to use for the path when the IG is published under http://hl7.org/fhir?  E.g. us/ccda -->
 
<!-- What is the realm code (2-character country code or 'uv') and IG code to use for the path when the IG is published under http://hl7.org/fhir?  E.g. us/ccda -->
  
Universal
+
uv/potential-drug-interaction
  
 
==Maintenance Plan==
 
==Maintenance Plan==
Line 107: Line 110:
 
<!-- What commitment does the WG have to maintaining this IG as the FHIR core specification continues to evolve - particularly if the initial project sponsors are no longer providing resources -->
 
<!-- What commitment does the WG have to maintaining this IG as the FHIR core specification continues to evolve - particularly if the initial project sponsors are no longer providing resources -->
  
This specification will be maintained by the CDS work group once the PDDI-CDS has completed the development.
+
The authors of this implementation guide are active in the CDS work group and will ensure that provided artifacts are relevant with evolving specifications. The knowledge supporting the CDS artifacts was, in part, derived by the Semantic Web in Health Care and Life Sciences Interest Group (W3C). This collaborator will help support the knowledge base for CDS artifacts.
  
 
==Short Description==
 
==Short Description==
Line 113: Line 116:
 
<!-- 1-2 sentences describing the purpose/scope of the IG for inclusion in the registry -->
 
<!-- 1-2 sentences describing the purpose/scope of the IG for inclusion in the registry -->
  
 +
This implementation guide is targeted at stakeholders who seek to increase the specificity and clinical relevance of drug-drug interaction alerts presented through the electronic health record. The approach is service-oriented and uses Web standards, a minimum information model for potential drug interactions, and emerging Health Information Technology standards including CDS Hooks, FHIR, and Clinical Quality Language (CQL).
  
 
==Long Description==
 
==Long Description==
Line 118: Line 122:
 
<!-- 1 paragraph describing the purpose/scope of the IG in more detail for inclusion in the version history -->
 
<!-- 1 paragraph describing the purpose/scope of the IG in more detail for inclusion in the version history -->
  
 +
This implementation guide:
 +
 +
# Describes knowledge and decision points for two exemplar PDDI CDS artifacts:
 +
#* Warfarin + NSAIDs
 +
#* Digoxin + Cyclosporine
 +
# Provides structured code for CDS artifacts using current Health Information Technology (HIT) specifications:
 +
#* HL7 – Fast Health Interoperability Resources (FHIR)
 +
#* CDS Hooks
 +
#* Clinical Quality Language (CQL)
 +
# Proposes and provides guidance to optimize PDDI CDS artifacts
  
 
==Involved parties==
 
==Involved parties==
Line 123: Line 137:
 
<!-- 1 paragraph describing who is sponsoring or involved in creating the IG for inclusion in the version history -->
 
<!-- 1 paragraph describing who is sponsoring or involved in creating the IG for inclusion in the version history -->
  
 +
W3C Healthcare and Lifesciences Working Group – volunteer-based task force (https://www.w3.org/wiki/HCLSIG/DDI )
  
 
==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. -->
 +
 +
This implementation guide is expected to be piloted this September (2018) at the FHIR CDS Hooks Connectathon and subsequent Connectathons. Potential implementers include University of Pittsburgh Medical Center, Wolters Kluwer Health, and EHR vendors.
  
 
==Content sources==
 
==Content sources==
Line 133: Line 150:
  
 
Are there any source specifications that you wish to consult but are concerned about access to or expertise to consider? -->
 
Are there any source specifications that you wish to consult but are concerned about access to or expertise to consider? -->
 +
 +
* CDS Hooks (one of the lead authors of the CDS Hooks specification is part of the PDDI IG team)
  
 
==Example Scenarios==
 
==Example Scenarios==
  
 
<!-- Provide a listing of the types of scenarios to be represented in the examples produced for this IG.  They should demonstrate the full scope of the IG and allow exercising of the IG's capabilities (all profiles, different types of applications, etc.) -->
 
<!-- Provide a listing of the types of scenarios to be represented in the examples produced for this IG.  They should demonstrate the full scope of the IG and allow exercising of the IG's capabilities (all profiles, different types of applications, etc.) -->
 +
 +
The PDDI CDS is targeted at the computerized provider order entry system. The implementation guide and provided artifacts are amenable to both inpatient and outpatient settings, and any clinician with prescribing privileges.
  
 
==IG Relationships==
 
==IG Relationships==
  
 
<!-- Are there any IGs this resource depends on or that depend on this IG? -->
 
<!-- Are there any IGs this resource depends on or that depend on this IG? -->
 +
 +
None
  
 
==Timelines==
 
==Timelines==
  
 
<!-- Indicate the target date for having the IGcomplete from a committee perspective and ready for vetting and voting -->
 
<!-- Indicate the target date for having the IGcomplete from a committee perspective and ready for vetting and voting -->
 +
 +
We plan to submit the specification for ballot for comments in September 2018 (see complete timelines on Project Insight)
  
 
==When IG Proposal Is Complete==
 
==When IG Proposal Is Complete==
Line 150: Line 175:
  
 
==FMG Notes==
 
==FMG Notes==
 +
Would be good to see evidence of greater non-US participation in a nominally international IG

Latest revision as of 15:46, 9 August 2018

Approved 2018-08-08



Potential Drug-Drug Interaction (PDDI) Clinical Decision Support (CDS)

Owning work group name

Clinical Decision Support

Committee Approval Date:

Aug 8th 2018

Contributing or Reviewing Work Groups

  • Pharmacy
  • Clinical Quality Information

FHIR Development Project Insight ID

1405

Scope of coverage

This project seeks to develop an implementation guide for potential drug-drug interaction (PDDI) clinical decision support (CDS). The implementation guide will specify both a knowledge representation format for PDDI logic and CDS services for PDDI with electronic health record (EHR) systems. Specifically, the implementation guide will include specifications for:

  1. How to represent PDDI logic in CQL and evidence in computational format using the FHIR Clinical Reasoning module.
  2. How to use CDS Hooks as a mechanism for EHRs to request PDDI CDS from CDS services.

The project may raise the need to create new FHIR resource(s) (e.g., a resource to represent drug interactions) and/or FHIR profile(s) (e,g, for PDDI context representation). The current scope is the universal realm. We will consider potential realm-specific work in the future.

IG Purpose

New information regarding potential drug-drug interactions (PDDIs) is published every day in primary sources such as drug product labeling and the scientific literature. A PubMed search for publications indexed with the Medical Subject Headings keyword “Drug interactions” shows an average of 3,970 publications per year from 2000 through 2016. This suggests that the body of evidence about PDDIs is overwhelming and dynamic. Food and drug regulatory agencies in the United States, European Union, and Japan have issued guidance to industry recommending the use of drug product labeling to communicate potential involvements in drug interactions (Rekić et al. 2017). As it is impossible for clinicians to keep up with the PDDI evidence base, drug experts generate summaries of PDDI evidence from primary sources. These summaries bring PDDI knowledge to clinicians in the form of published drug information compendia, clinical decision support rules, and interaction checking applications. However, there are currently no broadly accepted standards to guide these experts in the knowledge representation and services implementation of PDDI information that would be most effective for clinical decision support. Without international coordination for the extensions and profiles used to express PDDI CDS, needless variation is certain to occur in implementations. This project will provide the opportunity for the international community to collaborate and come to consensus on patterns used in implementations.

This need for a standard representation of PDDI information was one of the topics addressed at two multi-stakeholder conference meetings/series (Hines et al. 2011; Scheife et al. 2015; Payne et al. 2015; Tilson et al. 2016). Attendees at both conferences included international stakeholders from drug information content providers, regulatory agencies, and academic organizations. Among the key recommendations was the following suggested set of core information that should be included for every PDDI mentioned in a clinically-oriented drug information resource (Payne et al. 2015):

  • Drugs involved  
  • Clinical consequences
  • Frequency of exposure to the interacting drug pair
  • Frequency of harm for persons who have been exposed to the interacting drug pair
  • Contextual information/modifying factors
  • Evidence
  • Mechanism of the interaction
  • Recommended actions
  • Seriousness rating

These core information elements are consistent with the results of a separate international Delphi study on how to improve the delivery of medication alerts within computerized physician order entry systems (Riedmann et al. 2011). This suggested list of core information elements includes some that are present in one or more of the 15 PDDI conceptual models analyzed in a recent comprehensive review by Herrero-Zazo, Segura-Bedmar, and Martínez (Herrero-Zazo et al. 2016). However, there is little commonality across the conceptual models on those elements that are included and no single conceptual model covers all 9 of the information elements. Moreover, the creation and maintenance of PDDI decision support generally requires considerable time and energy from highly trained domain experts. An additional need is to standardize the EHR context that is sent to CDS services. This includes context parameters that are currently not available but that, if present, would be useful for increasing the specificity of the CDS alerts. This is important to ensure that PDDI decision support can be implemented across a variety of systems.

Rekić D, Reynolds KS, Zhao P, Zhang L, Yoshida K, Sachar M, Piquette Miller M, Huang SM, Zineh I. Clinical Drug-Drug Interaction Evaluations to Inform Drug Use and Enable Drug Access. J Pharm Sci. 2017 Apr 21. pii: S0022-3549(17)30249-6. doi: 10.1016/j.xphs.2017.04.016. [Epub ahead of print] PubMed PMID: 28435142.

Hines LE, Murphy JE, Grizzle AJ, Malone DC. Critical issues associated with drug-drug interactions: highlights of a multistakeholder conference. Am J Health Syst Pharm. 2011 May 15;68(10):941-6. doi: 10.2146/ajhp100440. PubMed PMID:21546646.

Scheife RT, Hines LE, Boyce RD, Chung SP, Momper JD, Sommer CD, Abernethy DR, Horn JR, Sklar SJ, Wong SK, Jones G, Brown ML, Grizzle AJ, Comes S, Wilkins TL, Borst C, Wittie MA, Malone DC. Consensus Recommendations for Systematic Evaluation of Drug-Drug Interaction Evidence for Clinical Decision Support. Drug Saf. 2015 Feb. 38(2):197-206 http://link.springer.com/article/10.1007%2Fs40264-014-0262-8. PubMed PMID: 25556085. PMCID: PMC4624322

Payne, Thomas H., et al. "Recommendations to improve the usability of drug-drug interaction clinical decision support alerts." Journal of the American Medical Informatics Association (2015): ocv011.

Tilson H, Hines LE, McEvoy G, Weinstein DM, Hansten PD, Matuszewski K, le Comte M, Higby-Baker S, Hanlon JT, Pezzullo L, Vieson K, Helwig AL, Huang SM, Perre A, Bates DW, Poikonen J, Wittie MA, Grizzle AJ, Brown M, Malone DC. Recommendations for selecting drug-drug interactions for clinical decision support. Am J Health Syst Pharm. 2016 Apr 15;73(8):576-85. doi: 10.2146/ajhp150565. PubMed PMID: 27045070; PubMed Central PMCID: PMC50649

Riedmann D, Jung M, Hackl WO, Ammenwerth E. How to improve the delivery of medication alerts within computerized physician order entry systems: an international Delphi study. J Am Med Inform Assoc. 2011 Nov-Dec;18(6):760-6. Doi: 10.1136/amiajnl-2010-000006. Epub 2011 Jun 22. PubMed

Content location

https://github.com/HL7/PDDI-CDS

Proposed IG realm and code

uv/potential-drug-interaction

Maintenance Plan

The authors of this implementation guide are active in the CDS work group and will ensure that provided artifacts are relevant with evolving specifications. The knowledge supporting the CDS artifacts was, in part, derived by the Semantic Web in Health Care and Life Sciences Interest Group (W3C). This collaborator will help support the knowledge base for CDS artifacts.

Short Description

This implementation guide is targeted at stakeholders who seek to increase the specificity and clinical relevance of drug-drug interaction alerts presented through the electronic health record. The approach is service-oriented and uses Web standards, a minimum information model for potential drug interactions, and emerging Health Information Technology standards including CDS Hooks, FHIR, and Clinical Quality Language (CQL).

Long Description

This implementation guide:

  1. Describes knowledge and decision points for two exemplar PDDI CDS artifacts:
    • Warfarin + NSAIDs
    • Digoxin + Cyclosporine
  2. Provides structured code for CDS artifacts using current Health Information Technology (HIT) specifications:
    • HL7 – Fast Health Interoperability Resources (FHIR)
    • CDS Hooks
    • Clinical Quality Language (CQL)
  3. Proposes and provides guidance to optimize PDDI CDS artifacts

Involved parties

W3C Healthcare and Lifesciences Working Group – volunteer-based task force (https://www.w3.org/wiki/HCLSIG/DDI )

Expected implementations

This implementation guide is expected to be piloted this September (2018) at the FHIR CDS Hooks Connectathon and subsequent Connectathons. Potential implementers include University of Pittsburgh Medical Center, Wolters Kluwer Health, and EHR vendors.

Content sources

  • CDS Hooks (one of the lead authors of the CDS Hooks specification is part of the PDDI IG team)

Example Scenarios

The PDDI CDS is targeted at the computerized provider order entry system. The implementation guide and provided artifacts are amenable to both inpatient and outpatient settings, and any clinician with prescribing privileges.

IG Relationships

None

Timelines

We plan to submit the specification for ballot for comments in September 2018 (see complete timelines on Project Insight)

When IG Proposal Is Complete

When you have completed your proposal, please send an email to FMGcontact@HL7.org

FMG Notes

Would be good to see evidence of greater non-US participation in a nominally international IG