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

Clarify if/how to modify member

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Medium Medium
    • US Da Vinci ATR (FHIR)
    • 2.0.0-ballot
    • Financial Mgmt
    • STU
    • Detailed Specification
    • 4.4.1
    • Hide

      In order to help implementers, the spec.html sections related to member-add and member-remove will be further updated with example scenarios that occur in the real world and the preferred parameter combinations that can be used for the scenario for each operation.

      For e.g if a consumer wants to periodically update all the attributions for a specific patient, using the member-remove passing the member-id and then performing the member-add for each attribution using member-id, provider-npi and attribution period would be the right method of achieving the result.

      Similarly we can add examples for making delta updates, explain member-add and member-remove operations.

      Add examples for each scenario to help implementers.

      Show
      In order to help implementers, the spec.html sections related to member-add and member-remove will be further updated with example scenarios that occur in the real world and the preferred parameter combinations that can be used for the scenario for each operation. For e.g if a consumer wants to periodically update all the attributions for a specific patient, using the member-remove passing the member-id and then performing the member-add for each attribution using member-id, provider-npi and attribution period would be the right method of achieving the result. Similarly we can add examples for making delta updates, explain member-add and member-remove operations. Add examples for each scenario to help implementers.
    • Nagesh Bashyam/Jeff Brown: 11-0-1
    • Clarification
    • Non-substantive

    Description

      "This interaction outlines the APIs for a Consumer (for example, Provider organization) to add a member to the Member Attribution List."
      "Expected Results: Successful addition of the Patient to the Member Attribution List if the member and the provider is found in the system."
      In https://build.fhir.org/ig/HL7/davinci-atr/usecases.html 2.5 figure 3 step 4, does "Consumer requests add/modify or delete of a member" suggest that the add operation might be used to modify the inactive and/or period properties of a member that is already on the list?

      Attachments

        Activity

          People

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

            Dates

              Created:
              Updated:
              Resolved: