California DxF provider participation and accessing data for Anthem members

As part of our ongoing communications regarding the California Health and Human Services (CalHHS) established Health and Human Services Data Exchange Framework (DxF), we are excited to share updates on the new technical capabilities we have implemented for care providers to access data for Anthem members. Please note, these new technical capabilities support IHE (Integrating the Healthcare Enterprise)–based and FHIR (Fast Healthcare Interoperability Resources)–based protocols for data access.

Consult the Technical FAQ section and additional information below for details on eligible participants in the DxF and for instructions on accessing data for our members

Who can participate in DxF?

To learn more about participating in DxF, please visit the official state website For Participants (ca.gov).

How do I access Anthem members' data using the DxF?

We follow the California DxF DSA agreement and support IHE‑ and FHIR‑based protocols for data access. For detailed information on the supported standards, see the Technical FAQ below.

If you need assistance

If there are any questions related to the onboarding, reach out to InteroperabilityWorkgroup@anthem.com. More information on DxF is available below and at Data Exchange Framework (ca.gov).

General FAQ

Note: See the Technical FAQ section for technical and specification‑related questions.

Where can I find more information on the California Data Exchange Framework (DxF)?

All relevant information related to DxF is at Data Exchange Framework (ca.gov).

What data can providers expect to receive?

We will provide clinical and claims data for our members who are receiving care from our provider partners.

See the Technical FAQ section for technical specifications used in the data exchange.

Do care providers need to obtain consent from members to access their data?

No, providers do not need to obtain consent from members to access their data through DxF. All member information, aside from sensitive data, is automatically included in the data set available to providers. However, in compliance with 42 CFR Part 2 and California state health data sharing guidelines, member consent is required when the request involves access to sensitive data, such as HIV status, reproductive health, behavioral health, and substance use disorder information

Can a member choose to opt out of the DxF?

Yes, if a member opts out or declines to share their data, we will not include data for that specific member.

Is it possible to conduct testing with Anthem before connecting to the production environment?

Yes, entities can register and perform testing in our sandbox environment by following the instructions provided at https://totalview.healthos.elevancehealth.com/fhir/documentation#overview‑section.

Technical FAQ

How can care providers request access to our DxF FHIR APIs?

Provider organizations can request access by following these steps. A link to the registration guide can be found on the Digital Solutions Learning Hub (on24.com).

1. Register/log in to https://Availity.com and navigate to Payer Space to access the Data Exchange Framework (DXF) Registration Payer Space Application.
2. Upon launch of the DxF application, you will be redirected to the DxF registration portal. Fill out the required information and submit the form. Detailed registration instructions can be found here (Availity.com).
3. The submitted form will be in a pending state while the Interoperability team reviews to decide on granting access to DxF FHIR APIs.
4. Once a decision is made, a notification is emailed to the submitter to return to the registration website and fetch the credentials needed to invoke DxF FHIR APIs.

Note: Registration approval typically takes two to four weeks.

How can care providers request access to our DxF IHE endpoints?

In addition to the FHIR capability described above, we have streamlined data access by adopting the IHE technical standard in partnership with Manifest MedEx, California’s largest nonprofit DxF qualified health information organization. Providers aiming to access our members' health data using the IHE standard must collaborate with Manifest MedEx.

Is there a technical document that highlights the capabilities supported by Anthem?

Our APIs and technical documentation can be accessed at https://totalview.healthos.elevancehealth.com/fhir/documentation#overview‑section.

What FHIR standard does Anthem use to exchange the data?

We support the FHIR 4.0.1 (hl7.org) standard to enable the data exchange.

What FHIR resource specifications does Anthem use for the data exchange?

• Inbound request format: For an inbound request, use the HRex Member Match Operation (hl7.org). The structure of the inbound request is also provided in the API/technical documentation cited above.
• Consent specification: For receiving the consent, we will be using the HRex Consent Profile (hl7.org). Consent is enabled using the policy field in the consent profile. The structure of the consent is also provided in the API/technical documentation cited above.
• Clinical data payload FHIR specification: A payload containing claims and clinical data as defined in US Core Implementation Guide, 5.0.1 (hl7.org) will be returned to the requester.