CHRISTUS Health Plan

Documentation

Developer Portal

Sandbox available?

Yes

Info Last Updated

May 11, 2026

Flexpa Endpoint ID

13f2e...

Success Rate

The percentage of authorization attempts that successfully complete, from initial redirect through token receipt. This metric directly reflects the reliability and usability of the authorization flow for end users.

Last 6 months

Authorization Overview

The authorization flow is often the biggest barrier to patient access. This dimension evaluates both the technical implementation and user experience.

Token Type

If an endpoint's access token is refreshable, the Token Refresh API can be used to issue a new access token prior to the refresh token expiring. Otherwise, if the access token is non-refreshable, the user is required to re-authorize the application after the access token expires.

Refreshable

Max Auth Period

This is the payer imposed upper bound on the time period for which a user can keep refreshing an access token. Once the maximum authorization period has elapsed, the user is required to re-authorize the application.

Unknown

Custom Settings Required?

If an endpoint deviates from the standard authorization flow and custom settings are required. These customizations vary from custom parameters in the authorization or token endpoints, to custom locations for retrieving the patient ID.

Yes

Requested scopes

The OAuth scopes Flexpa requests during the authorization flow for this endpoint. These determine what data Flexpa is authorized to access on behalf of the patient.

openidprofileofflineoffline_accessfhiruserlaunch/patient

Uptime

Flexpa checks the SMART authorization endpoint every 12 hours to verify it serves a reachable login page. Each square is one day. The percentage is the share of checked days where every check succeeded.

HTTP CheckSMART well-known endpoint reachability · every 12 hours

0% available

May 4, 2026: Unavailable

HTTP 500

2 bad responses

2 checks

May 5, 2026: Unavailable

HTTP 500

1 network failure

1 bad response

2 checks

May 6, 2026: Unavailable

HTTP 500

2 bad responses

2 checks

May 7, 2026: Unavailable

HTTP 500

2 bad responses

2 checks

May 8, 2026: Unavailable

HTTP 500

2 bad responses

2 checks

May 9, 2026: Unavailable

HTTP 500

2 bad responses

2 checks

May 10, 2026: Unavailable

HTTP 500

2 bad responses

2 checks

May 11, 2026: Unavailable

HTTP 500

2 bad responses

2 checks

May 12, 2026: Unavailable

HTTP 500

2 bad responses

2 checks

May 13, 2026: Unavailable

HTTP 500

2 bad responses

2 checks

May 14, 2026: Unavailable

HTTP 500

2 bad responses

2 checks

No data

May 25, 2026: Unavailable

HTTP 500

2 bad responses

2 checks

May 26, 2026: Unavailable

HTTP 403, 500

2 bad responses

2 checks

May 27, 2026: Unavailable

HTTP 403

2 bad responses

2 checks

May 28, 2026: Unavailable

HTTP 500

2 bad responses

2 checks

May 29, 2026: Unavailable

HTTP 500

2 bad responses

2 checks

May 30, 2026: Unavailable

HTTP 500

2 bad responses

2 checks

May 31, 2026: Unavailable

HTTP 500

2 bad responses

2 checks

Jun 1, 2026: Unavailable

HTTP 403, 500

8 bad responses

8 checks

Jun 2, 2026: Unavailable

HTTP 500

3 bad responses

3 checks

Jun 3, 2026: Unavailable

HTTP 500

2 bad responses

2 checks

Jun 4, 2026: Unavailable

HTTP 500

4 bad responses

4 checks

Jun 5, 2026: Unavailable

HTTP 500

3 bad responses

3 checks

Jun 6, 2026: Unavailable

HTTP 500

2 bad responses

2 checks

Jun 7, 2026: Unavailable

HTTP 500

2 bad responses

2 checks

Jun 8, 2026: Unavailable

HTTP 500

5 bad responses

5 checks

Jun 9, 2026: Unavailable

HTTP 500

2 bad responses

2 checks

Jun 10, 2026: Unavailable

HTTP 500

2 bad responses

2 checks

Jun 11, 2026: Unavailable

HTTP 500

2 bad responses

2 checks

Jun 12, 2026: Unavailable

HTTP 500

2 bad responses

2 checks

Jun 13, 2026: Unavailable

HTTP 500

2 bad responses

2 checks

Jun 14, 2026: Unavailable

HTTP 500

2 bad responses

2 checks

Jun 15, 2026: Unavailable

HTTP 500

2 bad responses

2 checks

Jun 16, 2026: Unavailable

HTTP 500

2 bad responses

2 checks

Jun 17, 2026: Unavailable

HTTP 500

2 bad responses

2 checks

Jun 18, 2026: Unavailable

HTTP 500

2 bad responses

2 checks

Jun 19, 2026: Unavailable

HTTP 500

1 bad response

1 check

Jun 20, 2026: Unavailable

HTTP 500

1 bad response

1 check

Jun 21, 2026: Unavailable

HTTP 500

1 bad response

1 check

Jun 22, 2026: Unavailable

HTTP 500

1 bad response

1 check

Jun 23, 2026: Unavailable

HTTP 500

1 bad response

1 check

Jun 24, 2026: Unavailable

HTTP 500

1 bad response

1 check

Jun 25, 2026: Unavailable

HTTP 500

1 bad response

1 check

Jun 26, 2026: Unavailable

HTTP 500

1 bad response

1 check

Jun 27, 2026: Unavailable

HTTP 500

1 bad response

1 check

Jun 28, 2026: Unavailable

HTTP 500

1 bad response

1 check

Jun 29, 2026: Unavailable

HTTP 500

1 bad response

1 check

Jun 30, 2026: Unavailable

HTTP 500

1 bad response

1 check

Jul 1, 2026: Unavailable

HTTP 500

1 bad response

1 check

Jul 2, 2026: Unavailable

HTTP 500

1 bad response

1 check

Jul 3, 2026: Unavailable

HTTP 500

1 bad response

1 check

Jul 4, 2026: Unavailable

HTTP 500

1 bad response

1 check

Jul 5, 2026: Unavailable

HTTP 500

1 bad response

1 check

Jul 6, 2026: Unavailable

HTTP 500

1 bad response

1 check

Jul 7, 2026: Unavailable

HTTP 500

1 bad response

1 check

Jul 8, 2026: Unavailable

HTTP 500

1 bad response

1 check

Jul 9, 2026: Unavailable

HTTP 500

1 bad response

1 check

Jul 10, 2026: Unavailable

HTTP 500

1 bad response

1 check

Jul 11, 2026: Unavailable

HTTP 500

1 bad response

1 check

Jul 12, 2026: Unavailable

HTTP 500

1 bad response

1 check

Jul 13, 2026: Unavailable

HTTP 500

1 bad response

1 check

Jul 14, 2026: Unavailable

HTTP 500

1 bad response

1 check

Jul 15, 2026: Unavailable

HTTP 500

1 bad response

1 check

Jul 16, 2026: Unavailable

HTTP 500

1 bad response

1 check

Jul 17, 2026: Unavailable

HTTP 500

1 bad response

1 check

Jul 18, 2026: Unavailable

HTTP 500

1 bad response

1 check

Jul 19, 2026: Unavailable

HTTP 500

1 bad response

1 check

Jul 20, 2026: Unavailable

HTTP 500

1 bad response

1 check

Jul 21, 2026: Unavailable

HTTP 500

1 bad response

1 check

Jul 22, 2026: Unavailable

HTTP 500

1 bad response

1 check

Jul 23, 2026: Unavailable

HTTP 500

1 bad response

1 check

Jul 24, 2026: Unavailable

HTTP 500

1 bad response

1 check

Jul 25, 2026: Unavailable

HTTP 500

1 bad response

1 check

Jul 26, 2026: Unavailable

HTTP 500

1 bad response

1 check

Jul 27, 2026: Unavailable

HTTP 500

1 bad response

1 check

Jul 28, 2026: Unavailable

HTTP 500

1 bad response

1 check

Jul 29, 2026: Unavailable

HTTP 500

1 bad response

1 check

Jul 30, 2026: Unavailable

HTTP 500

1 bad response

1 check

Jul 31, 2026: Unavailable

HTTP 500

1 bad response

1 check

Today — pending

Browser RenderLogin page classification · fires when the HTTP response can't be classified statically

No render

Today — pending

90 days agoToday

Available

Degraded

Unavailable

No data

FHIR API Implementation

The quality and completeness of the FHIR implementation determines the utility of the API for third-party applications and patients alike.

Lines of Business supported

No information

Supported FHIR Resources

Pills with a indicate resources observed in at least one successful sync within the last 6 months across our recent processing history. A resource not marked verified isn't necessarily unavailable — it may simply not appear in any connected user's record (e.g., a patient with no recorded immunizations), or be returned only rarely. Verification is based on what was successfully loaded into Flexpa's data store, including resources derived from EOBs for payer endpoints.

CARIN BB Core Profiles

No information

Other USCDI V1 Profiles

Payers primarily return claims via ExplanationOfBenefit. Flexpa derives Encounter, Condition, Procedure, and Provenance from EOBs — see Claims to Clinical. Some payers also return clinical resources directly; absence here doesn't mean unavailable.

No information