The use case description should be very clear that this is about information exchange only and refrain from generalizing that such exchange will facilitate treatment continuity. - PCDE #129

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive
    • Priority: Medium
    • US Da Vinci PCDE (FHIR)
    • STU3
    • Financial Mgmt
    • (profiles) [deprecated]
    • 2.2
    • Hide

      Will add a paragraph clarifying that this specification merely helps enable continuity of care through information sharing, but that actual continuity is dependent on the new payer's policies, their evaluation of the information received, and what coverage the new plan offers.

      Show
      Will add a paragraph clarifying that this specification merely helps enable continuity of care through information sharing, but that actual continuity is dependent on the new payer's policies, their evaluation of the information received, and what coverage the new plan offers.
    • Kathleen Connor / Rachael Foerster: 20-0-1
    • Clarification
    • Non-substantive

      Comment:

      While it is a laudable goal to provide this use case a solution to continuity of care when switching between plans, it's important to recognize that the payers are under no obligation to accept a previous payer's determination of medical necessity or cover drugs/services/therapies in the same manner as the previous payer. The use case description should be very clear that this is about information exchange only and refrain from generalizing that such exchange will facilitate treatment continuity. A payer may receive information more quickly, but a human on the backend will still be making determinations about coverage.

      Summary:

      The use case description should be very clear that this is about information exchange only and refrain from generalizing that such exchange will facilitate treatment continuity.

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

              Created:
              Updated:
              Resolved: