Missouri State Medicaid (MO HealthNet)
Documentation
Sandbox available?
Yes
Info Last Updated
May 11, 2026
Flexpa Endpoint ID
7bd85...
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.
0%
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.
Indefinitely
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.
No
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.
openidprofile
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% availableAug 5, 2026: Unavailable
HTTP 400
2 bad responses
2 checks
Aug 6, 2026: Unavailable
HTTP 400
1 bad response
1 check
Aug 7, 2026: Unavailable
HTTP 400
1 bad response
1 check
Aug 8, 2026: Unavailable
HTTP 400
1 bad response
1 check
Aug 9, 2026: Unavailable
HTTP 400
1 bad response
1 check
Aug 10, 2026: Unavailable
HTTP 400
1 bad response
1 check
Aug 11, 2026: Unavailable
HTTP 400
1 bad response
1 check
Aug 12, 2026: Unavailable
HTTP 400
1 bad response
1 check
Aug 13, 2026: Unavailable
HTTP 400
1 bad response
1 check
Aug 14, 2026: Unavailable
HTTP 400
1 bad response
1 check
Aug 15, 2026: Unavailable
HTTP 400
1 bad response
1 check
Aug 16, 2026: Unavailable
HTTP 400
1 bad response
1 check
Aug 17, 2026: Unavailable
HTTP 400
1 bad response
1 check
Aug 18, 2026: Unavailable
HTTP 400
1 bad response
1 check
Aug 19, 2026: Unavailable
HTTP 400
1 bad response
1 check
Aug 20, 2026: Unavailable
HTTP 400
1 bad response
1 check
Aug 21, 2026: Unavailable
HTTP 400
1 bad response
1 check
Aug 22, 2026: Unavailable
HTTP 400
1 bad response
1 check
Aug 23, 2026: Unavailable
HTTP 400
1 bad response
1 check
Aug 24, 2026: Unavailable
HTTP 400
2 bad responses
2 checks
Aug 25, 2026: Unavailable
HTTP 400
2 bad responses
2 checks
Aug 26, 2026: Unavailable
HTTP 400
2 bad responses
2 checks
Aug 27, 2026: Unavailable
HTTP 400
2 bad responses
2 checks
Aug 28, 2026: Unavailable
HTTP 400
1 bad response
1 check
Aug 29, 2026: Unavailable
HTTP 400
2 bad responses
2 checks
Aug 30, 2026: Unavailable
HTTP 400
2 bad responses
2 checks
Aug 31, 2026: Unavailable
HTTP 400
1 bad response
1 check
Sep 1, 2026: Unavailable
HTTP 400
1 bad response
1 check
Sep 2, 2026: Unavailable
HTTP 400
1 bad response
1 check
Sep 3, 2026: Unavailable
HTTP 400
1 bad response
1 check
Sep 4, 2026: Unavailable
HTTP 400
1 bad response
1 check
Sep 5, 2026: Unavailable
HTTP 400
1 bad response
1 check
Sep 6, 2026: Unavailable
HTTP 400
2 bad responses
2 checks
Sep 7, 2026: Unavailable
HTTP 400
1 bad response
1 check
Sep 8, 2026: Unavailable
HTTP 400
2 bad responses
2 checks
Sep 9, 2026: Unavailable
HTTP 400
1 bad response
1 check
Sep 10, 2026: Unavailable
HTTP 400
1 bad response
1 check
Sep 11, 2026: Unavailable
HTTP 400
1 bad response
1 check
Sep 12, 2026: Unavailable
HTTP 400
2 bad responses
2 checks
Sep 13, 2026: Unavailable
HTTP 400
1 bad response
1 check
Sep 14, 2026: Unavailable
HTTP 400
1 bad response
1 check
Sep 15, 2026: Unavailable
HTTP 400
2 bad responses
2 checks
Sep 16, 2026: Unavailable
HTTP 400
2 bad responses
2 checks
Sep 17, 2026: Unavailable
HTTP 400
2 bad responses
2 checks
Sep 18, 2026: Unavailable
HTTP 400
1 bad response
1 check
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
Oct 16, 2026: Unavailable
HTTP 400
2 bad responses
2 checks
Oct 17, 2026: Unavailable
HTTP 400
1 bad response
1 check
Oct 18, 2026: Unavailable
HTTP 400
1 bad response
1 check
Oct 19, 2026: Unavailable
HTTP 400
1 bad response
1 check
Oct 20, 2026: Unavailable
HTTP 400
1 bad response
1 check
Oct 21, 2026: Unavailable
HTTP 400
1 bad response
1 check
Oct 22, 2026: Unavailable
HTTP 400
1 bad response
1 check
Oct 23, 2026: Unavailable
HTTP 400
1 bad response
1 check
Oct 24, 2026: Unavailable
HTTP 400
1 bad response
1 check
Oct 25, 2026: Unavailable
HTTP 400
1 bad response
1 check
Oct 26, 2026: Unavailable
HTTP 400
1 bad response
1 check
Oct 27, 2026: Unavailable
HTTP 400
1 bad response
1 check
Oct 28, 2026: Unavailable
HTTP 400
1 bad response
1 check
Oct 29, 2026: Unavailable
HTTP 400
1 bad response
1 check
Oct 30, 2026: Unavailable
HTTP 400
1 bad response
1 check
Oct 31, 2026: Unavailable
HTTP 400
1 bad response
1 check
Nov 1, 2026: Unavailable
HTTP 400
1 bad response
1 check
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
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
PatientCoverageExplanationOfBenefit
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.
BundleOperationDefinitionOrganizationPractitionerStructureDefinition