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.

clintrialx: Connect and Work with Clinical Trials Data Sources

Are you spending too much time fetching and managing clinical trial data? Struggling with complex queries and bulk data extraction? What if you could simplify this process with just a few lines of code? Introducing 'clintrialx' - Fetch clinical trial data from sources like 'ClinicalTrials.gov' <https://clinicaltrials.gov/> and the 'Clinical Trials Transformation Initiative - Access to Aggregate Content of ClinicalTrials.gov' database <https://aact.ctti-clinicaltrials.org/>, supporting pagination and bulk downloads. Also, you can generate HTML reports based on the data obtained from the sources!

Version: 0.1.0
Depends: R (≥ 4.0.0)
Imports: httr, lubridate, readr, dplyr, progress, RPostgreSQL, tibble, DBI, rmarkdown, xfun (≥ 0.44)
Suggests: knitr
Published: 2024-09-03
DOI: 10.32614/CRAN.package.clintrialx
Author: Indraneel Chakraborty ORCID iD [aut, cre]
Maintainer: Indraneel Chakraborty <hello.indraneel at gmail.com>
License: Apache License 2.0
URL: http://www.indraneelchakraborty.com/clintrialx/
NeedsCompilation: no
Materials: README
CRAN checks: clintrialx results

Documentation:

Reference manual: clintrialx.pdf
Vignettes: Exploring Clinical Trial Data with clintrialx (source, R code)

Downloads:

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

Linking:

Please use the canonical form https://CRAN.R-project.org/package=clintrialx 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.