ERISA and Self-Insured Employer Health Plans in RWE
Employer-sponsored health plan arrangements governed by ERISA, including self-insured plans where the employer bears claim risk and plan design, reporting, carve-outs, and state-regulatory exposure differ from fully insured plans.
In plain language
ERISA is the federal law behind many employer health plans. In self-insured plans, employers carry the claim risk and often use vendors to administer benefits. That can make commercial claims incomplete or different across employers.
ERISA shapes US employer-sponsored health benefits and therefore shapes commercial claims data. In a fully insured plan, an insurer bears the claim risk subject to state insurance regulation. In a self-insured plan, the employer generally bears the claim risk and may use an administrator or insurer for network and claims operations. ERISA preemption and reporting rules make self-insured employer plans operationally different from fully insured products.
For RWE, self-insured status matters because plan design, covered benefits, network breadth, formulary design, carve-outs, stop-loss arrangements, and claims completeness can differ. A large self-insured employer may carve out pharmacy, behavioral health, fertility, or specialty benefits to separate vendors. A commercial database sourced from one administrator may therefore miss services handled by another vendor.
Analysts should not treat commercial claims as a homogeneous payer channel. ERISA/self-insured plan structure can drive selection, observability, benefit generosity, and job-related enrollment churn. Employer and plan identifiers, if available, should be used carefully for clustering, subgroup diagnostics, and benefit-completeness checks.
Pros, cons, and trade-offs
ERISA and self-insured plan metadata help explain why two commercial claims cohorts can have different benefit completeness, treatment access, cost sharing, and enrollment churn. This is valuable for data-fitness assessment and payer-channel interpretation. The trade-off is that ERISA status is legal and administrative context, not a patient-level clinical exposure. It can be hard to observe directly in vendor data, and plan funding may be confounded with employer size, industry, geography, workforce composition, and benefit generosity.
When to use
Use ERISA/self-insured plan information when plan funding, administrator structure, state mandate exposure, carve-outs, stop-loss arrangements, or employer-level clustering can affect exposures, outcomes, costs, or missing benefit channels. It is most useful in commercial claims studies where employer/plan metadata are available.
When NOT to use - and when it is actively misleading
Do not use ERISA as if it were a clinical characteristic of the patient. Do not assume every commercial plan is fully insured or every self-insured plan has complete integrated medical and pharmacy data. It is actively misleading to compare plan groups without checking whether carved-out benefits or administrator splits change what the dataset can observe.
Worked example
Scenario
A commercial database includes two employer groups. Employer A is fully insured with integrated medical and pharmacy claims. Employer B is self-insured under ERISA with medical claims administered by one vendor and pharmacy carved out to a PBM not present in the extract.
Dataset
Plan funding and benefit observability by employer group.
| employer_group | funding_type | medical_claims | pharmacy_claims | rwe_implication |
|---|---|---|---|---|
| A | fully insured | present | present | exposure and outcomes observable |
| B | self-insured | present | missing carve-out | pharmacy exposure/adherence invalid unless PBM feed is linked |
Steps
Use plan metadata to identify funding arrangement and administrators.
Profile required benefit channels before building exposure and cost endpoints.
Stratify or exclude employer groups with missing carved-out services for affected analyses.
Cluster standard errors or sensitivity-test by employer/plan when benefit design drives treatment choice.
Result
Employer B can contribute to medical-outcome analyses but not pharmacy-exposure or adherence analyses unless the carved-out PBM data are added.