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.
Functions to load Research Patient Data Registry ('RPDR') text queries from Partners Healthcare institutions into R. The package also provides helper functions to manipulate data and execute common procedures such as finding the closest radiological exams considering a given timepoint, or creating a DICOM header database from the downloaded images. All functionalities are parallelized for fast and efficient analyses.
| Version: | 1.1.1 |
| Depends: | R (≥ 4.0) |
| Imports: | data.table (≥ 1.14.1), stringr (≥ 1.4.0), readr (≥ 1.4.0), parallelly (≥ 1.36.0), foreach (≥ 1.5.1), future (≥ 1.33.1), doFuture (≥ 1.0.1), progressr (≥ 0.14.0) |
| Suggests: | testthat (≥ 3.0.0), reticulate (≥ 1.20), knitr, rmarkdown, covr |
| Published: | 2024-04-03 |
| DOI: | 10.32614/CRAN.package.parseRPDR |
| Author: | Marton Kolossvary [aut, cre] |
| Maintainer: | Marton Kolossvary <mkolossvary at mgh.harvard.edu> |
| BugReports: | https://github.com/martonkolossvary/parseRPDR/issues |
| License: | AGPL (≥ 3) |
| URL: | https://github.com/martonkolossvary/parseRPDR |
| NeedsCompilation: | no |
| Citation: | parseRPDR citation info |
| Materials: | README NEWS |
| CRAN checks: | parseRPDR results |
| Reference manual: | parseRPDR.pdf |
| Package source: | parseRPDR_1.1.1.tar.gz |
| Windows binaries: | r-devel: parseRPDR_1.1.1.zip, r-release: parseRPDR_1.1.1.zip, r-oldrel: parseRPDR_1.1.1.zip |
| macOS binaries: | r-release (arm64): parseRPDR_1.1.1.tgz, r-oldrel (arm64): parseRPDR_1.1.1.tgz, r-release (x86_64): parseRPDR_1.1.1.tgz, r-oldrel (x86_64): parseRPDR_1.1.1.tgz |
| Old sources: | parseRPDR archive |
Please use the canonical form https://CRAN.R-project.org/package=parseRPDR 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.