Public surface / Payer Patient Access APIs
Florida Blue Patient Access API (CMS Interoperability conformance endpoint)
This endpoint declares a solid public surface with minor gaps.
Observed surface
- Base URL
https://apigw.bcbsfl.com/interop/interop-developer-portal/cms/iop/v1/R4- Category
- Payer Patient Access APIs
- Availability
- answered 45 of the last 45 daily checks (100%)
- Last answered
- 2026-10-03 (answered on this run)
- Vantage agreement
- reachable from all 3 vantages, which are 3 hosts on one network (github-actions): one network's view sampled 3 times, not 3 independent networks
What each vantage saw
| Vantage | Result | What it saw | Condition |
|---|---|---|---|
github-actions/macos-latest | reached | answered in 486 ms | HTTP 200 |
github-actions/ubuntu-latest | reached | answered in 1181 ms | HTTP 200 |
github-actions/windows-latest | reached | answered in 875 ms | HTTP 200 |
Vantages on one network are one network’s view sampled several times. A rule applied to that network’s address space reaches every one of them at once and reads exactly like agreement.
Interpretation
A grade describes two public discovery documents at one point in time. It does not inspect patient data, authenticated behavior, or clinical quality.
Read the scoring method →This endpoint's full report: what was observed, what was not, and what would change it →
What its CapabilityStatement declares, resource by resource →
Findings
Observed since 2026-08-20; no changes to declared capability recorded.
Declared app-to-server access
What the endpoint's own documents declare about app-to-server access, observed on this run. Nothing here was requested or exercised, and none of it is graded. An absent field is reported as absent, not as a refusal: a document that does not mention a field has not said anything about it.
| Question | Answer | What the document says | Where it is declared |
|---|---|---|---|
| Declares private_key_jwt client authentication at the token endpoint | not retrieved on this run | the SMART discovery document was requested and not served on this run | SMART discovery: token_endpoint_auth_methods_supported |
| Declares the client_credentials grant, which SMART Backend Services uses | not retrieved on this run | the SMART discovery document was requested and not served on this run | SMART discovery: grant_types_supported |
| Declares the client-confidential-asymmetric capability | not retrieved on this run | the SMART discovery document was requested and not served on this run | SMART discovery: capabilities |
| Declares system-level scopes | not retrieved on this run | the SMART discovery document was requested and not served on this run | SMART discovery: scopes_supported |
| Declares an export operation | not listed | 27 operations are declared and none is named export | CapabilityStatement: rest.operation and rest.resource.operation |
| Instantiates the Bulk Data Access implementation guide | not listed | 0 canonicals are instantiated and none is Bulk Data's | CapabilityStatement: instantiates |
Registry provenance
How this entry was verified
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.
This is an observational snapshot of a public, unauthenticated surface. It is not an audit, a ranking of care quality, or a statement about anyone's regulatory compliance. See how we grade.
Every observation on record for this endpoint, with the dates it answered and the dates it did not.