60/100

Moderate evidence

GainPublished recordHealthGood Space

Incremental Propensity Score Interventions: A Primer for Pharmacoepidemiologists

Truvace record
TRV-2026-1233raw data (JSON)
Version
v4Revised
First published
Evidence type
Observational study
Sources
1 sourcePeer-reviewed
sha256
cfd8b8a684c9…check it

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…

The gain

In an analysis of 996 patients having a heart artery procedure, abciximab was linked to a 5.9-point lower risk of death at six months than the procedure alone (95% CI -0.104 to -0.015).

Sources

1 on file
  1. Peer-reviewed2026-10-01

Cite this record

v4

Truvace Impact Record TRV-2026-1233, v4: “Incremental Propensity Score Interventions: A Primer for Pharmacoepidemiologists.” Truvace, 2026-11-05. /record/TRV-2026-1233 (accessed on the day you copy it). sha256 cfd8b8a684c9a3e9…

Change history

4 versions

Every change made to this record since it was first published, and why.

  1. Revisedv4cfd8b8a684c9…

    Voice pass: plainer wording and study attribution; no facts or figures changed.

  2. Revisedv38ab1a3be8ea7…

    Editorial pass: sharper headline; gain/problem restated as concrete outcomes; refiled trace to g_space (gain outcome, problem unsupported).

  3. Revisedv2ffd054920763…

    Direction audit: the gain line described the method, not an outcome; restated as the finding; the problem line described the method, not an outcome; restated as the finding.

  4. Publishedv19bbf46ade60d…

    Certified into the record

Check this record hasn’t been altered

Check this record hasn’t been altered
How to check it yourself, without trusting this page

Download any version from /api/record/TRV-2026-1233 and hash its canonical field yourself, for example with shasum -a 256. You should get its content_hash. Each version’s text also ends with prev:and the hash of the version before it (version 1 points to 64 zeros). If anyone had changed a single character of any version after it was saved, those hashes wouldn’t line up.