The hardware and bandwidth for this mirror is donated by dogado GmbH, the Webhosting and Full Service-Cloud Provider. Check out our Wordpress Tutorial.
If you wish to report a bug, or if you are interested in having us mirror your free-software or open-source project, please feel free to contact us at mirror[@]dogado.de.

outstandR: Outcome regression standardisation

R-CMD-check Lifecycle: experimental License: GPL v3 outstandR status badge

Indirect treatment comparison with limited subject-level data

Overview

{outstandR} is an R package designed to facilitate outcome regression standardisation using model-based approaches, particularly focusing on G-estimation. The package provides tools to apply standardisation techniques for indirect treatment comparisons, especially in scenarios with limited individual patient data.

Who is this package for?

The target audience of {outstandR} is those who want to perform model-based standardization in the specific context of two-study indirect treatment comparisons with limited subject-level data. This is model-based standardization with two additional steps:

  1. Covariate simulation (to overcome limited subject-level data for one of the studies)
  2. Indirect comparison across studies

Installation

Install the development version from GitHub using R-universe:

install.packages("outstandR", repos = c("https://statisticshealtheconomics.r-universe.dev", "https://cloud.r-project.org"))

Alternatively, you may wish to download directly from the repo with remotes::install_github("StatisticsHealthEconomics/outstandR").

Background

Population adjustment methods are increasingly used to compare marginal treatment effects when there are cross-trial differences in effect modifiers and limited patient-level data.

The {outstandR} package allows the implementation of a range of methods for this situation including the following:

General problem

Consider one trial, for which the company has IPD, comparing treatments A and C, from herein call the AC trial. Also, consider a second trial comparing treatments B and C, similarly called the BC trial. For this trial only published aggregate data are available. We wish to estimate a comparison of the effects of treatments A and B on an appropriate scale in some target population P, denoted by the parameter \(d_{AB(P)}\). We make use of bracketed subscripts to denote a specific population. Within the BC population there are parameters \(\mu_{B(BC)}\) and \(\mu_{C(BC)}\) representing the expected outcome on each treatment (including parameters for treatments not studied in the BC trial, e.g. treatment A). The BC trial provides estimators \(\bar Y_{B(BC)}\) and \(\bar Y_{C(BC)}\) of \(\mu_{B(BC)}\), \(\mu_{C(BC)}\), respectively, which are the summary outcomes. It is the same situation for the AC trial.

For a suitable scale, for example a log-odds ratio, or risk difference, we form estimators \(\Delta_{BC(BC)}\) and \(\Delta_{AC(AC)}\) of the trial level (or marginal) relative treatment effects. We shall assume that this is always represented as a difference so, for example, for the risk ratio this is on the log scale.

\[ \Delta_{AB(BC)} = g(\bar{Y}_{B{(BC)}}) - g(\bar{Y}_{A{(BC)}}) \]

References

This R package contains code originally written for the papers:

Remiro-Azócar, A., Heath, A. & Baio, G. (2022) Parametric G-computation for Compatible Indirect Treatment Comparisons with Limited Individual Patient Data. Res Synth Methods;1–31.

and

Remiro-Azócar, A., Heath, A., & Baio, G. (2023) Model-based standardization using multiple imputation. BMC Medical Research Methodology, 1–15. https://doi.org/10.1186/s12874-024-02157-x

Contributing

We welcome contributions! Please submit contributions through Pull Requests, following the contributing guidelines. To report issues and/or seek support, please file a new ticket in the issue tracker.

Please note that this project is released with a Contributor Code of Conduct. By participating in this project you agree to abide by its terms.

[!NOTE] This package is licensed under the GPLv3. For more information, see LICENSE.

These binaries (installable software) and packages are in development.
They may not be fully stable and should be used with caution. We make no claims about them.
Health stats visible at Monitor.