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

API for change request in scenario #1

XMLWordPrintableJSON

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Medium Medium
    • US Da Vinci ATR (FHIR)
    • 2.0.0-ballot
    • Financial Mgmt
    • STU
    • Use Cases and Overview
    • 2.4
    • Hide

      Check the IG for places where reconciliation is designated as "considered for future" and make necessary changes by identifying the appropriate use of member-add and member-remove functions. 

      Show
      Check the IG for places where reconciliation is designated as "considered for future" and make necessary changes by identifying the appropriate use of member-add and member-remove functions. 
    • Nagesh Bashyam/Jeff Brown: 11-0-1
    • Correction
    • Compatible, substantive

      In 2.4 #3a, "Provider reconciles the list with internal lists and data and in case changes are needed, notifies the Payer about specific changes. These changes could be to add additional patients, remove patients from the list etc. The specific mechanism of how this exchange happens varies based on Payers and Providers. Future versions of this implementation guide will specify standards for requesting and notifying of changes."
      In 2.5 #4, "Providers reconcile the list internally and identify that there may be members who need to be added and members who need to be removed from the list. In order to do so, the Provider uses the member-add and member-remove APIs to add and remove members from the list."
      Do we expect that scenario #1 will also use the member-add and member-remove APIs to communicate changes, or is the mechanism still "future"?

            Unassigned Unassigned
            sutley Spencer Utley
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: