1.  Diagram as attached will be added to the IG. Verbiage will be updated as follows: 2.  Update Actors description: Consumer (aka Subscriber, Beneficiary, Patient, or Personal Representative) Consumer App- A digital third-party application selected by and primarily for the Consumer with a consumer-facing user interface Health Plan API (aka Payer, Covered Entity) Health Plan’s Identity and Access Authorization server 3.  Update Flow narrative per below; remove the word ‘Normal’   1. Consumer App presents a list of potential Payers / Health Plans to access to the Consumer.   2. Consumer selects the Payer / Health Plan.   3. Consumer App opens the link to the Health Plan's Identity and Access Authorization server.   4. Consumer enters the credentials.   5. Health Plan's Identity and Access Authorization server validates the credentials, generates and returns to the Consumer App an OIDC token with Consumer and authorized patient/beneficiary identities encoded.   6. Consumer App successfully links the user to the Payer / Health Plan and notifies the Consumer.   7. Consumer requests the Consumer App to fetch Explanation Of Benefit records.   8. Consumer App generates and sends to the Health Plan's CARIN BB enabled FHIR API a request (which includes Patient ID, and token from the step #5) to fetch the Explanation Of Benefit (EOB) and supporting reference FHIR resources.   9. Health Plan's CARIN BB enabled FHIR API responds with a bundle of the requested EOB and supporting reference FHIR resources.   10. Consumer App presents the EOB and supporting reference FHIR resources to the Consumer.