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

DTR links would be better handled as part of the coverage-information extension in a systemAction than in a Card

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Medium Medium
    • US Da Vinci CRD (FHIR)
    • 1.1.0-ballot [deprecated]
    • Clinical Decision Support
    • Coverage Information
    • Hide

      Proposal: make the below mandatory rather than a configuration option. I.e. DTR will always come back as a system action, not a SMART App launch card. Seeking feedback from other EHRs on system action being mandatory.

      Will add a configuration option that allows DTR links to come back as a system action.  CRD clients SHALL expose the option to launch the EHR's DTR solution to clinicians if the updated order extension indicates clinical input is needed and SHOULD allow clinicians to launch non-clinical DTR if they wish.

      Show
      Proposal: make the below mandatory rather than a configuration option. I.e. DTR will always come back as a system action, not a SMART App launch card. Seeking feedback from other EHRs on system action being mandatory. Will add a configuration option that allows DTR links to come back as a system action.  CRD clients SHALL expose the option to launch the EHR's DTR solution to clinicians if the updated order extension indicates clinical input is needed and SHOULD allow clinicians to launch non-clinical DTR if they wish.
    • Bob Dieterle / Mark Scrimshire : 4-0-1
    • Enhancement
    • Compatible, substantive
    • Yes

    Description

      Continuing discussion from- https://chat.fhir.org/#narrow/stream/179283-Da-Vinci/topic/Prior.20Authorization.20Q.26A/near/286092887

       

      Currently DTR links come back as part of Cards that are displayed to the physician, however as we discussed often the physician will prefer to let staff handle it, or the contents may be entirely administrative information that doesn't require their input.

      Instead of using Cards, we should prefer System Actions via updating http://hl7.org/fhir/us/davinci-crd/2022May/StructureDefinition-ext-coverage-information.html to have an extension defining the URL and the appContext as if we had received a https://cds-hooks.org/specification/current/#link in a card. We would expect it to to be populated whenever the extension has one of the http://hl7.org/fhir/us/davinci-crd/2022May/ValueSet-coverageGuidance.html values meaning that there is DTR questionnaire.

      That way we can more clearly store and route the DTR link to whichever user can best  handle it (be it the physician choosing to, or staff following up).

      Attachments

        Activity

          People

            Unassigned Unassigned
            kjohnsen Kyle Johnsen
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: