Uploaded image for project: 'FHIR Specification Feedback'
  1. FHIR Specification Feedback
  2. FHIR-18804

DetectedIssue in CDS service response - PDDI #1

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive
    • Icon: Medium Medium
    • Potential Drug-Drug Interaction (PDDI) (FHIR)
    • STU3
    • Clinical Decision Support
    • Profiles defined as part of the PDDI CDS Implementation Guide
    • 4.0.0
    • Hide

      We are no longer proposing to include a DetectedIssue resource in Card.suggestion.action.

      Show
      We are no longer proposing to include a DetectedIssue resource in Card.suggestion.action.
    • Peter Muir/Guilherme del Fiol: 11-0-1
    • Clarification
    • Non-substantive

    Description

      Existing Wording: A CDS Hooks Card extension so that a DetectedIssue resource can be included in a Card response

      Comment:

      Looking over the IG, it seems that DetectedIssue is at a level too high for CDS Hooks. However, I hesitate to make a comment, as the overall workflow on positive DDI dectection would yield a hard-stop for the EHR. I.e., no record would ever be entered for the Patient. My hesitation is that it doesn't really belong in Card.suggestion.action, as those are focused on creating, updating or deleting resources, but it also doesn't belong on Card.suggestion as it has no context whatsoever.

      Which is actually a bigger issue with CDS Hooks—there is no standard placeholder for adding rationale for the Card.indicator.

      Summary:

      DetectedIssue in CDS service response

      Attachments

        Activity

          People

            Unassigned Unassigned
            euvitudo Phillip Warner
            Phillip Warner
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: