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

AEOB Query should take a different approach

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Highest Highest
    • US Da Vinci Patient Cost Transparency (PCT) (FHIR)
    • 0.1.0 [deprecated]
    • Financial Mgmt
    • STU
    • Formal Specification
    • Hide

      Based on the updated workflow diagram, we will now be using the async pattern for provider access and an OAuth2 + FHIR REST API approach inspired by the patient access api for patient access. Will redo API documentation to reflect the new approach. 

      Show
      Based on the updated workflow diagram, we will now be using the async pattern for provider access and an OAuth2 + FHIR REST API approach inspired by the patient access api for patient access. Will redo API documentation to reflect the new approach. 
    • Rick Geimer/Paul Knapp: 9-0-1
    • Enhancement
    • Non-compatible

    Description

      The API is not well defined. The search on a Bundle identifier does not seem to make much sense. The provider would not know an AEOB Bundle identifier.

      The Server may store bundles for other purposes and a simple ID may cause collisions.

      Perhaps the query should also be an operation with a parameter indicating a defined ID of the original GFE submission. Could have more complex queries that would allow queries for batches of AEOBs instead of querying for individual AEOBs.

      Scale needs to be considered.

       

      Attachments

        Activity

          People

            rgeimer Rick Geimer
            corey_spears Corey Spears
            Corey Spears
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: