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.

healthyR: Hospital Data Analysis Workflow Tools

Hospital data analysis workflow tools, modeling, and automations. This library provides many useful tools to review common administrative hospital data. Some of these include average length of stay, readmission rates, average net pay amounts by service lines just to name a few. The aim is to provide a simple and consistent verb framework that takes the guesswork out of everything.

Version: 0.2.2
Depends: R (≥ 3.3)
Imports: magrittr, rlang (≥ 0.1.2), tibble, timetk, ggplot2, dplyr, lubridate, graphics, purrr, stringr, writexl, cowplot, scales, sqldf, plotly
Suggests: knitr, rmarkdown, pacman, healthyR.data, broom, tidyselect
Published: 2024-07-01
DOI: 10.32614/CRAN.package.healthyR
Author: Steven Sanderson ORCID iD [aut, cre, cph]
Maintainer: Steven Sanderson <spsanderson at gmail.com>
BugReports: https://github.com/spsanderson/healthyR/issues
License: MIT + file LICENSE
URL: https://github.com/spsanderson/healthyR
NeedsCompilation: no
Materials: README NEWS
CRAN checks: healthyR results

Documentation:

Reference manual: healthyR.pdf
Vignettes: Getting Started with healthyR

Downloads:

Package source: healthyR_0.2.2.tar.gz
Windows binaries: r-devel: healthyR_0.2.2.zip, r-release: healthyR_0.2.2.zip, r-oldrel: healthyR_0.2.2.zip
macOS binaries: r-release (arm64): healthyR_0.2.2.tgz, r-oldrel (arm64): healthyR_0.2.2.tgz, r-release (x86_64): healthyR_0.2.2.tgz, r-oldrel (x86_64): healthyR_0.2.2.tgz
Old sources: healthyR archive

Reverse dependencies:

Reverse imports: healthyverse

Linking:

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