The hardware and bandwidth for this mirror is donated by METANET, the Webhosting and Full Service-Cloud Provider.
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[@]metanet.ch.

r4subpharma: 'pharmaverse' Adapters for R4SUB Submission Readiness Evidence

Bridges the 'pharmaverse' clinical reporting stack and the R4SUB (Ready for Submission) ecosystem. Converts 'metacore' metadata objects and ADaM (Analysis Data Model) datasets - such as those built with 'admiral' - into standardized R4SUB evidence table rows via 'r4subcore', so that submission readiness can be scored with 'r4subscore' without changing an existing pharmaverse pipeline.

Version: 0.1.0
Depends: R (≥ 4.2)
Imports: cli, r4subcore, tibble
Suggests: knitr, metacore, pharmaverseadam, r4subdata, r4subprofile, r4subscore, rmarkdown, testthat (≥ 3.0.0)
Published: 2026-09-11
DOI: 10.32614/CRAN.package.r4subpharma (may not be active yet)
Author: Pawan Rama Mali ORCID iD [aut, cre, cph]
Maintainer: Pawan Rama Mali <prm at outlook.in>
BugReports: https://github.com/R4SUB/r4subpharma/issues
License: MIT + file LICENSE
URL: https://r4sub.github.io/r4subpharma/, https://github.com/R4SUB/r4subpharma
NeedsCompilation: no
Materials: README, NEWS
CRAN checks: r4subpharma results

Documentation:

Reference manual: r4subpharma.html , r4subpharma.pdf
Vignettes: Case study: scoring the CDISC pilot ADaM package (source, R code)
Scoring submission readiness from a pharmaverse pipeline (source, R code)

Downloads:

Package source: r4subpharma_0.1.0.tar.gz
Windows binaries: r-devel: not available, r-release: not available, r-oldrel: r4subpharma_0.1.0.zip
macOS binaries: r-release (arm64): not available, r-oldrel (arm64): r4subpharma_0.1.0.tgz, r-release (x86_64): r4subpharma_0.1.0.tgz, r-oldrel (x86_64): r4subpharma_0.1.0.tgz

Linking:

Please use the canonical form https://CRAN.R-project.org/package=r4subpharma to link to this page.

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.