This section suggests the use of DTR to retrieve relevant payer documentation rules in computable form. - PAS #240

XMLWordPrintableJSON

    • Type: Question
    • Resolution: Considered - Question answered
    • Priority: Medium
    • US Da Vinci PAS (FHIR)
    • STU3
    • Financial Mgmt
    • (profiles) [deprecated]
    • 2.3.2
    • Hide

      CDS hooks indicates how to tie into workflow and indicate that requirements exist. DTR defines how to actually communicate the rules (and optionally, how to use SMART to collect necessary data).

      Show
      CDS hooks indicates how to tie into workflow and indicate that requirements exist. DTR defines how to actually communicate the rules (and optionally, how to use SMART to collect necessary data).
    • Kathleen Connor / Robert Dieterle: 20-0-1

      Comment:

      When determining if there is a need for Prior Authorization, this section suggests the use of DTR to retrieve relevant payer documentation rules in computable form as well as associated FHIR questionnaires to support the assembly of information for a prior authorization.

      Question - isn't that the purpose of CDS Hooks - to pull out rules that can be consumed by an EHR to execute a function? Is DTR, in this context 'competing' or 'duplicating' the purpose of CDS Hooks?

      Summary:

      This section suggests the use of DTR to retrieve relevant payer documentation rules in computable form.

            Assignee:
            Unassigned
            Reporter:
            Walter Suarez
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: