XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive
    • Icon: Medium Medium
    • US Da Vinci DTR (FHIR)
    • STU3
    • Financial Mgmt
    • (profiles) [deprecated]
    • 2.1.5
    • Hide

      Agree to use Proposed Wording:

      "Within DTR, the SMART on FHIR app serves as a middleware layer easing payer and provider integrations. Specifically, the relatively low adoption of CQL by providers and FHIR by payers is eased through the use of a third-party "app"."

      Show
      Agree to use Proposed Wording: "Within DTR, the SMART on FHIR app serves as a middleware layer easing payer and provider integrations. Specifically, the relatively low adoption of CQL by providers and FHIR by payers is eased through the use of a third-party "app"."
    • Larry Decelles / Isaac Vetter: 14-0-6
    • Correction
    • Non-substantive

    Description

      Existing Wording: Within Documentation Templates and Rules (DTR) the SMART on FHIR app is considered a key component because of the inherent nature of SMART on FHIR apps, namely the ability to call into backend systems such as payers using the SMART launch protocol and FHIR as well as the ability to run rules such as Clinical Quality Language (CQL).

      Proposed Wording: Within DTR, the SMART on FHIR app serves as a middleware layer easing payer and provider integrations. Specifically, the relatively low adoption of CQL by providers and FHIR by payers is eased through the use of a third-party "app".

      Comment:

      In the long run, a DTR app hurts interoperability. The goal should be direct provider/payer interoperability.

      Summary:

      DTR app

      Attachments

        Activity

          People

            Unassigned Unassigned
            Isaac.Vetter Isaac Vetter
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: