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.

symptomcheckR: Analyzing and Visualizing Symptom Checker Performance

Easily analyze and visualize the performance of symptom checkers. This package can be used to gain comprehensive insights into the performance of single symptom checkers or the performance of multiple symptom checkers. It can be used to easily compare these symptom checkers across several metrics to gain an understanding of their strengths and weaknesses. The metrics are developed in Kopka et al. (2023) <doi:10.1177/20552076231194929>.

Version: 0.1.3
Depends: R (≥ 3.5.0)
Imports: dplyr (≥ 1.0.0), ggplot2 (≥ 3.2.0), ggpubr (≥ 0.6.0), tidyr (≥ 1.3.0), irr (≥ 0.84.1)
Suggests: knitr, rmarkdown, testthat (≥ 3.0.0)
Published: 2024-04-16
DOI: 10.32614/CRAN.package.symptomcheckR
Author: Marvin Kopka ORCID iD [cre, aut], Malte L. Schmieding ORCID iD [aut], Markus A. Feufel ORCID iD [aut]
Maintainer: Marvin Kopka <marvin.kopka at tu-berlin.de>
BugReports: https://github.com/ma-kopka/symptomcheckR/issues
License: GPL-3
URL: https://github.com/ma-kopka/symptomcheckR
NeedsCompilation: no
Language: en-US
Materials: README NEWS
CRAN checks: symptomcheckR results

Documentation:

Reference manual: symptomcheckR.pdf

Downloads:

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

Linking:

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