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

How can we reduce provider burden in DTR? - DTR #67

    XMLWordPrintableJSON

Details

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

      Other available data sources (e.g. the Payer) SHOULD be used to enable the collection of necessary information to support any documentation of medical necessity and to streamline the clinical user experience.

       

      Show
      Other available data sources (e.g. the Payer) SHOULD be used to enable the collection of necessary information to support any documentation of medical necessity and to streamline the clinical user experience.  
    • Larry Decelles / Isaac Vetter: 14-0-6
    • Enhancement
    • Compatible, substantive

    Description

      Comment:

      Overall, in the case where the payer has clinicial data about the patient or even derived clinical data, why can't the app pre-populate questions on the form unanswerable via CQL generated FHIR queries against the provider's system, by also querying the payer?

      Summary:

      How can we reduce provider burden in DTR?

      Attachments

        Activity

          People

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

            Dates

              Created:
              Updated:
              Resolved: