diff --git a/DESCRIPTION b/DESCRIPTION
index 10f57b28..696caf39 100644
--- a/DESCRIPTION
+++ b/DESCRIPTION
@@ -1,6 +1,6 @@
Package: AMR
-Version: 1.8.0.9004
-Date: 2022-03-03
+Version: 1.8.0.9005
+Date: 2022-03-10
Title: Antimicrobial Resistance Data Analysis
Description: Functions to simplify and standardise antimicrobial resistance (AMR)
data analysis and to work with microbial and antimicrobial properties by
diff --git a/NEWS.md b/NEWS.md
index 6c57d18b..e98b492e 100755
--- a/NEWS.md
+++ b/NEWS.md
@@ -1,9 +1,10 @@
-# `AMR` 1.8.0.9004
-## Last updated: 3 March 2022
+# `AMR` 1.8.0.9005
+## Last updated: 10 March 2022
All functions in this package are considered to be stable. Updates to the AMR interpretation rules (such as by EUCAST and CLSI), the microbial taxonomy, and the antibiotic dosages will all be updated every 6 to 12 months.
### Changed
+* Fix for using `as.rsi()` on values containing capped values (such as `>=`), sometimes leading to `NA`
* Support for antibiotic interpretations of the MIPS laboratory system: `"U"` for S ('susceptible urine'), `"D"` for I ('susceptible dose-dependent')
* Improved algorithm of `as.mo()`, especially for ignoring non-taxonomic text, such as:
```r
diff --git a/R/lifecycle.R b/R/lifecycle.R
index 7fd460a3..867992c5 100644
--- a/R/lifecycle.R
+++ b/R/lifecycle.R
@@ -44,7 +44,7 @@
#' \if{html}{\figure{lifecycle_stable.svg}{options: style=margin-bottom:"5"} \cr}
#' The [lifecycle][AMR::lifecycle] of this function is **stable**. In a stable function, major changes are unlikely. This means that the unlying code will generally evolve by adding new arguments; removing arguments or changing the meaning of existing arguments will be avoided.
#'
-#' If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit an message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
+#' If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit a message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
#' @section Retired Lifecycle:
#' \if{html}{\figure{lifecycle_retired.svg}{options: style=margin-bottom:"5"} \cr}
#' The [lifecycle][AMR::lifecycle] of this function is **retired**. A retired function is no longer under active development, and (if appropiate) a better alternative is available. No new arguments will be added, and only the most critical bugs will be fixed. In a future version, this function will be removed.
diff --git a/R/mic.R b/R/mic.R
index e9bb97e6..adf73c8d 100755
--- a/R/mic.R
+++ b/R/mic.R
@@ -243,14 +243,12 @@ droplevels.mic <- function(x, exclude = if (any(is.na(levels(x)))) NULL else NA,
pillar_shaft.mic <- function(x, ...) {
crude_numbers <- as.double(x)
operators <- gsub("[^<=>]+", "", as.character(x))
- pasted <- trimws(paste0(operators, trimws(format(crude_numbers))))
- out <- pasted
+ operators[operators != ""] <- font_silver(operators[operators != ""], collapse = NULL)
+ out <- trimws(paste0(operators, trimws(format(crude_numbers))))
out[is.na(x)] <- font_na(NA)
- out <- gsub("(<|=|>)", font_silver("\\1"), out)
- if (any(out %like% "[.]", na.rm = TRUE)) {
- out <- gsub("([.]?0+)$", font_white("\\1"), out)
- }
- create_pillar_column(out, align = "right", width = max(nchar(pasted)))
+ # maketrailing zeroes almost invisible
+ out[out %like% "[.]"] <- gsub("([.]?0+)$", font_white("\\1"), out[out %like% "[.]"], perl = TRUE)
+ create_pillar_column(out, align = "right", width = max(nchar(font_stripstyle(out))))
}
# will be exported using s3_register() in R/zzz.R
diff --git a/R/rsi.R b/R/rsi.R
index 33c9215a..24772746 100755
--- a/R/rsi.R
+++ b/R/rsi.R
@@ -690,7 +690,6 @@ as_rsi_method <- function(method_short = "mic",
"... ",
appendLF = FALSE,
as_note = FALSE)
-
result <- exec_as.rsi(method = method_short,
x = x,
mo = mo_coerced,
@@ -715,7 +714,7 @@ exec_as.rsi <- function(method,
metadata_mo <- get_mo_failures_uncertainties_renamed()
x_bak <- data.frame(x_mo = paste0(x, mo), stringsAsFactors = FALSE)
- df <- unique(data.frame(x, mo), stringsAsFactors = FALSE)
+ df <- unique(data.frame(x, mo, x_mo = paste0(x, mo), stringsAsFactors = FALSE))
x <- df$x
mo <- df$mo
@@ -848,7 +847,7 @@ exec_as.rsi <- function(method,
}
new_rsi <- x_bak %pm>%
- pm_left_join(data.frame(x_mo = paste0(df$x, df$mo), new_rsi,
+ pm_left_join(data.frame(x_mo = paste0(x, mo), new_rsi,
stringsAsFactors = FALSE),
by = "x_mo") %pm>%
pm_pull(new_rsi)
@@ -907,13 +906,13 @@ freq.rsi <- function(x, ...) {
.add_header = list(
Drug = paste0(ab_name(ab, language = NULL), " (", ab, ", ", paste(ab_atc(ab), collapse = "/"), ")"),
`Drug group` = ab_group(ab, language = NULL),
- `%SI` = percentage(susceptibility(x, minimum = 0, as_percent = FALSE),
- digits = digits)))
+ `%SI` = trimws(percentage(susceptibility(x, minimum = 0, as_percent = FALSE),
+ digits = digits))))
} else {
cleaner::freq.default(x = x, ...,
.add_header = list(
- `%SI` = percentage(susceptibility(x, minimum = 0, as_percent = FALSE),
- digits = digits)))
+ `%SI` = trimws(percentage(susceptibility(x, minimum = 0, as_percent = FALSE),
+ digits = digits))))
}
}
diff --git a/data-raw/AMR_latest.tar.gz b/data-raw/AMR_latest.tar.gz
index a5d13f57..ef69a073 100644
Binary files a/data-raw/AMR_latest.tar.gz and b/data-raw/AMR_latest.tar.gz differ
diff --git a/docs/404.html b/docs/404.html
index 88793f5f..7bc24820 100644
--- a/docs/404.html
+++ b/docs/404.html
@@ -43,7 +43,7 @@
AMR (for R)
- 1.8.0.9004
+ 1.8.0.9005
@@ -205,12 +205,14 @@ Content not found. Please use links in the navbar.
diff --git a/docs/LICENSE-text.html b/docs/LICENSE-text.html
index 6a5c4d38..b9eafa18 100644
--- a/docs/LICENSE-text.html
+++ b/docs/LICENSE-text.html
@@ -17,7 +17,7 @@
AMR (for R)
- 1.8.0.9004
+ 1.8.0.9005
@@ -416,11 +416,13 @@ END OF TERMS AND CONDITIONS
diff --git a/docs/articles/AMR.html b/docs/articles/AMR.html
index 52bc2f71..bf8916e3 100644
--- a/docs/articles/AMR.html
+++ b/docs/articles/AMR.html
@@ -44,7 +44,7 @@
AMR (for R)
- 1.8.0
+ 1.8.0.9005
@@ -189,9 +189,10 @@
Note: values on this page will change with every website update since they are based on randomly created values and the page was written in R Markdown. However, the methodology remains unchanged. This page was generated on 23 December 2021.
-
-
Introduction
-
-
Conducting AMR data analysis unfortunately requires in-depth knowledge from different scientific fields, which makes it hard to do right. At least, it requires:
+
Note: values on this page will change with every
+website update since they are based on randomly created values and the
+page was written in R
+Markdown. However, the methodology remains unchanged. This page was
+generated on 10 March 2022.
+
+
Introduction
+
+
Conducting AMR data analysis unfortunately requires in-depth
+knowledge from different scientific fields, which makes it hard to do
+right. At least, it requires:
Good questions (always start with those!)
-
A thorough understanding of (clinical) epidemiology, to understand the clinical and epidemiological relevance and possible bias of results
-
A thorough understanding of (clinical) microbiology/infectious diseases, to understand which microorganisms are causal to which infections and the implications of pharmaceutical treatment, as well as understanding intrinsic and acquired microbial resistance
-
Experience with data analysis with microbiological tests and their results, to understand the determination and limitations of MIC values and their interpretations to RSI values
-
Availability of the biological taxonomy of microorganisms and probably normalisation factors for pharmaceuticals, such as defined daily doses (DDD)
-
Available (inter-)national guidelines, and profound methods to apply them
+
A thorough understanding of (clinical) epidemiology, to understand
+the clinical and epidemiological relevance and possible bias of
+results
+
A thorough understanding of (clinical) microbiology/infectious
+diseases, to understand which microorganisms are causal to which
+infections and the implications of pharmaceutical treatment, as well as
+understanding intrinsic and acquired microbial resistance
+
Experience with data analysis with microbiological tests and their
+results, to understand the determination and limitations of MIC values
+and their interpretations to RSI values
+
Availability of the biological taxonomy of microorganisms and
+probably normalisation factors for pharmaceuticals, such as defined
+daily doses (DDD)
+
Available (inter-)national guidelines, and profound methods to apply
+them
-
Of course, we cannot instantly provide you with knowledge and experience. But with this AMR package, we aimed at providing (1) tools to simplify antimicrobial resistance data cleaning, transformation and analysis, (2) methods to easily incorporate international guidelines and (3) scientifically reliable reference data, including the requirements mentioned above.
-
The AMR package enables standardised and reproducible AMR data analysis, with the application of evidence-based rules, determination of first isolates, translation of various codes for microorganisms and antimicrobial agents, determination of (multi-drug) resistant microorganisms, and calculation of antimicrobial resistance, prevalence and future trends.
+
Of course, we cannot instantly provide you with knowledge and
+experience. But with this AMR package, we aimed at
+providing (1) tools to simplify antimicrobial resistance data cleaning,
+transformation and analysis, (2) methods to easily incorporate
+international guidelines and (3) scientifically reliable reference data,
+including the requirements mentioned above.
+
The AMR package enables standardised and reproducible
+AMR data analysis, with the application of evidence-based rules,
+determination of first isolates, translation of various codes for
+microorganisms and antimicrobial agents, determination of (multi-drug)
+resistant microorganisms, and calculation of antimicrobial resistance,
+prevalence and future trends.
-
-
Preparation
-
-
For this tutorial, we will create fake demonstration data to work with.
-
You can skip to Cleaning the data if you already have your own data ready. If you start your analysis, try to make the structure of your data generally look like this:
+
+
Preparation
+
+
For this tutorial, we will create fake demonstration data to work
+with.
+
You can skip to Cleaning the data if
+you already have your own data ready. If you start your analysis, try to
+make the structure of your data generally look like this:
date
@@ -231,21 +261,21 @@
-
2021-12-23
+
2022-03-10
abcd
Escherichia coli
S
S
-
2021-12-23
+
2022-03-10
abcd
Escherichia coli
S
R
-
2021-12-23
+
2022-03-10
efgh
Escherichia coli
R
@@ -253,59 +283,84 @@
-
-
Needed R packages
-
-
As with many uses in R, we need some additional packages for AMR data analysis. Our package works closely together with the tidyverse packagesdplyr and ggplot2 by RStudio. The tidyverse tremendously improves the way we conduct data science - it allows for a very natural way of writing syntaxes and creating beautiful plots in R.
-
We will also use the cleaner package, that can be used for cleaning data and creating frequency tables.
+
+
Needed R packages
+
+
As with many uses in R, we need some additional packages for AMR data
+analysis. Our package works closely together with the tidyverse packagesdplyr and ggplot2 by
+RStudio. The tidyverse tremendously improves the way we conduct data
+science - it allows for a very natural way of writing syntaxes and
+creating beautiful plots in R.
+
We will also use the cleaner package, that can be used
+for cleaning data and creating frequency tables.
We will create some fake example data to use for analysis. For AMR data analysis, we need at least: a patient ID, name or code of a microorganism, a date and antimicrobial results (an antibiogram). It could also include a specimen type (e.g. to filter on blood or urine), the ward type (e.g. to filter on ICUs).
-
With additional columns (like a hospital name, the patients gender of even [well-defined] clinical properties) you can do a comparative analysis, as this tutorial will demonstrate too.
-
Patients
+
Creation of data
+
We will create some fake example data to use for analysis. For AMR
+data analysis, we need at least: a patient ID, name or code of a
+microorganism, a date and antimicrobial results (an antibiogram). It
+could also include a specimen type (e.g. to filter on blood or urine),
+the ward type (e.g. to filter on ICUs).
+
With additional columns (like a hospital name, the patients gender of
+even [well-defined] clinical properties) you can do a comparative
+analysis, as this tutorial will demonstrate too.
+
+
Patients
+
To start with patients, we need a unique list of patients.
The LETTERS object is available in R - it’s a vector with 26 characters: A to Z. The patients object we just created is now a vector of length 260, with values (patient IDs) varying from A1 to Z10. Now we we also set the gender of our patients, by putting the ID and the gender in a table:
+
The LETTERS object is available in R - it’s a vector
+with 26 characters: A to Z. The
+patients object we just created is now a vector of length
+260, with values (patient IDs) varying from A1 to
+Z10. Now we we also set the gender of our patients, by
+putting the ID and the gender in a table:
This dates object now contains all days in our date range.
-
-
Microorganisms
-
-
For this tutorial, we will uses four different microorganisms: Escherichia coli, Staphylococcus aureus, Streptococcus pneumoniae, and Klebsiella pneumoniae:
+
This dates object now contains all days in our date
+range.
+
+
Microorganisms
+
+
For this tutorial, we will uses four different microorganisms:
+Escherichia coli, Staphylococcus aureus,
+Streptococcus pneumoniae, and Klebsiella
+pneumoniae:
Using the sample() function, we can randomly select items from all objects we defined earlier. To let our fake data reflect reality a bit, we will also approximately define the probabilities of bacteria and the antibiotic results, using the random_rsi() function.
+
+
Put everything together
+
+
Using the sample() function, we can randomly select
+items from all objects we defined earlier. To let our fake data reflect
+reality a bit, we will also approximately define the probabilities of
+bacteria and the antibiotic results, using the random_rsi()
+function.
We also created a package dedicated to data cleaning and checking, called the cleaner package. It freq() function can be used to create frequency tables.
+
+
Cleaning the data
+
+
We also created a package dedicated to data cleaning and checking,
+called the cleaner package. It freq() function
+can be used to create frequency tables.
So, we can draw at least two conclusions immediately. From a data scientists perspective, the data looks clean: only values M and F. From a researchers perspective: there are slightly more men. Nothing we didn’t already know.
-
The data is already quite clean, but we still need to transform some variables. The bacteria column now consists of text, and we want to add more variables based on microbial IDs later on. So, we will transform this column to valid IDs. The mutate() function of the dplyr package makes this really easy:
+
So, we can draw at least two conclusions immediately. From a data
+scientists perspective, the data looks clean: only values M
+and F. From a researchers perspective: there are slightly
+more men. Nothing we didn’t already know.
+
The data is already quite clean, but we still need to transform some
+variables. The bacteria column now consists of text, and we
+want to add more variables based on microbial IDs later on. So, we will
+transform this column to valid IDs. The mutate() function
+of the dplyr package makes this really easy:
We also want to transform the antibiotics, because in real life data we don’t know if they are really clean. The as.rsi() function ensures reliability and reproducibility in these kind of variables. The is.rsi.eligible() can check which columns are probably columns with R/SI test results. Using mutate() and across(), we can apply the transformation to the formal <rsi> class:
+
We also want to transform the antibiotics, because in real life data
+we don’t know if they are really clean. The as.rsi()
+function ensures reliability and reproducibility in these kind of
+variables. The is.rsi.eligible() can check which columns
+are probably columns with R/SI test results. Using mutate()
+and across(), we can apply the transformation to the formal
+<rsi> class:
Finally, we will apply EUCAST rules on our antimicrobial results. In Europe, most medical microbiological laboratories already apply these rules. Our package features their latest insights on intrinsic resistance and exceptional phenotypes. Moreover, the eucast_rules() function can also apply additional rules, like forcing ampicillin = R when amoxicillin/clavulanic acid = R.
-
Because the amoxicillin (column AMX) and amoxicillin/clavulanic acid (column AMC) in our data were generated randomly, some rows will undoubtedly contain AMX = S and AMC = R, which is technically impossible. The eucast_rules() fixes this:
+
Finally, we will apply EUCAST
+rules on our antimicrobial results. In Europe, most medical
+microbiological laboratories already apply these rules. Our package
+features their latest insights on intrinsic resistance and exceptional
+phenotypes. Moreover, the eucast_rules() function can also
+apply additional rules, like forcing
+ampicillin = R when
+amoxicillin/clavulanic acid = R.
+
Because the amoxicillin (column AMX) and
+amoxicillin/clavulanic acid (column AMC) in our data were
+generated randomly, some rows will undoubtedly contain AMX = S and AMC =
+R, which is technically impossible. The eucast_rules()
+fixes this:
We also need to know which isolates we can actually use for analysis.
-
To conduct an analysis of antimicrobial resistance, you must only include the first isolate of every patient per episode (Hindler et al., Clin Infect Dis. 2007). If you would not do this, you could easily get an overestimate or underestimate of the resistance of an antibiotic. Imagine that a patient was admitted with an MRSA and that it was found in 5 different blood cultures the following weeks (yes, some countries like the Netherlands have these blood drawing policies). The resistance percentage of oxacillin of all isolates would be overestimated, because you included this MRSA more than once. It would clearly be selection bias.
-
The Clinical and Laboratory Standards Institute (CLSI) appoints this as follows:
+
+
First isolates
+
+
We also need to know which isolates we can actually use for
+analysis.
+
To conduct an analysis of antimicrobial resistance, you must only include the first
+isolate of every patient per episode (Hindler et al., Clin
+Infect Dis. 2007). If you would not do this, you could easily get an
+overestimate or underestimate of the resistance of an antibiotic.
+Imagine that a patient was admitted with an MRSA and that it was found
+in 5 different blood cultures the following weeks (yes, some countries
+like the Netherlands have these blood drawing policies). The resistance
+percentage of oxacillin of all isolates would be overestimated, because
+you included this MRSA more than once. It would clearly be selection
+bias.
+
The Clinical and Laboratory Standards Institute (CLSI) appoints this
+as follows:
-
(…) When preparing a cumulative antibiogram to guide clinical decisions about empirical antimicrobial therapy of initial infections, only the first isolate of a given species per patient, per analysis period (eg, one year) should be included, irrespective of body site, antimicrobial susceptibility profile, or other phenotypical characteristics (eg, biotype). The first isolate is easily identified, and cumulative antimicrobial susceptibility test data prepared using the first isolate are generally comparable to cumulative antimicrobial susceptibility test data calculated by other methods, providing duplicate isolates are excluded. M39-A4 Analysis and Presentation of Cumulative Antimicrobial Susceptibility Test Data, 4th Edition. CLSI, 2014. Chapter 6.4
+
(…) When preparing a cumulative antibiogram to guide clinical
+decisions about empirical antimicrobial therapy of initial infections,
+only the first isolate of a given species per patient, per
+analysis period (eg, one year) should be included, irrespective of body
+site, antimicrobial susceptibility profile, or other phenotypical
+characteristics (eg, biotype). The first isolate is easily
+identified, and cumulative antimicrobial susceptibility test data
+prepared using the first isolate are generally comparable to cumulative
+antimicrobial susceptibility test data calculated by other methods,
+providing duplicate isolates are excluded. M39-A4
+Analysis and Presentation of Cumulative Antimicrobial Susceptibility
+Test Data, 4th Edition. CLSI, 2014. Chapter 6.4
-
This AMR package includes this methodology with the first_isolate() function and is able to apply the four different methods as defined by Hindler et al. in 2007: phenotype-based, episode-based, patient-based, isolate-based. The right method depends on your goals and analysis, but the default phenotype-based method is in any case the method to properly correct for most duplicate isolates. This method also takes into account the antimicrobial susceptibility test results using all_microbials(). Read more about the methods on the first_isolate() page.
+
This AMR package includes this methodology with the
+first_isolate() function and is able to apply the four
+different methods as defined by Hindler
+et al. in 2007: phenotype-based, episode-based,
+patient-based, isolate-based. The right method depends on your goals and
+analysis, but the default phenotype-based method is in any case the
+method to properly correct for most duplicate isolates. This method also
+takes into account the antimicrobial susceptibility test results using
+all_microbials(). Read more about the methods on the
+first_isolate() page.
The outcome of the function can easily be added to our data:
data<-data%>%
@@ -502,9 +630,11 @@ Longest: 1
# ℹ Using column 'patient_id' as input for `col_patient_id`.# Basing inclusion on all antimicrobial results, using a points threshold of# 2
-# => Found 10,677 'phenotype-based' first isolates (53.4% of total where a
+# => Found 10,713 'phenotype-based' first isolates (53.6% of total where a# microbial ID was available)
-
So only 53.4% is suitable for resistance analysis! We can now filter on it with the filter() function, also from the dplyr package:
+
So only 53.6% is suitable for resistance analysis! We can now filter
+on it with the filter() function, also from the
+dplyr package:
You might want to start by getting an idea of how the data is distributed. It’s an important start, because it also decides how you will continue your analysis. Although this package contains a convenient function to make frequency tables, exploratory data analysis (EDA) is not the primary scope of this package. Use a package like DataExplorer for that, or read the free online book Exploratory Data Analysis with R by Roger D. Peng.
-
-
Dispersion of species
-
-
To just get an idea how the species are distributed, create a frequency table with our freq() function. We created the genus and species column earlier based on the microbial ID. With paste(), we can concatenate them together.
-
The freq() function can be used like the base R language was intended:
# ℹ For `aminoglycosides()` using column 'GEN' (gentamicin)
-
-
-
-
-
-
-
-
-
-
-
-
+
date
patient_id
hospital
@@ -757,23 +681,252 @@ Longest: 24
-
2017-04-11
-
I3
+
3
+
2016-12-08
+
I1
Hospital B
+
B_STPHY_AURS
+
R
+
I
+
S
+
S
+
M
+
Gram-positive
+
Staphylococcus
+
aureus
+
TRUE
+
+
+
5
+
2014-11-30
+
N6
+
Hospital C
+
B_ESCHR_COLI
+
R
+
S
+
R
+
S
+
F
+
Gram-negative
+
Escherichia
+
coli
+
TRUE
+
+
+
8
+
2016-12-03
+
J3
+
Hospital A
+
B_KLBSL_PNMN
+
R
+
S
+
R
+
R
+
M
+
Gram-negative
+
Klebsiella
+
pneumoniae
+
TRUE
+
+
+
9
+
2010-04-28
+
J10
+
Hospital A
B_ESCHR_COLI
S
S
R
-
R
+
S
M
Gram-negative
Escherichia
coli
TRUE
+
+
15
+
2010-08-04
+
L1
+
Hospital B
+
B_STRPT_PNMN
+
R
+
R
+
S
+
R
+
M
+
Gram-positive
+
Streptococcus
+
pneumoniae
+
TRUE
+
-
2013-07-04
-
C4
+
17
+
2014-04-28
+
Q5
+
Hospital C
+
B_STRPT_PNMN
+
R
+
R
+
S
+
R
+
F
+
Gram-positive
+
Streptococcus
+
pneumoniae
+
TRUE
+
+
+
+
Time for the analysis!
+
+
+
+
Analysing the data
+
+
You might want to start by getting an idea of how the data is
+distributed. It’s an important start, because it also decides how you
+will continue your analysis. Although this package contains a convenient
+function to make frequency tables, exploratory data analysis (EDA) is
+not the primary scope of this package. Use a package like DataExplorer
+for that, or read the free online book Exploratory Data Analysis
+with R by Roger D. Peng.
+
+
Dispersion of species
+
+
To just get an idea how the species are distributed, create a
+frequency table with our freq() function. We created the
+genus and species column earlier based on the
+microbial ID. With paste(), we can concatenate them
+together.
+
The freq() function can be used like the base R language
+was intended:
This will only give you the crude numbers in the data. To calculate antimicrobial resistance in a more sensible way, also by correcting for too few results, we use the resistance() and susceptibility() functions.
+
This will only give you the crude numbers in the data. To calculate
+antimicrobial resistance in a more sensible way, also by correcting for
+too few results, we use the resistance() and
+susceptibility() functions.
All these functions contain a minimum argument, denoting the minimum required number of test results for returning a value. These functions will otherwise return NA. The default is minimum = 30, following the CLSI M39-A4 guideline for applying microbial epidemiology.
-
As per the EUCAST guideline of 2019, we calculate resistance as the proportion of R (proportion_R(), equal to resistance()) and susceptibility as the proportion of S and I (proportion_SI(), equal to susceptibility()). These functions can be used on their own:
All these functions contain a minimum argument, denoting
+the minimum required number of test results for returning a value. These
+functions will otherwise return NA. The default is
+minimum = 30, following the CLSI
+M39-A4 guideline for applying microbial epidemiology.
+
As per the EUCAST guideline of 2019, we calculate resistance as the
+proportion of R (proportion_R(), equal to
+resistance()) and susceptibility as the proportion of S and
+I (proportion_SI(), equal to
+susceptibility()). These functions can be used on their
+own:
Of course it would be very convenient to know the number of isolates responsible for the percentages. For that purpose the n_rsi() can be used, which works exactly like n_distinct() from the dplyr package. It counts all isolates available for every group (i.e. values S, I or R):
+
Of course it would be very convenient to know the number of isolates
+responsible for the percentages. For that purpose the
+n_rsi() can be used, which works exactly like
+n_distinct() from the dplyr package. It counts
+all isolates available for every group (i.e. values S, I or R):
These functions can also be used to get the proportion of multiple antibiotics, to calculate empiric susceptibility of combination therapies very easily:
+
These functions can also be used to get the proportion of multiple
+antibiotics, to calculate empiric susceptibility of combination
+therapies very easily:
Or if you are curious for the resistance within certain antibiotic classes, use a antibiotic class selector such as penicillins(), which automatically will include the columns AMX and AMC of our data:
+
Or if you are curious for the resistance within certain antibiotic
+classes, use a antibiotic class selector such as
+penicillins(), which automatically will include the columns
+AMX and AMC of our data:
data_1st%>%# group by hospital
@@ -1101,27 +1284,28 @@ Longest: 24
Hospital A
-
53.5%
-
26.0%
+
54.1%
+
27.2%
Hospital B
-
54.8%
-
26.1%
+
54.1%
+
27.4%
Hospital C
-
58.0%
-
28.5%
+
54.5%
+
25.0%
Hospital D
-
52.4%
-
25.4%
+
54.5%
+
25.9%
-
To make a transition to the next part, let’s see how differences in the previously calculated combination therapies could be plotted:
+
To make a transition to the next part, let’s see how differences in
+the previously calculated combination therapies could be plotted:
To show results in plots, most R users would nowadays use the ggplot2 package. This package lets you create plots in layers. You can read more about it on their website. A quick example would look like these syntaxes:
+
+
Plots
+
+
To show results in plots, most R users would nowadays use the
+ggplot2 package. This package lets you create plots in
+layers. You can read more about it on their website. A quick
+example would look like these syntaxes:
ggplot(data =a_data_set,
mapping =aes(x =year,
@@ -1153,13 +1340,21 @@ Longest: 24
# or as short as:ggplot(a_data_set)+geom_bar(aes(year))
-
The AMR package contains functions to extend this ggplot2 package, for example geom_rsi(). It automatically transforms data with count_df() or proportion_df() and show results in stacked bars. Its simplest and shortest example:
+
The AMR package contains functions to extend this
+ggplot2 package, for example geom_rsi(). It
+automatically transforms data with count_df() or
+proportion_df() and show results in stacked bars. Its
+simplest and shortest example:
Omit the translate_ab = FALSE to have the antibiotic codes (AMX, AMC, CIP, GEN) translated to official WHO names (amoxicillin, amoxicillin/clavulanic acid, ciprofloxacin, gentamicin).
-
If we group on e.g. the genus column and add some additional functions from our package, we can create this:
+
Omit the translate_ab = FALSE to have the antibiotic
+codes (AMX, AMC, CIP, GEN) translated to official WHO names
+(amoxicillin, amoxicillin/clavulanic acid, ciprofloxacin,
+gentamicin).
+
If we group on e.g. the genus column and add some
+additional functions from our package, we can create this:
# group the data on `genus`ggplot(data_1st%>%group_by(genus))+
@@ -1182,7 +1377,8 @@ Longest: 24
# (is now y axis because we turned the plot)theme(axis.text.y =element_text(face ="italic"))
-
To simplify this, we also created the ggplot_rsi() function, which combines almost all above functions:
+
To simplify this, we also created the ggplot_rsi()
+function, which combines almost all above functions:
The AMR package also extends the plot() and ggplot2::autoplot() functions for plotting minimum inhibitory concentrations (MIC, created with as.mic()) and disk diffusion diameters (created with as.disk()).
-
With the random_mic() and random_disk() functions, we can generate sampled values for the new data types (S3 classes) <mic> and <disk>:
+
+
Plotting MIC and disk diffusion values
+
+
The AMR package also extends the plot() and
+ggplot2::autoplot() functions for plotting minimum
+inhibitory concentrations (MIC, created with as.mic()) and
+disk diffusion diameters (created with as.disk()).
+
With the random_mic() and random_disk()
+functions, we can generate sampled values for the new data types (S3
+classes) <mic> and <disk>:
But we could also be more specific, by generating MICs that are likely to be found in E. coli for ciprofloxacin:
+
But we could also be more specific, by generating MICs that are
+likely to be found in E. coli for ciprofloxacin:
mic_values<-random_mic(size =100, mo ="E. coli", ab ="cipro")
-
For the plot() and autoplot() function, we can define the microorganism and an antimicrobial agent the same way. This will add the interpretation of those values according to a chosen guidelines (defaults to the latest EUCAST guideline).
-
Default colours are colour-blind friendly, while maintaining the convention that e.g. ‘susceptible’ should be green and ‘resistant’ should be red:
+
For the plot() and autoplot() function, we
+can define the microorganism and an antimicrobial agent the same way.
+This will add the interpretation of those values according to a chosen
+guidelines (defaults to the latest EUCAST guideline).
+
Default colours are colour-blind friendly, while maintaining the
+convention that e.g. ‘susceptible’ should be green and ‘resistant’
+should be red:
# base R:plot(mic_values, mo ="E. coli", ab ="cipro")
@@ -1232,22 +1439,25 @@ Longest: 24
# ggplot2:autoplot(mic_values, mo ="E. coli", ab ="cipro")
-
For disk diffusion values, there is not much of a difference in plotting:
+
For disk diffusion values, there is not much of a difference in
+plotting:
# base R:plot(disk_values, mo ="E. coli", ab ="cipro")
-
And when using the ggplot2 package, but now choosing the latest implemented CLSI guideline (notice that the EUCAST-specific term “Susceptible, incr. exp.” has changed to “Intermediate”):
+
And when using the ggplot2 package, but now choosing the
+latest implemented CLSI guideline (notice that the EUCAST-specific term
+“Susceptible, incr. exp.” has changed to “Intermediate”):
autoplot(disk_values,
mo ="E. coli",
@@ -1256,11 +1466,17 @@ Longest: 24
-
-
Independence test
-
-
The next example uses the example_isolates data set. This is a data set included with this package and contains 2,000 microbial isolates with their full antibiograms. It reflects reality and can be used to practice AMR data analysis.
-
We will compare the resistance to fosfomycin (column FOS) in hospital A and D. The input for the fisher.test() can be retrieved with a transformation like this:
+
+
Independence test
+
+
The next example uses the example_isolates data set.
+This is a data set included with this package and contains 2,000
+microbial isolates with their full antibiograms. It reflects reality and
+can be used to practice AMR data analysis.
+
We will compare the resistance to fosfomycin (column
+FOS) in hospital A and D. The input for the
+fisher.test() can be retrieved with a transformation like
+this:
# use package 'tidyr' to pivot data:library(tidyr)
@@ -1294,7 +1510,9 @@ Longest: 24
# sample estimates:# odds ratio # 0.4488318
-
As can be seen, the p value is 0.031, which means that the fosfomycin resistance found in isolates from patients in hospital A and D are really different.
+
As can be seen, the p value is 0.031, which means that the fosfomycin
+resistance found in isolates from patients in hospital A and D are
+really different.
@@ -1311,12 +1529,14 @@ Longest: 24
diff --git a/docs/articles/AMR_files/figure-html/disk_plots-1.png b/docs/articles/AMR_files/figure-html/disk_plots-1.png
index bad9c989..e38e8ef8 100644
Binary files a/docs/articles/AMR_files/figure-html/disk_plots-1.png and b/docs/articles/AMR_files/figure-html/disk_plots-1.png differ
diff --git a/docs/articles/AMR_files/figure-html/disk_plots_mo_ab-1.png b/docs/articles/AMR_files/figure-html/disk_plots_mo_ab-1.png
index 331ff07a..eca8ce35 100644
Binary files a/docs/articles/AMR_files/figure-html/disk_plots_mo_ab-1.png and b/docs/articles/AMR_files/figure-html/disk_plots_mo_ab-1.png differ
diff --git a/docs/articles/AMR_files/figure-html/mic_plots-1.png b/docs/articles/AMR_files/figure-html/mic_plots-1.png
index 9088b85f..65083fd9 100644
Binary files a/docs/articles/AMR_files/figure-html/mic_plots-1.png and b/docs/articles/AMR_files/figure-html/mic_plots-1.png differ
diff --git a/docs/articles/AMR_files/figure-html/mic_plots-2.png b/docs/articles/AMR_files/figure-html/mic_plots-2.png
index ac936a0b..4b60d86e 100644
Binary files a/docs/articles/AMR_files/figure-html/mic_plots-2.png and b/docs/articles/AMR_files/figure-html/mic_plots-2.png differ
diff --git a/docs/articles/AMR_files/figure-html/mic_plots_mo_ab-1.png b/docs/articles/AMR_files/figure-html/mic_plots_mo_ab-1.png
index 05c50b61..45bd2747 100644
Binary files a/docs/articles/AMR_files/figure-html/mic_plots_mo_ab-1.png and b/docs/articles/AMR_files/figure-html/mic_plots_mo_ab-1.png differ
diff --git a/docs/articles/AMR_files/figure-html/mic_plots_mo_ab-2.png b/docs/articles/AMR_files/figure-html/mic_plots_mo_ab-2.png
index 3d282199..cf7dfb91 100644
Binary files a/docs/articles/AMR_files/figure-html/mic_plots_mo_ab-2.png and b/docs/articles/AMR_files/figure-html/mic_plots_mo_ab-2.png differ
diff --git a/docs/articles/AMR_files/figure-html/plot 1-1.png b/docs/articles/AMR_files/figure-html/plot 1-1.png
index a25ce222..4dae0d9a 100644
Binary files a/docs/articles/AMR_files/figure-html/plot 1-1.png and b/docs/articles/AMR_files/figure-html/plot 1-1.png differ
diff --git a/docs/articles/AMR_files/figure-html/plot 3-1.png b/docs/articles/AMR_files/figure-html/plot 3-1.png
index ba8cb20d..8eeb3b4f 100644
Binary files a/docs/articles/AMR_files/figure-html/plot 3-1.png and b/docs/articles/AMR_files/figure-html/plot 3-1.png differ
diff --git a/docs/articles/AMR_files/figure-html/plot 4-1.png b/docs/articles/AMR_files/figure-html/plot 4-1.png
index 5a2f053e..8065338b 100644
Binary files a/docs/articles/AMR_files/figure-html/plot 4-1.png and b/docs/articles/AMR_files/figure-html/plot 4-1.png differ
diff --git a/docs/articles/AMR_files/figure-html/plot 5-1.png b/docs/articles/AMR_files/figure-html/plot 5-1.png
index 43a9fada..03e388bb 100644
Binary files a/docs/articles/AMR_files/figure-html/plot 5-1.png and b/docs/articles/AMR_files/figure-html/plot 5-1.png differ
diff --git a/docs/articles/datasets.html b/docs/articles/datasets.html
index 96ba838f..c1109448 100644
--- a/docs/articles/datasets.html
+++ b/docs/articles/datasets.html
@@ -44,7 +44,7 @@
AMR (for R)
- 1.8.0.9004
+ 1.8.0.9005
All reference data (about microorganisms, antibiotics, R/SI interpretation, EUCAST rules, etc.) in this AMR package are reliable, up-to-date and freely available. We continually export our data sets to formats for use in R, SPSS, SAS, Stata and Excel. We also supply tab separated files that are machine-readable and suitable for input in any software program, such as laboratory information systems.
-
On this page, we explain how to download them and how the structure of the data sets look like.
+
All reference data (about microorganisms, antibiotics, R/SI
+interpretation, EUCAST rules, etc.) in this AMR package are
+reliable, up-to-date and freely available. We continually export our
+data sets to formats for use in R, SPSS, SAS, Stata and Excel. We also
+supply tab separated files that are machine-readable and suitable for
+input in any software program, such as laboratory information
+systems.
+
On this page, we explain how to download them and how the structure
+of the data sets look like.
-If you are reading this page from within R, please visit our website, which is automatically updated with every code change.
+If you are reading this page from within R, please
+visit
+our website, which is automatically updated with every code change.
Microorganisms (currently accepted names)
-
A data set with 70,760 rows and 16 columns, containing the following column names: mo, fullname, kingdom, phylum, class, order, family, genus, species, subspecies, rank, ref, species_id, source, prevalence and snomed.
-
This data set is in R available as microorganisms, after you load the AMR package.
-
It was last updated on 29 November 2021 11:38:23 UTC. Find more info about the structure of this data set here.
+
A data set with 70,760 rows and 16 columns, containing the following
+column names: mo, fullname, kingdom, phylum,
+class, order, family, genus,
+species, subspecies, rank, ref,
+species_id, source, prevalence and
+snomed.
+
This data set is in R available as microorganisms, after
+you load the AMR package.
+
It was last updated on 29 November 2021 11:38:23 UTC. Find more info
+about the structure of this data set here.
NOTE: The exported files for SAS, SPSS and Stata do not contain SNOMED codes, as their file size would exceed 100 MB; the file size limit of GitHub. Advice? Use R instead.
+
NOTE: The exported files for SAS, SPSS and Stata do not
+contain SNOMED codes, as their file size would exceed 100 MB; the file
+size limit of GitHub. Advice? Use R instead.
Source
-
Our full taxonomy of microorganisms is based on the authoritative and comprehensive:
+
Our full taxonomy of microorganisms is based on the authoritative and
+comprehensive:
A data set with 14,338 rows and 4 columns, containing the following column names: fullname, fullname_new, ref and prevalence.
-
Note: remember that the ‘ref’ columns contains the scientific reference to the old taxonomic entries, i.e. of column ‘fullname’. For the scientific reference of the new names, i.e. of column ‘fullname_new’, see the microorganisms data set.
-
This data set is in R available as microorganisms.old, after you load the AMR package.
-
It was last updated on 6 October 2021 14:38:29 UTC. Find more info about the structure of this data set here.
+
A data set with 14,338 rows and 4 columns, containing the following
+column names: fullname, fullname_new, ref and
+prevalence.
+
Note: remember that the ‘ref’ columns contains the
+scientific reference to the old taxonomic entries, i.e. of column
+‘fullname’. For the scientific reference of the new names,
+i.e. of column ‘fullname_new’, see the
+microorganisms data set.
+
This data set is in R available as microorganisms.old,
+after you load the AMR package.
+
It was last updated on 6 October 2021 14:38:29 UTC. Find more info
+about the structure of this data set here.
A data set with 464 rows and 14 columns, containing the following column names: ab, cid, name, group, atc, atc_group1, atc_group2, abbreviations, synonyms, oral_ddd, oral_units, iv_ddd, iv_units and loinc.
-
This data set is in R available as antibiotics, after you load the AMR package.
-
It was last updated on 14 December 2021 21:59:33 UTC. Find more info about the structure of this data set here.
+
A data set with 464 rows and 14 columns, containing the following
+column names: ab, cid, name, group, atc,
+atc_group1, atc_group2, abbreviations,
+synonyms, oral_ddd, oral_units,
+iv_ddd, iv_units and loinc.
+
This data set is in R available as antibiotics, after
+you load the AMR package.
+
It was last updated on 14 December 2021 21:59:33 UTC. Find more info
+about the structure of this data set here.
This data set contains all EARS-Net and ATC codes gathered from WHO and WHONET, and all compound IDs from PubChem. It also contains all brand names (synonyms) as found on PubChem and Defined Daily Doses (DDDs) for oral and parenteral administration.
+
This data set contains all EARS-Net and ATC codes gathered from WHO
+and WHONET, and all compound IDs from PubChem. It also contains all
+brand names (synonyms) as found on PubChem and Defined Daily Doses
+(DDDs) for oral and parenteral administration.
A data set with 102 rows and 9 columns, containing the following column names: atc, cid, name, atc_group, synonyms, oral_ddd, oral_units, iv_ddd and iv_units.
-
This data set is in R available as antivirals, after you load the AMR package.
-
It was last updated on 29 August 2020 19:53:07 UTC. Find more info about the structure of this data set here.
+
A data set with 102 rows and 9 columns, containing the following
+column names: atc, cid, name, atc_group,
+synonyms, oral_ddd, oral_units,
+iv_ddd and iv_units.
+
This data set is in R available as antivirals, after you
+load the AMR package.
+
It was last updated on 29 August 2020 19:53:07 UTC. Find more info
+about the structure of this data set here.
This data set contains all ATC codes gathered from WHO and all compound IDs from PubChem. It also contains all brand names (synonyms) as found on PubChem and Defined Daily Doses (DDDs) for oral and parenteral administration.
+
This data set contains all ATC codes gathered from WHO and all
+compound IDs from PubChem. It also contains all brand names (synonyms)
+as found on PubChem and Defined Daily Doses (DDDs) for oral and
+parenteral administration.
A data set with 20,318 rows and 11 columns, containing the following column names: guideline, method, site, mo, rank_index, ab, ref_tbl, disk_dose, breakpoint_S, breakpoint_R and uti.
-
This data set is in R available as rsi_translation, after you load the AMR package.
-
It was last updated on 14 December 2021 21:59:33 UTC. Find more info about the structure of this data set here.
+
A data set with 20,318 rows and 11 columns, containing the following
+column names: guideline, method, site, mo,
+rank_index, ab, ref_tbl, disk_dose,
+breakpoint_S, breakpoint_R and uti.
+
This data set is in R available as rsi_translation,
+after you load the AMR package.
+
It was last updated on 14 December 2021 21:59:33 UTC. Find more info
+about the structure of this data set here.
This data set contains interpretation rules for MIC values and disk diffusion diameters. Included guidelines are CLSI (2010-2021) and EUCAST (2011-2021).
+
This data set contains interpretation rules for MIC values and disk
+diffusion diameters. Included guidelines are CLSI (2010-2021) and EUCAST
+(2011-2021).
Example content
@@ -1193,33 +1313,57 @@ If you are reading this page from within R, please
A data set with 169 rows and 9 columns, containing the following column names: ab, name, type, dose, dose_times, administration, notes, original_txt and eucast_version.
-
This data set is in R available as dosage, after you load the AMR package.
-
It was last updated on 25 January 2021 20:58:20 UTC. Find more info about the structure of this data set here.
+
A data set with 169 rows and 9 columns, containing the following
+column names: ab, name, type, dose,
+dose_times, administration, notes,
+original_txt and eucast_version.
+
This data set is in R available as dosage, after you
+load the AMR package.
+
It was last updated on 25 January 2021 20:58:20 UTC. Find more info
+about the structure of this data set here.
Update: The latest EUCAST guideline for intrinsic resistance (v3.3, October 2021) is now supported, the CLSI 2021 interpretation guideline is now supported, and our taxonomy tables have been updated as well (LPSN, 5 October 2021).
+
Update: The latest EUCAST
+guideline for intrinsic resistance (v3.3, October 2021) is now
+supported, the CLSI 2021 interpretation guideline is now supported, and
+our taxonomy tables have been updated as well (LPSN, 5 October
+2021).
What is AMR (for R)?
-
AMR is a free, open-source and independent R package (see Copyright) to simplify the analysis and prediction of Antimicrobial Resistance (AMR) and to work with microbial and antimicrobial data and properties, by using evidence-based methods. Our aim is to provide a standard for clean and reproducible AMR data analysis, that can therefore empower epidemiological analyses to continuously enable surveillance and treatment evaluation in any setting.
The AMR package is available in Danish, Dutch, English, French, German, Italian, Portuguese, Russian, Spanish and Swedish. Antimicrobial drug (group) names and colloquial microorganism names are provided in these languages.
AMR is a free, open-source and independent R package (see Copyright) to simplify the analysis and prediction
+of Antimicrobial Resistance (AMR) and to work with microbial and
+antimicrobial data and properties, by using evidence-based methods.
+Our aim is to provide a standard for clean and
+reproducible AMR data analysis, that can therefore empower
+epidemiological analyses to continuously enable surveillance and
+treatment evaluation in any setting.
The AMR package is available in
+
+Danish,
+
+Dutch,
+
+English,
+
+French,
+
+German,
+
+Italian,
+
+Portuguese,
+
+Russian,
+
+Spanish and
+
+Swedish. Antimicrobial drug (group) names and colloquial microorganism
+names are provided in these languages.
-Used in 175 countries Since its first public release in early 2018, this R package has been used in almost all countries in the world. Click the map to enlarge and to see the country names.
+
+Used in 175 countries Since its first public
+release in early 2018, this R package has been used in almost all
+countries in the world. Click the map to enlarge and to see the country
+names.
-
With AMR (for R), there’s always a knowledgeable microbiologist by your side!
+
With AMR (for R), there’s always a knowledgeable
+microbiologist by your side!
# AMR works great with dplyr, but it's not required or neccesary
@@ -224,7 +277,12 @@
select(bacteria,
aminoglycosides(),
carbapenems())
It will be downloaded and installed automatically. For RStudio, click on the menu Tools > Install Packages… and then type in “AMR” and press Install.
-
Note: Not all functions on this website may be available in this latest release. To use all functions and data sets mentioned on this website, install the latest development version.
+
It will be downloaded and installed automatically. For RStudio, click
+on the menu Tools > Install Packages… and then type
+in “AMR” and press Install.
+
Note: Not all functions on this website may be
+available in this latest release. To use all functions and data sets
+mentioned on this website, install the latest development version.
Latest development version
-
The latest and unpublished development version can be installed from GitHub in two ways:
+
The latest and unpublished development version can be installed from
+GitHub in two ways:
After this, you can install and update this AMR package like any official release (e.g., using install.packages("AMR") or in RStudio via Tools > Check for Package Updates…).
+
After this, you can install and update this AMR package
+like any official release (e.g., using
+install.packages("AMR") or in RStudio via Tools
+> Check for Package Updates…).
This package contains the complete taxonomic tree of almost all ~70,000 microorganisms from the authoritative and comprehensive Catalogue of Life (CoL, www.catalogueoflife.org), supplemented by data from the List of Prokaryotic names with Standing in Nomenclature (LPSN, lpsn.dsmz.de). This supplementation is needed until the CoL+ project is finished, which we await. With catalogue_of_life_version() can be checked which version of the CoL is included in this package.
+
This package contains the complete taxonomic tree of almost all
+~70,000 microorganisms from the authoritative and comprehensive
+Catalogue of Life (CoL, www.catalogueoflife.org),
+supplemented by data from the List of Prokaryotic names with Standing in
+Nomenclature (LPSN, lpsn.dsmz.de).
+This supplementation is needed until the CoL+ project is finished,
+which we await. With catalogue_of_life_version() can be
+checked which version of the CoL is included in this package.
Read more about which data from the Catalogue of Life in our manual.
Antimicrobial reference data
-
This package contains all ~550 antibiotic, antimycotic and antiviral drugs and their Anatomical Therapeutic Chemical (ATC) codes, ATC groups and Defined Daily Dose (DDD, oral and IV) from the World Health Organization Collaborating Centre for Drug Statistics Methodology (WHOCC, https://www.whocc.no) and the Pharmaceuticals Community Register of the European Commission.
This package contains all ~550 antibiotic, antimycotic and
+antiviral drugs and their Anatomical Therapeutic Chemical (ATC)
+codes, ATC groups and Defined Daily Dose (DDD, oral and IV) from the
+World Health Organization Collaborating Centre for Drug Statistics
+Methodology (WHOCC, https://www.whocc.no) and the Pharmaceuticals
+Community Register of the European Commission.
We support WHONET and EARS-Net data. Exported files from WHONET can be imported into R and can be analysed easily using this package. For education purposes, we created an example data set WHONET with the exact same structure as a WHONET export file. Furthermore, this package also contains a data set antibiotics with all EARS-Net antibiotic abbreviations, and knows almost all WHONET abbreviations for microorganisms. When using WHONET data as input for analysis, all input parameters will be set automatically.
We support WHONET and EARS-Net data. Exported files from WHONET can
+be imported into R and can be analysed easily using this package. For
+education purposes, we created an example data set WHONET
+with the exact same structure as a WHONET export file. Furthermore, this
+package also contains a data set
+antibiotics with all EARS-Net antibiotic abbreviations, and knows
+almost all WHONET abbreviations for microorganisms. When using WHONET
+data as input for analysis, all input parameters will be set
+automatically.
The AMR package basically does four important things:
+
The AMR package basically does four important
+things:
-
It cleanses existing data by providing new classes for microoganisms, antibiotics and antimicrobial results (both S/I/R and MIC). By installing this package, you teach R everything about microbiology that is needed for analysis. These functions all use intelligent rules to guess results that you would expect:
+
It cleanses existing data by providing new
+classes for microoganisms, antibiotics and antimicrobial
+results (both S/I/R and MIC). By installing this package, you teach R
+everything about microbiology that is needed for analysis. These
+functions all use intelligent rules to guess results that you would
+expect:
-
Use as.mo() to get a microbial ID. The IDs are human readable for the trained eye - the ID of Klebsiella pneumoniae is “B_KLBSL_PNMN” (B stands for Bacteria) and the ID of S. aureus is “B_STPHY_AURS”. The function takes almost any text as input that looks like the name or code of a microorganism like “E. coli”, “esco” or “esccol” and tries to find expected results using intelligent rules combined with the included Catalogue of Life data set. It only takes milliseconds to find results, please see our benchmarks. Moreover, it can group Staphylococci into coagulase negative and positive (CoNS and CoPS, see source) and can categorise Streptococci into Lancefield groups (like beta-haemolytic Streptococcus Group B, source).
-
Use as.ab() to get an antibiotic ID. Like microbial IDs, these IDs are also human readable based on those used by EARS-Net. For example, the ID of amoxicillin is AMX and the ID of gentamicin is GEN. The as.ab() function also uses intelligent rules to find results like accepting misspelling, trade names and abbrevations used in many laboratory systems. For instance, the values “Furabid”, “Furadantin”, “nitro” all return the ID of Nitrofurantoine. To accomplish this, the package contains a database with most LIS codes, official names, trade names, ATC codes, defined daily doses (DDD) and drug categories of antibiotics.
-
Use as.rsi() to get antibiotic interpretations based on raw MIC values (in mg/L) or disk diffusion values (in mm), or transform existing values to valid antimicrobial results. It produces just S, I or R based on your input and warns about invalid values. Even values like “<=0.002; S” (combined MIC/RSI) will result in “S”.
-
Use as.mic() to cleanse your MIC values. It produces a so-called factor (called ordinal in SPSS) with valid MIC values as levels. A value like “<=0.002; S” (combined MIC/RSI) will result in “<=0.002”.
+
Use as.mo() to get a microbial ID. The IDs are human
+readable for the trained eye - the ID of Klebsiella pneumoniae
+is “B_KLBSL_PNMN” (B stands for Bacteria) and the ID of S.
+aureus is “B_STPHY_AURS”. The function takes almost any text as
+input that looks like the name or code of a microorganism like “E.
+coli”, “esco” or “esccol” and tries to find expected results using
+intelligent rules combined with the included Catalogue of Life data set.
+It only takes milliseconds to find results, please see our benchmarks. Moreover, it can group
+Staphylococci into coagulase negative and positive (CoNS and
+CoPS, see source) and can
+categorise Streptococci into Lancefield groups (like
+beta-haemolytic Streptococcus Group B, source).
+
Use as.ab() to get an antibiotic ID. Like microbial
+IDs, these IDs are also human readable based on those used by EARS-Net.
+For example, the ID of amoxicillin is AMX and the ID of
+gentamicin is GEN. The as.ab() function also
+uses intelligent rules to find results like accepting misspelling, trade
+names and abbrevations used in many laboratory systems. For instance,
+the values “Furabid”, “Furadantin”, “nitro” all return the ID of
+Nitrofurantoine. To accomplish this, the package contains a database
+with most LIS codes, official names, trade names, ATC codes, defined
+daily doses (DDD) and drug categories of antibiotics.
+
Use as.rsi() to get antibiotic interpretations based on
+raw MIC values (in mg/L) or disk diffusion values (in mm), or transform
+existing values to valid antimicrobial results. It produces just S, I or
+R based on your input and warns about invalid values. Even values like
+“<=0.002; S” (combined MIC/RSI) will result in “S”.
+
Use as.mic() to cleanse your MIC values. It produces a
+so-called factor (called ordinal in SPSS) with valid MIC values
+as levels. A value like “<=0.002; S” (combined MIC/RSI) will result
+in “<=0.002”.
-
It enhances existing data and adds new data from data sets included in this package.
+
It enhances existing data and adds new
+data from data sets included in this package.
You can also identify first weighted isolates of every patient, an adjusted version of the CLSI guideline. This takes into account key antibiotics of every strain and compares them.
+
You can also identify first weighted isolates of every
+patient, an adjusted version of the CLSI guideline. This takes into
+account key antibiotics of every strain and compares them.
-
Use mdro() to determine which micro-organisms are multi-drug resistant organisms (MDRO). It supports a variety of international guidelines, such as the MDR-paper by Magiorakos et al. (2012, PMID 21793988), the exceptional phenotype definitions of EUCAST and the WHO guideline on multi-drug resistant TB. It also supports the national guidelines of the Netherlands and Germany.
-
The data set microorganisms contains the complete taxonomic tree of ~70,000 microorganisms. Furthermore, some colloquial names and all Gram stains are available, which enables resistance analysis of e.g. different antibiotics per Gram stain. The package also contains functions to look up values in this data set like mo_genus(), mo_family(), mo_gramstain() or even mo_phylum(). Use mo_snomed() to look up any SNOMED CT code associated with a microorganism. As all these function use as.mo() internally, they also use the same intelligent rules for determination. For example, mo_genus("MRSA") and mo_genus("S. aureus") will both return "Staphylococcus". They also come with support for German, Danish, Dutch, Spanish, Italian, French and Portuguese. These functions can be used to add new variables to your data.
-
The data set antibiotics contains ~450 antimicrobial drugs with their EARS-Net code, ATC code, PubChem compound ID, LOINC code, official name, common LIS codes and DDDs of both oral and parenteral administration. It also contains all (thousands of) trade names found in PubChem. Use functions like ab_name(), ab_group(), ab_atc(), ab_loinc() and ab_tradenames() to look up values. The ab_* functions use as.ab() internally so they support the same intelligent rules to guess the most probable result. For example, ab_name("Fluclox"), ab_name("Floxapen") and ab_name("J01CF05") will all return "Flucloxacillin". These functions can again be used to add new variables to your data.
+
Use mdro() to determine which micro-organisms are
+multi-drug resistant organisms (MDRO). It supports a variety of
+international guidelines, such as the MDR-paper by Magiorakos et
+al. (2012, PMID
+21793988), the exceptional phenotype definitions of EUCAST and the
+WHO guideline on multi-drug resistant TB. It also supports the national
+guidelines of the Netherlands and Germany.
+
The data set
+microorganisms contains the complete taxonomic tree of ~70,000
+microorganisms. Furthermore, some colloquial names and all Gram stains
+are available, which enables resistance analysis of e.g. different
+antibiotics per Gram stain. The package also contains functions to look
+up values in this data set like mo_genus(),
+mo_family(), mo_gramstain() or even
+mo_phylum(). Use mo_snomed() to look up any
+SNOMED CT code associated with a microorganism. As all these function
+use as.mo() internally, they also use the same intelligent
+rules for determination. For example, mo_genus("MRSA") and
+mo_genus("S. aureus") will both return
+"Staphylococcus". They also come with support for German,
+Danish, Dutch, Spanish, Italian, French and Portuguese. These functions
+can be used to add new variables to your data.
+
The data set antibiotics
+contains ~450 antimicrobial drugs with their EARS-Net code, ATC code,
+PubChem compound ID, LOINC code, official name, common LIS codes and
+DDDs of both oral and parenteral administration. It also contains all
+(thousands of) trade names found in PubChem. Use functions like
+ab_name(), ab_group(), ab_atc(),
+ab_loinc() and ab_tradenames() to look up
+values. The ab_* functions use as.ab()
+internally so they support the same intelligent rules to guess the most
+probable result. For example, ab_name("Fluclox"),
+ab_name("Floxapen") and ab_name("J01CF05")
+will all return "Flucloxacillin". These functions can again
+be used to add new variables to your data.
-
It analyses the data with convenient functions that use well-known methods.
+
It analyses the data with convenient functions
+that use well-known methods.
Plot AMR results with geom_rsi(), a function made for
+the ggplot2 package
+
Predict antimicrobial resistance for the nextcoming years using
+logistic regression models with the resistance_predict()
+function
-
It teaches the user how to use all the above actions.
+
It teaches the user how to use all the above
+actions.
-
Aside from this website with many tutorials, the package itself contains extensive help pages with many examples for all functions.
+
Aside from this website with many tutorials, the package itself
+contains extensive help pages with many examples for all functions.
The package also contains example data sets:
-
The example_isolates data set. This data set contains 2,000 microbial isolates with their full antibiograms. It reflects reality and can be used to practice AMR data analysis.
-
The WHONET data set. This data set only contains fake data, but with the exact same structure as files exported by WHONET. Read more about WHONET on its tutorial page.
+
The example_isolates
+data set. This data set contains 2,000 microbial isolates with their
+full antibiograms. It reflects reality and can be used to practice AMR
+data analysis.
+
The WHONET data
+set. This data set only contains fake data, but with the exact same
+structure as files exported by WHONET. Read more about WHONET on its tutorial page.
The lifecycle of this function is stable. In a stable function, major changes are unlikely. This means that the unlying code will generally evolve by adding new arguments; removing arguments or changing the meaning of existing arguments will be avoided.
-
If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit an message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
+
If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit a message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
Read more on Our Website!
@@ -275,11 +275,13 @@ The lifecycle of this function is stable
-
Developed by Matthijs S. Berends, Christian F. Luz, Dennis Souverein, Erwin E. A. Hassing.
+
Developed by Matthijs S. Berends, Christian F. Luz, Dennis Souverein,
+Erwin E. A. Hassing.
The lifecycle of this function is stable. In a stable function, major changes are unlikely. This means that the unlying code will generally evolve by adding new arguments; removing arguments or changing the meaning of existing arguments will be avoided.
-
If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit an message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
+
If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit a message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
Source
@@ -344,11 +344,13 @@ The lifecycle of this function is stable
-
Developed by Matthijs S. Berends, Christian F. Luz, Dennis Souverein, Erwin E. A. Hassing.
+
Developed by Matthijs S. Berends, Christian F. Luz, Dennis Souverein,
+Erwin E. A. Hassing.
The lifecycle of this function is stable. In a stable function, major changes are unlikely. This means that the unlying code will generally evolve by adding new arguments; removing arguments or changing the meaning of existing arguments will be avoided.
-
If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit an message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
+
If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit a message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
Read more on Our Website!
@@ -226,11 +226,13 @@ The lifecycle of this function is stable
-
Developed by Matthijs S. Berends, Christian F. Luz, Dennis Souverein, Erwin E. A. Hassing.
+
Developed by Matthijs S. Berends, Christian F. Luz, Dennis Souverein,
+Erwin E. A. Hassing.
diff --git a/docs/reference/age_groups.html b/docs/reference/age_groups.html
index d261d8df..3fe52145 100644
--- a/docs/reference/age_groups.html
+++ b/docs/reference/age_groups.html
@@ -17,7 +17,7 @@
AMR (for R)
- 1.8.0.9004
+ 1.8.0.9005
@@ -194,7 +194,7 @@ The default is to split on young children (0-11), youth (12-24), young adults (2
The lifecycle of this function is stable. In a stable function, major changes are unlikely. This means that the unlying code will generally evolve by adding new arguments; removing arguments or changing the meaning of existing arguments will be avoided.
-
If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit an message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
+
If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit a message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
Read more on Our Website!
@@ -250,11 +250,13 @@ The lifecycle of this function is stable
-
Developed by Matthijs S. Berends, Christian F. Luz, Dennis Souverein, Erwin E. A. Hassing.
+
Developed by Matthijs S. Berends, Christian F. Luz, Dennis Souverein,
+Erwin E. A. Hassing.
The lifecycle of this function is stable. In a stable function, major changes are unlikely. This means that the unlying code will generally evolve by adding new arguments; removing arguments or changing the meaning of existing arguments will be avoided.
-
If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit an message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
+
If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit a message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
Reference Data Publicly Available
@@ -430,11 +430,13 @@ The lifecycle of this function is stable
-
Developed by Matthijs S. Berends, Christian F. Luz, Dennis Souverein, Erwin E. A. Hassing.
+
Developed by Matthijs S. Berends, Christian F. Luz, Dennis Souverein,
+Erwin E. A. Hassing.
The lifecycle of this function is stable. In a stable function, major changes are unlikely. This means that the unlying code will generally evolve by adding new arguments; removing arguments or changing the meaning of existing arguments will be avoided.
-
If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit an message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
+
If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit a message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
WHOCC
@@ -280,11 +280,13 @@ This package contains all ~550 antibiotic, antimycotic and antiviral dru
The lifecycle of this function is stable. In a stable function, major changes are unlikely. This means that the unlying code will generally evolve by adding new arguments; removing arguments or changing the meaning of existing arguments will be avoided.
-
If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit an message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
+
If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit a message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
Read more on Our Website!
@@ -239,11 +239,13 @@ The lifecycle of this function is stable
-
Developed by Matthijs S. Berends, Christian F. Luz, Dennis Souverein, Erwin E. A. Hassing.
+
Developed by Matthijs S. Berends, Christian F. Luz, Dennis Souverein,
+Erwin E. A. Hassing.
The lifecycle of this function is stable. In a stable function, major changes are unlikely. This means that the unlying code will generally evolve by adding new arguments; removing arguments or changing the meaning of existing arguments will be avoided.
-
If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit an message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
+
If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit a message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
Read more on Our Website!
@@ -273,11 +273,13 @@ The lifecycle of this function is stable
-
Developed by Matthijs S. Berends, Christian F. Luz, Dennis Souverein, Erwin E. A. Hassing.
+
Developed by Matthijs S. Berends, Christian F. Luz, Dennis Souverein,
+Erwin E. A. Hassing.
The lifecycle of this function is stable. In a stable function, major changes are unlikely. This means that the unlying code will generally evolve by adding new arguments; removing arguments or changing the meaning of existing arguments will be avoided.
-
If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit an message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
+
If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit a message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
Matching Score for Microorganisms
@@ -377,11 +377,13 @@ This package contains the complete taxonomic tree of almost all microorganisms (
diff --git a/docs/reference/as.rsi.html b/docs/reference/as.rsi.html
index b996975b..05e31b60 100644
--- a/docs/reference/as.rsi.html
+++ b/docs/reference/as.rsi.html
@@ -17,7 +17,7 @@
AMR (for R)
- 1.8.0.9004
+ 1.8.0.9005
@@ -309,7 +309,7 @@ A microorganism is categorised as Susceptible, Increased exposure when
The lifecycle of this function is stable. In a stable function, major changes are unlikely. This means that the unlying code will generally evolve by adding new arguments; removing arguments or changing the meaning of existing arguments will be avoided.
-
If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit an message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
+
If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit a message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
Reference Data Publicly Available
@@ -423,11 +423,13 @@ The lifecycle of this function is stable
-
Developed by Matthijs S. Berends, Christian F. Luz, Dennis Souverein, Erwin E. A. Hassing.
+
Developed by Matthijs S. Berends, Christian F. Luz, Dennis Souverein,
+Erwin E. A. Hassing.
The lifecycle of this function is stable. In a stable function, major changes are unlikely. This means that the unlying code will generally evolve by adding new arguments; removing arguments or changing the meaning of existing arguments will be avoided.
-
If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit an message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
+
If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit a message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
Read more on Our Website!
@@ -257,11 +257,13 @@ The lifecycle of this function is stable
-
Developed by Matthijs S. Berends, Christian F. Luz, Dennis Souverein, Erwin E. A. Hassing.
+
Developed by Matthijs S. Berends, Christian F. Luz, Dennis Souverein,
+Erwin E. A. Hassing.
The lifecycle of this function is stable. In a stable function, major changes are unlikely. This means that the unlying code will generally evolve by adding new arguments; removing arguments or changing the meaning of existing arguments will be avoided.
-
If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit an message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
+
If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit a message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
Read more on Our Website!
@@ -216,11 +216,13 @@ The lifecycle of this function is stable
-
Developed by Matthijs S. Berends, Christian F. Luz, Dennis Souverein, Erwin E. A. Hassing.
+
Developed by Matthijs S. Berends, Christian F. Luz, Dennis Souverein,
+Erwin E. A. Hassing.
The lifecycle of this function is stable. In a stable function, major changes are unlikely. This means that the unlying code will generally evolve by adding new arguments; removing arguments or changing the meaning of existing arguments will be avoided.
-
If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit an message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
+
If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit a message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
Read more on Our Website!
@@ -265,11 +265,13 @@ The lifecycle of this function is stable
-
Developed by Matthijs S. Berends, Christian F. Luz, Dennis Souverein, Erwin E. A. Hassing.
+
Developed by Matthijs S. Berends, Christian F. Luz, Dennis Souverein,
+Erwin E. A. Hassing.
diff --git a/docs/reference/count.html b/docs/reference/count.html
index 2e7935c7..d35f444e 100644
--- a/docs/reference/count.html
+++ b/docs/reference/count.html
@@ -18,7 +18,7 @@ count_resistant() should be used to count resistant isolates, count_susceptible(
AMR (for R)
- 1.8.0.9004
+ 1.8.0.9005
@@ -225,7 +225,7 @@ count_resistant() should be used to count resistant isolates, count_susceptible(
The lifecycle of this function is stable. In a stable function, major changes are unlikely. This means that the unlying code will generally evolve by adding new arguments; removing arguments or changing the meaning of existing arguments will be avoided.
-
If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit an message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
+
If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit a message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
Interpretation of R and S/I
@@ -358,11 +358,13 @@ A microorganism is categorised as Susceptible, Increased exposure when
The lifecycle of this function is stable. In a stable function, major changes are unlikely. This means that the unlying code will generally evolve by adding new arguments; removing arguments or changing the meaning of existing arguments will be avoided.
-
If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit an message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
+
If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit a message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
Read more on Our Website!
@@ -301,11 +301,13 @@ The lifecycle of this function is stable
-
Developed by Matthijs S. Berends, Christian F. Luz, Dennis Souverein, Erwin E. A. Hassing.
+
Developed by Matthijs S. Berends, Christian F. Luz, Dennis Souverein,
+Erwin E. A. Hassing.
diff --git a/docs/reference/eucast_rules.html b/docs/reference/eucast_rules.html
index b7b2aef0..1cee5457 100644
--- a/docs/reference/eucast_rules.html
+++ b/docs/reference/eucast_rules.html
@@ -18,7 +18,7 @@ To improve the interpretation of the antibiogram before EUCAST rules are applied
AMR (for R)
- 1.8.0.9004
+ 1.8.0.9005
@@ -265,7 +265,7 @@ Leclercq et al. EUCAST expert rules in antimicrobial susceptibility test
The lifecycle of this function is stable. In a stable function, major changes are unlikely. This means that the unlying code will generally evolve by adding new arguments; removing arguments or changing the meaning of existing arguments will be avoided.
-
If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit an message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
+
If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit a message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
Reference Data Publicly Available
@@ -334,11 +334,13 @@ The lifecycle of this function is stable
-
Developed by Matthijs S. Berends, Christian F. Luz, Dennis Souverein, Erwin E. A. Hassing.
+
Developed by Matthijs S. Berends, Christian F. Luz, Dennis Souverein,
+Erwin E. A. Hassing.
The lifecycle of this function is stable. In a stable function, major changes are unlikely. This means that the unlying code will generally evolve by adding new arguments; removing arguments or changing the meaning of existing arguments will be avoided.
-
If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit an message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
+
If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit a message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
Read more on Our Website!
@@ -371,11 +371,13 @@ The lifecycle of this function is stable
-
Developed by Matthijs S. Berends, Christian F. Luz, Dennis Souverein, Erwin E. A. Hassing.
+
Developed by Matthijs S. Berends, Christian F. Luz, Dennis Souverein,
+Erwin E. A. Hassing.
The lifecycle of this function is stable. In a stable function, major changes are unlikely. This means that the unlying code will generally evolve by adding new arguments; removing arguments or changing the meaning of existing arguments will be avoided.
-
If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit an message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
+
If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit a message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
Read more on Our Website!
@@ -278,11 +278,13 @@ The lifecycle of this function is stable
-
Developed by Matthijs S. Berends, Christian F. Luz, Dennis Souverein, Erwin E. A. Hassing.
+
Developed by Matthijs S. Berends, Christian F. Luz, Dennis Souverein,
+Erwin E. A. Hassing.
The lifecycle of this function is stable. In a stable function, major changes are unlikely. This means that the unlying code will generally evolve by adding new arguments; removing arguments or changing the meaning of existing arguments will be avoided.
-
If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit an message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
+
If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit a message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
@@ -304,11 +304,13 @@ The lifecycle of this function is stable
-
Developed by Matthijs S. Berends, Christian F. Luz, Dennis Souverein, Erwin E. A. Hassing.
+
Developed by Matthijs S. Berends, Christian F. Luz, Dennis Souverein,
+Erwin E. A. Hassing.
The lifecycle of this function is stable. In a stable function, major changes are unlikely. This means that the unlying code will generally evolve by adding new arguments; removing arguments or changing the meaning of existing arguments will be avoided.
-
If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit an message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
+
If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit a message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
Read more on Our Website!
@@ -395,11 +395,13 @@ The lifecycle of this function is stable
-
Developed by Matthijs S. Berends, Christian F. Luz, Dennis Souverein, Erwin E. A. Hassing.
+
Developed by Matthijs S. Berends, Christian F. Luz, Dennis Souverein,
+Erwin E. A. Hassing.
The lifecycle of this function is stable. In a stable function, major changes are unlikely. This means that the unlying code will generally evolve by adding new arguments; removing arguments or changing the meaning of existing arguments will be avoided.
-
If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit an message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
+
If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit a message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
Read more on Our Website!
@@ -243,11 +243,13 @@ The lifecycle of this function is stable
-
Developed by Matthijs S. Berends, Christian F. Luz, Dennis Souverein, Erwin E. A. Hassing.
+
Developed by Matthijs S. Berends, Christian F. Luz, Dennis Souverein,
+Erwin E. A. Hassing.
These functions are meant to get taxonomically valid properties of microorganisms from any input. Use mo_source() to teach this package how to translate your own codes to valid microorganism codes.
+
These functions are meant to get taxonomically valid properties of
+microorganisms from any input. Use mo_source() to teach
+this package how to translate your own codes to valid microorganism
+codes.
User-Defined Reference Data Set for Microorganisms
Preparing data: antibiotics
-
Use these functions to get valid properties of antibiotics from any input or to clean your input. You can even retrieve drug names and doses from clinical text records, using ab_from_text().
+
Use these functions to get valid properties of antibiotics from any
+input or to clean your input. You can even retrieve drug names and doses
+from clinical text records, using ab_from_text().
With as.mic() and as.disk() you can transform your raw input to valid MIC or disk diffusion values. Use as.rsi() for cleaning raw data to let it only contain “R”, “I” and “S”, or to interpret MIC or disk diffusion values as R/SI based on the lastest EUCAST and CLSI guidelines. Afterwards, you can extend antibiotic interpretations by applying EUCAST rules with eucast_rules().
+
With as.mic() and as.disk() you can
+transform your raw input to valid MIC or disk diffusion values. Use
+as.rsi() for cleaning raw data to let it only contain “R”,
+“I” and “S”, or to interpret MIC or disk diffusion values as R/SI based
+on the lastest EUCAST and CLSI guidelines. Afterwards, you can extend
+antibiotic interpretations by applying EUCAST
+rules with eucast_rules().
Use these function for the analysis part. You can use susceptibility() or resistance() on any antibiotic column. Be sure to first select the isolates that are appropiate for analysis, by using first_isolate() or is_new_episode(). You can also filter your data on certain resistance in certain antibiotic classes (carbapenems(), aminoglycosides()), or determine multi-drug resistant microorganisms (MDRO, mdro()).
+
Use these function for the analysis part. You can use
+susceptibility() or resistance() on any
+antibiotic column. Be sure to first select the isolates that are
+appropiate for analysis, by using first_isolate() or
+is_new_episode(). You can also filter your data on certain
+resistance in certain antibiotic classes (carbapenems(),
+aminoglycosides()), or determine multi-drug resistant
+microorganisms (MDRO, mdro()).
Some pages about our package and its external sources. Be sure to read our How To’s for more information about how to work with functions in this package.
+
Some pages about our package and its external sources. Be sure to
+read our How To’s for more
+information about how to work with functions in this package.
These functions are mostly for internal use, but some of them may also be suitable for your analysis. Especially the ‘like’ function can be useful: if (x %like% y) {...}.
+
These functions are mostly for internal use, but some of them may
+also be suitable for your analysis. Especially the ‘like’ function can
+be useful: if (x %like% y) {...}.
The lifecycle of this function is stable. In a stable function, major changes are unlikely. This means that the unlying code will generally evolve by adding new arguments; removing arguments or changing the meaning of existing arguments will be avoided.
-
If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit an message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
+
If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit a message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
Read more on Our Website!
@@ -221,11 +221,13 @@ The lifecycle of this function is stable
-
Developed by Matthijs S. Berends, Christian F. Luz, Dennis Souverein, Erwin E. A. Hassing.
+
Developed by Matthijs S. Berends, Christian F. Luz, Dennis Souverein,
+Erwin E. A. Hassing.
The lifecycle of this function is stable. In a stable function, major changes are unlikely. This means that the unlying code will generally evolve by adding new arguments; removing arguments or changing the meaning of existing arguments will be avoided.
-
If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit an message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
+
If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit a message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
Read more on Our Website!
@@ -242,11 +242,13 @@ The lifecycle of this function is stable
-
Developed by Matthijs S. Berends, Christian F. Luz, Dennis Souverein, Erwin E. A. Hassing.
+
Developed by Matthijs S. Berends, Christian F. Luz, Dennis Souverein,
+Erwin E. A. Hassing.
The lifecycle of this function is stable. In a stable function, major changes are unlikely. This means that the unlying code will generally evolve by adding new arguments; removing arguments or changing the meaning of existing arguments will be avoided.
-
If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit an message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
+
If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit a message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
Read more on Our Website!
@@ -308,11 +308,13 @@ The lifecycle of this function is stable
-
Developed by Matthijs S. Berends, Christian F. Luz, Dennis Souverein, Erwin E. A. Hassing.
+
Developed by Matthijs S. Berends, Christian F. Luz, Dennis Souverein,
+Erwin E. A. Hassing.
The lifecycle of this function is stable. In a stable function, major changes are unlikely. This means that the unlying code will generally evolve by adding new arguments; removing arguments or changing the meaning of existing arguments will be avoided.
-
If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit an message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
+
If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit a message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
Read more on Our Website!
@@ -210,11 +210,13 @@ The lifecycle of this function is stable
-
Developed by Matthijs S. Berends, Christian F. Luz, Dennis Souverein, Erwin E. A. Hassing.
+
Developed by Matthijs S. Berends, Christian F. Luz, Dennis Souverein,
+Erwin E. A. Hassing.
diff --git a/docs/reference/lifecycle.html b/docs/reference/lifecycle.html
index 7f49db42..aac85a16 100644
--- a/docs/reference/lifecycle.html
+++ b/docs/reference/lifecycle.html
@@ -19,7 +19,7 @@ This page contains a section for every lifecycle (with text borrowed from the af
AMR (for R)
- 1.8.0.9004
+ 1.8.0.9005
@@ -186,7 +186,7 @@ The lifecycle of this function is maturing. The unlying code of
The lifecycle of this function is stable. In a stable function, major changes are unlikely. This means that the unlying code will generally evolve by adding new arguments; removing arguments or changing the meaning of existing arguments will be avoided.
-
If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit an message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
+
If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit a message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
Retired Lifecycle
@@ -211,11 +211,13 @@ The lifecycle of this function is questioning. This function mi
The lifecycle of this function is stable. In a stable function, major changes are unlikely. This means that the unlying code will generally evolve by adding new arguments; removing arguments or changing the meaning of existing arguments will be avoided.
-
If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit an message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
+
If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit a message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
Read more on Our Website!
@@ -260,11 +260,13 @@ The lifecycle of this function is stable
-
Developed by Matthijs S. Berends, Christian F. Luz, Dennis Souverein, Erwin E. A. Hassing.
+
Developed by Matthijs S. Berends, Christian F. Luz, Dennis Souverein,
+Erwin E. A. Hassing.
diff --git a/docs/reference/mdro.html b/docs/reference/mdro.html
index 25230bd2..c0cf7fbd 100644
--- a/docs/reference/mdro.html
+++ b/docs/reference/mdro.html
@@ -17,7 +17,7 @@
AMR (for R)
- 1.8.0.9004
+ 1.8.0.9005
@@ -291,7 +291,7 @@ Ordered facto
The lifecycle of this function is stable. In a stable function, major changes are unlikely. This means that the unlying code will generally evolve by adding new arguments; removing arguments or changing the meaning of existing arguments will be avoided.
-
If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit an message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
+
If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit a message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
Antibiotics
@@ -352,11 +352,13 @@ A microorganism is categorised as Susceptible, Increased exposure when
The lifecycle of this function is stable. In a stable function, major changes are unlikely. This means that the unlying code will generally evolve by adding new arguments; removing arguments or changing the meaning of existing arguments will be avoided.
-
If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit an message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
+
If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit a message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
Reference Data Publicly Available
@@ -231,11 +231,13 @@ The lifecycle of this function is stable
-
Developed by Matthijs S. Berends, Christian F. Luz, Dennis Souverein, Erwin E. A. Hassing.
+
Developed by Matthijs S. Berends, Christian F. Luz, Dennis Souverein,
+Erwin E. A. Hassing.
The lifecycle of this function is stable. In a stable function, major changes are unlikely. This means that the unlying code will generally evolve by adding new arguments; removing arguments or changing the meaning of existing arguments will be avoided.
-
If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit an message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
+
If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit a message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
Matching Score for Microorganisms
@@ -433,11 +433,13 @@ This package contains the complete taxonomic tree of almost all microorganisms (
diff --git a/docs/reference/mo_source.html b/docs/reference/mo_source.html
index d2be9274..0ce2ecb3 100644
--- a/docs/reference/mo_source.html
+++ b/docs/reference/mo_source.html
@@ -18,7 +18,7 @@ This is the fastest way to have your organisation (or analysis) specific codes p
AMR (for R)
- 1.8.0.9004
+ 1.8.0.9005
@@ -250,7 +250,7 @@ This is the fastest way to have your organisation (or analysis) specific codes p
The lifecycle of this function is stable. In a stable function, major changes are unlikely. This means that the unlying code will generally evolve by adding new arguments; removing arguments or changing the meaning of existing arguments will be avoided.
-
If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit an message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
+
If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit a message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
Read more on Our Website!
@@ -267,11 +267,13 @@ The lifecycle of this function is stable
-
Developed by Matthijs S. Berends, Christian F. Luz, Dennis Souverein, Erwin E. A. Hassing.
+
Developed by Matthijs S. Berends, Christian F. Luz, Dennis Souverein,
+Erwin E. A. Hassing.
The lifecycle of this function is stable. In a stable function, major changes are unlikely. This means that the unlying code will generally evolve by adding new arguments; removing arguments or changing the meaning of existing arguments will be avoided.
-
If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit an message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
+
If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit a message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
Read more on Our Website!
@@ -266,11 +266,13 @@ The lifecycle of this function is stable
-
Developed by Matthijs S. Berends, Christian F. Luz, Dennis Souverein, Erwin E. A. Hassing.
+
Developed by Matthijs S. Berends, Christian F. Luz, Dennis Souverein,
+Erwin E. A. Hassing.
diff --git a/docs/reference/plot.html b/docs/reference/plot.html
index 6927d23b..d76ee05a 100644
--- a/docs/reference/plot.html
+++ b/docs/reference/plot.html
@@ -17,7 +17,7 @@
AMR (for R)
- 1.8.0.9004
+ 1.8.0.9005
@@ -292,7 +292,7 @@ The
The lifecycle of this function is stable. In a stable function, major changes are unlikely. This means that the unlying code will generally evolve by adding new arguments; removing arguments or changing the meaning of existing arguments will be avoided.
-
If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit an message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
+
If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit a message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
Read more on Our Website!
@@ -332,11 +332,13 @@ The lifecycle of this function is stable
-
Developed by Matthijs S. Berends, Christian F. Luz, Dennis Souverein, Erwin E. A. Hassing.
+
Developed by Matthijs S. Berends, Christian F. Luz, Dennis Souverein,
+Erwin E. A. Hassing.
diff --git a/docs/reference/proportion.html b/docs/reference/proportion.html
index 2dfd113e..2eba482a 100644
--- a/docs/reference/proportion.html
+++ b/docs/reference/proportion.html
@@ -18,7 +18,7 @@ resistance() should be used to calculate resistance, susceptibility() should be
AMR (for R)
- 1.8.0.9004
+ 1.8.0.9005
@@ -271,7 +271,7 @@ resistance() should be used to calculate resistance, susceptibility() should be
The lifecycle of this function is stable. In a stable function, major changes are unlikely. This means that the unlying code will generally evolve by adding new arguments; removing arguments or changing the meaning of existing arguments will be avoided.
-
If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit an message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
+
If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit a message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
Interpretation of R and S/I
@@ -381,11 +381,13 @@ A microorganism is categorised as Susceptible, Increased exposure when
The lifecycle of this function is stable. In a stable function, major changes are unlikely. This means that the unlying code will generally evolve by adding new arguments; removing arguments or changing the meaning of existing arguments will be avoided.
-
If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit an message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
+
If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit a message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
Read more on Our Website!
@@ -232,11 +232,13 @@ The lifecycle of this function is stable
-
Developed by Matthijs S. Berends, Christian F. Luz, Dennis Souverein, Erwin E. A. Hassing.
+
Developed by Matthijs S. Berends, Christian F. Luz, Dennis Souverein,
+Erwin E. A. Hassing.
The lifecycle of this function is stable. In a stable function, major changes are unlikely. This means that the unlying code will generally evolve by adding new arguments; removing arguments or changing the meaning of existing arguments will be avoided.
-
If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit an message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
+
If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit a message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
Interpretation of R and S/I
@@ -358,11 +358,13 @@ A microorganism is categorised as Susceptible, Increased exposure when
diff --git a/docs/reference/skewness.html b/docs/reference/skewness.html
index cb12d060..e092e822 100644
--- a/docs/reference/skewness.html
+++ b/docs/reference/skewness.html
@@ -18,7 +18,7 @@ When negative ('left-skewed'): the left tail is longer; the mass of the distribu
AMR (for R)
- 1.8.0.9004
+ 1.8.0.9005
@@ -189,7 +189,7 @@ When negative ('left-skewed'): the left tail is longer; the mass of the distribu
The lifecycle of this function is stable. In a stable function, major changes are unlikely. This means that the unlying code will generally evolve by adding new arguments; removing arguments or changing the meaning of existing arguments will be avoided.
-
If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit an message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
+
If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit a message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
Read more on Our Website!
@@ -210,11 +210,13 @@ The lifecycle of this function is stable
-
Developed by Matthijs S. Berends, Christian F. Luz, Dennis Souverein, Erwin E. A. Hassing.
+
Developed by Matthijs S. Berends, Christian F. Luz, Dennis Souverein,
+Erwin E. A. Hassing.
The lifecycle of this function is stable. In a stable function, major changes are unlikely. This means that the unlying code will generally evolve by adding new arguments; removing arguments or changing the meaning of existing arguments will be avoided.
-
If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit an message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
+
If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit a message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
Read more on Our Website!
@@ -237,11 +237,13 @@ The lifecycle of this function is stable
-
Developed by Matthijs S. Berends, Christian F. Luz, Dennis Souverein, Erwin E. A. Hassing.
+
Developed by Matthijs S. Berends, Christian F. Luz, Dennis Souverein,
+Erwin E. A. Hassing.
diff --git a/docs/survey.html b/docs/survey.html
index 44606cd9..560979fd 100644
--- a/docs/survey.html
+++ b/docs/survey.html
@@ -17,7 +17,7 @@
AMR (for R)
- 1.8.0.9004
+ 1.8.0.9005
@@ -168,11 +168,13 @@
diff --git a/man/ab_from_text.Rd b/man/ab_from_text.Rd
index f89b3161..5cf5164d 100644
--- a/man/ab_from_text.Rd
+++ b/man/ab_from_text.Rd
@@ -62,7 +62,7 @@ With using \code{collapse}, this function will return a \link{character}:\cr
\if{html}{\figure{lifecycle_stable.svg}{options: style=margin-bottom:"5"} \cr}
The \link[=lifecycle]{lifecycle} of this function is \strong{stable}. In a stable function, major changes are unlikely. This means that the unlying code will generally evolve by adding new arguments; removing arguments or changing the meaning of existing arguments will be avoided.
-If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit an message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
+If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit a message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
}
\section{Read more on Our Website!}{
diff --git a/man/ab_property.Rd b/man/ab_property.Rd
index 4f32fefb..c83f7875 100644
--- a/man/ab_property.Rd
+++ b/man/ab_property.Rd
@@ -100,7 +100,7 @@ The function \code{\link[=set_ab_names]{set_ab_names()}} is a special column ren
\if{html}{\figure{lifecycle_stable.svg}{options: style=margin-bottom:"5"} \cr}
The \link[=lifecycle]{lifecycle} of this function is \strong{stable}. In a stable function, major changes are unlikely. This means that the unlying code will generally evolve by adding new arguments; removing arguments or changing the meaning of existing arguments will be avoided.
-If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit an message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
+If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit a message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
}
\section{Source}{
diff --git a/man/age.Rd b/man/age.Rd
index 23b91b04..92639fd1 100644
--- a/man/age.Rd
+++ b/man/age.Rd
@@ -33,7 +33,7 @@ This function vectorises over both \code{x} and \code{reference}, meaning that e
\if{html}{\figure{lifecycle_stable.svg}{options: style=margin-bottom:"5"} \cr}
The \link[=lifecycle]{lifecycle} of this function is \strong{stable}. In a stable function, major changes are unlikely. This means that the unlying code will generally evolve by adding new arguments; removing arguments or changing the meaning of existing arguments will be avoided.
-If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit an message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
+If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit a message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
}
\section{Read more on Our Website!}{
diff --git a/man/age_groups.Rd b/man/age_groups.Rd
index a772a961..aa976fea 100644
--- a/man/age_groups.Rd
+++ b/man/age_groups.Rd
@@ -38,7 +38,7 @@ The default is to split on young children (0-11), youth (12-24), young adults (2
\if{html}{\figure{lifecycle_stable.svg}{options: style=margin-bottom:"5"} \cr}
The \link[=lifecycle]{lifecycle} of this function is \strong{stable}. In a stable function, major changes are unlikely. This means that the unlying code will generally evolve by adding new arguments; removing arguments or changing the meaning of existing arguments will be avoided.
-If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit an message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
+If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit a message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
}
\section{Read more on Our Website!}{
diff --git a/man/antibiotic_class_selectors.Rd b/man/antibiotic_class_selectors.Rd
index 7dbe1ce9..eb8ba1a2 100644
--- a/man/antibiotic_class_selectors.Rd
+++ b/man/antibiotic_class_selectors.Rd
@@ -169,7 +169,7 @@ The \code{\link[=not_intrinsic_resistant]{not_intrinsic_resistant()}} function c
\if{html}{\figure{lifecycle_stable.svg}{options: style=margin-bottom:"5"} \cr}
The \link[=lifecycle]{lifecycle} of this function is \strong{stable}. In a stable function, major changes are unlikely. This means that the unlying code will generally evolve by adding new arguments; removing arguments or changing the meaning of existing arguments will be avoided.
-If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit an message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
+If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit a message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
}
\section{Reference Data Publicly Available}{
diff --git a/man/as.ab.Rd b/man/as.ab.Rd
index f9bf62f3..1a7f6952 100644
--- a/man/as.ab.Rd
+++ b/man/as.ab.Rd
@@ -52,7 +52,7 @@ European Commission Public Health PHARMACEUTICALS - COMMUNITY REGISTER: \url{htt
\if{html}{\figure{lifecycle_stable.svg}{options: style=margin-bottom:"5"} \cr}
The \link[=lifecycle]{lifecycle} of this function is \strong{stable}. In a stable function, major changes are unlikely. This means that the unlying code will generally evolve by adding new arguments; removing arguments or changing the meaning of existing arguments will be avoided.
-If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit an message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
+If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit a message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
}
\section{WHOCC}{
diff --git a/man/as.disk.Rd b/man/as.disk.Rd
index e3b107f8..d8193ec0 100644
--- a/man/as.disk.Rd
+++ b/man/as.disk.Rd
@@ -38,7 +38,7 @@ Interpret disk values as RSI values with \code{\link[=as.rsi]{as.rsi()}}. It sup
\if{html}{\figure{lifecycle_stable.svg}{options: style=margin-bottom:"5"} \cr}
The \link[=lifecycle]{lifecycle} of this function is \strong{stable}. In a stable function, major changes are unlikely. This means that the unlying code will generally evolve by adding new arguments; removing arguments or changing the meaning of existing arguments will be avoided.
-If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit an message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
+If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit a message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
}
\section{Read more on Our Website!}{
diff --git a/man/as.mic.Rd b/man/as.mic.Rd
index 3a68a2cc..71c7126d 100755
--- a/man/as.mic.Rd
+++ b/man/as.mic.Rd
@@ -70,7 +70,7 @@ The following \link[=groupGeneric]{generic functions} are implemented for the MI
\if{html}{\figure{lifecycle_stable.svg}{options: style=margin-bottom:"5"} \cr}
The \link[=lifecycle]{lifecycle} of this function is \strong{stable}. In a stable function, major changes are unlikely. This means that the unlying code will generally evolve by adding new arguments; removing arguments or changing the meaning of existing arguments will be avoided.
-If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit an message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
+If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit a message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
}
\section{Read more on Our Website!}{
diff --git a/man/as.mo.Rd b/man/as.mo.Rd
index 175c5e20..945ea50e 100644
--- a/man/as.mo.Rd
+++ b/man/as.mo.Rd
@@ -141,7 +141,7 @@ The intelligent rules consider the prevalence of microorganisms in humans groupe
\if{html}{\figure{lifecycle_stable.svg}{options: style=margin-bottom:"5"} \cr}
The \link[=lifecycle]{lifecycle} of this function is \strong{stable}. In a stable function, major changes are unlikely. This means that the unlying code will generally evolve by adding new arguments; removing arguments or changing the meaning of existing arguments will be avoided.
-If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit an message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
+If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit a message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
}
\section{Matching Score for Microorganisms}{
diff --git a/man/as.rsi.Rd b/man/as.rsi.Rd
index 8d55cec2..73b6ac71 100755
--- a/man/as.rsi.Rd
+++ b/man/as.rsi.Rd
@@ -155,7 +155,7 @@ This AMR package honours this (new) insight. Use \code{\link[=susceptibility]{su
\if{html}{\figure{lifecycle_stable.svg}{options: style=margin-bottom:"5"} \cr}
The \link[=lifecycle]{lifecycle} of this function is \strong{stable}. In a stable function, major changes are unlikely. This means that the unlying code will generally evolve by adding new arguments; removing arguments or changing the meaning of existing arguments will be avoided.
-If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit an message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
+If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit a message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
}
\section{Reference Data Publicly Available}{
diff --git a/man/atc_online.Rd b/man/atc_online.Rd
index 0059da63..7f05de8f 100644
--- a/man/atc_online.Rd
+++ b/man/atc_online.Rd
@@ -74,7 +74,7 @@ Abbreviations of return values when using \code{property = "U"} (unit):
\if{html}{\figure{lifecycle_stable.svg}{options: style=margin-bottom:"5"} \cr}
The \link[=lifecycle]{lifecycle} of this function is \strong{stable}. In a stable function, major changes are unlikely. This means that the unlying code will generally evolve by adding new arguments; removing arguments or changing the meaning of existing arguments will be avoided.
-If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit an message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
+If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit a message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
}
\section{Read more on Our Website!}{
diff --git a/man/availability.Rd b/man/availability.Rd
index 54c81b22..caaeb92f 100644
--- a/man/availability.Rd
+++ b/man/availability.Rd
@@ -25,7 +25,7 @@ The function returns a \link{data.frame} with columns \code{"resistant"} and \co
\if{html}{\figure{lifecycle_stable.svg}{options: style=margin-bottom:"5"} \cr}
The \link[=lifecycle]{lifecycle} of this function is \strong{stable}. In a stable function, major changes are unlikely. This means that the unlying code will generally evolve by adding new arguments; removing arguments or changing the meaning of existing arguments will be avoided.
-If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit an message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
+If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit a message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
}
\section{Read more on Our Website!}{
diff --git a/man/bug_drug_combinations.Rd b/man/bug_drug_combinations.Rd
index a54d87fa..16a7be31 100644
--- a/man/bug_drug_combinations.Rd
+++ b/man/bug_drug_combinations.Rd
@@ -68,7 +68,7 @@ The function \code{\link[=format]{format()}} calculates the resistance per bug-d
\if{html}{\figure{lifecycle_stable.svg}{options: style=margin-bottom:"5"} \cr}
The \link[=lifecycle]{lifecycle} of this function is \strong{stable}. In a stable function, major changes are unlikely. This means that the unlying code will generally evolve by adding new arguments; removing arguments or changing the meaning of existing arguments will be avoided.
-If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit an message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
+If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit a message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
}
\section{Read more on Our Website!}{
diff --git a/man/count.Rd b/man/count.Rd
index f78f243e..4da9cb7f 100644
--- a/man/count.Rd
+++ b/man/count.Rd
@@ -77,7 +77,7 @@ The function \code{\link[=count_df]{count_df()}} takes any variable from \code{d
\if{html}{\figure{lifecycle_stable.svg}{options: style=margin-bottom:"5"} \cr}
The \link[=lifecycle]{lifecycle} of this function is \strong{stable}. In a stable function, major changes are unlikely. This means that the unlying code will generally evolve by adding new arguments; removing arguments or changing the meaning of existing arguments will be avoided.
-If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit an message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
+If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit a message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
}
\section{Interpretation of R and S/I}{
diff --git a/man/custom_eucast_rules.Rd b/man/custom_eucast_rules.Rd
index 1f7deb3d..cbf3e334 100644
--- a/man/custom_eucast_rules.Rd
+++ b/man/custom_eucast_rules.Rd
@@ -105,7 +105,7 @@ It is possible to define antibiotic groups instead of single antibiotics for the
\if{html}{\figure{lifecycle_stable.svg}{options: style=margin-bottom:"5"} \cr}
The \link[=lifecycle]{lifecycle} of this function is \strong{stable}. In a stable function, major changes are unlikely. This means that the unlying code will generally evolve by adding new arguments; removing arguments or changing the meaning of existing arguments will be avoided.
-If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit an message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
+If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit a message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
}
\section{Read more on Our Website!}{
diff --git a/man/eucast_rules.Rd b/man/eucast_rules.Rd
index 466a0cf0..a900dac2 100644
--- a/man/eucast_rules.Rd
+++ b/man/eucast_rules.Rd
@@ -110,7 +110,7 @@ Amikacin (\code{AMK}, \href{https://www.whocc.no/atc_ddd_index/?code=J01GB06&sho
\if{html}{\figure{lifecycle_stable.svg}{options: style=margin-bottom:"5"} \cr}
The \link[=lifecycle]{lifecycle} of this function is \strong{stable}. In a stable function, major changes are unlikely. This means that the unlying code will generally evolve by adding new arguments; removing arguments or changing the meaning of existing arguments will be avoided.
-If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit an message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
+If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit a message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
}
\section{Reference Data Publicly Available}{
diff --git a/man/first_isolate.Rd b/man/first_isolate.Rd
index 81359ebc..83e07351 100755
--- a/man/first_isolate.Rd
+++ b/man/first_isolate.Rd
@@ -169,7 +169,7 @@ The default method is phenotype-based (using \code{type = "points"}) and episode
\if{html}{\figure{lifecycle_stable.svg}{options: style=margin-bottom:"5"} \cr}
The \link[=lifecycle]{lifecycle} of this function is \strong{stable}. In a stable function, major changes are unlikely. This means that the unlying code will generally evolve by adding new arguments; removing arguments or changing the meaning of existing arguments will be avoided.
-If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit an message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
+If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit a message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
}
\section{Read more on Our Website!}{
diff --git a/man/get_episode.Rd b/man/get_episode.Rd
index 1f94f257..9cf329c4 100644
--- a/man/get_episode.Rd
+++ b/man/get_episode.Rd
@@ -37,7 +37,7 @@ The \code{dplyr} package is not required for these functions to work, but these
\if{html}{\figure{lifecycle_stable.svg}{options: style=margin-bottom:"5"} \cr}
The \link[=lifecycle]{lifecycle} of this function is \strong{stable}. In a stable function, major changes are unlikely. This means that the unlying code will generally evolve by adding new arguments; removing arguments or changing the meaning of existing arguments will be avoided.
-If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit an message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
+If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit a message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
}
\section{Read more on Our Website!}{
diff --git a/man/ggplot_pca.Rd b/man/ggplot_pca.Rd
index a8d6d80e..08ef13dd 100644
--- a/man/ggplot_pca.Rd
+++ b/man/ggplot_pca.Rd
@@ -113,7 +113,7 @@ The colours for labels and points can be changed by adding another scale layer f
\if{html}{\figure{lifecycle_stable.svg}{options: style=margin-bottom:"5"} \cr}
The \link[=lifecycle]{lifecycle} of this function is \strong{stable}. In a stable function, major changes are unlikely. This means that the unlying code will generally evolve by adding new arguments; removing arguments or changing the meaning of existing arguments will be avoided.
-If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit an message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
+If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit a message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
}
\examples{
diff --git a/man/ggplot_rsi.Rd b/man/ggplot_rsi.Rd
index 06662676..b805696a 100644
--- a/man/ggplot_rsi.Rd
+++ b/man/ggplot_rsi.Rd
@@ -145,7 +145,7 @@ At default, the names of antibiotics will be shown on the plots using \code{\lin
\if{html}{\figure{lifecycle_stable.svg}{options: style=margin-bottom:"5"} \cr}
The \link[=lifecycle]{lifecycle} of this function is \strong{stable}. In a stable function, major changes are unlikely. This means that the unlying code will generally evolve by adding new arguments; removing arguments or changing the meaning of existing arguments will be avoided.
-If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit an message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
+If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit a message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
}
\section{Read more on Our Website!}{
diff --git a/man/guess_ab_col.Rd b/man/guess_ab_col.Rd
index 6909a383..9f72be7a 100644
--- a/man/guess_ab_col.Rd
+++ b/man/guess_ab_col.Rd
@@ -34,7 +34,7 @@ You can look for an antibiotic (trade) name or abbreviation and it will search \
\if{html}{\figure{lifecycle_stable.svg}{options: style=margin-bottom:"5"} \cr}
The \link[=lifecycle]{lifecycle} of this function is \strong{stable}. In a stable function, major changes are unlikely. This means that the unlying code will generally evolve by adding new arguments; removing arguments or changing the meaning of existing arguments will be avoided.
-If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit an message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
+If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit a message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
}
\section{Read more on Our Website!}{
diff --git a/man/italicise_taxonomy.Rd b/man/italicise_taxonomy.Rd
index 37559098..9d5ba2a8 100644
--- a/man/italicise_taxonomy.Rd
+++ b/man/italicise_taxonomy.Rd
@@ -29,7 +29,7 @@ This function also supports abbreviation of the genus if it is followed by a spe
\if{html}{\figure{lifecycle_stable.svg}{options: style=margin-bottom:"5"} \cr}
The \link[=lifecycle]{lifecycle} of this function is \strong{stable}. In a stable function, major changes are unlikely. This means that the unlying code will generally evolve by adding new arguments; removing arguments or changing the meaning of existing arguments will be avoided.
-If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit an message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
+If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit a message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
}
\section{Read more on Our Website!}{
diff --git a/man/join.Rd b/man/join.Rd
index df196f2e..3b647791 100755
--- a/man/join.Rd
+++ b/man/join.Rd
@@ -48,7 +48,7 @@ If the \code{dplyr} package is installed, their join functions will be used. Oth
\if{html}{\figure{lifecycle_stable.svg}{options: style=margin-bottom:"5"} \cr}
The \link[=lifecycle]{lifecycle} of this function is \strong{stable}. In a stable function, major changes are unlikely. This means that the unlying code will generally evolve by adding new arguments; removing arguments or changing the meaning of existing arguments will be avoided.
-If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit an message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
+If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit a message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
}
\section{Read more on Our Website!}{
diff --git a/man/key_antimicrobials.Rd b/man/key_antimicrobials.Rd
index 46730d9f..feee1f3b 100644
--- a/man/key_antimicrobials.Rd
+++ b/man/key_antimicrobials.Rd
@@ -112,7 +112,7 @@ The default antimicrobial agents used for \strong{fungi} (set in \code{antifunga
\if{html}{\figure{lifecycle_stable.svg}{options: style=margin-bottom:"5"} \cr}
The \link[=lifecycle]{lifecycle} of this function is \strong{stable}. In a stable function, major changes are unlikely. This means that the unlying code will generally evolve by adding new arguments; removing arguments or changing the meaning of existing arguments will be avoided.
-If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit an message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
+If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit a message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
}
\section{Read more on Our Website!}{
diff --git a/man/kurtosis.Rd b/man/kurtosis.Rd
index 43ecfb8f..08d54146 100644
--- a/man/kurtosis.Rd
+++ b/man/kurtosis.Rd
@@ -30,7 +30,7 @@ Kurtosis is a measure of the "tailedness" of the probability distribution of a r
\if{html}{\figure{lifecycle_stable.svg}{options: style=margin-bottom:"5"} \cr}
The \link[=lifecycle]{lifecycle} of this function is \strong{stable}. In a stable function, major changes are unlikely. This means that the unlying code will generally evolve by adding new arguments; removing arguments or changing the meaning of existing arguments will be avoided.
-If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit an message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
+If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit a message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
}
\section{Read more on Our Website!}{
diff --git a/man/lifecycle.Rd b/man/lifecycle.Rd
index 826c235c..5062077f 100644
--- a/man/lifecycle.Rd
+++ b/man/lifecycle.Rd
@@ -26,7 +26,7 @@ The \link[=lifecycle]{lifecycle} of this function is \strong{maturing}. The unly
\if{html}{\figure{lifecycle_stable.svg}{options: style=margin-bottom:"5"} \cr}
The \link[=lifecycle]{lifecycle} of this function is \strong{stable}. In a stable function, major changes are unlikely. This means that the unlying code will generally evolve by adding new arguments; removing arguments or changing the meaning of existing arguments will be avoided.
-If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit an message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
+If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit a message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
}
\section{Retired Lifecycle}{
diff --git a/man/like.Rd b/man/like.Rd
index 61899aa0..a6dc2fbb 100755
--- a/man/like.Rd
+++ b/man/like.Rd
@@ -50,7 +50,7 @@ Using RStudio? The \verb{\%like\%}/\verb{\%unlike\%} functions can also be direc
\if{html}{\figure{lifecycle_stable.svg}{options: style=margin-bottom:"5"} \cr}
The \link[=lifecycle]{lifecycle} of this function is \strong{stable}. In a stable function, major changes are unlikely. This means that the unlying code will generally evolve by adding new arguments; removing arguments or changing the meaning of existing arguments will be avoided.
-If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit an message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
+If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit a message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
}
\section{Read more on Our Website!}{
diff --git a/man/mdro.Rd b/man/mdro.Rd
index fb022d33..306a4522 100644
--- a/man/mdro.Rd
+++ b/man/mdro.Rd
@@ -160,7 +160,7 @@ The rules set (the \code{custom} object in this case) could be exported to a sha
\if{html}{\figure{lifecycle_stable.svg}{options: style=margin-bottom:"5"} \cr}
The \link[=lifecycle]{lifecycle} of this function is \strong{stable}. In a stable function, major changes are unlikely. This means that the unlying code will generally evolve by adding new arguments; removing arguments or changing the meaning of existing arguments will be avoided.
-If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit an message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
+If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit a message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
}
\section{Antibiotics}{
diff --git a/man/mo_matching_score.Rd b/man/mo_matching_score.Rd
index e9ea3616..ed09b53a 100644
--- a/man/mo_matching_score.Rd
+++ b/man/mo_matching_score.Rd
@@ -44,7 +44,7 @@ Since \code{AMR} version 1.8.1, common microorganism abbreviations are ignored i
\if{html}{\figure{lifecycle_stable.svg}{options: style=margin-bottom:"5"} \cr}
The \link[=lifecycle]{lifecycle} of this function is \strong{stable}. In a stable function, major changes are unlikely. This means that the unlying code will generally evolve by adding new arguments; removing arguments or changing the meaning of existing arguments will be avoided.
-If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit an message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
+If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit a message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
}
\section{Reference Data Publicly Available}{
diff --git a/man/mo_property.Rd b/man/mo_property.Rd
index 95a214ef..dd9f2579 100644
--- a/man/mo_property.Rd
+++ b/man/mo_property.Rd
@@ -144,7 +144,7 @@ SNOMED codes - \code{\link[=mo_snomed]{mo_snomed()}} - are from the US Edition o
\if{html}{\figure{lifecycle_stable.svg}{options: style=margin-bottom:"5"} \cr}
The \link[=lifecycle]{lifecycle} of this function is \strong{stable}. In a stable function, major changes are unlikely. This means that the unlying code will generally evolve by adding new arguments; removing arguments or changing the meaning of existing arguments will be avoided.
-If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit an message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
+If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit a message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
}
\section{Matching Score for Microorganisms}{
diff --git a/man/mo_source.Rd b/man/mo_source.Rd
index 902f2acc..1c37fb15 100644
--- a/man/mo_source.Rd
+++ b/man/mo_source.Rd
@@ -100,7 +100,7 @@ If the original file (in the previous case an Excel file) is moved or deleted, t
\if{html}{\figure{lifecycle_stable.svg}{options: style=margin-bottom:"5"} \cr}
The \link[=lifecycle]{lifecycle} of this function is \strong{stable}. In a stable function, major changes are unlikely. This means that the unlying code will generally evolve by adding new arguments; removing arguments or changing the meaning of existing arguments will be avoided.
-If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit an message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
+If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit a message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
}
\section{Read more on Our Website!}{
diff --git a/man/pca.Rd b/man/pca.Rd
index 7f67dced..e4611898 100644
--- a/man/pca.Rd
+++ b/man/pca.Rd
@@ -64,7 +64,7 @@ The result of the \code{\link[=pca]{pca()}} function is a \link{prcomp} object,
\if{html}{\figure{lifecycle_stable.svg}{options: style=margin-bottom:"5"} \cr}
The \link[=lifecycle]{lifecycle} of this function is \strong{stable}. In a stable function, major changes are unlikely. This means that the unlying code will generally evolve by adding new arguments; removing arguments or changing the meaning of existing arguments will be avoided.
-If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit an message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
+If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit a message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
}
\section{Read more on Our Website!}{
diff --git a/man/plot.Rd b/man/plot.Rd
index b2605ac6..4a007fa2 100644
--- a/man/plot.Rd
+++ b/man/plot.Rd
@@ -134,7 +134,7 @@ Simply using \code{"CLSI"} or \code{"EUCAST"} as input will automatically select
\if{html}{\figure{lifecycle_stable.svg}{options: style=margin-bottom:"5"} \cr}
The \link[=lifecycle]{lifecycle} of this function is \strong{stable}. In a stable function, major changes are unlikely. This means that the unlying code will generally evolve by adding new arguments; removing arguments or changing the meaning of existing arguments will be avoided.
-If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit an message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
+If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit a message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
}
\section{Read more on Our Website!}{
diff --git a/man/proportion.Rd b/man/proportion.Rd
index 711beef3..7ecd3b57 100644
--- a/man/proportion.Rd
+++ b/man/proportion.Rd
@@ -123,7 +123,7 @@ Using \code{only_all_tested} has no impact when only using one antibiotic as inp
\if{html}{\figure{lifecycle_stable.svg}{options: style=margin-bottom:"5"} \cr}
The \link[=lifecycle]{lifecycle} of this function is \strong{stable}. In a stable function, major changes are unlikely. This means that the unlying code will generally evolve by adding new arguments; removing arguments or changing the meaning of existing arguments will be avoided.
-If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit an message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
+If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit a message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
}
\section{Interpretation of R and S/I}{
diff --git a/man/random.Rd b/man/random.Rd
index ad7d9d33..55a7b123 100644
--- a/man/random.Rd
+++ b/man/random.Rd
@@ -40,7 +40,7 @@ Generated values are based on the latest EUCAST guideline implemented in the \li
\if{html}{\figure{lifecycle_stable.svg}{options: style=margin-bottom:"5"} \cr}
The \link[=lifecycle]{lifecycle} of this function is \strong{stable}. In a stable function, major changes are unlikely. This means that the unlying code will generally evolve by adding new arguments; removing arguments or changing the meaning of existing arguments will be avoided.
-If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit an message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
+If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit a message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
}
\section{Read more on Our Website!}{
diff --git a/man/resistance_predict.Rd b/man/resistance_predict.Rd
index 5b724b3a..445baeb6 100644
--- a/man/resistance_predict.Rd
+++ b/man/resistance_predict.Rd
@@ -115,7 +115,7 @@ Valid options for the statistical model (argument \code{model}) are:
\if{html}{\figure{lifecycle_stable.svg}{options: style=margin-bottom:"5"} \cr}
The \link[=lifecycle]{lifecycle} of this function is \strong{stable}. In a stable function, major changes are unlikely. This means that the unlying code will generally evolve by adding new arguments; removing arguments or changing the meaning of existing arguments will be avoided.
-If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit an message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
+If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit a message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
}
\section{Interpretation of R and S/I}{
diff --git a/man/skewness.Rd b/man/skewness.Rd
index 1664460d..137f6a45 100644
--- a/man/skewness.Rd
+++ b/man/skewness.Rd
@@ -30,7 +30,7 @@ When negative ('left-skewed'): the left tail is longer; the mass of the distribu
\if{html}{\figure{lifecycle_stable.svg}{options: style=margin-bottom:"5"} \cr}
The \link[=lifecycle]{lifecycle} of this function is \strong{stable}. In a stable function, major changes are unlikely. This means that the unlying code will generally evolve by adding new arguments; removing arguments or changing the meaning of existing arguments will be avoided.
-If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit an message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
+If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit a message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
}
\section{Read more on Our Website!}{
diff --git a/man/translate.Rd b/man/translate.Rd
index 4702ba28..8f90b194 100644
--- a/man/translate.Rd
+++ b/man/translate.Rd
@@ -32,7 +32,7 @@ Thus, if the R option \code{AMR_locale} is set, the system variables \code{LANGU
\if{html}{\figure{lifecycle_stable.svg}{options: style=margin-bottom:"5"} \cr}
The \link[=lifecycle]{lifecycle} of this function is \strong{stable}. In a stable function, major changes are unlikely. This means that the unlying code will generally evolve by adding new arguments; removing arguments or changing the meaning of existing arguments will be avoided.
-If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit an message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
+If the unlying code needs breaking changes, they will occur gradually. For example, an argument will be deprecated and first continue to work, but will emit a message informing you of the change. Next, typically after at least one newly released version on CRAN, the message will be transformed to an error.
}
\section{Read more on Our Website!}{
diff --git a/vignettes/AMR.Rmd b/vignettes/AMR.Rmd
index 03cd1d9b..4dda8291 100755
--- a/vignettes/AMR.Rmd
+++ b/vignettes/AMR.Rmd
@@ -1,6 +1,6 @@
---
title: "How to conduct AMR data analysis"
-author: "Dr. Matthijs Berends"
+author: "Dr Matthijs Berends"
date: '`r format(Sys.Date(), "%d %B %Y")`'
output:
rmarkdown::html_vignette: