TRV-2026-1233Certified recordPeer-reviewed

Incremental Propensity Score Interventions: A Primer for Pharmacoepidemiologists

Background In observational pharmacoepidemiology, estimating average treatment effects (ATEs) is often challenging due to a lack of practical positivity. In highly selective clinical settings, certain patients almost always or never receive treatment, causing ATE estimators to rely on unstable extrapolation. Incremental propensity score interventions (IPSIs) offer a stochastic alternative by shifting each patient's probability of treatment, providing a more clinically realistic framework that circumvents positiv…

Health · The Trace — both readings · certified 2026-10-01 · v1 · article view · machine-readable

Current reading — gain

Using a Super Learner ensemble to estimate propensity scores, shifting each patient's odds of receiving abciximab during PCI reduced 6-month mortality, with a strong pro-treatment incremental policy showing significant benefit.

Current reading — problem

In highly selective PCI settings, conventional ATE estimation for abciximab suffers from lack of practical positivity, forcing unstable extrapolation and assuming patients with near-certain treatment probability could realistically be assigned to withhold therapy.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-1233, v1: “Incremental Propensity Score Interventions: A Primer for Pharmacoepidemiologists.” Truvace, 2026-10-01. /record/TRV-2026-1233 (accessed at citation time). sha256 9bbf46ade60d2934…

Calibration history

Every change to this record since certification, in the open. None yet — the reading has held since it entered the record.

  1. Certifiedv19bbf46ade60d…

    Certified into the record

Verify this record
How to verify without trusting this page

Fetch the canonical text of any version from /api/record/TRV-2026-1233 and hash it yourself — for example shasum -a 256 on the saved canonical field. The result must equal content_hash, and each version’s text ends with prev:followed by the prior version’s hash (version 1 chains to 64 zeros). If a single character of any version had been altered since certification, the chain would not reproduce.