Flexpa
state-of-utah

Utah State Medicaid

Try it →

Documentation

Sandbox available?

Yes

Info Last Updated

June 18, 2026

Flexpa Endpoint ID

cd3e2...

Success Rate

Of patients who finished signing in, the share who connected. A sign-in is finished when it ends in a connection or an error reported by the payer or provider. A patient who connected after an earlier error counts as connected.

57.14%

Last 6 months

Finished Signing In

Of patients who started signing in, the share who finished. Patients who leave before finishing are not counted as failures above, because Flexpa cannot tell a patient who chose not to continue from one blocked on the payer or provider's own sign-in page.

87.5%

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

12 hours

Custom Settings Required?

Yes

Requested scopes

openidprofileemail

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
Aug 29, 2026: Available
HTTP 200
1 check
No data
No data
No data
No data
No data
No data
No data
No data
No data
Sep 8, 2026: Available
HTTP 200
2 checks
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
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
Aug 15, 2026: Available
Result: LOGIN
1 check
Aug 16, 2026: Available
Result: LOGIN
1 check
Aug 17, 2026: Available
Result: LOGIN
1 check
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
Nov 5, 2026: Available
Result: LOGIN
1 check
Nov 6, 2026: Unavailable
Result: ERROR
1 check
Nov 7, 2026: Available
Result: LOGIN
1 check
Nov 8, 2026: Unavailable
Result: ERROR
1 check
Nov 9, 2026: Available
Result: LOGIN
1 check
Nov 10, 2026: Available
Result: LOGIN
1 check
Nov 11, 2026: Unavailable
Result: ERROR
1 check
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

Medicaid

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

Patient (verified)ExplanationOfBenefit (verified)

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.

HealthcareServiceInsurancePlanLocationOperationDefinitionPractitionerRoleRelatedPerson