doi abstract bibtex

The use of propensity score methods to adjust for selection bias in observational studies has become increasingly popular in public health and medical research. A substantial portion of studies using propensity score adjustment treat the propensity score as a conventional regression predictor. Through a Monte Carlo simulation study, Austin and colleagues. investigated the bias associated with treatment effect estimation when the propensity score is used as a covariate in nonlinear regression models, such as logistic regression and Cox proportional hazards models. We show that the bias exists even in a linear regression model when the estimated propensity score is used and derive the explicit form of the bias. We also conduct an extensive simulation study to compare the performance of such covariate adjustment with propensity score stratification, propensity score matching, inverse probability of treatment weighted method, and nonparametric functional estimation using splines. The simulation scenarios are designed to reflect real data analysis practice. Instead of specifying a known parametric propensity score model, we generate the data by considering various degrees of overlap of the covariate distributions between treated and control groups. Propensity score matching excels when the treated group is contained within a larger control pool, while the model-based adjustment may have an edge when treated and control groups do not have too much overlap. Overall, adjusting for the propensity score through stratification or matching followed by regression or using splines, appears to be a good practical strategy.

@article{had14bia, title = {Bias Associated with Using the Estimated Propensity Score as a Regression Covariate}, volume = {33}, issn = {1097-0258}, abstract = {The use of propensity score methods to adjust for selection bias in observational studies has become increasingly popular in public health and medical research. A substantial portion of studies using propensity score adjustment treat the propensity score as a conventional regression predictor. Through a Monte Carlo simulation study, Austin and colleagues. investigated the bias associated with treatment effect estimation when the propensity score is used as a covariate in nonlinear regression models, such as logistic regression and Cox proportional hazards models. We show that the bias exists even in a linear regression model when the estimated propensity score is used and derive the explicit form of the bias. We also conduct an extensive simulation study to compare the performance of such covariate adjustment with propensity score stratification, propensity score matching, inverse probability of treatment weighted method, and nonparametric functional estimation using splines. The simulation scenarios are designed to reflect real data analysis practice. Instead of specifying a known parametric propensity score model, we generate the data by considering various degrees of overlap of the covariate distributions between treated and control groups. Propensity score matching excels when the treated group is contained within a larger control pool, while the model-based adjustment may have an edge when treated and control groups do not have too much overlap. Overall, adjusting for the propensity score through stratification or matching followed by regression or using splines, appears to be a good practical strategy.}, number = {1}, journal = {Stat Med}, doi = {10.1002/sim.5884}, author = {Hade, Erinn M. and Lu, Bo}, month = jan, year = {2014}, keywords = {observational-study,bias,propensity-score,covariable-adjustment}, pages = {74-87}, citeulike-article-id = {12445750}, citeulike-attachment-1 = {had14bia.pdf; /pdf/user/harrelfe/article/12445750/996108/had14bia.pdf; e432263d6788007ac57fbc904f87dbcc4ccad464}, citeulike-linkout-0 = {http://dx.doi.org/10.1002/sim.5884}, citeulike-linkout-1 = {http://view.ncbi.nlm.nih.gov/pubmed/23787715}, citeulike-linkout-2 = {http://www.hubmed.org/display.cgi?uids=23787715}, day = {15}, pmid = {23787715}, posted-at = {2014-11-29 16:49:33}, priority = {2} }

Downloads: 0