TRV-2026-1233Version 3 · Revised

Saved · see the current record

Why this version exists

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

The exact text we saved

This is the version exactly as it was saved, character for character. The SHA-256 hash below is a 64-character code worked out from that text. Run the same text through SHA-256 and you get the same code; change a single letter and the code comes out completely different. Each version also stores the previous version’s hash, which chains them together so no version can be swapped out quietly.

TRUVACE RECORD VERSION
record: TRV-2026-1233
version: 3
kind: revised
reason: Editorial pass: sharper headline; gain/problem restated as concrete outcomes; refiled trace to g_space (gain outcome, problem unsupported).
timestamp: 2026-11-04T09:55:39.626680Z
status: published
lens: g_space
sector: health
headline: Incremental Propensity Score Interventions: A Primer for Pharmacoepidemiologists
dek: 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…
gain_title: In 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).
problem_title: (none)
trace_subject: (none)
gain_reading: In 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).
gain_evidence: shifting each patient's probability of receiving abciximab by a predetermined amount on six-month mortality | 6-month mortality would be significantly reduced under a strong treatment policy promoting abciximab administration
problem_reading: (none)
problem_evidence: (none)
quick_read: Researchers illustrated incremental propensity score interventions using 996 patients undergoing percutaneous coronary intervention, estimating propensity scores and outcomes with a Super Learner ensemble and 10-fold splitting to evaluate shifting each patient's probability of receiving abciximab on six-month mortality.

The work matters because standard ATE estimates in this highly selective setting rely on unrealistic assignment assumptions, while IPSIs offer a clinically realistic stochastic alternative; uncertainty remains about generalizability beyond this single PCI cohort and about optimal shift magnitude for policy implementation.
limitation: 
tag: Evidence-backed gain
key_points: Analysis used observational data from a cohort of 996 patients undergoing percutaneous coronary intervention (PCI). | Propensity scores and outcome predictions were estimated using a machine learning ensemble (Super Learner) with 10-fold sample splitting. | ATE estimate was risk difference = -0.059, 95% CI: -0.104 to -0.015 for abciximab vs PCI alone. | IPSIs evaluated by shifting treatment propensity by odds ratios ranging from 0.1 to 10.
rundown: The study applied incremental propensity score interventions to 996 PCI patients to avoid strict positivity requirements, estimating effects across odds ratio shifts from 0.1 to 10 rather than forcing all patients into treated vs untreated counterfactuals.

Propensity and outcome models were fit with Super Learner and 10-fold sample splitting, yielding an ATE risk difference of -0.059 for abciximab, while IPSI results supported mortality reduction under policies that increase treatment propensity.
sources:
- peer_reviewed | Pharmacoepidemiology and Drug Safety | https://doi.org/10.1002/pds.70484 | 2026-10-01
prev: ffd054920763e526e22689fe1644621898819d2f733cef3d8dba74392bbdf2f8
SHA-256 hash
8ab1a3be8ea738727fa60ba950927f0c0085fe840176289298a7e2dd9a088041
Previous version’s hash
ffd054920763e526e22689fe1644621898819d2f733cef3d8dba74392bbdf2f8
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.