What Happens After You Submit to HPMS

The Review Process Is Not a Black Box

Most Medicare Advantage plans experience the post-submission period as an extended silence punctuated by either an approval or a deficiency notice. The silence is not CMS inactivity — it is a multi-stage review process that follows a predictable sequence. Plans that understand that sequence can take concrete actions during the review window to improve their outcomes. Plans that don't are reactive by design, responding to findings rather than anticipating them.

The CMS network adequacy review process has five identifiable stages, each with a different mechanism, a different risk surface, and a different set of plan-side actions that can influence the outcome. Walking through them explicitly demystifies a process that generates unnecessary anxiety through opacity.

Stage One: HPMS Automated Validation

The first pass after submission is automated. HPMS checks for structural completeness and data integrity: are all required HSD table rows present, are NPI formats correctly structured, are specialty codes from the valid taxonomy, does the submission include every county in the plan's service area, and are required attestations complete. This stage does not evaluate adequacy — it evaluates whether the submission is processable.

Failures at this stage generate system-level flags that are returned to the plan before any analyst review begins. Common triggers include missing HSD rows for required specialties, malformed NPI entries, and county coverage gaps where the plan's filed service area doesn't match its HPMS enrollment data. These are fixable, but fixing them takes time — time that compresses the remaining review window.

The practical implication is straightforward: validate your HSD table against NPPES and your county coverage against your current service area enrollment before you submit. HPMS's automated validation is running the same basic data integrity checks that you can run yourself with a pre-submission audit. Plans that arrive at submission with clean data clear this stage quickly and move to analyst review without losing days to correction cycles.

Stage Two: NPPES Cross-Reference and Provider Verification

Once automated validation clears, CMS analysts cross-reference the providers in your HSD table against NPPES — the National Plan and Provider Enumeration System — and PECOS, the Medicare enrollment database. The purpose is to verify active enrollment status, practice specialty, and location. Providers who have retired, moved, changed their enrollment specialty, or lost active Medicare enrollment are identified at this stage.

This is where stale provider data surfaces as a direct adequacy problem. A provider who was practicing in a county at your last data refresh but has since relocated creates a time-distance failure in that county. A provider whose NPPES specialty designation doesn't match the specialty you've listed in your HSD table creates a coverage gap in that specialty. The NPPES record is the ground truth that CMS uses — not your internal provider directory, not the provider's attestation, and not the contract itself.

Plans should run a full NPPES cross-reference on their HSD table no earlier than 30 days before submission. Provider records change continuously. An NPPES check from six months prior is not reliable enough to catch the drift that matters at submission.

Stage Three: Time-Distance Model and County Flagging

After provider verification, CMS runs the time-distance calculation against its county-type thresholds. For each required specialty in each county, the model identifies whether your nearest verified in-network provider meets the applicable distance and travel time standard. The standard varies by county type — urban, suburban, rural, and frontier counties have different thresholds — and by specialty within county type.

Counties that fail the time-distance test are flagged for analyst review. The flag is not a deficiency finding — it is a signal that the county requires human evaluation. Counties can clear the flag through telehealth provider arrangements (where applicable), approved exception documentation, or analyst judgment about alternative access. But flagged counties receive attention, and the quality of your documentation determines how that attention resolves.

During the review period, CMS contractors may conduct secret shopper calls to providers listed in marginal counties. A provider who answers that they are not accepting new Medicare Advantage patients, are not contracted with your plan, or are no longer practicing at the listed location creates an immediate adequacy problem regardless of your HSD table. Plans operating in borderline counties should verify that their listed providers are answering correctly before and during the review period.

Stage Four: Analyst Review, Exception Evaluation, and Preliminary Findings

Human analysts review flagged counties against the plan's submitted exception documentation, telehealth arrangements, and prior filing history. Plans with well-organized exception files — documented outreach logs, provider response records, evidence of alternative access arrangements — move through this stage faster and with better outcomes than plans that submitted sparse or poorly organized documentation.

Preliminary findings are communicated to the plan through HPMS notifications. This is the moment when plans learn which counties have generated adequacy concerns and have their first opportunity to respond with additional evidence. The response window is typically 30 to 45 days. Plans that have anticipated which counties might generate flags — and have prepared additional documentation in advance — can respond quickly and substantively. Plans assembling documentation from scratch during the response window are working from a deficit.

The Operational Checklist for the 45–90 Day Window

The review period is not passive time. There are concrete actions that improve outcomes:

• Monitor HPMS notifications actively. Notifications about data flags, analyst questions, and preliminary findings appear in HPMS. They should be checked at least weekly — preferably every business day during the review period. A notification that sits unread for two weeks costs you response time on a fixed clock.
• Keep provider data current. If a provider in your network changes their status during the review period — retiring, relocating, terminating the contract — update your records and notify your compliance team immediately. A provider valid at submission who is unreachable during secret shopper calls creates a deficiency regardless of the submission data.
• Pre-stage exception documentation for flagged counties. Based on your own pre-submission time-distance analysis, identify the counties you consider marginal and have your exception documentation organized before HPMS surfaces a notification about them. Responding to a preliminary finding in five days is much stronger than responding in twenty-five.
• Run your own spot-check calls. Before and during the review period, call providers in borderline counties to verify they are answering correctly about accepting new MA patients and their contracted status. Fix discrepancies before a secret shopper call surfaces them.

The 45–90 day review window is your last opportunity to influence the determination before a deficiency notice issues. Plans that treat it as passive waiting are ceding that opportunity entirely.

The final determination — approval or deficiency notice — reflects the quality of both the submitted data and the plan's behavior during the review window. Submission is not the finish line. It is the beginning of an active review management period that rewards preparation and attention.