By Melissa Harbert Miskell, Solution Advisor at Revecore
The baby was delivered. The mother’s insurance paid. The newborn’s own claim came back denied or paid at the wrong rate. And your team may not have caught it.
Most states allow newborns to be covered under the mother’s policy for approximately 30 days following delivery. Under federal law, group health plans must allow at least a 30-day special enrollment window for a newborn, with coverage retroactive to the date of birth if enrollment is timely requested. But that grace period is conditional. If the newborn isn’t formally enrolled within the required timeframe, the payer’s obligation to cover post-delivery claims can evaporate retroactively. NICU stays, readmissions, and professional claims billed under the mother’s member ID after the baby is assigned their own ID are among the highest-risk accounts — often billed correctly in the moment and only flagged later, after the window has passed.
The Rule That Changes Everything: Fully Insured vs. Self-Funded
One of the most important distinctions revenue cycle teams miss is whether the plan is fully insured or self-funded. Fully insured plans are governed by state law — including state-specific enrollment windows and COB mandates. Self-funded plans are governed by ERISA. As the Employee Benefit Research Institute notes, self-funded private sector plans are not subject to state health insurance laws, including coverage mandates and certain consumer protections — a consequence of ERISA’s preemption clause.
That means a self-funded employer plan may legally impose shorter enrollment windows or different COB sequencing rules than your team assumes, and there’s no state regulator to appeal to when it does.
When both parents carry coverage, COB sequencing adds another layer. Most fully insured plans follow the NAIC Coordination of Benefits Model Regulation, which establishes the widely used “birthday rule”: the plan of the parent whose birthday falls earlier in the calendar year is primary for the child. But self-insured plans are not subject to state COB mandates under ERISA preemption, which means they may follow different sequencing logic, or none at all. Getting COB wrong at submission doesn’t just produce a denial. It produces a denial that requires resequencing, re-verification, and resubmission — multiplying the cost of the original error.
This Isn’t Just One State’s Problem
New York’s rules make a useful reference point, but the underlying dynamic exists everywhere. Every state has its own enrollment window requirements, dependent coverage mandates, and COB sequencing rules. According to the U.S. Department of Labor, marketplace plans allow up to 60 days for newborn enrollment; employer-based plans operate under the federal 30-day floor, with some states extending that window further. And self-funded plans operate outside state mandates entirely regardless of where the employer is located.
The accounts that generate the most exposure are predictable: NICU stays, readmissions within 30 days of delivery, and any claim where COB sequencing wasn’t validated before submission. The broader denial environment only heightens the stakes — the AHA has reported that hospitals spent $43 billion in 2025 trying to collect payments from insurers for care already delivered. The challenge for most organizations is the absence of a structured workflow that catches these accounts on a defined timeline, every time.
How Revecore Supports
Revecore works with more than 1,300 hospitals and health systems nationwide. That scale creates network intelligence that no individual organization can replicate. When a payer begins applying enrollment timing rules more aggressively, or a COB pattern shifts without formal notice, we see it across the network before most systems have enough data to recognize the trend. Our clients benefit from that network effect.
We work newborn COB exposure through two pathways:
- Open Balance Denial Solution: COB-related denials — dependent not enrolled, member ID mismatches, sequencing errors — are worked, corrected, and resubmitted within timely filing windows, with the root cause addressed so the account doesn’t recycle.
- Specialty Review — COB Zero Balance (Underpayment) Opportunities: Not all COB errors produce a denial. Some produce underpayments, which are accounts that close as paid but were reimbursed at the wrong rate because the secondary was never billed or the primary’s adjudication was accepted without validation. Our specialty review identifies and pursues these zero-balance accounts.
While Newborn COB is one example, the underlying exposure it reveals isn’t unique to this claim type. Enrollment timing gaps, fully insured versus self-funded misclassification, and COB sequencing errors surface across many areas of the revenue cycle. When the workflow isn’t built to catch them, they don’t announce themselves. They close as paid, sit in a denial queue without pattern recognition, or recycle without root cause resolution. The organizations that close the newborn gap often find it’s the first of several. And that the clock was running on more than one account. That’s exactly the kind of signal Revecore is built to catch, and the kind of infrastructure we help our partners build, so the next gap doesn’t go undetected for as long as the last one did.

