This is just replicating current problems with payers sending unsolicited 278 with final PA decision - this should be fixed, not built into the new FHIR system. - PAS #186

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive with Modification
    • Priority: Medium
    • US Da Vinci PAS (FHIR)
    • STU3
    • Financial Mgmt
    • (profiles) [deprecated]
    • Use Cases and Overvi
    • Hide

      Update the guide to indicate that polling is supported at this time, where subscription cannot be supported, with the intent to move to subscription only in a future release of the guide.

      Show
      Update the guide to indicate that polling is supported at this time, where subscription cannot be supported, with the intent to move to subscription only in a future release of the guide.
    • Robert Dieterle / Rachael Foerster: 20-0-1
    • Enhancement
    • Non-substantive

      Existing Wording: This will be done by querying the payer system/intermediary. This might be done at regular intervals (polling) or it might be done in response to a subscription notification indicating that the prior authorization has been changed

      Comment:

      One of the continual issues with the 278 that has been expressed by industry stakeholders is the inability of some payers to answer a previously pended response decision has been made. By creating a situation where the onus is on the provider's system to check on payer status for a prior authorization, this is just replicating current problems with payers sending unsolicited 278 with final PA decision - this should be fixed, not built into the new FHIR system.

      Summary:

      This is just replicating current problems with payers sending unsolicited 278 with final PA decision - this should be fixed, not built into the new FHIR system.

            Assignee:
            Unassigned
            Reporter:
            Terrence Cunningham
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: