Qualified health plan (QHP) filings do not exist in one system. They move through a connected process involving CMS, state divisions of insurance, SERFF, HIOS and MPMS. Each has a different role, and the handoffs between them are often where filings slow down, data falls out of sync or teams lose visibility.
In this episode of Regulatory Joe, ClearFile President Joe Boyle breaks down how QHP filing data moves from submission to certification, where issuers often get tripped up and what teams need to maintain across systems throughout the year.
How SERFF, HIOS and MPMS Shape the QHP Filing Process
The QHP filing process has several core players:
- Centers for Medicare & Medicaid Services (CMS) sets the federal rules and governs the federal marketplace.
- State divisions of insurance review and certify filings at the state level.
- SERFF, governed by the NAIC, is where many issuers submit directly to their states
- HIOS is the federal system where issuer data is maintained, and MPMS is the HIOS module issuers use for QHP application validation, cross-validation, and CMS submission.
Each of these systems plays a distinct role, but they are not independent. Data moves through them in sequence, and understanding that flow is what separates a smooth filing cycle from one full of avoidable delays.
Where QHP Filing Risk Builds Between Systems
The biggest QHP filing risks often show up between systems, not inside one template.
A binder may be submitted in SERFF, but plan data still has to be transferred into the CMS environment before issuers can fully validate and manage it in HIOS and MPMS. If teams assume that handoff has happened automatically, they can lose time confirming visibility, resolving errors or responding before a deadline.
The same issue applies to Plan Finder Product Data Collection and system access. Company information, issuer administrator details and account ownership need to stay current so filing data matches across systems and regulators can reach the right people when it matters.
QHP filing readiness is not just about completing the required documents. It is about making sure the systems, data and people behind the filing are aligned before filing activity intensifies.
Recommendations for ACA Issuers Managing QHP Filings
- Map a filing pathway for each state. Know where each filing begins, which systems are involved, and how the data needs to move before certification.
- Track plan transfer separately from SERFF submission. A binder submission does not automatically mean plan data is available in HIOS. Build plan transfer into the filing calendar as its own step.
- Use MPMS validation and cross-validation intentionally. Treat validation and cross-validation as separate checkpoints so teams can identify and resolve issues before they create downstream filing problems.
- Review Plan Finder Product Data Collection before filing season. Confirm that company information, issuer administrator data, legal names, DBA information and tax IDs are accurate and consistent with SERFF.
- Start company setup early for new markets or brand changes. HIOS updates take time. Handle company setup during product strategy planning, not when the filing window is already compressed.
- Audit system access and account ownership. Run SERFF account reports, review state portal access and confirm CMS/HIOS account status so the right people receive the right filing communications.
