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

Patient should be able to search EOBs, not get Bundles

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Medium Medium
    • US Da Vinci Patient Cost Transparency (PCT) (FHIR)
    • 1.0.0
    • Financial Mgmt
    • Formal Specification
      Use Case and Actors
    • Hide

      Will leverage the Patient Access API approach from the CARIN BB IG, allowing for query/retrieval of AEOB and related resources without having to search on a Bundle. 

      Will defer the group identifier discussion for when we tackle the AEOB summary, which would need to tie multiple AEOBs together anyway. 

      Show
      Will leverage the Patient Access API approach from the CARIN BB IG, allowing for query/retrieval of AEOB and related resources without having to search on a Bundle.  Will defer the group identifier discussion for when we tackle the AEOB summary, which would need to tie multiple AEOBs together anyway. 
    • Rick Geimer/Paul Knapp: 9-0-1
    • Correction
    • Non-compatible

    Description

      The current design of the PCT IG has flaws in that it requires a Bundle identifier to be transmitted to the patient or patient app in order to do the subsequent steps of GET Bundle.

      The transmission of a Bundle is impossible to implement in practice. A simpler design would have the AEOBs be available for searching after the patient authenticates with the payer, using the same RESTful exchange already implemented for CMS Patient Access APIs, reducing burden on implementing payers.

      The original Bundle mechanism and Bundle search that is being investigated is designed to accommodate requirements that:

      1. AEOBs should be grouped together for a single period of care
      2. AEOBs should be linked back to the GFE in some fashion

      However, this creates problems with searching Bundles.

      A simpler design that accomplishes these requirements is that the EOBs should include a group identifier in EOB.identifier. This allows for searching by that identifier to identify grouped AEOBs.

      Attachments

        Activity

          People

            rgeimer Rick Geimer
            healthbjk Brendan Keeler
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: