```{css, code = readLines(params$my_css), hide=TRUE, echo = FALSE}
```r knitr::opts_chunk$set( collapse = TRUE, comment = "#>" ) library(httptest) start_vignette("5")
#if (!library(ctxR, logical.return = TRUE)){ devtools::load_all() #} old_options <- options("width")
# Redefining the knit_print method to truncate character values to 25 characters # in each column and to truncate the columns in the print call to prevent # wrapping tables with several columns. #library(ctxR) knit_print.data.table = function(x, ...) { y <- data.table::copy(x) y <- y[, lapply(.SD, function(t){ if (is.character(t)){ t <- strtrim(t, 25) } return(t) })] print(y, trunc.cols = TRUE) } registerS3method( "knit_print", "data.table", knit_print.data.table, envir = asNamespace("knitr") )
In this vignette, the CTX Exposure API will be explored.
Data provided by the Exposure API are broadly organized in four different areas, Functional Use Information, Product Data, List Presence Data, and Exposure estimates. Data from the Functional Use, Product Data, and List Presence resources (aside from the Functional Use Probability endpoint) are developed from publicly available documents and are also accessible using the Chemical Exposure Knowledgebase (ChempExpo) interactive web application developed by the United States Environmental Protection Agency. The underlying database for the Functional Use, Product Data, and List Presence endpoints of the Exposure API and ChemExpo is the Chemicals and Products Database (CPDat). CPDat provides reported information on how chemicals are used in commerce and (where possible) at what quantities they occur in consumer and industrial products; see (Dionisio et al. 2018) for more information on CPDat. The data provided by the Functional Use Probability endpoint are predictions from EPA's Quantitative Structure Use Relationship (QSUR) models (Phillips et al. 2017). Exposure data is represented by predictions from the httk
R package, introduced in (Pearce, R. et al. 2017) and several exposure models including the SEEM models. Information on the SEEM2 model can be found at (Wambaugh, J. et al. 2014) and on the SEEM3 model can be found at (Ring, C. et al. 2018)
Product Data are organized by harmonized Product Use Categories (PUCs). The PUCs are assigned to products (which are associated with Composition Documents) and indicate the type of product associated to each data record. They are organized hierarchicially, with General Category containing Product Family, which in turn contains Product Type. The Exposure API also provide information on how the PUC was assigned. Do note that a natural language processing model is used to assign PUCs with the "classificationmethod" equal to "Automatic". As such, these assignments are less certain and may contain inaccuracies. More information on PUC categories can be found in (Isaacs et al. 2020).
List Presence Data reflect the occurrence of chemicals on lists present in publicly available documents (sourced from a variety of federal and state agencies and trade associations). These lists are tagged with List Presence Keywords (LPKs) that together describe information contained in the document relevant to how the chemical was used. LPKs are an updated version of the cassettes provided in the Chemical and Product Categories (CPCat) database; see (Dionisio et al. 2015). For the most up to date information on the current LPKs and to see how the CPCat cassettes were updated, see (Koval et al. 2022).
Both reported and predicted Function Use Information is available. Reported functional use information is organized by harmonized Function Categories (FCs) that describe the role a chemical serves in a product or industrial process. The harmonized technical function categories and definitions were developed by the Organisation for Economic Co-operation and Development (OECD) (with the exception of a few categories unique to consumer products which are noted as being developed by EPA). These categories have been augmented with additional categories needed to describe chemicals in personal care, pharmaceutical, or other commercial sectors. The reported function data form the basis for ORD's QSUR models (Phillips et al. 2016). These models provide the structure-based predictions of chemical function available in the Functional Use Probability endpoint. Note that these models were developed prior to the OECD function categories, so their function categories are not yet aligned with the harmonized categories used in the reported data. Updated models for the harmonized categories are under development.
The R package httk
provides users with a variety of tools to incorporate toxickinetics and in vitro-in vivo extrapolation into bioinformatics and comes with pre-made models that can be used with specific chemical data. The SEEM models were developed to provide predictions for potential human exposure to chemicals with little or no exposure data. For SEEM2, Bayesian methods were used to infer ranges of exposure consistent with data from the National Health and Nutrition Examination Survey. Predictions for different demographic groups were made. For SEEM3, chemical exposures through four different pathways were predicted and in turn weighting of different models through these exposure pathways was conducted to produce consensus predictions.
Information for ChemExpo is sourced from: Sakshi Handa, Katherine A. Phillips, Kenta Baron-Furuyama, and Kristin K. Isaacs. 2023. “ChemExpo Knowledgebase User Guide”. https://comptox.epa.gov/chemexpo/static/user_guide/index.html.
::: {.noticebox data-latex=""} NOTE: Please see the introductory vignette for an overview of the ctxR package and initial set up instruction with API key storage. :::
Several ctxR functions can be used to access the CTX Exposure API data, as described in the following sections. Tables output in each example have been filtered to only display the first few rows of data.
Functional uses for chemicals may be searched.
get_exposure_functional_use()
retrieves FCs and associated metadata for a specific chemical (by DTXSID).
exp_fun_use <- get_exposure_functional_use(DTXSID = 'DTXSID7020182')
knitr::kable(head(exp_fun_use)) %>% kableExtra::kable_styling("striped") %>% kableExtra::scroll_box(width = "100%")
get_exposure_functional_use_probability()
retrieves the probability of functional use within different FCs for a given chemical (by DTXSID). Each value represents the probability of the chemical being classified as having this function, as predicted by the QSUR models.
exp_fun_use_prob <- get_exposure_functional_use_probability(DTXSID = 'DTXSID7020182')
knitr::kable(head(exp_fun_use_prob))
get_exposure_functional_use_categories()
retrieves definitions of all the available FCs. This is not specific to a chemical, but rather a list of all FCs.
exp_fun_use_cat <- get_exposure_functional_use_category()
knitr::kable(head(exp_fun_use_cat))
There are a few resources for retrieving product use data associated with chemical identifiers (DTXSID) or general use.
get_exposure_product_data()
retrieves the product data (PUCs and related data) for products that use the specified chemical (by DTXSID).
exp_prod_dat <- get_exposure_product_data(DTXSID = 'DTXSID7020182')
knitr::kable(head(exp_prod_dat))%>% kableExtra::kable_styling("striped") %>% kableExtra::scroll_box(width = "100%")
get_exposure_product_data_puc()
retrieves the definitions of all the PUCs. This is not specific to a chemical, but rather a list of all PUCs.
exp_prod_data_puc <- get_exposure_product_data_puc()
knitr::kable(head(exp_prod_data_puc))
httk
dataThere is a single resource that returns httk
model data when available
bpa_httk <- get_httk_data(DTXSID = 'DTXSID7020182') head(bpa_httk)
There are a few resources for retrieving list data for specific chemicals (by DTXSID) or general list presence information.
get_exposure_list_presence_tags()
retrieves all the list presence keywords. This is not specific to a chemical, but rather a list of the the list presence keywords. Note that some List Presence Keywords align with PUCs, but the keywords are assigned to documents that refer to product category as a whole, while PUCs are assigned to documents referring to specific products (e.g., ingredient list).
exp_list_tags <- get_exposure_list_presence_tags()
knitr::kable(head(exp_list_tags))
get_exposure_list_presence_tags_by_dtxsid()
retrieves LPKs and associated data for a specific chemical (by DTXSID).
exp_list_tags_dat <- get_exposure_list_presence_tags_by_dtxsid(DTXSID = 'DTXSID7020182')
knitr::kable(head(exp_list_tags_dat))%>% kableExtra::kable_styling("striped") %>% kableExtra::scroll_box(width = "100%")
There are two functions that provide access to exposure prediction data. The first provides general information on exposure pathways while the second provides exposure predictions from a variety of exposure models. The general information corresponds to SEEM3 predictions of exposure pathways, while the exposure predictions feature SEEM2 predictions broken down by demographic groups, general consensus predictions from SEEM3, and in some cases additional exposure predictions from other models
get_general_exposure_prediction()
returns general exposure information for a given chemical.
bpa_general_exposure <- get_general_exposure_prediction(DTXSID = 'DTXSID7020182') head(bpa_general_exposure)
get_demographic_exposure_prediction()
returns exposure prediction information split across different demographics for a given chemical.
bpa_demographic_exposure <- get_demographic_exposure_prediction(DTXSID = 'DTXSID7020182') bpa_demographic_exposure
There are batch search versions for several endpoints that gather data specific to a chemical. Namely, get_exposure_functional_use_batch()
, get_exposure_functional_use_probability()
, get_exposure_product_data_batch()
, get_exposure_list_presence_tags_by_dtxsid_batch()
, get_general_exposure_prediction_batch()
, and get_demographic_exposure_prediction_batch()
. The function get_exposure_functional_use_probability()
returns a data.table with each row corresponding to a unique chemical and each column representing a functional use category associated to at least one input chemical. The other batch functions return a named list of data.frames or data.tables, the names corresponding to the unique chemicals input and the data.frames or data.tables corresponding to the information to each individual chemical.
We demonstrate how the individual results differ from the batch results when retrieving functional use probabilities.
bpa_prob <- get_exposure_functional_use_probability(DTXSID = 'DTXSID7020182') caf_prob <- get_exposure_functional_use_probability(DTXSID = 'DTXSID0020232') bpa_caf_prob <- get_exposure_functional_use_probability_batch(DTXSID = c('DTXSID7020182', 'DTXSID0020232'))
bpa_prob
caf_prob
bpa_caf_prob
Observe that Caffeine only has probabilities assigned to four functional use categories while Bisphenol A has probabilities assigned to twelve categories. For single chemical search, functional use categories denote the row. However, when using the batch search function, all reported categories are included as columns, with rows corresponding to each chemical. If a chemical does not have a probability associated to a functional use, the corresponding entry is given by an NA.
There are several CTX Exposure
API endpoints and ctxR contains functions for each, and batch versions for some of these as well. These allow users to access various types of exposure data associated to a given chemical. In this vignette, we explored all of the non-batch versions and discussed the batch versions. We encourage the user to experiment with the different endpoints to understand better what sorts of data are available.
# This chunk will be hidden in the final product. It serves to undo defining the # custom print function to prevent unexpected behavior after this module during # the final knitting process and restores original option values. knit_print.data.table = knitr::normal_print registerS3method( "knit_print", "data.table", knit_print.data.table, envir = asNamespace("knitr") ) options(old_options)
end_vignette()
Any scripts or data that you put into this service are public.
Add the following code to your website.
For more information on customizing the embed code, read Embedding Snippets.