mds?Medical device event data are messy.
Common challenges include:
mds?The mds package provides a standardized framework to
address these challenges:
R files for auditability,
documentation, and reproducibilityNote on Statistical Algorithms
mds data and analysis standards allow for seamless
application of various statistical trending algorithms via the
mdsstat package (under development).
The general workflow to go from data to trending over time is as follows:
deviceevent() to standardize device-event
data.exposure() to standardize exposure data
(optional).define_analyses() to enumerate possible analysis
combinations.time_series() to generate counts (and/or rates) by
time based on your defined analyses.library(mds)
# Step 1 - Device Events
de <- deviceevent(
maude,
time="date_received",
device_hierarchy=c("device_name", "device_class"),
event_hierarchy=c("event_type", "medical_specialty_description"),
key="report_number",
covariates="region",
descriptors="_all_")
# Step 2 - Exposures (Optional step)
ex <- exposure(
sales,
time="sales_month",
device_hierarchy="device_name",
match_levels="region",
count="sales_volume")
# Step 3 - Define Analyses
da <- define_analyses(
de,
device_level="device_name",
exposure=ex,
covariates="region")
# Step 4 - Time Series
ts <- time_series(
da,
deviceevents=de,
exposure=ex)plot(ts[[4]], "rate", type='l')
Need a high-speed mirror for your open-source project?
Contact our mirror admin team at info@clientvps.com.
This archive is provided as a free public service to the community.
Proudly supported by infrastructure from VPSPulse , RxServers , BuyNumber , UnitVPS , OffshoreName and secure payment technology by ArionPay.