ENCePP Checklist for Study Protocols

What it is

The ENCePP Checklist for Study Protocols (Revision 4, 2018) is a methodological protocol-completeness checklist maintained by the European Network of Centres for Pharmacoepidemiology and Pharmacovigilance (ENCePP), a network coordinated by the European Medicines Agency (EMA). It is not a manuscript reporting checklist and not a risk-of-bias score: it is a pre-specification prompt list that walks a protocol author through the epidemiological decisions that determine whether a non-interventional study can yield credible causal or descriptive evidence — research question, study design, data source, exposure and outcome definitions, bias and confounding control, analysis, data management, and quality assurance. Its purpose, in ENCePP's own words, is to encourage researchers to reflect on important epidemiological principles, to promote transparency about the methods actually used, and to keep protocols aligned with contemporary methodological standards. The Checklist is the operational companion to the ENCePP Guide on Methodological Standards in Pharmacoepidemiology (the narrative standards reference): the Guide explains how to do each step well; the Checklist forces you to confirm, item by item, that the protocol addresses it.

When to use

Apply the ENCePP Checklist at the protocol stage, before data access and before any analysis. It is mandatory as a signed annex for EMA-imposed Post-Authorisation Safety Studies (PASS) under the GVP Module VIII regime, and it is required for any study seeking the ENCePP Study seal registered in the EU PAS Register (HMA-EMA Catalogues). It is strongly recommended for voluntary PASS, drug-utilisation studies, and comparative safety/effectiveness cohort or case-control studies built on routinely collected European data. Decision rules versus siblings in this catalog: (1) Use the ENCePP Checklist when you need a completeness gate on the protocol and a regulatory deliverable; use the `encepp-guide` (ENCePP Methodological Standards Guide) when you need the substantive methodological reasoning behind a choice — they are paired, not interchangeable. (2) Use `harper` (HARmonized Protocol Template) or `start-rwe` when you need a structured protocol template with prescribed tables and a causal-roadmap layout — the ENCePP Checklist verifies coverage but does not supply the protocol skeleton, so the common pattern is HARPER/START-RWE to draft and the ENCePP Checklist to certify. (3) Use `record-pe` or `strobe` for final manuscript/report reporting of a completed pharmacoepidemiology study — those govern what you publish, the ENCePP Checklist governs what you plan. For a US-FDA submission, pair it with `fda-rwe-framework` / `fda-rwe-noninterventional` rather than treating it as sufficient on its own.

What it requires

The Checklist enforces explicit protocol-level documentation across the domains that decide whether real-world data can answer the question: (a) research question and study design stated as a clear objective with a named design (cohort, case-control, self-controlled, drug-utilisation) and, where causal, an explicit comparison and estimand; (b) data source fitness-for-use — provenance, coverage, relevant data quality dimensions, lag, and whether the source can actually capture the exposure, outcome, and confounders required; (c) population, exposure, and outcome operational definitions — eligibility, washout/lookback, code lists, and validated phenotype/algorithm definitions with performance metrics where available; (d) time-zero/index-date alignment and follow-up rules that avoid immortal time and prevalent-user bias; (e) bias and confounding control — confounders, the analytic strategy to address them (matching, propensity/disease-risk scores, restriction, design-based control), and residual/unmeasured confounding; (f) statistical analysis — primary and sensitivity/quantitative-bias analyses, handling of missing data, competing risks, and effect-measure modification; and (g) data management, quality assurance, and reporting — versioned code lists, validation, and a plan to report attrition transparently. Each "no" or "not applicable" must be justified, which is the mechanism that turns the list from a box-ticking exercise into a design critique.

When NOT to use — limitations and common misapplications

The single most common error is treating the ENCePP Checklist as a quality score or a risk-of-bias instrument — it is neither. A fully completed checklist does not certify that a study is low-bias, and it does not make an observational comparison causal; you can answer every item affirmatively and still have a fatally confounded estimate. Use `robins-i`/`robins-e` (or the relevant JBI/NOS tool) when you actually need a graded risk-of-bias appraisal, and a real causal design (target-trial emulation, active-comparator new-user) when you need to defend a causal contrast. "Checklist-as-theater" — completing it for the badge while the protocol remains vague on time-zero, comparator, or estimand — defeats its purpose; the justification fields exist precisely to expose that. Do not substitute the ENCePP Checklist for a reporting checklist (`record-pe`/`strobe`) at manuscript stage, and do not substitute it for the protocol template itself — it certifies a protocol, it does not write one. Finally, it is a European pharmacoepidemiology instrument: for purely health-economic, systematic-review, or US-only regulatory deliverables, the appropriate ISPOR/PRISMA/FDA guidance leads and the ENCePP Checklist plays at most a supporting role.

How it maps to this catalog

Each ENCePP domain is implemented by concrete concepts here. Research question / design / estimand → `picots-framework-rwe`, `target-trial-emulation`, `estimands-ate-att-intercurrent-events-rwe`, and `estimand-analysis-traceability-rwe`. Data source fitness → `fit-for-purpose-data-assessment-rwe`, `claims-analysis`, and `database-feasibility-attrition-funnel-rwe`. Phenotype / exposure / outcome definitions → `diagnosis-phenotype-algorithm-1ip-2op-time-window-rwe`, `claims-outcome-algorithm-ppv-sensitivity-rwe`, and `washout-clean-lookback-period-rwe`. Time-zero and follow-up → `time-zero-index-date-alignment-rwe` and `continuous-enrollment-observable-time-rwe`. Confounding control → `active-comparator-new-user`, `high-dimensional-propensity-score-hdps-rwe`, and `propensity-score-methods-psm-iptw`. Analysis, attrition, and bias quantification → `competing-risks-cause-specific-fine-gray-rwe`, `attrition-and-loss-to-follow-up-rwe`, `e-value-sensitivity-analysis`, and `quantitative-bias-analysis-toolkit-rwe`. Applied note (claims/EHR/registry RWE): in claims, the Checklist's data-fitness items should force a statement on enrollment continuity and Medicare-Advantage versus fee-for-service capture (see `medicare-ffs-ma-commercial-claims-differences-rwe`) before any "no prior exposure" washout is trusted as observed rather than missing; in EHR/registry work the same items should force a loss-to-follow-up and linkage-selection plan. The disciplined way to use this entry: draft the protocol with HARPER or START-RWE, build each component from the linked concept, then run the ENCePP Checklist as the final pre-submission gate.