Single-endpoint report

Florida Blue Patient Access API (CMS Interoperability conformance endpoint): endpoint report

Everything this project observed about this one endpoint, everything it did not observe, and what would change the result. Free to read, link, print and hand on; there is nothing here behind a sign-in and nothing to buy.

Built to print. Use your browser’s print or “Save as PDF” to keep a dated copy; the page carries its own address and observation date.

What was observed, and what was not

This report covers 9 checks. 9 ran. 0 were asked from every reporting vantage and answered by none. 0 were never asked, because nothing was retrieved for them to read. The three are different facts and none of them is a zero: a check that did not run publishes no number, no mark against this endpoint, and nothing below to act on.

What would change this

Ordered by the points each would recover. Every item below comes from a check that actually ran on this run; nothing derived from a check that did not run appears here. The three dimensions are weighted, so recovering points does not guarantee a different letter — how we grade gives the weights.

1. Publish .well-known/smart-configuration at the base URL, carrying at least authorization_endpoint and token_endpoint.

   Worth up to 35 of the 100 points in Interop readiness.

   This run observed: SMART .well-known/smart-configuration absent or incomplete

   I2: what this check isSpec ↗

If this does not match what you see

Every number here describes two public documents at one moment, read from the vantages listed above. If it does not match what you serve, the difference is worth knowing.

Correct or dispute this record. There is no sign-in, no fee, and nothing to buy: this report is free to read, link, print and hand on, and this project collects nothing about the people who read it.

Where this came from

live CapabilityStatement fetch (fhirVersion 4.0.1, HAPI FHIR Server 5.4.1.12_edfx, 24 rest resources). The base is the server URL plus the /R4/metadata route printed together in the OpenAPI spec Florida Blue's own developer portal embeds for its 'CMS Interoperability Patient Access Metadata' product, whose page says the Florida Blue Capability Statement endpoint for the CMS Interoperability APIs is accessed via that route. Florida Blue publishes its conformance document on a different base than its OAuth-gated member-data base (which answers 401 to an unauthenticated GET of /metadata and is in the candidate log); the entry is the base that serves the document this project grades. The document's implementation.url names an internal Edifecs host, so attribution rests on Florida Blue printing this base in its own portal. The portal covers the corporate family: its own disclaimer says HMO coverage is offered by Health Options Inc., DBA Florida Blue HMO, and no separate HMO endpoint is published (recorded 2026-08-19). No later re-check is recorded, so the date above is the last time anyone checked this entry against the live endpoint.

The same run, as data: this endpoint's JSON, what its CapabilityStatement declares, resource by resource, and every observation on record for it, with the dates it answered and the dates it did not.