Anthem Personal Health Assistant
Privacy and data use
Last updated: October 2, 2026
Anthem Personal Health Assistant is a read-only assistant designed to help a member review health-plan information made available through Anthem Patient Access APIs after the member signs in with Anthem and gives consent.
Current status
The current implementation is connected only to Anthem sandbox data. It does not access production Anthem member records. Production use requires Anthem approval, production OAuth credentials, and member consent through Anthem.
Information the assistant may access
With member consent, the assistant may read information returned by Anthem, including:
- Member profile information needed to identify the connected record.
- Coverage and plan-related records.
- Claims and ExplanationOfBenefit records.
- Claim payment fields, such as submitted amount, benefit amount, paid-to-provider amount, copay, coinsurance, deductible, noncovered amount, discount, member liability, and payment date or amount when returned.
- Pharmacy claim history, including drug code, quantity, days supply, refill fields, and payment fields when returned.
- Supported clinical records returned by Anthem Patient Access APIs, such as observations, conditions, procedures, encounters, diagnostic reports, immunizations, care plans, medication records, and document references.
How information is used
The assistant uses connected Anthem information to answer the member's questions and summarize available records in plain language. Examples include summarizing claims, explaining payment fields, listing pharmacy claims, and showing what coverage or clinical records are available.
What the assistant does not do
- It does not write data back to Anthem.
- It does not submit or modify claims.
- It does not create eligibility requests.
- It does not initiate payments.
- It does not sell member data or use Anthem data for advertising.
- It does not diagnose medical conditions.
- It does not infer annual deductible, out-of-pocket maximum, stop-loss, current medication use, or patient balances when those values are not directly returned by Anthem.
Token and credential handling
The assistant connects through Anthem's OAuth consent flow. Access and refresh tokens are stored privately and are used only to retrieve the consenting member's records. Tokens are not stored in the plugin source code repository.
Member control
The member controls whether to connect Anthem data. The member can revoke access through Anthem's consent or revocation process, or request that the application delete stored connection tokens.
Important limits
Information shown by the assistant depends on what Anthem returns through the connected API. Missing fields are treated as unavailable, not zero. Submitted claim amounts are not necessarily amounts owed by the member. Historical pharmacy claims are not proof that a medication is currently being taken.
Support
For access, deletion, privacy, or support questions, use the support page.