Potential Drug-Drug Interaction (PDDI) Clinical Decision Support
1.0.0 - STU 1 International flag

Potential Drug-Drug Interaction (PDDI) Clinical Decision Support, published by HL7 International / Clinical Decision Support. This guide is not an authorized publication; it is the continuous build for version 1.0.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/PDDI-CDS/ and changes regularly. See the Directory of published versions

Changes

Page standards status: Informative

STU 1 (1.0.0)

Non-Substantive Changes Applied

  • FHIR-50176: Add discussion of delivery/integration using a SMART app
  • FHIR-37696: In "what you will need" - update or remove "list of FHIR tools"
  • FHIR-37693: Add a paragraph that makes clear what is meant by a 'remote' CDS service
  • FHIR-37694: Need to fill in the section about patient-view
  • FHIR-37695: ensure that the minimal information model for representing clinically actionable knowledge about PDDIs is not referred to as the "minimum" information model
  • FHIR-37697: add a paragraph on evidence resource and EBM on FHIR
  • FHIR-39969: Improve the "universal" orientation of the guide
  • FHIR-39970: Revise the way profiles are included in the guide
  • FHIR-40035: Consider incorporation of DetectedIssue
  • FHIR-40037: Make the value sets based upon use of drug classes wherever possible
  • FHIR-40097: Clarify CDS Hooks indicator values
  • FHIR-39922: Typo in Introduction page

STU 1 Ballot (1.0.0-ballot)

The following resolutions have been voted on by the members of the sponsoring work group HL7 International Clinical Decision Support.

Comments and their resolutions

Listed below are the resolved trackers for this version:

Status: Summary:(Jira Issue)

  1. Applied: Typo: World (FHIR-29616)
  2. Applied: Grammar correction : The barriers to a successful PDDI CDS are both theoretical and technological (FHIR-29614)
  3. Applied: Incorrect use of dratOrders on order-sign (FHIR-29608)
  4. Applied: Typo: Digoxin (FHIR-29623)
  5. Applied: "Recommend not getting rid of ""prescribe.""" (FHIR-29613)
  6. Applied: "Throughout: correct ""decision making"" to ""decision-making""" (FHIR-29615)
  7. Applied: typo: knowledge - here and in 2.0.0 (FHIR-29618)
  8. Applied: Not convinced that a web service based decision support can do better than existing DDI solutions. (FHIR-29598)
  9. Applied: It is not clear what the additional context field is. (FHIR-29601)
  10. Applied: "Missing required ""cds-services"" path segment for CDS Hooks examples" (FHIR-29607)
  11. Applied: Remove and correct the referenced sentence. (FHIR-29627)
  12. Applied: The Homepage and most of the sections of the IG need proofreading. (FHIR-29611)
  13. Applied: Correct link to CDS Hooks feedfback service details (FHIR-29606)
  14. Applied: "Recommend that PDDI CDS IG address security and privacy concerns, that may arise due to a patient's consent directive." (FHIR-29626)
  15. Applied: CDS Discovery examples include wrong attribute (FHIR-29605)
  16. Applied: "Make the page structure consistent regarding ""Page Contents.""" (FHIR-29610)
  17. Applied: The discussion/presentation of Knowldege Artifacts is helpful (FHIR-29632)
  18. Applied: Fix CDS Hooks discovery url typo,dennispatterson (FHIR-29604)
  19. Applied: "Consider expanding the IG to include drug interactions with vitamins, herbs and food." (FHIR-29596)
  20. Applied: Practicing clinicians using the EHR must be consulted re: any configuration decisions made related to the CDS service and what alerts to present. (FHIR-29622)
  21. Applied: The emission of the coded response would be useful for clinicians reviewing the specificaiton to see. (FHIR-29630)
  22. Applied: This section provides a good overview with the 2 use cases provided for implementers. (FHIR-29628)
  23. Applied: The basic implementation is a repetition of the CDS Hooks standard. (FHIR-29600)
  24. Applied: Clarify whether these have NCPDP SCRIPT functions in outpatient e-prescribing world? (FHIR-29617)
  25. Applied: "IG needs to include dosage, route are required for CDS hook." (FHIR-29633)
  26. Applied: Suggest only one alert at the point of ordering the drug unless the orderer is different than the order signer. (FHIR-29597)
  27. Applied: Required coordiation extensions should be included within PDDI implementation guide (FHIR-29609)
  28. Applied: "When using acronyms, specify meaning on first use or in a glossary." (FHIR-29629)
  29. Applied: Summary of the Terminology section and list of value sets is very helpful for implementers. (FHIR-29631)
  30. Applied: Disagree with configuration to not address certain drugs - this might be an added risk. (FHIR-29621)
  31. Applied: The scope of this document related to inpatient drug orders vs. outpatient (retail) prescription drugs should be clarified. (FHIR-29612)
  32. Applied: Please clarify: how does outpatient e-prescribing via NCPDP SCRIPT fit in here? (FHIR-29619)
  33. Applied: Is it possible to provide the CDS information at an intermediate step between product selection and signing the order? (FHIR-29620)
  34. Applied: "In Figure 10, note that an order selection dropdown list may or may not include the route; therefore, the node that evaluates whether or not the selected order is topical diclofenac may or may not be able to be evaluated." (FHIR-28511)
  35. Applied: Please change MUST to SHOULD in the following sentence: “If the CDS rule execution engine does not receive prefetch data in the request it MUST query the FHIR server via network call.” (FHIR-28508)
  36. Applied: Not always possible to evaluate an order at order-select stage (FHIR-28514)
  37. Applied: Card Action Example seems backwards (FHIR-28428)
  38. Applied: Question about order-select prefetch content (FHIR-28429)
  39. Applied: Redundancy in Figures 10 and 11 (FHIR-28512)
  40. Applied: "The link to the description of “configuration-items” works, but no information about “configuration-items” is provided at the destination web page (the CDS Hooks specification)." (FHIR-28510)
  41. Applied: "Consider removing this sentence: “It is RECOMMENDED that the rule engine be able to execute CDS rules written in CQL and represented as a FHIR Library resource, either directly or compiled to HL7 Expression Logical Model.” " (FHIR-28509)
  42. Applied: resources named without text formatting (FHIR-18074)
  43. Applied: Fix navigation,smrobertson (FHIR-18056)
  44. Applied: PDDI CarePlan - bad link - PDDI #9 (FHIR-18805)
  45. Applied: Fix references (FHIR-18057)
  46. Applied: Wording correction (FHIR-18073)
  47. Applied: All of the Resource links point to the Documentation page. - PDDI #10 (FHIR-18806)
  48. Applied: Making conformance criteria more visible (FHIR-18078)
  49. Applied: DetectedIssue in CDS service response - PDDI #1 (FHIR-18804)
  50. Applied: Editorial fix (FHIR-18072)
  51. Applied: Bad links - PDDI #11 (FHIR-18807)
  52. Applied: section 6 Documentation needs to be expanded (FHIR-18079)