Insurance, Benefit-Design, and Access-Policy Exposures

Definition and scope

Time-specific definitions of coverage and access rules such as copays, prior authorization, step therapy, or insurance transitions, separating policy eligibility from actual enforcement, receipt, and care use. The target population, use, and analysis remain protocol decisions; this card explains the choices and their consequences rather than approving a study.

Operational specification

Specify the decision authority, plan/product, employer or geography, announcement and effective dates, affected population, benefit details, grandfathering/exemptions, enforcement, and concurrent policy changes. Keep benefit exposure separate from medical/pharmacy data observability and actual care access; moving plans can change both the intervention and what is recorded.

Analysis and diagnostics

Construct a policy timeline and eligible population before outcomes, document staggered adoption and anticipation, and choose a credible comparison/design. Assess composition changes, enrollment selection, secular trends, provider behavior, spillover, and whether parallel-trends or discontinuity assumptions are supported. Report policy-level and patient-level denominators separately.

When NOT to use and common errors

Do not treat a plan label as a complete benefit definition, assign exposure by a future denial or appeal, equate a missing claim with denial of needed care, or infer a policy effect from an uncontrolled pre/post trend.

Worked example and implementation boundary

A synthetic policy applies to 800 of 1000 enrolled members at its effective date. Calculate eligibility coverage, without assuming all eligible people seek or receive the affected treatment. Policy eligibility coverage is 0.80. Treatment uptake, access failures, and health effects require separate measures. The code performs that explicitly stated calculation with synthetic inputs. It is not a complete fitted analysis and does not demonstrate the identification assumptions, estimate sampling uncertainty, or certify application in another population.

Data-source and reporting requirements

Preserve the provenance, dates, units, and observation rule for each input. Claims capture services and transactions under observable benefits; absence of a record is not proof that an event or resource use did not occur. EHR and registry measurements depend on the collection process and may miss care outside the system. Linked sources add reconciliation and selection questions. Primary collection can improve a missing domain but still requires valid measurement and follow-up. Report which of these limitations affects the stated use, which evidence supports the chosen inputs, and what remains uncertain.

Worked example

Scenario

A synthetic policy applies to 800 of 1000 enrolled members at its effective date. Calculate eligibility coverage, without assuming all eligible people seek or receive the affected treatment.

Dataset

Synthetic inputs with units defined in the scenario; no patient data.

Steps

Result

Policy eligibility coverage is 0.80. Treatment uptake, access failures, and health effects require separate measures.

Trade-offs

Code example

policy_eligible = 800
enrolled = 1000
result = policy_eligible/enrolled
assert abs(result - 0.8) < 1e-9
print(result)

policy_eligible <- 800
enrolled <- 1000
result <- policy_eligible/enrolled
stopifnot(abs(result - 0.8) < 1e-9)
print(result)

data worked_example;
  policy_eligible = 800;
  enrolled = 1000;
  result = policy_eligible/enrolled;
  put result=;
run;

Citations

1. [1]Skivington K, et al. A new framework for developing and evaluating complex interventions: update of Medical Research Council guidance. BMJ. 2021.
2. [2]Hernán MA, Robins JM. Using big data to emulate a target trial when a randomized trial is not available. American Journal of Epidemiology. 2016;183(8):758-764.