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

do not support multiple CRDs

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Not Persuasive
    • Icon: Highest Highest
    • US Da Vinci CRD (FHIR)
    • 1.1.0-ballot [deprecated]
    • Financial Mgmt
    • STU
    • Use Cases and Overview
    • Hide

      By definition, each payer (or at least most payers) will have their own CRD services.  The logic that drives the responses as well as the data available for detecting things like duplicate or contraindicated therapy will be proprietary to that payer.  It's possible that some payers will coordinate and leverage a shared service, but most won't.

      This imposes no significant cost on EHRs.  EHRs expect to support a wide variety of CDS Hook services - that's sort of the point.  Services can be 'plugged in' to the relevant hooks and all receive the notifications and provide decision support when/if relevant.  In the case of CRD, there will typically only be one or two CRD services called for a given clinical action because the EHR will be required to filter hook calls to only send to payers with whom the patient has active coverage.

      Show
      By definition, each payer (or at least most payers) will have their own CRD services.  The logic that drives the responses as well as the data available for detecting things like duplicate or contraindicated therapy will be proprietary to that payer.  It's possible that some payers will coordinate and leverage a shared service, but most won't. This imposes no significant cost on EHRs.  EHRs expect to support a wide variety of CDS Hook services - that's sort of the point.  Services can be 'plugged in' to the relevant hooks and all receive the notifications and provide decision support when/if relevant.  In the case of CRD, there will typically only be one or two CRD services called for a given clinical action because the EHR will be required to filter hook calls to only send to payers with whom the patient has active coverage.
    • Bob Dieterle / Chris Cioffi : 12-0-0

    Description

      What are the implications of this? The guide should address how multiple CRD services can integrate with a single physician's EMR. Will EMRs need to support a large number of CRDs? This will be costly/burdensome.

      Attachments

        Activity

          People

            Unassigned Unassigned
            celine_lefebvre Celine Lefebvre
            Celine Lefebvre
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: