Curated cohort / fixed public roster
Florida marketplace issuer cohort
The Patient Access and Provider Directory APIs of every issuer selling an individual-market qualified health plan on HealthCare.gov in Florida for 2026, graded on the same public surfaces as every other endpoint here.
15organizations reviewed
9published a base URL we could verify
17endpoints listed
15answered on this run
9 of 15 member organizations publish a FHIR base URL this project could verify from public documentation, which is a curation record with a date on it, not a live figure; 17 verified endpoints are listed below. Of those, 15 answered when this page was generated, which is the measured number: it comes from this run's probes, and it moves when the endpoints do. The rest of the roster is recorded with the reason it could not be listed, because for a cohort whose membership is public and finite, the gap is itself a finding.
Membership is CMS's own file, not a list assembled here. The QHP Landscape PY2026 Individual Medical dataset published by the Center for Consumer Information and Insurance Oversight lists every plan sold on HealthCare.gov; filtered to Florida it carries 7,569 plan-county rows, 16 HIOS issuer IDs, and 15 issuer names. The unit of analysis is the issuer organization CMS names, so the denominator is 15: one name, Ambetter Health, carries two HIOS IDs. The per-issuer rows are committed beside this file in florida-marketplace.roster.csv, so the denominator can be recomputed from data rather than trusted from prose.
Florida is a federally-facilitated exchange state, the same prong of CMS-9115-F as the Texas cohort: 45 CFR 156.221 reaches qualified health plan issuers on the federal exchanges, so every organization on this roster is an impacted payer through this line of business alone. Florida is the largest HealthCare.gov market in the country, which is why it is the frame's second state.
The roster names corporate siblings separately and this cohort keeps them separate. Florida Blue and Florida Blue HMO are one GuideWell family selling under two licenses (the HMO is Health Options Inc.), and Cigna Healthcare and Cigna HealthCare of Florida, Inc. are two Cigna entities. The unit stays the name CMS prints, because collapsing them would substitute this project's corporate-structure judgment for the regulator's enumeration; each pair shares its family's published endpoints, and a reader who collapses the pairs gets 13 organizations the other way.
Where a member's endpoints are its national parent's, the parent's documentation covers the Florida line by brand or by plan type, never by state: Cigna's Patient Access documentation covers 'Individual Family Plans governed by CMS', Wellpoint is a brand row in Elevance's Interoperability API Endpoint Support Document (IO105 v15.0), and UnitedHealthcare's documentation names no line of business at all. The word 'Florida' appears in none of them, which is recorded here because attribution by brand is weaker than attribution by state and a reader should know which one they are getting.
The rule requires the API. It does not require an issuer to print its base URL where an unregistered visitor can read it, and nothing on this page treats an issuer that does not as being out of compliance with anything. What a missing base URL costs is narrower and worth naming exactly: conformance stops being checkable by anyone who has not already entered a business relationship with the issuer.
Every count on this page distinguishes what an issuer publishes from what answers. A published base URL that returns 404, an expired certificate in front of a maintenance page, and a portal that shows an unregistered visitor an empty shell are three different findings, and each member's record says which one it is.
Membership sources
- CMS / CCIIO: QHP Landscape PY2026 Individual Medical (individual_market_medical.zip, issued 2026-08-04, modified 2026-08-10) (retrieved 2026-08-19)
Listed endpoints
| Plan | Programs | Endpoint | Category | Grade |
|---|---|---|---|---|
| 22 Health (Community Care Plan) | Florida individual marketplace (HealthCare.gov) | 22 Health (Community Care Plan) Patient Access API | Payer Patient Access APIs | C |
| 22 Health (Community Care Plan) | Florida individual marketplace (HealthCare.gov) | 22 Health (Community Care Plan) Provider Directory API | Payer Provider Directory APIs | A |
| AmeriHealth Caritas Next, Florida | Florida individual marketplace (HealthCare.gov) | AmeriHealth Caritas Next (Florida) Patient Access API | Payer Patient Access APIs | B |
| AmeriHealth Caritas Next, Florida | Florida individual marketplace (HealthCare.gov) | AmeriHealth Caritas Next (Florida) Provider Directory API | Payer Provider Directory APIs | C |
| AvMed (Sentara) | Florida individual marketplace (HealthCare.gov) | AvMed Patient Access API | Payer Patient Access APIs | B |
| AvMed (Sentara) | Florida individual marketplace (HealthCare.gov) | AvMed Provider Directory API | Payer Provider Directory APIs | not observed |
| Cigna Healthcare | Florida individual marketplace (HealthCare.gov) | Cigna Patient Access API | Payer Patient Access APIs | A |
| Cigna Healthcare | Florida individual marketplace (HealthCare.gov) | Cigna Provider Directory API | Payer Provider Directory APIs | A |
| Cigna HealthCare of Florida, Inc. | Florida individual marketplace (HealthCare.gov) | Cigna Patient Access API | Payer Patient Access APIs | A |
| Cigna HealthCare of Florida, Inc. | Florida individual marketplace (HealthCare.gov) | Cigna Provider Directory API | Payer Provider Directory APIs | A |
| Florida Blue (BlueCross BlueShield FL) | Florida individual marketplace (HealthCare.gov) | Florida Blue Patient Access API (CMS Interoperability conformance endpoint) | Payer Patient Access APIs | A |
| Florida Blue (BlueCross BlueShield FL) | Florida individual marketplace (HealthCare.gov) | Florida Blue Provider Directory API (CMS Interoperability conformance endpoint) | Payer Provider Directory APIs | A |
| Florida Blue HMO (Health Options Inc.) | Florida individual marketplace (HealthCare.gov) | Florida Blue Patient Access API (CMS Interoperability conformance endpoint) | Payer Patient Access APIs | A |
| Florida Blue HMO (Health Options Inc.) | Florida individual marketplace (HealthCare.gov) | Florida Blue Provider Directory API (CMS Interoperability conformance endpoint) | Payer Provider Directory APIs | A |
| UnitedHealthcare | Florida individual marketplace (HealthCare.gov) | UnitedHealthcare Provider Directory API | Payer Provider Directory APIs | C |
| Wellpoint (Elevance Health) | Florida individual marketplace (HealthCare.gov) | Wellpoint Patient Access API | Payer Patient Access APIs | not observed |
| Wellpoint (Elevance Health) | Florida individual marketplace (HealthCare.gov) | Elevance Health shared Provider Directory API | Payer Provider Directory APIs | C |
Grades are comparable within a category only: a Patient Access API and a Provider Directory API answer to different expectations and are never ranked against each other.
Members reviewed and not listed
Each exclusion records how far the review went, on what date, and where to check it. A review that found nothing is not proof that nothing exists: if one of these plans publishes a base URL we missed, please tell us.
| Plan | Programs | Why it is not listed |
|---|---|---|
| Ambetter Health (Centene / Sunshine Health) | Florida individual marketplace (HealthCare.gov) | the issuer's own interoperability page describes both APIs and prints no base URL for either, directing developers to Centene's Partner Portal, which serves a 1,128-byte single-page-app shell with no API content to an unregistered visitor - the same posture, byte for byte, as the Texas Ambetter brand's (the plan's own documentation was reviewed, 2026-08-19; source) |
| Capital Health Plan | Florida individual marketplace (HealthCare.gov) | the issuer's only interoperability page says CHP has contracted with 1Up Resources to manage both APIs and prints no base URL; every 'FHIR API' link on it lands on the vendor's generic FHIR education page, which prints none either and never mentions CHP. The page itself notes that the mandate requires this information to be publicly available (the plan's own documentation was reviewed, 2026-08-19; source) |
| Florida Health Care Plans | Florida individual marketplace (HealthCare.gov) | the issuer's third-party API page says FHCP has contracted with mPulse to manage and support both APIs and prints no base URL; the vendor's public documentation prints only multi-tenant HealthTrio hosts with no FHCP identifier anywhere, and those hosts reject the standard FHIR media type, answering 406 to an Accept: application/fhir+json request for /metadata (the plan's own documentation was reviewed, 2026-08-19; source) |
| Health First Commercial Plans, Inc. (Health First Health Plans) | Florida individual marketplace (HealthCare.gov) | the issuer's developer documentation says Health First Health Plans has partnered with Epic for its interoperability solution and prints no base URL, linking only to Epic's generic developer pages; neither documentation page mentions a Provider Directory API at all. Epic's public endpoint directory prints a 'Health First' row that answers, but nothing connects that row to this issuer beyond the shared name, and a vendor's directory row is the attribution this registry excludes (the plan's own documentation was reviewed, 2026-08-19; source) |
| Molina Healthcare | Florida individual marketplace (HealthCare.gov) | the issuer's developer portal - an Azure API Management instance operated by Cognizant TriZetto - names 'FL - Molina Healthcare' in its servicing list and prints no hostname anywhere; the API list it serves an unregistered visitor renders no API entries, only portal chrome, and its 47-page product documentation PDF is generic vendor material containing no occurrence of 'Molina' and no absolute base URL (the plan's own documentation was reviewed, 2026-08-19; source) |
| Oscar Health Maintenance Organization of Florida | Florida individual marketplace (HealthCare.gov) | the issuer's member and developer pages describe the Patient Access API as delegated to 1upHealth and print no endpoint; reaching one requires creating a 1upHealth developer account. No Provider Directory API documentation exists anywhere on hioscar.com: its complete sitemaps hold only the two patient-access pages and their Spanish variants (the plan's own documentation was reviewed, 2026-08-19; source) |
Observational snapshots of public discovery surfaces. Not audits, not compliance determinations, and not statements about care quality. Publishing a base URL to unregistered visitors is not required by any rule this project reads, and a plan that does not is not violating anything; it is only not independently checkable from outside.