Flexpa
reliance-medicare-advantage

Reliance Medicare Advantage

Documentation

Sandbox available?

Yes

Info Last Updated

August 7, 2026

Flexpa Endpoint ID

9ba6e...

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.

No data available

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

Refreshable

Max Auth Period

Unknown

Custom Settings Required?

No

Requested scopes

openidoffline_accessa45c41b6-6e09-49e4-a2ee-321bd011c677

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
100% available
No data
No data
No data
No data
No data
No data
No data
No data
No data
No data
No data
No data
No data
No data
No data
No data
No data
No data
No data
No data
No data
No data
No data
No data
No data
No data
No data
No data
No data
No data
No data
No data
No data
No data
No data
No data
No data
No data
No data
No data
No data
No data
No data
No data
No data
No data
No data
No data
No data
No data
No data
No data
No data
No data
No data
No data
No data
No data
No data
Aug 25, 2026: Available
HTTP 200
1 check
Aug 26, 2026: Available
HTTP 200
1 check
Aug 27, 2026: Available
HTTP 200
1 check
Aug 28, 2026: Available
HTTP 200
1 check
Aug 29, 2026: Available
HTTP 200
2 checks
No data
Aug 31, 2026: Available
HTTP 200
1 check
Sep 1, 2026: Available
HTTP 200
1 check
Sep 2, 2026: Available
HTTP 200
1 check
Sep 3, 2026: Available
HTTP 200
1 check
Sep 4, 2026: Available
HTTP 200
1 check
Sep 5, 2026: Available
HTTP 200
1 check
Sep 6, 2026: Available
HTTP 200
2 checks
Sep 7, 2026: Available
HTTP 200
1 check
Sep 8, 2026: Available
HTTP 200
1 check
Sep 9, 2026: Available
HTTP 200
1 check
Sep 10, 2026: Available
HTTP 200
1 check
Sep 11, 2026: Available
HTTP 200
1 check
Sep 12, 2026: Available
HTTP 200
2 checks
Sep 13, 2026: Available
HTTP 200
1 check
Sep 14, 2026: Available
HTTP 200
1 check
Sep 15, 2026: Available
HTTP 200
2 checks
Sep 16, 2026: Available
HTTP 200
2 checks
Sep 17, 2026: Available
HTTP 200
2 checks
Sep 18, 2026: Available
HTTP 200
1 check
No data
No data
No data
No data
No data
Today — pending
Browser RenderLogin page classification · fires when the HTTP response can't be classified statically
No render
No render
No render
No render
No render
No render
No render
No render
No render
No render
No render
No render
No render
No render
No render
No render
No render
No render
No render
No render
No render
No render
No render
No render
No render
No render
No render
No render
No render
No render
No render
No render
No render
No render
No render
No render
No render
No render
No render
No render
No render
No render
No render
No render
No render
No render
No render
No render
No render
No render
No render
No render
No render
No render
No render
No render
No render
No render
No render
No render
No render
No render
No render
No render
No render
No render
No render
No render
No render
No render
No render
No render
No render
No render
No render
No render
No render
No render
No render
No render
No render
No render
No render
No render
No render
No render
No render
No render
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