Is one employee enough to trigger state insurance regulation?

Is one employee enough to trigger state insurance regulation?

Historically, fully insured group health plans have been regulated by the state where the policy is sitused—usually the employer’s home state. That state’s insurance mandates apply, and other states typically defer.

But as remote work and multistate workforces become the norm, that framework is being tested.

In BlueCross TN v. Nicolopoulos, a New Hampshire employee was denied fertility treatment coverage under a Tennessee-sitused ERISA plan. The catch? New Hampshire mandates fertility coverage. Tennessee does not.

New Hampshire regulators tried to enforce their mandate—even though the policy was issued in Tennessee and the insurer isn’t licensed in New Hampshire.

The Sixth Circuit upheld the regulator’s authority under ERISA’s “saving clause”, finding that the enforcement targeted BlueCross as an insurer, not a fiduciary. But the court did not decide whether New Hampshire actually had jurisdiction over BlueCross—it left that door open for the insurer to argue in state proceedings.

So we’re still left with some big questions:

• What does it mean to “engage in the business of insurance” in a state?

• Is covering just one employee in a state enough for that state to assert jurisdiction?

• If so, what’s the scope of state power over group insurance in the multistate era?

This isn’t the sky falling—but it may signal a shift.

If more states assert jurisdiction based on where covered lives reside, insurers may face a patchwork of benefit mandates beyond situs. And that could affect plan design, pricing, and predictability for multistate employers.

For now, self-funded plans remain largely shielded by ERISA preemption. But for fully insured plans, it may be time to revisit how “local” regulation really is.

What impacts would this have on the group insurance market?