diff --git a/.Rbuildignore b/.Rbuildignore index ab2f169e..893b8fef 100644 --- a/.Rbuildignore +++ b/.Rbuildignore @@ -14,3 +14,4 @@ ^CRAN-RELEASE$ ^customSettings$ ^\.github$ +^LICENSE\.md$ diff --git a/DESCRIPTION b/DESCRIPTION index 934c89c8..d15e10ff 100644 --- a/DESCRIPTION +++ b/DESCRIPTION @@ -2,13 +2,12 @@ Package: safetyGraphics Title: Create Interactive Graphics Related to Clinical Trial Safety Version: 2.0.0 Authors@R: c( - person("Jeremy", "Wildfire", email = "jeremy_wildfire@rhoworld.com", role = c("cre","aut")), + person("Jeremy", "Wildfire", email = "jwildfire@gmail.com", role = c("cre","aut")), person("Becca", "Krouse", role="aut"), person("Preston","Burns", role="aut"), person("Xiao","Ni", role = "aut"), person("James","Buchanan", role="aut"), - person("Susan","Duke", role="aut"), - person("Interactive Safety Graphics Working Group", role = "aut")) + person("Susan","Duke", role="aut")) Maintainer: Jeremy Wildfire Description: A framework for evaluation of clinical trial safety. Users can interactively explore their data using the 'Shiny' application or create standalone 'htmlwidget' charts. Interactive charts are built using 'd3.js' and 'webcharts.js' 'JavaScript' libraries. URL: https://github.com/SafetyGraphics/safetyGraphics diff --git a/LICENSE b/LICENSE index f7b8a19e..f02ff01c 100644 --- a/LICENSE +++ b/LICENSE @@ -1,2 +1,2 @@ -YEAR: 2018 -COPYRIGHT HOLDER: Rho Inc. +YEAR: 2021 +COPYRIGHT HOLDER: safetyGraphics authors diff --git a/LICENSE.md b/LICENSE.md new file mode 100644 index 00000000..db5cbda1 --- /dev/null +++ b/LICENSE.md @@ -0,0 +1,21 @@ +# MIT License + +Copyright (c) 2021 safetyGraphics authors + +Permission is hereby granted, free of charge, to any person obtaining a copy +of this software and associated documentation files (the "Software"), to deal +in the Software without restriction, including without limitation the rights +to use, copy, modify, merge, publish, distribute, sublicense, and/or sell +copies of the Software, and to permit persons to whom the Software is +furnished to do so, subject to the following conditions: + +The above copyright notice and this permission notice shall be included in all +copies or substantial portions of the Software. + +THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR +IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, +FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE +AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER +LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, +OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE +SOFTWARE. diff --git a/NAMESPACE b/NAMESPACE index 432ddc30..ba3befaa 100644 --- a/NAMESPACE +++ b/NAMESPACE @@ -84,5 +84,3 @@ importFrom(stringr,str_to_upper) importFrom(utils,hasName) importFrom(utils,zip) importFrom(yaml,as.yaml) -importFrom(yaml,write_yaml) - diff --git a/R/meta.R b/R/meta.R index 503e52a4..8df6856a 100644 --- a/R/meta.R +++ b/R/meta.R @@ -1,5 +1,3 @@ -#' meta -#' #' Metadata data frame containing information about the data mapping used to configure safetyGraphics charts. One record per unique data mapping #' #' @format A data frame with 31 rows and 7 columns diff --git a/R/mod_chartsNav.R b/R/mod_chartsNav.R index 6a5762bb..6904a81e 100644 --- a/R/mod_chartsNav.R +++ b/R/mod_chartsNav.R @@ -1,4 +1,4 @@ -#' Add a navbar tab that initializes the Chart Module UI +#' Adds a navbar tab that initializes the Chart Module UI #' #' @param chart chart metadata #' @param ns namespace diff --git a/R/mod_chartsTab.R b/R/mod_chartsTab.R index 8883b315..7b274b5f 100644 --- a/R/mod_chartsTab.R +++ b/R/mod_chartsTab.R @@ -1,8 +1,7 @@ -#' @title Charts Tab -#' @description Charting module +#' @title UI for chart module, designed to be re-used for each chart generated. #' #' @param id module id -#' @param chart list containing chart specifications +#' @param chart list containing chart specifications like those returned by \link{makeChartConfig}. #' #' @importFrom stringr str_to_title #' @importFrom purrr map2 @@ -17,13 +16,12 @@ chartsTabUI <- function(id, chart){ return(list(header, chartWrap)) } -#' @title home tab - server -#' @description server for the display of the chart tab +#' @title Server for chart module, designed to be re-used for each chart generated. #' #' @param input Input objects from module namespace #' @param output Output objects from module namespace #' @param session An environment that can be used to access information and functionality relating to the session -#' @param chart list containing a safetyGraphics chart object. see custom chart vignette for details. +#' @param chart list containing a safetyGraphics chart object like those returned by \link{makeChartConfig}. #' @param data named list of current data sets (Reactive). #' @param mapping tibble capturing the current data mappings (Reactive). #' diff --git a/R/mod_filterTab.R b/R/mod_filterTab.R index dfd8cf43..aa31ad70 100644 --- a/R/mod_filterTab.R +++ b/R/mod_filterTab.R @@ -1,5 +1,4 @@ -#' @title filterTabUI -#' @description UI that facilitates the filtering data with datamods::filter_data_ui +#' @title UI for the filter module in datamods::filter_data_ui #' #' @param id module id #' @@ -39,8 +38,7 @@ filterTabUI <- function(id){ } -#' @title filter module server -#' @description server function that facilitates the data filtering with the datamods::filter_data_server module +#' @title Server for the filter module in datamods::filter_data_ui #' #' @param input Shiny input object #' @param output Shiny output object diff --git a/R/mod_filterTabChecks.R b/R/mod_filterTabChecks.R index 9da0dea3..5d93abbc 100644 --- a/R/mod_filterTabChecks.R +++ b/R/mod_filterTabChecks.R @@ -1,5 +1,4 @@ -#' @title filter module checks -#' @description function that checks whether the current data and settings are appropriate for the filter tab +#' @title Checks for whether the current data and settings support a filter tab #' #' @param domainData list of data files for each domain #' @param filterDomain domain to use for filtering (typically "dm") diff --git a/R/mod_homeTab.R b/R/mod_homeTab.R index edcdb9fa..cea29776 100644 --- a/R/mod_homeTab.R +++ b/R/mod_homeTab.R @@ -1,5 +1,4 @@ -#' @title Home Tab -#' @description Home Tab - sub-module showing details for the data loaded in the app - UI +#' @title UI for the home module #' #' @param id module id #' @@ -13,8 +12,7 @@ homeTabUI <- function(id){ ) } -#' @title home tab - server -#' @description server for the display of the home tab +#' @title Server for the filter module in datamods::filter_data_ui #' #' @param input mod input #' @param output mod output diff --git a/R/mod_loadCharts.R b/R/mod_loadCharts.R index 7de657c5..858095a0 100644 --- a/R/mod_loadCharts.R +++ b/R/mod_loadCharts.R @@ -1,8 +1,7 @@ -#' @title loadChartsUI -#' @description UI that helps users pick charts +#' @title UI for the chart loading module used in safetyGraphicsInit() #' #' @param id module id -#' @param charts list of charts +#' @param charts list containing chart specifications like those returned by \link{makeChartConfig}. #' #' @importFrom purrr keep #' @importFrom sortable bucket_list add_rank_list @@ -21,15 +20,15 @@ loadChartsUI <- function(id, charts=makeChartConfig()){ ) } -#' @title loadCharts -#' @description server that facilitates selection of charts for safetyGraphicsApp +#' @title Server for the chart loading module used in safetyGraphicsInit() #' #' @param input Shiny input object #' @param output Shiny output object #' @param session Shiny session object -#' @param charts Initial list of charts - +#' @param charts list containing chart specifications like those returned by \link{makeChartConfig}. +#' #' @export + loadCharts <- function(input, output, session, charts=makeChartConfig()) { ns<-session$ns labels<-charts%>%map(~makeChartSummary(.x,showLinks=FALSE,class="chart-sortable")) diff --git a/R/mod_loadData.R b/R/mod_loadData.R index 8f76429e..9673952e 100644 --- a/R/mod_loadData.R +++ b/R/mod_loadData.R @@ -1,5 +1,4 @@ -#' @title loadDataUI -#' @description UI that facilitates the mapping of a column data domain +#' @title UI for the data loading module used in safetyGraphicsInit() #' #' @param id module id #' @param domain character vector with domains to be loaded @@ -19,8 +18,7 @@ loadDataUI <- function(id, domain=NULL){ ) } -#' @title loadDataServer -#' @description UI that facilitates the mapping of a column data domain +#' @title Server for the data loading module used in safetyGraphicsInit() #' #' @param domain data domain to be loaded #' @param input Shiny input object diff --git a/R/mod_mappingColumn.R b/R/mod_mappingColumn.R index a991d446..a08d2f29 100644 --- a/R/mod_mappingColumn.R +++ b/R/mod_mappingColumn.R @@ -1,5 +1,4 @@ -#' @title mappingColumnUI -#' @description UI that facilitates the mapping of a column data domain +#' @title UI that facilitates the mapping of a column data (and any associated fields) #' #' @param id module id #' @param meta metadata for the column (and related fields) @@ -66,8 +65,7 @@ mappingColumnUI <- function(id, meta, data, mapping=NULL){ col_ui } -#' @title mappingColumn -#' @description server function that facilitates the mapping of a single data element (column of field) with a simple select UI +#' @title Server that facilitates the mapping of a column data (and any associated fields) #' #' @param input Shiny input object #' @param output Shiny output object diff --git a/R/mod_mappingDomain.R b/R/mod_mappingDomain.R index be814e27..38871694 100644 --- a/R/mod_mappingDomain.R +++ b/R/mod_mappingDomain.R @@ -1,5 +1,4 @@ -#' @title mappingDomainUI -#' @description UI that facilitates the mapping of a full data domain +#' @title UI that facilitates the mapping of a full data domain #' #' @param id module id #' @param meta metadata for the domain @@ -37,8 +36,7 @@ mappingDomainUI <- function(id, meta, data, mapping=NULL){ } -#' @title mappingDomain -#' @description server function that facilitates the mapping of a single data domain +#' @title Server that facilitates the mapping of a full data domain #' #' @param input Shiny input object #' @param output Shiny output object diff --git a/R/mod_mappingSelect.R b/R/mod_mappingSelect.R index 43c3d7ba..38eb1ef4 100644 --- a/R/mod_mappingSelect.R +++ b/R/mod_mappingSelect.R @@ -1,7 +1,5 @@ -#' Mapping Select UI +#' @title UI that facilitates the mapping of a single data element (column or field) with a simple select UI #' -#' UI that facilitates the mapping of a single data element (column or field) with a simple select UI -#' #' @param id unique id for the UI #' @param label label associated with the control #' @param choices a list of options for the control @@ -33,8 +31,7 @@ mappingSelectUI <- function(id, label, choices=NULL, default=NULL){ ) } -#' @title mappingSelect -#' @description server function that facilitates the mapping of a single data element (column of field) with a simple select UI +#' @title Server that facilitates the mapping of a single data element (column or field) with a simple select UI #' #' @param input Shiny input object #' @param output Shiny output object diff --git a/R/mod_mappingTab.R b/R/mod_mappingTab.R index 21e7bc35..d41bdf52 100644 --- a/R/mod_mappingTab.R +++ b/R/mod_mappingTab.R @@ -1,5 +1,4 @@ -#' @title mappingTabUI -#' @description UI that facilitates the mapping of all data domain +#' @title UI for mapping tab covering of all data domains #' #' @param id module id #' @param meta metadata for all domains @@ -68,8 +67,7 @@ mappingTabUI <- function(id, meta, domainData, mappings=NULL, standards=NULL){ } -#' @title mapping module server -#' @description server function that facilitates the mapping of a single data domain +#' @title Server for mapping tab covering of all data domains #' #' @param input Shiny input object #' @param output Shiny output object diff --git a/R/mod_safetyGraphicsServer.R b/R/mod_safetyGraphicsServer.R index cfa78086..89126bde 100644 --- a/R/mod_safetyGraphicsServer.R +++ b/R/mod_safetyGraphicsServer.R @@ -1,4 +1,4 @@ -#' Server for the default safetyGraphics shiny app +#' Server for core safetyGraphics app including Home, Mapping, Filter, Charts and Settings modules. #' #' This function returns a server function suitable for use in shiny::runApp() #' diff --git a/R/mod_safetyGraphicsUI.R b/R/mod_safetyGraphicsUI.R index 62be772a..db044db5 100644 --- a/R/mod_safetyGraphicsUI.R +++ b/R/mod_safetyGraphicsUI.R @@ -1,4 +1,5 @@ -#' UI for the default safetyGraphics shiny app +#' UI for the core safetyGraphics app including Home, Mapping, Filter, Charts and Settings modules. +#' #' #' @param id module ID #' @param meta data frame containing the metadata for use in the app. See the preloaded file (\code{?safetyGraphics::meta}) for more data specifications and details. Defaults to \code{safetyGraphics::meta}. diff --git a/R/mod_settingsCharts.R b/R/mod_settingsCharts.R index 25ad6e32..2d69976d 100644 --- a/R/mod_settingsCharts.R +++ b/R/mod_settingsCharts.R @@ -1,5 +1,4 @@ -#' @title Settings Module - chart details -#' @description Settings Module - sub-module showing details for the charts loaded in the app - UI +#' @title UI for settings tab showing details for the charts loaded in the app #' #' @param id module id #' @@ -23,8 +22,7 @@ settingsChartsUI <- function(id){ ) } -#' @title Settings Module - charts details - server -#' @description server for the display of the charts +#' @title Server for settings tab showing details for the charts loaded in the app #' #' @param input Shiny input object #' @param output Shiny output object diff --git a/R/mod_settingsCode.R b/R/mod_settingsCode.R index a55c14a4..a778bfc0 100644 --- a/R/mod_settingsCode.R +++ b/R/mod_settingsCode.R @@ -1,5 +1,5 @@ -#' UI for the settings page -#' +#' @title UI for settings tab providing code to re-start the app with current data/settings +#' #' @param id module ID #' #' @export @@ -92,8 +92,8 @@ settingsCodeUI <- function(id){ } -#' @title Server for the setting code page -#' +#' @title Server for settings tab providing code to re-start the app with current data/settings +#' #' @param input Shiny input object #' @param output Shiny output object #' @param session Shiny session object diff --git a/R/mod_settingsData.R b/R/mod_settingsData.R index 45e85175..8d15aae3 100644 --- a/R/mod_settingsData.R +++ b/R/mod_settingsData.R @@ -1,5 +1,4 @@ -#' @title Settings Module - data details -#' @description Settings Module - sub-module showing details for the data loaded in the app - UI +#' @title UI for settings tab showing current data #' #' @param id module id #' @@ -20,8 +19,7 @@ settingsDataUI <- function(id){ ) } -#' @title Settings Module - data details - server -#' @description server for the display of the loaded data +#' @title Server for settings tab showing current data #' #' @param input Shiny input object #' @param output Shiny output object diff --git a/R/mod_settingsMapping.R b/R/mod_settingsMapping.R index d114fe30..9b1b353e 100644 --- a/R/mod_settingsMapping.R +++ b/R/mod_settingsMapping.R @@ -1,6 +1,5 @@ -#' @title Settings view of Metadata/Mapping - UI -#' @description UI that displays the data mapping metadata. -#' +#' @title UI for settings tab showing current mapping +#' #' @param id module id #' #' @import rclipboard @@ -19,8 +18,7 @@ settingsMappingUI <- function(id){ ) } -#' @title Settings view of Metadata/Mapping - server -#' @description server for the display of the data mapping metadata. +#' @title Server for settings tab showing current mapping #' #' @param input Shiny input object #' @param output Shiny output object diff --git a/R/mod_settingsTab.R b/R/mod_settingsTab.R index b16ecf0a..380cd13b 100644 --- a/R/mod_settingsTab.R +++ b/R/mod_settingsTab.R @@ -1,4 +1,4 @@ -#' UI for the settings page +#' @title UI for the settings tab #' #' @param id module ID #' @@ -16,7 +16,7 @@ settingsTabUI <- function(id){ } -#' @title Server for the setting page +#' @title Server for the setting page #' #' @param input Shiny input object #' @param output Shiny output object diff --git a/R/safetyGraphicsApp.R b/R/safetyGraphicsApp.R index 8902c97a..1b90206c 100644 --- a/R/safetyGraphicsApp.R +++ b/R/safetyGraphicsApp.R @@ -1,4 +1,4 @@ -#' Run the interactive safety graphics app +#' Run the core safetyGraphics App #' #' @param domainData named list of data.frames to be loaded in to the app. Sample AdAM data from the safetyData package used by default #' @param meta data frame containing the metadata for use in the app. See the preloaded file (\code{?safetyGraphics::meta}) for more data specifications and details. Defaults to \code{safetyGraphics::meta}. diff --git a/R/safetyGraphicsInit.R b/R/safetyGraphicsInit.R index 81bde317..7c136424 100644 --- a/R/safetyGraphicsInit.R +++ b/R/safetyGraphicsInit.R @@ -1,4 +1,4 @@ -#' Run the interactive safety graphics app +#' App to select charts, load data and then initialize the core safetyGraphics app #' #' @param charts chart object #' @param delayTime time (in ms) between drawing app UI and starting server. Default set to 1000 (1 second), but could need to be higher on slow machine. diff --git a/README.md b/README.md index 171012f0..a62df0da 100644 --- a/README.md +++ b/README.md @@ -2,24 +2,15 @@ [![R build status](https://github.com/ASA-DIA-InteractiveSafetyGraphics/safetyGraphics/workflows/R-CMD-check/badge.svg)](https://github.com/ASA-DIA-InteractiveSafetyGraphics/safetyGraphics/actions) -# safetyGraphics: Clinical Trial Safety Graphics with R +# safetyGraphics: Clinical Trial Monitoring with R -The **safetyGraphics** package provides a framework for evaluation of clinical trial safety in R. It includes several safety-focused visualizations to empower clinical data monitoring. Chief among these is the Hepatic Explorer, based on the [Evaluation of the Drug-Induced Serious Hepatotoxicity (eDish)](https://www.ncbi.nlm.nih.gov/pubmed/21332248) visualization. A demo of the Hepatic Explorer interactive graphic is available [here](https://safetygraphics.github.io/hep-explorer/test-page/example1/) and is shown below. - -This package is being built in conjunction with the [hep-explorer](https://github.com/SafetyGraphics/hep-explorer) javascript library. +The {safetyGraphics} package provides a framework for the evaluation of clinical trial safety data in R using a flexible data pipeline. The package includes a shiny application that allows users to explore safety data using a series of interactive graphics, including the hepatic safety explorer shown below. The package has been developed as part of the Interactive Safety Graphics (ISG) workstream of the ASA Biopharm-DIA Safety Working Group. ![edishgif](https://user-images.githubusercontent.com/3680095/45834450-02b3a000-bcbc-11e8-8172-324c2fe43521.gif) -## Usage - -Users can interactively explore their data with a shiny application or create standalone interactive charts. +## Using the app -### Shiny application - -The Shiny app provides a simple interface for: -- Loading data -- Customizing settings and data mappings -- Viewing and exporting the interactive graphics +A demo of the app using sample data is available [here](https://jwildfire.shinyapps.io/safetyGraphics/) or can be initialized as follows: ```r devtools::install_github("SafetyGraphics/safetyGraphics") @@ -27,29 +18,10 @@ library("safetyGraphics") safetyGraphicsApp() #open the shiny application ``` -### Standalone charts +The most common workflow is for a user to initialize the app with their data, adjust settings as needed, and view the interactive charts. Finally, the user can share any chart by exporting its source code or by generating a self-contained, fully reproducible report that can be shared with others. -Users can also initialize customized standalone charts with a few lines of code. +Instructions for loading study data are provided in the introductory vignette and more complex customizations are provided in the cookbook vignette. -```r -devtools::install_github("safetyGraphics/safetyGraphics") -library("safetyGraphics") - -settings <- list( - id_col = "USUBJID", - value_col = "AVAL", - measure_col = "PARAM", - visit_col = "VISIT", - visitn_col = "VISITNUM", - studyday_col = "ADY", - normal_col_low = "A1LO", - normal_col_high = "A1HI", - measure_values = list(ALT = "Alanine Aminotransferase (U/L)", - AST = "Aspartate Aminotransferase (U/L)", - TB = "Bilirubin (umol/L)", - ALP = "Alkaline Phosphatase (U/L)") - ) - -chartRenderer(data=adlbc, settings=settings, chart="hepexplorer") +# Charts +The app is built to support a wide variety of chart types including static plots (e.g. from {ggplot2}), shiny modules, {htmlwidgets} and even static outputs like RTFs. Several pre-configured charts are included in the companion {safetyCharts} R Package, and are available by default in the app. Other charts can be added using the process descibed in this vignette. -``` diff --git a/_pkgdown.yml b/_pkgdown.yml index fce6b351..7539e8eb 100644 --- a/_pkgdown.yml +++ b/_pkgdown.yml @@ -5,6 +5,24 @@ template: bootswatch: cerulean navbar: + title: safetyGraphics + left: + - icon: fa-home fa-lg + href: index.html + - text: Vignettes + menu: + - text: Intro to Shiny App + href: articles/intro.html + - text: Chart Configuration + href: articles/chartConfiguration.html + - text: Examples Cookbook + href: articles/cookbook.html + - text: Technical FAQ + href: articles/technicalFAQ.html + - text: Functions + href: reference/index.html + - text: News + href: news/index.html right: - icon: fa-github href: https://github.com/SafetyGraphics/safetyGraphics @@ -12,27 +30,60 @@ navbar: development: mode: release - reference: - - title: Main Functions + - title: Main Shiny App Functions contents: - safetyGraphicsApp + - safetyGraphicsInit + - title: Shiny Modules + desc: Reusable Shiny Modules + contents: + - safetyGraphicsServer + - safetyGraphicsUI + - chartsTab + - chartsTabUI + - filterTab + - filterTabUI + - homeTab + - homeTabUI + - loadCharts + - loadChartsUI + - loadData + - loadDataUI + - mappingTab + - mappingTabUI + - mappingDomain + - mappingDomainUI + - mappingColumn + - mappingColumnUI + - mappingSelect + - mappingSelectUI + - settingsTab + - settingsTabUI + - settingsCharts + - settingsChartsUI + - settingsData + - settingsDataUI + - settingsMapping + - settingsMappingUI + - settingsCode + - settingsCodeUI + - title: Data + desc: Data sets used in the apps + contents: + - meta - title: Helper Functions - desc: these functions are used by the main app + desc: Utility functions used in the apps contents: - - addChart - - addSetting - - adlbc - - chartRenderer-shiny - - chartRenderer - - chartsMetadata + - app_startup + - chartsNav - detectStandard - - generateSettings - - getRequiredSettings - - getSettingsMetadata - - removeCharts - - removeSettings - - settingsMetadata - - standardsMetadata - - trimSettings - - validateSettings + - evaluateStandard + - filterTabChecks + - generateMappingList + - makeChartConfig + - makeChartExport + - makeChartParams + - makeChartSummary + - makeMapping + - prepareChart diff --git a/docs/404.html b/docs/404.html index 0eaf4b23..1013dc52 100644 --- a/docs/404.html +++ b/docs/404.html @@ -8,23 +8,29 @@ Page not found (404) • safetyGraphics + - + - + + - + + + + + - - + + - + - - + + @@ -32,10 +38,12 @@ + + @@ -49,7 +57,7 @@ - +
@@ -71,33 +79,38 @@ -
+ + diff --git a/docs/LICENSE-text.html b/docs/LICENSE-text.html index 83016c8b..b5b04273 100644 --- a/docs/LICENSE-text.html +++ b/docs/LICENSE-text.html @@ -8,23 +8,29 @@ License • safetyGraphics + - + - + + - + + + + + - - + + - + - - + + @@ -32,10 +38,12 @@ + + @@ -49,7 +57,7 @@ - +
@@ -71,33 +79,38 @@ -
-
YEAR: 2018
-COPYRIGHT HOLDER: Rho Inc.
+
YEAR: 2021
+COPYRIGHT HOLDER: safetyGraphics authors
 

 
   
 
+  
+
 
 
 
 
       
diff --git a/docs/LICENSE.html b/docs/LICENSE.html
new file mode 100644
index 00000000..96f3686c
--- /dev/null
+++ b/docs/LICENSE.html
@@ -0,0 +1,175 @@
+
+
+
+  
+  
+
+
+
+MIT License • safetyGraphics
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+  
+
+  
+    

+      

+      
+
+      
+
+      

+
+

+  

+    

+      
MIT License

+    

+
+

+
+
Copyright (c) 2021 safetyGraphics authors

+
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

+
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

+
THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

+

+
+  

+
+  
+
+

+
+
+
+      

+      

+  
Developed by Jeremy Wildfire, Becca Krouse, Preston Burns, Xiao Ni, James Buchanan, Susan Duke.

+

+
+

+  
Site built with pkgdown 1.6.1.

+

+
+      

+   

+
+  
+
+
+  
+
+
+
diff --git a/docs/articles/Cookbook.html b/docs/articles/Cookbook.html
new file mode 100644
index 00000000..24121fd4
--- /dev/null
+++ b/docs/articles/Cookbook.html
@@ -0,0 +1,238 @@
+
+
+
+
+
+
+
+Cookbook • safetyGraphics
+
+
+
+
+
+
+
+
+
+
+    

+      

+
+
+      
+
+      

+  

+    

+      
Cookbook

+                        
Jeremy Wildfire

+            
+            
2021-09-02

+      
+      Source: vignettes/Cookbook.Rmd
+      
+
+    

+
+    
+    
+

+

+Cookbook Vignette

+
This vignette contains a series of examples showing how to initialize the safetyGraphics Shiny app in different scenarios. For a general overview of the app see this vignette. For more details about adding custom charts, see this vignette.

+

+

+Setup and installation

+
safetyGraphics requires R v4 or higher. These examples have been tested using RStudio v1.4, but should work on other platforms with proper configuration.

+
You can install safetyGraphics from CRAN like any other R package:

+
install.packages("safetyGraphics")
+library("safetyGraphics")

+
Or to use the most recent development version from GitHub, call:

+
devtools::install_github("safetyGraphics/safetyCharts", ref="dev")
+library(safetyCharts)
+devtools::install_github("safetyGraphics/safetyGraphics", ref="dev")
+library(safetyGraphics)
+safetyGraphics::safetyGraphicsApp()

+

+

+

+Example 1 - Default App

+
To run the app with no customizations using sample AdAM data from the {safetyData} package, install the package and run:

+
safetyGraphics::safetyGraphicsApp()

+

+

+

+Example 2 - SDTM Data

+
The data passed in to the safetyGraphics app can be customized using the data parameter in safetyGraphicsApp(). For example, to run the app with SDTM data saved in {safetyData}, call:

+
sdtm <- list(
+    dm=safetyData::sdtm_dm,
+    aes=safetyData::sdtm_ae,
+    labs=safetyData::sdtm_lb
+)
+
+safetyGraphics::safetyGraphicsApp(domainData=sdtm)

+

+

+

+Example 3 - Single Data Domain

+
Running the app for a single data domain, is similar:

+
justLabs <- list(labs=safetyData::adam_adlbc)
+safetyGraphics::safetyGraphicsApp(domainData=justLabs)

+
Note that charts with missing data are automatically dropped and the filtering tab is not present since it requires demographics data by default.

+

+

+

+Example 4 - Drop Unwanted Charts

+
Users can also generate a list of charts and then drop charts that they don’t want to include. For example, if you wanted to drop charts with type of “htmlwidgets” you could run this code.

+
library(purrr)
+charts <- makeChartConfig() #gets charts from safetyCharts pacakge by default
+notWidgets <- charts %>% purrr::keep(~.x$type != "htmlwidget")
+safetyGraphicsApp(charts=notWidgets)

+

+

+

+Example 6 - Add a chart

+
The code below adds a new simple chart showing participants’ age distribution by sex.

+
ageDist <- function(data, settings){
+    p<-ggplot(data = data, aes_(x=as.name(settings$age_col))) +
+        geom_histogram() + 
+        facet_wrap(as.name(settings$sex_col))
+    return(p)
+}
+ageDist_chart<-list(
+    env="safetyGraphics",
+    name="ageDist",
+    label="Age Distribution",
+    type="plot",
+    domain="dm",
+    workflow=list(
+        main="ageDist"
+    )
+)
+charts <- makeChartConfig() 
+charts$ageDist<-ageDist_chart
+safetyGraphicsApp(charts=charts)

+
For extensive details on adding and customizing different types of charts, see this vignette.

+

+

+

+Example 7 - Non-standard data

+
Next, let’s initialize the the app with non-standard data. {safetyGraphics} automatically detects AdAM and SDTM data when possible, but for non-standard data, the user must provide a data mapping. This can be done in the app using the data/mapping tab, or can be done when the app is initialized by passing a mapping list to safetyGraphicsApp(). For example:

+
notAdAM <- list(labs=safetyData::adam_adlbc %>% rename(id = USUBJID))
+idMapping<- list(labs=list(id_col="id"))
+safetyGraphicsApp(domainData=notAdAM, mapping=idMapping)

+

+

+

+Example 8 - Non-standard data #2

+
For a more realistic example, consider this labs data set (csv). The data can be loaded in to safetyGraphics with the code below, but several items in the mapping page need to be filled in:

+
labs <- read.csv("https://raw.githubusercontent.com/SafetyGraphics/SafetyGraphics.github.io/master/pilot/SampleData_NoStandard.csv")
+safetyGraphics::safetyGraphicsApp(domainData=list(labs=labs))

+
drawing

+
Fortunately there is no need to re-enter this mapping information in every time you re-start the app. After filling in these values once, you can export code to restart the app with the specified settings pre-populated. First, click on the setting icon in the header and then on “code” to see this page:

+

+
The YAML code provided here captures the updates you’ve made on the mapping page. To re-start the app with those settings, just save these YAML code in a new file called customSettings.yaml in your working directory, and then call:

+
labs <- read.csv("https://raw.githubusercontent.com/SafetyGraphics/SafetyGraphics.github.io/master/pilot/SampleData_NoStandard.csv")
+customMapping <- read_yaml("customSettings.yaml")
+safetyGraphics::safetyGraphicsApp(
+    domainData=list(labs=labs),
+    mapping=customMapping   
+)

+
Note, that for more complex customizations, the setting page also provides a .zip file with a fully re-usable version of the app.

+

+

+  

+
+  
+
+

+
+
+
+      

+  
Developed by Jeremy Wildfire, Becca Krouse, Preston Burns, Xiao Ni, James Buchanan, Susan Duke.

+

+
+

+  
Site built with pkgdown 1.6.1.

+

+
+      

+

+
+  
+
+
+  
+
diff --git a/docs/articles/Cookbook_files/header-attrs-2.10/header-attrs.js b/docs/articles/Cookbook_files/header-attrs-2.10/header-attrs.js
new file mode 100644
index 00000000..dd57d92e
--- /dev/null
+++ b/docs/articles/Cookbook_files/header-attrs-2.10/header-attrs.js
@@ -0,0 +1,12 @@
+// Pandoc 2.9 adds attributes on both header and div. We remove the former (to
+// be compatible with the behavior of Pandoc < 2.8).
+document.addEventListener('DOMContentLoaded', function(e) {
+  var hs = document.querySelectorAll("div.section[class*='level'] > :first-child");
+  var i, h, a;
+  for (i = 0; i < hs.length; i++) {
+    h = hs[i];
+    if (!/^h[1-6]$/i.test(h.tagName)) continue;  // it should be a header h1-h6
+    a = h.attributes;
+    while (a.length > 0) h.removeAttribute(a[0].name);
+  }
+});
diff --git a/docs/articles/Cookbook_files/header-attrs-2.9/header-attrs.js b/docs/articles/Cookbook_files/header-attrs-2.9/header-attrs.js
new file mode 100644
index 00000000..dd57d92e
--- /dev/null
+++ b/docs/articles/Cookbook_files/header-attrs-2.9/header-attrs.js
@@ -0,0 +1,12 @@
+// Pandoc 2.9 adds attributes on both header and div. We remove the former (to
+// be compatible with the behavior of Pandoc < 2.8).
+document.addEventListener('DOMContentLoaded', function(e) {
+  var hs = document.querySelectorAll("div.section[class*='level'] > :first-child");
+  var i, h, a;
+  for (i = 0; i < hs.length; i++) {
+    h = hs[i];
+    if (!/^h[1-6]$/i.test(h.tagName)) continue;  // it should be a header h1-h6
+    a = h.attributes;
+    while (a.length > 0) h.removeAttribute(a[0].name);
+  }
+});
diff --git a/docs/articles/TechnicalFAQ.html b/docs/articles/TechnicalFAQ.html
new file mode 100644
index 00000000..b1191736
--- /dev/null
+++ b/docs/articles/TechnicalFAQ.html
@@ -0,0 +1,236 @@
+
+
+
+
+
+
+
+Technical FAQ • safetyGraphics
+
+
+
+
+
+
+
+
+
+
+    

+      

+
+
+      
+
+      

+  

+    

+      
Technical FAQ

+                        
Jeremy Wildfire

+            
+            
2021-09-02

+      
+      Source: vignettes/TechnicalFAQ.Rmd
+      
+
+    

+
+    
+    
+

+

+Technical FAQ Vignette

+
This vignette answers frequently asked technical questions about {safetyGraphics}. It addressees questions on a variety of technical topics including Qualification and Validation status, Common Data Pipelines and Security.

+
Whenever new questions come in, we’ll update the version of this FAQ in our wiki - so check there first if you have a question. We’ll update the vignette on CRAN whenever a new version of the package is released.

+

+

+

+Validation, Quality Control and Testing

+

+

+Q: Is the safetyGraphics package validated?

+
A: As of the version 2 release, the safetyGraphics package is intended for exploratory use only and is not validated or qualified per 21 CFR Part 11. No warranty or guarantees are included as part of the package. Further, any formal validation should be fit for purpose and follow your organization’s procedures. That said, extensive quality checks are built in to the package (see the question below for details) and in to many of charts that are included by default. We follow the work of R Validation hub closely, and may release validation guidance based on the approach described in their white paper at a future date.

+

+

+

+Q: Can I validate charts created by safetyGraphics?

+
A: Study-specific instances of most safetyGraphics charts can be exported either as an R script or as a standalone html report. It may be possible to treat those outputs as standard TLFs (Tables, Listings and Figures) and conduct QC/Validation on them using standard statistical SOPs. Consult with your companies procedures to confirm.

+

+

+

+Q: What testing/QC process for safetyGraphics?

+
A: Several layers of quality control are included in our standard development workflow including: - Over 200 automated unit tests with testthat that run automatically via Continuous integration with GitHub actions. - Automated unit tests for shiny modules run via a headless browser using shinytest. - Pass all standard R checks in R cmd check - Full code review of all new functionality documented in GitHub PR. - Issue tracking in GitHub - Formal Alpha/Beta user testing before major releases - Basic user tests conducted before minor release

+

+

+

+

+Use Cases, Data Sources and Deployment

+

+

+Q: What are some common use cases for safetyGraphics?

+
A: safetyGraphics graphics has been used in a variety of ways. Some of the most common use cases thus far are: - Analysts exploring safety data - Clinicians monitoring ongoing studies - Analysts and Clinicians evaluating safety signals in completed studies

+
As an open source tool with a flexible data pipeline, many other use cases have been discussed: - Data review by Data Safety Monitoring Boards (link) - Submissions to FDA (link) - Visualizing Analysis results data (link) - Risk based monitoring

+

+

+

+Q: Do I have to use a certain data standard with safetyGraphics?

+
A: No. Any standard (or non-standard) data can be loaded as long as it meets the minimum data requirements for the selected data domain. Metadata capturing default CDISC standards are included with the app (see ?safetyGraphics::meta) so that data mappings can be automatically populated when AdAM and SDTM data are loaded. Other data standards require the user to manually complete the data mapping in the mapping tab - see the cookbook vignette for examples.

+

+

+

+Q: What data sources does safetyGraphics support? How do I load custom data?

+
A: This topic is covered in detail in the Loading data section of the Introductory vignettesafetyGraphics is designed to support a flexible data pipeline that supports many data types. In short, data can be loaded using the the dataDomains parameter in the safetyGraphicsApp() function or via the safetyGraphicsInit() graphical user interface.

+
safetyGraphicsApp() - custom data can be loaded via the dataDomains parameter, which should be a list containing dataframes or tibbles for each clinical domain; that list can be populated by importing data from any number of sources including databases, sas files or any number of other sources. See the cookbook vignette for some basic examples of loading custom data.

+
safetyGraphicsInit() - allows users to load tabular data from a variety of sources using the point-and-click interface provided in the {datamods} package.

+
More detail is provided in the Loading data section of the Introductory vignette

+

+

+

+Q: How can the safetyGraphics app be shared?

+
A: The safetyGraphics app can be shared using standard shiny methodology. More details for a specific use cases are given in the next few questions. Charts created by safetyGraphics can also be exported and re-used. Charts created with htmlwidgets are especially flexible and can be used in many contexts - including in web applications outside of R.

+

+

+

+Q: Can I deploy safetyGraphics to shinyapps.io to explore trial data from my organization?

+
A: No, we advise against loading non-authorized, private, or non-deidentified patient data outside of your organization’s firewall. Consult with your IT and QA first. There is huge risk associated with confidentiality, IP, and patient privacy. Also refer to ShinyApps.io Chapter 8 Security and Compliance.

+

+
+

+

+

+Misc.

+

+

+Q: How do I avoid R not choking on the huge volume of lab data? (from @AlbrechtDurer)

+
A: This is a very good question @AlbrechtDurer, and in my experience the answer is complex and varies for different use cases. Focusing on specific toxicities helps, but probably isn’t enough in really big studies. In those cases, I think the most important thing is to design a good data pipeline that includes both a database backend (as opposed to loading all of your study data each time you initialize the app) and visualizations that summarize the data in a reasonable way (as opposed to just plotting every single data point in a scatter plot no matter what). Fortunately this is all doable in R, and improvements in this area are our radar for safetyGraphics after v2 goes live.

+

+

+  

+
+  
+
+

+
+
+
+      

+  
Developed by Jeremy Wildfire, Becca Krouse, Preston Burns, Xiao Ni, James Buchanan, Susan Duke.

+

+
+

+  
Site built with pkgdown 1.6.1.

+

+
+      

+

+
+  
+
+
+  
+
diff --git a/docs/articles/TechnicalFAQ_files/header-attrs-2.10/header-attrs.js b/docs/articles/TechnicalFAQ_files/header-attrs-2.10/header-attrs.js
new file mode 100644
index 00000000..dd57d92e
--- /dev/null
+++ b/docs/articles/TechnicalFAQ_files/header-attrs-2.10/header-attrs.js
@@ -0,0 +1,12 @@
+// Pandoc 2.9 adds attributes on both header and div. We remove the former (to
+// be compatible with the behavior of Pandoc < 2.8).
+document.addEventListener('DOMContentLoaded', function(e) {
+  var hs = document.querySelectorAll("div.section[class*='level'] > :first-child");
+  var i, h, a;
+  for (i = 0; i < hs.length; i++) {
+    h = hs[i];
+    if (!/^h[1-6]$/i.test(h.tagName)) continue;  // it should be a header h1-h6
+    a = h.attributes;
+    while (a.length > 0) h.removeAttribute(a[0].name);
+  }
+});
diff --git a/docs/articles/TechnicalFAQ_files/header-attrs-2.9/header-attrs.js b/docs/articles/TechnicalFAQ_files/header-attrs-2.9/header-attrs.js
new file mode 100644
index 00000000..dd57d92e
--- /dev/null
+++ b/docs/articles/TechnicalFAQ_files/header-attrs-2.9/header-attrs.js
@@ -0,0 +1,12 @@
+// Pandoc 2.9 adds attributes on both header and div. We remove the former (to
+// be compatible with the behavior of Pandoc < 2.8).
+document.addEventListener('DOMContentLoaded', function(e) {
+  var hs = document.querySelectorAll("div.section[class*='level'] > :first-child");
+  var i, h, a;
+  for (i = 0; i < hs.length; i++) {
+    h = hs[i];
+    if (!/^h[1-6]$/i.test(h.tagName)) continue;  // it should be a header h1-h6
+    a = h.attributes;
+    while (a.length > 0) h.removeAttribute(a[0].name);
+  }
+});
diff --git a/docs/articles/chartConfiguration.html b/docs/articles/chartConfiguration.html
new file mode 100644
index 00000000..82c5b574
--- /dev/null
+++ b/docs/articles/chartConfiguration.html
@@ -0,0 +1,411 @@
+
+
+
+
+
+
+
+Chart Configuration • safetyGraphics
+
+
+
+
+
+
+
+
+
+
+    

+      

+
+
+      
+
+      

+  

+    

+      
Chart Configuration

+                        
Jeremy Wildfire

+            
+            
2021-09-02

+      
+      Source: vignettes/chartConfiguration.Rmd
+      
+
+    

+
+    
+    
+

+

+Chart Configuration Vignette

+
The {safetyGraphics} shiny app can be used to display a wide variety of charts. This vignette provides details about the charting process including step-by-step instructions for adding new charts and technical specifications, but first we need to talk about a 2nd package …

+

+

+

+Introducing {safetyCharts}

+
While this is technically a vignette for {safetyGraphics}, the {safetyCharts} package is just as important here. The roles of the packages can be summarized in just a few words:

+
The {safetyGraphics} platform displays charts from {safetyCharts}.

+
This relationship is central to the technical framework for the safetyGraphics app. By itself, the safetyGraphics platform really doesn’t do much! In fact, none of the content on the Charts tab is actually found in the safetyGraphics package; it’s all imported from elsewhere! As you’ve probably guessed, the default charts live in the safetyCharts package. safetyCharts has over a dozen charts that are configured to work with {safetyGraphics}, but can also easily be used independently.

+
While {safetyGraphics} and {safetyCharts} are designed to work seamlessly together, users can also add charts from other packages. In fact, several charts in {safetyCharts} are just wrappers that load charts from other packages for use in {safetyGraphics}. The rest of this vignette provides a series of step-by-step examples detailing how this process works for different types of charts.

+

+

+

+{safetyGraphics} Chart Components

+
To add a chart to safetyGraphics, two components are required:

+
    
+
  1. A Configuration Object
    2. 
+
  2. A Chart Function
    3. 
+

+
The configuration file captures metadata about the chart for use in the app and is typically saved as a YAML file. Several example configuration files are provided in the examples below, and YAML Configuration files for {safetyCharts} are saved here.

+
The chart function typically takes a list of settings and a list of data as inputs and returns a chart object ready to be displayed in the app. Details of charting functions vary somewhat for different chart types, as explained in the examples below.

+
A full technical specification of this chart configuration framework is provided in Appendix 1.

+

+

+

+Example 1 - Hello World

+
Once you’ve created the configuration and chart functions, the chart can be added to the app via the charts parameter in safetyGraphicsApp(). Consider this simple “Hello World” example:

+
# Chart Function
+helloWorld <- function(data, settings){
+    plot(-1:1, -1:1)
+    text(runif(20, -1,1),runif(20, -1,1),"Hello World")
+}
+
+# Chart Configuration
+helloworld_chart<-list(
+    env="safetyGraphics",
+    name="HelloWorld",
+    label="Hello World!",
+    type="plot",
+    domain="aes",
+    workflow=list(
+        main="helloWorld"
+    )
+)
+
+safetyGraphicsApp(charts=list(helloworld_chart))

+
It’s also easy to add a custom chart to the default charts provided in {safetyCharts} using the makeChartConfig() function:

+
charts <- makeChartConfig(packages="safetyCharts") # or just makeChartConfig() since safetyCharts is included by default
+charts$helloworld<-helloworld_chart
+safetyGraphicsApp(charts=charts)

+
Here’s our Hello World the chart running in the app:

+

+

+

+

+Example 2 - Static Outlier Explorer

+
Now let’s consider a more complex example that makes use of the data and settings provided in safetyGraphics. In this section, we use {ggplot2} to create a spaghetti plot for tracking outliers in lab data. First, consider the following code which creates a stand-alone plot for a single data set:

+
# Use sample clinical trial data sets from the {safetyData} package
+library(safetyData) 
+library(ggplot2)
+library(dplyr)
+
+# Define data mapping using a format similar to a reactive safetyGraphics mapping 
+settings <- list(
+    id_col="USUBJID",
+    value_col="LBSTRESN",
+    measure_col="LBTEST",
+    studyday_col="LBDY"
+)
+
+# Define a plotting function that takes data and settings as inputs 
+spaghettiPlot <- function( data, settings ){
+    # define plot aes - note use of standard evaluation! 
+    plot_aes <- aes_(
+        x=as.name(settings$studyday_col), 
+        y=as.name(settings$value_col), 
+        group=as.name(settings$id_col)
+    )
+
+    #create the plot
+    p<-ggplot(data = data, plot_aes) +
+        geom_path(alpha=0.15) + 
+        facet_wrap(
+            as.name(settings$measure_col),
+            scales="free_y"
+        )
+    return(p)
+}
+
+spaghettiPlot(
+    safetyData::sdtm_lb %>% 
+        filter(LBTEST %in% c("Albumin","Bilirubin","Calcium","Chloride")), 
+    settings
+)

+
Running the code above should create a plot with 4 panels:

+

+
With minor modifications, this chart can be added to the {safetyGraphics} shiny app, which allows us to create the chart with any mappings/data combination loaded in the app. The spaghettiPlot() function above is already written to work with safetyGraphics, so we just need to create the chart configuration object. This time we’ll capture the configuration in a YAML file.

+
env: safetyGraphics
+label: Spaghetti Plot
+type: plot
+domain: 
+  - labs
+workflow:
+  main: spaghettiPlot
+links:
+  safetyCharts: https://github.com/SafetyGraphics/safetycharts

+
With the charting function loaded in to our session and the configuration file saved in our working directory as spaghetti.yaml, we can add the chart to the app as follows:

+
library(yaml)
+charts <- makeChartConfig()
+charts$spaghetti<-prepareChart(read_yaml('spaghetti.yaml'))
+safetyGraphicsApp(charts=charts)

+
Under the charts tab, you’ll see:

+

+
If you look closely at the spaghettiPlot() code above, you’ll noticed some details that make the chart work in the app:

+
    
+
  • The chart function is written as a function taking data and settings as inputs. This is the expected parameterization for most charts in {safetyGraphics}.
    • 
+
  • The references to settings use parameters that are defined on the mapping tab. Behind the scenes, these are defined in the safetyGraphics::meta.
    • 
+
  • The spaghettiPlot function is referenced in the main item the YAML workflow. This tells the app which function to use to draw the chart.
    • 
+

+
These details allow users to dynamically define data attributes for any labs data set, allowing the chart to be reused across many different types of data.

+
This example is inspired by safetyCharts::safety_outlier_explorer - the charting function and yaml configuration file on are GitHub.

+

+

+

+Example 3 - Shiny Module

+
{safetyGraphics} also supports defining charts as Shiny Modules. Once you’re familiar with modules, they are relatively straightforward to use with safetyGraphics.

+
Let’s take a look at a simple module that extends the functionality of the static chart from the example above. Once again, this example is based upon safetyCharts, and you can see the code and config on GitHub.

+
The config object for a module differs from a static chart is that the workflow section of the YAML file must specify ui and server functions instead of a main charting function. This example defines a simple UI function that allows users to select which lab measurements should be included in the spaghetti plot from example 1:

+
safetyOutlierExplorer_ui <- function(id) {
+    ns <- NS(id) 
+    sidebar<-sidebarPanel(
+        selectizeInput(
+            ns("measures"), 
+            "Select Measures", 
+            multiple=TRUE, 
+            choices=c("")
+        )
+    )
+    main<-mainPanel(plotOutput(ns("outlierExplorer")))
+    ui<-fluidPage(
+        sidebarLayout(
+            sidebar,
+            main,
+            position = c("right"),
+            fluid=TRUE
+        )
+    )
+    return(ui)
+}

+
Next we define a server function that populates the control for selecting measurements and then draws the plot using safetyCharts::safety_outlier_explorer() charting function - which is based on the spaghetti() function ! Note that the server function takes a single reactive params object containing the data (params$data) and settings (param$settings) as input.

+
safetyOutlierExplorer_server <- function(input, output, session, params) {
+
+    ns <- session$ns
+    # Populate control with measures and select all by default
+    observe({
+        measure_col <- params()$settings$measure_col
+        measures <- unique(params()$data[[measure_col]])
+        updateSelectizeInput(
+            session, 
+            "measures",
+            choices = measures,
+            selected = measures
+        )
+    })
+
+    # customize selected measures based on input
+    settingsR <- reactive({
+        settings <- params()$settings
+        settings$measure_values <- input$measures
+        return(settings)
+    })
+
+    #draw the chart
+    output$outlierExplorer <- renderPlot({safety_outlier_explorer(params()$data, settingsR())})
+}

+
Finally, the YAML configuration file looks like this - just the workflow and label changes from Example 1:

+
env: safetyGraphics
+label: Outlier Explorer - Module
+type: module
+package: safetyCharts
+domain: 
+  - labs
+workflow:
+  ui: safetyOutlierExplorer_ui
+  server: safetyOutlierExplorer_server
+links:
+  safetyCharts: https://github.com/SafetyGraphics/safetycharts

+
Initializing the app as usual by adding it to the chart list: charts$outlierMod<-prepareChart(read_yaml('outlierMod.yaml'))

+
Unselecting a few measures gives the following display: 

+

+

+

+Example 4 - htmlwidgets and init functions

+
You can also add custom htmlwidgets to safetyGraphics. In fact, many of the default charts imported from safetyCharts are javascript libraries that are imported as htmlwidgets. Like shiny modules, htmlwidgets are relatively simple to use once you are familiar with the basics.

+
The biggest differences between widgets and other charts in safetyGraphics are:

+
    
+
  1. The widget must be contained in a package, which must be specified in the YAML file.
    2. 
+
  2. The widget expects a widget item giving the name of the widget in the YAML workflow.
    3. 
+
  3. By default, the data and settings for a widget are passed in a list (list(data=data, settings=settings)) to the x parameter in htmlwidget::createWidget.
    4. 
+

+
Items 1 and 2 above are simple enough, but #3 is likely to create problems unless the widget is designed specifically for usage with safetyGraphics. That is, if the widget isn’t expecting x$settings to be a list that it uses to configure the chart, it probably isn’t going to work as expected.

+
Fortunately, there’s a workaround built in to safetyGraphics in the form of init workflow functions. Init functions run before the chart is drawn, and can be used to create custom parameterizations. The init function should take data and settings as inputs and return params which should be a list which is then provided to the chart (see the appendix for more details). The init function for the the interactive AE Explorer is a good example. It starts by merging demographics and adverse event data and then proceeds to create a customized settings object to match the configuration requirements of the javascript chart renderer. This init function is then saved under workflow$init in the chart config object.

+
The rest of the chart configuration YAML is similar to the examples above, and the chart is once again by passing the chart config object to safetyGraphicsApp()

+

+

+

+Appendix #1 - Chart Framework Technical Specifications

+

+

+Configuration Overview

+

+
The diagram above summarizes the various components of the safetyGraphics charting framework: - The safetyGraphicsApp() function allows users to specify which charts to include in the shiny app via the charts parameter, which expects a list of charts. - Each item in charts is itself defined as a list that provides configuration details for a single chart. These configuration lists have several required parameters, which are described in the technical specification below. - Configuration lists are typically saved as YAML files, but can be also be loaded directly as list objects as shown in the Hello World example above. - Needed functions are bound to the chart object via the prepareChart() function. See the documentation for chart$functions below for full details.

+

+

+

+Chart Specification

+
Each item in the charts list should be a list() with the following parameters: - env: Environment for the chart. Must be set to “safetyGraphics” or the chart is dropped. Type: character. Required - name: Name of the chart. Type: character. Required - type:: Type of chart. Valid options are: “plot”,“htmlwidget”,“html”,“table” and “module”. Type: character. Required - label: A short description of the chart. chart\(name is used if not provided. Type: *character*. *Optional* - `domain`: The data domain(s) used in the chart. Type: *character*. **Required** - `package`: The package where the {htmlwidget} is saved. Type: *character*. **Required** when `chart\)typeis "htmlwidget" -order: Order in which to display the chart. If order is a negative number, the chart is dropped. Defaults to 999999. Type: *Integer*. *Optional* -links:  Named list of link names/urls to be shown in the chart header. Type: *list of character*. *Optional* -path: Full path of the YAML file. Auto-generated bymakeChartConfig()Type: *character* *optional* -workflow: Names of functions used to create the chart. Should be loaded in global environment or included inchart\(package` before calling `prepareChart()`. Supported parameters are listed below. Type: *list of character*. **Required**  - `workflow\)main: name of the function to draw the chart. The function should takedataandsettingsparameters unless the input parameters are customized by aninitfunction. **Required**, unlesschart\(type` is "htmlwidget" or "module")  - `workflow\)init: name of initialization function that runs before chart is drawn via the main function. Should take data and settings as input and return a list of parameters accepted by the main function. Optional - workflow$widget: name or widget saved in chart$package to be passed to htmlwidgets::createWidget Required when chart$type is “htmlwidget” - workflow$ui and workflow$server: names of functions to render shiny ui and server. Automatically generated in prepareChart() unless chart$type is “module”. Required when chart$type is ‘module’ - functions: a list of functions used to create the chart. Typically generated at runtime by prepareChart() using information in chart$workflow, chart$type and chart$package. Not recommended to generate manually. Type: list of functions. Required

+

+

+

+Default Technical workflow

+
This appendix describe the technical process used to render a chart when safetyGraphicsApp() is called with the default parameters.

+
    
+
  1. 
+safetyGraphicsApp() is called with charts and chartSettingsPath as NULL (the default).
    2. 
+
  2. 
+app_startup is called, which then immediately calls makeChartConfig().
    3. 
+
  3. 
+makeChartConfig() looks for charts in the safetyCharts package (the default) since no path was specified. The function looks for the package in all current .libPaths() and then looks in the inst/config folder once the package is found.
    4. 
+
  4. 
+makeChartConfig loads YAML configuration files in the specified directories and saves them to a list. name and path parameters are added.
    5. 
+
  5. 
+makeChartConfig calls prepareChart for each chart configuration. prepareChart sets default values for order, name and export, and then binds relevant functions to a chart$functions list based on the chart’s type, workflow and package.
    6. 
+
  6. That list of charts is then returned to app_startup() which runs a few actions on each chart:
+
      
+
    • If chart$functions is missing, prepareChart is called (not relevant in the default workflow, but useful for adding custom charts)
      • 
+
    • If chart$order is negative, the chart is dropped with a message.
      • 
+
    • If chart$env is not “safetyGraphics”, the chart is dropped with a message.
      • 
+
    • If chart$domains has elements not found in the dataDomains passed to `app_startup(), the chart is dropped with a message.
      • 
+
    • 
+charts are re-ordered based on chart$order
+
      • 
+
    
+
    7. 
+
  7. 
+app_startup returns the list of charts to safetyGraphicsApp which then then passes them along to safetyGraphicsServer as the charts parameter.
    8. 
+
  8. 
+safetyGraphicsServer then creates modules for each chart. First, UIs are created via chartsNav() which then calls:
+
      
+
    • 
+makeChartSummary to create the chart header with links and metadata and …
      • 
+
    • 
+ChartsTabUI which then calls chart$functions$ui to create the proper UI element based on chart$type.
      • 
+
    
+
    9. 
+
  9. Next, safetyGraphicsServer draws the charts using chartsTab() which:
+
      
+
    • Creates a reactive params object containing mappings and data using makeChartParams() which:
+
        
+
      • Subsets domainData based on chart$domain
+
        • 
+
      • Calls charts$functions$init if provided
        • 
+
      • Does custom formatting for chart$type of “htmlwidget”
        • 
+
      
+
      • 
+
    • Chart is drawn using chart$functions$server and chart$functions$main
+
      • 
+
    • Button to download R script is added to header. Script is created by makeChartExport()
+
      • 
+
    • Button to download html report is added to header unless type=“module”. Report template is at “inst/reports/safetyGraphicsReport.Rmd”
      • 
+
    
+
    10. 
+
  10. Finally, safetyGraphicsServer passes the charts to settingsTab, which uses them to help populate the charts and code subtabs.
    11. 
+

+

+

+  

+
+  
+
+

+
+
+
+      

+  
Developed by Jeremy Wildfire, Becca Krouse, Preston Burns, Xiao Ni, James Buchanan, Susan Duke.

+

+
+

+  
Site built with pkgdown 1.6.1.

+

+
+      

+

+
+  
+
+
+  
+
diff --git a/docs/articles/chartConfiguration_files/header-attrs-2.10/header-attrs.js b/docs/articles/chartConfiguration_files/header-attrs-2.10/header-attrs.js
new file mode 100644
index 00000000..dd57d92e
--- /dev/null
+++ b/docs/articles/chartConfiguration_files/header-attrs-2.10/header-attrs.js
@@ -0,0 +1,12 @@
+// Pandoc 2.9 adds attributes on both header and div. We remove the former (to
+// be compatible with the behavior of Pandoc < 2.8).
+document.addEventListener('DOMContentLoaded', function(e) {
+  var hs = document.querySelectorAll("div.section[class*='level'] > :first-child");
+  var i, h, a;
+  for (i = 0; i < hs.length; i++) {
+    h = hs[i];
+    if (!/^h[1-6]$/i.test(h.tagName)) continue;  // it should be a header h1-h6
+    a = h.attributes;
+    while (a.length > 0) h.removeAttribute(a[0].name);
+  }
+});
diff --git a/docs/articles/chartConfiguration_files/header-attrs-2.9/header-attrs.js b/docs/articles/chartConfiguration_files/header-attrs-2.9/header-attrs.js
new file mode 100644
index 00000000..dd57d92e
--- /dev/null
+++ b/docs/articles/chartConfiguration_files/header-attrs-2.9/header-attrs.js
@@ -0,0 +1,12 @@
+// Pandoc 2.9 adds attributes on both header and div. We remove the former (to
+// be compatible with the behavior of Pandoc < 2.8).
+document.addEventListener('DOMContentLoaded', function(e) {
+  var hs = document.querySelectorAll("div.section[class*='level'] > :first-child");
+  var i, h, a;
+  for (i = 0; i < hs.length; i++) {
+    h = hs[i];
+    if (!/^h[1-6]$/i.test(h.tagName)) continue;  // it should be a header h1-h6
+    a = h.attributes;
+    while (a.length > 0) h.removeAttribute(a[0].name);
+  }
+});
diff --git a/docs/articles/index.html b/docs/articles/index.html
index 2adb935d..ad545bd5 100644
--- a/docs/articles/index.html
+++ b/docs/articles/index.html
@@ -8,23 +8,29 @@
 
 Articles • safetyGraphics
 
+
 
-
+
 
-
+
+
 
-
+
+
+
+
+
 
 
-
-
+
+
 
 
-
+
 
 
-
-
+
+
 
 
 
@@ -32,10 +38,12 @@
 
 
 
+
 
 
 
 
+
 
 
 
@@ -49,7 +57,7 @@
 
   
 
-  
+  
     

       

       
 
@@ -71,33 +79,38 @@
       
-      
       

   
 
@@ -136,11 +155,11 @@ 
All vignettes

 
       

       

-  
Developed by Jeremy Wildfire, Becca Krouse, Preston Burns, Xiao Ni, James Buchanan, Susan Duke, Interactive Safety Graphics Working Group.

+  
Developed by Jeremy Wildfire, Becca Krouse, Preston Burns, Xiao Ni, James Buchanan, Susan Duke.

 

 
 

-  
Site built with pkgdown 1.4.1.

+  
Site built with pkgdown 1.6.1.

 

 
       

diff --git a/docs/articles/intro.html b/docs/articles/intro.html
new file mode 100644
index 00000000..ee4c805d
--- /dev/null
+++ b/docs/articles/intro.html
@@ -0,0 +1,245 @@
+
+
+
+
+
+
+
+Intro to Shiny App • safetyGraphics
+
+
+
+
+
+
+
+
+
+
+    

+      

+
+
+      
+
+      

+  

+    

+      
Intro to Shiny App

+                        
Jeremy Wildfire

+            
+            
2021-09-02

+      
+      Source: vignettes/intro.Rmd
+      
+
+    

+
+    
+    
+

+

+Intro Vignette

+
The safetyGraphics shiny app provides an easy-to-use shiny interface for creating shareable safety graphics for any study. This vignette provides an overview of the app’s functionality, shows how to initialize the app with your own study data, and provides links to technical resources explaining how to customize the app.

+

+

+

+safetyGraphics Demo

+
A demo of shiny application using data from the {safetyData} package is hosted here. The app can also be initialized with the safetyGraphicsApp() function in the R console - see Appendix 1 for details.

+
Let’s take a quick look at the various pages in the app.

+

+

+Home Tab

+
A home page has a basic overview of the app.

+

+

+

+

+Mapping Tab

+
The Mapping tab is used to tell charts which data columns and fields to use for various chart components.

+

+
This mapping process makes it easy to re-use charts across many different studies. You can see previews of the loaded data using the checkbox at the top of the page. The demo data has 3 data domains (labs, adverse events (aes) and demographics (dm)), but others can be added as well. The mapping tab is automatically filled in for common data standards, like the ADaM data shown here, but can also be filled in manually for non-standard data.

+

+

+

+Filtering Tab

+
The Filtering tab allows users to interactively select which participants to include in charts.

+

+
This tab is created using the filter functionality included in the {datamods} package. Whenever data is filtered in this tab, those filtered data are used in all charts (across all data domains). Note that the number of participants selected is always shown in the upper right hand corner of the app.

+

+

+

+Charts Tab

+
Clicking the Charts tab opens a dropdown menu containing a series of charts related to clinical trial safety. Clicking the Hepatic Safety Explorer opens this page:

+

+
safetyGraphics supports many different kinds of charts including web-based interactive graphics using {htmlwidgets} (like the chart shown above), static plots, plotly plots and custom shiny modules. Each chart has a header that provides details about the chart, links to chart-specific resources and buttons that allow users to download a stand-alone html report or a .R file that reproduces the chart. See the Chart Configuration Vignette for more detail about the safetyGraphics charting framework.

+

+

+

+⚙️ (Settings) Tab

+
Finally, the Settings tab - shown as a gear icon ⚙️ - contains technical details that can be used to customize/troubleshoot the app. Clicking on the “Code” sub-tab (shown below) allows you to download a zip file that can be used to re-open the app with with any customizations that have been made during your current session.

+

+

+

+

+

+Loading Study Data

+
There are 2 primary ways to load your study data in to the safetyGraphics shiny app:

+
    
+
  1. Using safetyGraphicsInit() shiny interface
    2. 
+
  2. Passing data directly to safetyGraphicsApp()
+
    3. 
+

+

+

+Loading data with safetyGraphicsInit()
+

+
The safetyGraphicsInit() function starts a simple app that allows users to select charts and then load the data required via a point-and-click interface as shown below:

+

+
The app dynamically determines which data sets are required for the selected charts and updates the “Data Loader” UI when the charts selection changes. Below, we’ve selected 2 charts from the labs domain - so the other data domains are automatically hidden.

+

+
Once you’ve picked charts, click the “Load” buttons in the “Data Loader” section to select data files for each domain. Data is loaded using the import functionality from the {datamods} package which allows you to select data loaded in your R session or load data files directly from your file system. datamods supports any file format that {rio} can handle including text files, Excel, SAS and SPSS format.

+
Once you’ve loaded files for all of the active data domains, the “Run App” button will become active. Click it to initialize the app.

+

+

+

+Passing data to safetyGraphicsApp()
+

+
You can also initialize the app with custom data directly from the R console. The basic workflow is as follows:

+
    
+
  1. Load your data in to the R session
    2. 
+
  2. Save your data as a named list. The name of each list item should correspond to a safetyGraphics data domain.
    3. 
+
  3. Run safetyGraphicsApp() using the domainData to pass the list of data frames.
    4. 
+

+
Here is a simple example that starts the app with SDTM data from the safetyData library:

+
library(safetyData)
+sdtm <- list(
+    dm=safetyData::sdtm_dm,
+    aes=safetyData::sdtm_ae,
+    labs=safetyData::sdtm_lb
+)
+
+safetyGraphics::safetyGraphicsApp(domainData=sdtm)

+
This example and other use cases are described in the safetyGraphics Cookbook - Advanced Examples Vignette.

+

+

+

+

+Additional Resources

+
Several additional vignettes are available for more advanced topics: - Chart Configuration Vignette - details about the charting process including technical specifications and step-by-step instructions - Cookbook Vignette - a series of examples showing how to initialize the safetyGraphics Shiny app in different scenarios - Technical FAQ Vignette Vignette - vignette discussing security, validation and other technical issues

+
The {safetyGraphics} app is maintained by the Interactive Safety Graphics (ISG) subteam of the ASA Biopharm-DIA Safety Working Group. You can learn more about the team and find links to recent presentations and publications at our home page.

+

+

+

+Appendix 1 - Initialization code

+
We suggest running the app in RStudio with R version 4.0 or higher. The following code installs the {safetyGraphics} package and initializes the app demo:

+
install.packages('safetyGraphics')
+library(safetyGraphics)
+safetyGraphicsApp() 

+
Or to use the initialization workflow:

+
install.packages('safetyGraphics')
+library(safetyGraphics)
+safetyGraphicsInit() 

+
Or you can install the most recent development version of {safetyGraphics} and the companion package {safetyCharts} directly from GitHub:

+
install.packages("devtools")
+library(devtools)
+devtools::install_github("safetyGraphics/safetyGraphics") 
+library(safetyGraphics)
+devtools::install_github("safetyGraphics/safetyCharts") 
+library(safetyCharts)
+safetyGraphicsApp() #or safetyGraphicsInit()

+

+  

+
+  
+
+

+
+
+
+      

+  
Developed by Jeremy Wildfire, Becca Krouse, Preston Burns, Xiao Ni, James Buchanan, Susan Duke.

+

+
+

+  
Site built with pkgdown 1.6.1.

+

+
+      

+

+
+  
+
+
+  
+
diff --git a/docs/articles/intro_files/header-attrs-2.10/header-attrs.js b/docs/articles/intro_files/header-attrs-2.10/header-attrs.js
new file mode 100644
index 00000000..dd57d92e
--- /dev/null
+++ b/docs/articles/intro_files/header-attrs-2.10/header-attrs.js
@@ -0,0 +1,12 @@
+// Pandoc 2.9 adds attributes on both header and div. We remove the former (to
+// be compatible with the behavior of Pandoc < 2.8).
+document.addEventListener('DOMContentLoaded', function(e) {
+  var hs = document.querySelectorAll("div.section[class*='level'] > :first-child");
+  var i, h, a;
+  for (i = 0; i < hs.length; i++) {
+    h = hs[i];
+    if (!/^h[1-6]$/i.test(h.tagName)) continue;  // it should be a header h1-h6
+    a = h.attributes;
+    while (a.length > 0) h.removeAttribute(a[0].name);
+  }
+});
diff --git a/docs/articles/intro_files/header-attrs-2.9/header-attrs.js b/docs/articles/intro_files/header-attrs-2.9/header-attrs.js
new file mode 100644
index 00000000..dd57d92e
--- /dev/null
+++ b/docs/articles/intro_files/header-attrs-2.9/header-attrs.js
@@ -0,0 +1,12 @@
+// Pandoc 2.9 adds attributes on both header and div. We remove the former (to
+// be compatible with the behavior of Pandoc < 2.8).
+document.addEventListener('DOMContentLoaded', function(e) {
+  var hs = document.querySelectorAll("div.section[class*='level'] > :first-child");
+  var i, h, a;
+  for (i = 0; i < hs.length; i++) {
+    h = hs[i];
+    if (!/^h[1-6]$/i.test(h.tagName)) continue;  // it should be a header h1-h6
+    a = h.attributes;
+    while (a.length > 0) h.removeAttribute(a[0].name);
+  }
+});
diff --git a/docs/authors.html b/docs/authors.html
index 231c124c..06c9745f 100644
--- a/docs/authors.html
+++ b/docs/authors.html
@@ -8,23 +8,29 @@
 
 Authors • safetyGraphics
 
+
 
-
+
 
-
+
+
+
+
 
-
+
+
+
 
 
-
-
+
+
 
 
-
+
 
 
-
-
+
+
 
 
 
@@ -32,10 +38,12 @@
 
 
 
+
 
 
 
 
+
 
 
 
@@ -49,7 +57,7 @@
 
   
 
-  
+  
     

       

       
 
@@ -71,33 +79,38 @@
       
-      
       
 
   

@@ -164,11 +169,11 @@ 
Authors

 
       
diff --git a/docs/bootstrap-toc.css b/docs/bootstrap-toc.css
new file mode 100644
index 00000000..5a859415
--- /dev/null
+++ b/docs/bootstrap-toc.css
@@ -0,0 +1,60 @@
+/*!
+ * Bootstrap Table of Contents v0.4.1 (http://afeld.github.io/bootstrap-toc/)
+ * Copyright 2015 Aidan Feldman
+ * Licensed under MIT (https://github.com/afeld/bootstrap-toc/blob/gh-pages/LICENSE.md) */
+
+/* modified from https://github.com/twbs/bootstrap/blob/94b4076dd2efba9af71f0b18d4ee4b163aa9e0dd/docs/assets/css/src/docs.css#L548-L601 */
+
+/* All levels of nav */
+nav[data-toggle='toc'] .nav > li > a {
+  display: block;
+  padding: 4px 20px;
+  font-size: 13px;
+  font-weight: 500;
+  color: #767676;
+}
+nav[data-toggle='toc'] .nav > li > a:hover,
+nav[data-toggle='toc'] .nav > li > a:focus {
+  padding-left: 19px;
+  color: #563d7c;
+  text-decoration: none;
+  background-color: transparent;
+  border-left: 1px solid #563d7c;
+}
+nav[data-toggle='toc'] .nav > .active > a,
+nav[data-toggle='toc'] .nav > .active:hover > a,
+nav[data-toggle='toc'] .nav > .active:focus > a {
+  padding-left: 18px;
+  font-weight: bold;
+  color: #563d7c;
+  background-color: transparent;
+  border-left: 2px solid #563d7c;
+}
+
+/* Nav: second level (shown on .active) */
+nav[data-toggle='toc'] .nav .nav {
+  display: none; /* Hide by default, but at >768px, show it */
+  padding-bottom: 10px;
+}
+nav[data-toggle='toc'] .nav .nav > li > a {
+  padding-top: 1px;
+  padding-bottom: 1px;
+  padding-left: 30px;
+  font-size: 12px;
+  font-weight: normal;
+}
+nav[data-toggle='toc'] .nav .nav > li > a:hover,
+nav[data-toggle='toc'] .nav .nav > li > a:focus {
+  padding-left: 29px;
+}
+nav[data-toggle='toc'] .nav .nav > .active > a,
+nav[data-toggle='toc'] .nav .nav > .active:hover > a,
+nav[data-toggle='toc'] .nav .nav > .active:focus > a {
+  padding-left: 28px;
+  font-weight: 500;
+}
+
+/* from https://github.com/twbs/bootstrap/blob/e38f066d8c203c3e032da0ff23cd2d6098ee2dd6/docs/assets/css/src/docs.css#L631-L634 */
+nav[data-toggle='toc'] .nav > .active > ul {
+  display: block;
+}
diff --git a/docs/bootstrap-toc.js b/docs/bootstrap-toc.js
new file mode 100644
index 00000000..1cdd573b
--- /dev/null
+++ b/docs/bootstrap-toc.js
@@ -0,0 +1,159 @@
+/*!
+ * Bootstrap Table of Contents v0.4.1 (http://afeld.github.io/bootstrap-toc/)
+ * Copyright 2015 Aidan Feldman
+ * Licensed under MIT (https://github.com/afeld/bootstrap-toc/blob/gh-pages/LICENSE.md) */
+(function() {
+  'use strict';
+
+  window.Toc = {
+    helpers: {
+      // return all matching elements in the set, or their descendants
+      findOrFilter: function($el, selector) {
+        // http://danielnouri.org/notes/2011/03/14/a-jquery-find-that-also-finds-the-root-element/
+        // http://stackoverflow.com/a/12731439/358804
+        var $descendants = $el.find(selector);
+        return $el.filter(selector).add($descendants).filter(':not([data-toc-skip])');
+      },
+
+      generateUniqueIdBase: function(el) {
+        var text = $(el).text();
+        var anchor = text.trim().toLowerCase().replace(/[^A-Za-z0-9]+/g, '-');
+        return anchor || el.tagName.toLowerCase();
+      },
+
+      generateUniqueId: function(el) {
+        var anchorBase = this.generateUniqueIdBase(el);
+        for (var i = 0; ; i++) {
+          var anchor = anchorBase;
+          if (i > 0) {
+            // add suffix
+            anchor += '-' + i;
+          }
+          // check if ID already exists
+          if (!document.getElementById(anchor)) {
+            return anchor;
+          }
+        }
+      },
+
+      generateAnchor: function(el) {
+        if (el.id) {
+          return el.id;
+        } else {
+          var anchor = this.generateUniqueId(el);
+          el.id = anchor;
+          return anchor;
+        }
+      },
+
+      createNavList: function() {
+        return $('');
+      },
+
+      createChildNavList: function($parent) {
+        var $childList = this.createNavList();
+        $parent.append($childList);
+        return $childList;
+      },
+
+      generateNavEl: function(anchor, text) {
+        var $a = $('');
+        $a.attr('href', '#' + anchor);
+        $a.text(text);
+        var $li = $('
  • ');
+        $li.append($a);
+        return $li;
+      },
+
+      generateNavItem: function(headingEl) {
+        var anchor = this.generateAnchor(headingEl);
+        var $heading = $(headingEl);
+        var text = $heading.data('toc-text') || $heading.text();
+        return this.generateNavEl(anchor, text);
+      },
+
+      // Find the first heading level (`
    `, then `
    `, etc.) that has more than one element. Defaults to 1 (for `
    `).
+      getTopLevel: function($scope) {
+        for (var i = 1; i <= 6; i++) {
+          var $headings = this.findOrFilter($scope, 'h' + i);
+          if ($headings.length > 1) {
+            return i;
+          }
+        }
+
+        return 1;
+      },
+
+      // returns the elements for the top level, and the next below it
+      getHeadings: function($scope, topLevel) {
+        var topSelector = 'h' + topLevel;
+
+        var secondaryLevel = topLevel + 1;
+        var secondarySelector = 'h' + secondaryLevel;
+
+        return this.findOrFilter($scope, topSelector + ',' + secondarySelector);
+      },
+
+      getNavLevel: function(el) {
+        return parseInt(el.tagName.charAt(1), 10);
+      },
+
+      populateNav: function($topContext, topLevel, $headings) {
+        var $context = $topContext;
+        var $prevNav;
+
+        var helpers = this;
+        $headings.each(function(i, el) {
+          var $newNav = helpers.generateNavItem(el);
+          var navLevel = helpers.getNavLevel(el);
+
+          // determine the proper $context
+          if (navLevel === topLevel) {
+            // use top level
+            $context = $topContext;
+          } else if ($prevNav && $context === $topContext) {
+            // create a new level of the tree and switch to it
+            $context = helpers.createChildNavList($prevNav);
+          } // else use the current $context
+
+          $context.append($newNav);
+
+          $prevNav = $newNav;
+        });
+      },
+
+      parseOps: function(arg) {
+        var opts;
+        if (arg.jquery) {
+          opts = {
+            $nav: arg
+          };
+        } else {
+          opts = arg;
+        }
+        opts.$scope = opts.$scope || $(document.body);
+        return opts;
+      }
+    },
+
+    // accepts a jQuery object, or an options object
+    init: function(opts) {
+      opts = this.helpers.parseOps(opts);
+
+      // ensure that the data attribute is in place for styling
+      opts.$nav.attr('data-toggle', 'toc');
+
+      var $topContext = this.helpers.createChildNavList(opts.$nav);
+      var topLevel = this.helpers.getTopLevel(opts.$scope);
+      var $headings = this.helpers.getHeadings(opts.$scope, topLevel);
+      this.helpers.populateNav($topContext, topLevel, $headings);
+    }
+  };
+
+  $(function() {
+    $('nav[data-toggle="toc"]').each(function(i, el) {
+      var $nav = $(el);
+      Toc.init($nav);
+    });
+  });
+})();
diff --git a/docs/index.html b/docs/index.html
index 763ab389..0426f362 100644
--- a/docs/index.html
+++ b/docs/index.html
@@ -6,19 +6,19 @@
 
 
 Create Interactive Graphics Related to Clinical Trial Safety • safetyGraphics
-
-
-
-
+
+
+
+
+
 
 
-
 
 
-
+
     
    
       
    
   
    
 
-
-
    
+
     R build status 
    
+
    
 
    
-safetyGraphics: Clinical Trial Safety Graphics with R 
+safetyGraphics: Clinical Trial Monitoring with R 
 
    
-
    The safetyGraphics package provides a framework for evaluation of clinical trial safety in R. It includes several safety-focused visualizations to empower clinical data monitoring. Chief among these is the Hepatic Explorer, based on the Evaluation of the Drug-Induced Serious Hepatotoxicity (eDish) visualization. A demo of the Hepatic Explorer interactive graphic is available here and is shown below.
    
-
    This package is being built in conjunction with the hep-explorer javascript library.
    
+
    The {safetyGraphics} package provides a framework for the evaluation of clinical trial safety data in R using a flexible data pipeline. The package includes a shiny application that allows users to explore safety data using a series of interactive graphics, including the hepatic safety explorer shown below. The package has been developed as part of the Interactive Safety Graphics (ISG) workstream of the ASA Biopharm-DIA Safety Working Group.
    
 
    edishgif
    
-
    
+
    
 
    
-Usage
    
-
    Users can interactively explore their data with a shiny application or create standalone interactive charts.
    
-
    
-
    
-Shiny application
    
-
    The Shiny app provides a simple interface for:
    
-
      
-
    • Loading data
      • 
-
    • Customizing settings and data mappings
      • 
-
    • Viewing and exporting the interactive graphics
      • 
-
    
-
    devtools::install_github("SafetyGraphics/safetyGraphics")
-library("safetyGraphics")
-safetyGraphicsApp() #open the shiny application
    
-
    
-
    
-
    
-Standalone charts
    
-
    Users can also initialize customized standalone charts with a few lines of code.
    
-
    devtools::install_github("safetyGraphics/safetyGraphics")
-library("safetyGraphics")
-
-settings <- list(
-  id_col = "USUBJID",
-  value_col = "AVAL",
-  measure_col = "PARAM",
-  visit_col = "VISIT",
-  visitn_col = "VISITNUM",
-  studyday_col = "ADY",
-  normal_col_low = "A1LO",
-  normal_col_high = "A1HI",
-  measure_values = list(ALT = "Alanine Aminotransferase (U/L)",
-                        AST = "Aspartate Aminotransferase (U/L)",
-                        TB = "Bilirubin (umol/L)",
-                        ALP = "Alkaline Phosphatase (U/L)")
-  )
-
-chartRenderer(data=adlbc, settings=settings, chart="hepexplorer")
    
+Using the app
    
+
    A demo of the app using sample data is available here or can be initialized as follows:
    
+
    +devtools::install_github("SafetyGraphics/safetyGraphics")
+library("safetyGraphics")
+safetyGraphicsApp() #open the shiny application
    
+
    The most common workflow is for a user to initialize the app with their data, adjust settings as needed, and view the interactive charts. Finally, the user can share any chart by exporting its source code or by generating a self-contained, fully reproducible report that can be shared with others.
    
+
    Instructions for loading study data are provided in the introductory vignette and more complex customizations are provided in the cookbook vignette.
    
 
 
+
    
+
    
+Charts
    
+
    The app is built to support a wide variety of chart types including static plots (e.g. from {ggplot2}), shiny modules, {htmlwidgets} and even static outputs like RTFs. Several pre-configured charts are included in the companion {safetyCharts} R Package, and are available by default in the app. Other charts can be added using the process descibed in this vignette.
    
 
    
 
   
 
-  
 
 
 
       
    
-  
    Developed by Jeremy Wildfire, Becca Krouse, Preston Burns, Xiao Ni, James Buchanan, Susan Duke, Interactive Safety Graphics Working Group.
    
+  
    Developed by Jeremy Wildfire, Becca Krouse, Preston Burns, Xiao Ni, James Buchanan, Susan Duke.
    
 
    
 
 
    
-  
    Site built with pkgdown 1.4.1.
    
+  
    Site built with pkgdown 1.6.1.
    
 
    
 
       
    
diff --git a/docs/news/index.html b/docs/news/index.html
index ce95a77e..5868715f 100644
--- a/docs/news/index.html
+++ b/docs/news/index.html
@@ -8,23 +8,29 @@
 
 Changelog • safetyGraphics
 
+
 
-
+
 
-
+
+
 
-
+
+
+
+
+
 
 
-
-
+
+
 
 
-
+
 
 
-
-
+
+
 
 
 
@@ -32,10 +38,12 @@
 
 
 
+
 
 
 
 
+
 
 
 
@@ -49,7 +57,7 @@
 
   
 
-  
+  
     
    
       
    
       
 
@@ -71,33 +79,38 @@
       
-      
       
      
         
    • 
   
@@ -118,40 +131,35 @@
 
      
   
      
     
      
-      
      Changelog 
      
+      
      Changelog 
      
       Source:       NEWS.md
     
      
 
-    
      
-
      
-safetyGraphics v1.1.0 Unreleased 
+    
      
+
      
+safetyGraphics v1.1.0 2020-01-15 
 
      
 
      Allows users to preload their own charts and data sets for use in the safetyGraphics Shiny Application. See the “Custom Workflows” Vignette for details and examples.
      
 
      
-    
      
-
      
-safetyGraphics v1.0.0 2019-06-14 
+    
      
+
      
+safetyGraphics v1.0.0 2019-06-14 
 
      
 
      The first production release of safetyGraphics includes many improvements including the addition of 5 new interactive graphics and an embedded help page with a detailed clinical workflow for using the tool.
      
 
      
-    
      
-
      
-safetyGraphics v0.7.3 2019-02-04 
+    
      
+
      
+safetyGraphics v0.7.3 2019-02-04 
 
      
 
      Initial CRAN release for safetyGraphics. The safetyGraphics package provides framework for evaluation of clinical trial safety. Users can interactively explore their data using the ‘Shiny’ application or create standalone ‘htmlwidget’ charts. Interactive charts are built using ‘d3.js’ and ‘webcharts.js’ ‘JavaScript’ libraries.
      
 
      See the GitHub release tracker for additional release documentation and links to issues.
      
 
      
   
      
 
-  
@@ -159,11 +167,11 @@ 
      Contents
      
 
       
      
       
      
-  
      Developed by Jeremy Wildfire, Becca Krouse, Preston Burns, Xiao Ni, James Buchanan, Susan Duke, Interactive Safety Graphics Working Group.
      
+  
      Developed by Jeremy Wildfire, Becca Krouse, Preston Burns, Xiao Ni, James Buchanan, Susan Duke.
      
 
      
 
 
      
-  
      Site built with pkgdown 1.4.1.
      
+  
      Site built with pkgdown 1.6.1.
      
 
      
 
       
      
diff --git a/docs/pkgdown.css b/docs/pkgdown.css
index 91459581..1273238d 100644
--- a/docs/pkgdown.css
+++ b/docs/pkgdown.css
@@ -17,6 +17,10 @@ html, body {
   height: 100%;
 }
 
+body {
+  position: relative;
+}
+
 body > .container {
   display: flex;
   height: 100%;
@@ -67,6 +71,10 @@ summary {
   margin-top: calc(-60px + 1em);
 }
 
+dd {
+  margin-left: 3em;
+}
+
 /* Section anchors ---------------------------------*/
 
 a.anchor {
@@ -100,29 +108,132 @@ a.anchor {
   margin-top: -40px;
 }
 
+/* Navbar submenu --------------------------*/
+
+.dropdown-submenu {
+  position: relative;
+}
+
+.dropdown-submenu>.dropdown-menu {
+  top: 0;
+  left: 100%;
+  margin-top: -6px;
+  margin-left: -1px;
+  border-radius: 0 6px 6px 6px;
+}
+
+.dropdown-submenu:hover>.dropdown-menu {
+  display: block;
+}
+
+.dropdown-submenu>a:after {
+  display: block;
+  content: " ";
+  float: right;
+  width: 0;
+  height: 0;
+  border-color: transparent;
+  border-style: solid;
+  border-width: 5px 0 5px 5px;
+  border-left-color: #cccccc;
+  margin-top: 5px;
+  margin-right: -10px;
+}
+
+.dropdown-submenu:hover>a:after {
+  border-left-color: #ffffff;
+}
+
+.dropdown-submenu.pull-left {
+  float: none;
+}
+
+.dropdown-submenu.pull-left>.dropdown-menu {
+  left: -100%;
+  margin-left: 10px;
+  border-radius: 6px 0 6px 6px;
+}
+
 /* Sidebar --------------------------*/
 
-#sidebar {
+#pkgdown-sidebar {
   margin-top: 30px;
   position: -webkit-sticky;
   position: sticky;
   top: 70px;
 }
-#sidebar h2 {
+
+#pkgdown-sidebar h2 {
   font-size: 1.5em;
   margin-top: 1em;
 }
 
-#sidebar h2:first-child {
+#pkgdown-sidebar h2:first-child {
   margin-top: 0;
 }
 
-#sidebar .list-unstyled li {
+#pkgdown-sidebar .list-unstyled li {
   margin-bottom: 0.5em;
 }
 
+/* bootstrap-toc tweaks ------------------------------------------------------*/
+
+/* All levels of nav */
+
+nav[data-toggle='toc'] .nav > li > a {
+  padding: 4px 20px 4px 6px;
+  font-size: 1.5rem;
+  font-weight: 400;
+  color: inherit;
+}
+
+nav[data-toggle='toc'] .nav > li > a:hover,
+nav[data-toggle='toc'] .nav > li > a:focus {
+  padding-left: 5px;
+  color: inherit;
+  border-left: 1px solid #878787;
+}
+
+nav[data-toggle='toc'] .nav > .active > a,
+nav[data-toggle='toc'] .nav > .active:hover > a,
+nav[data-toggle='toc'] .nav > .active:focus > a {
+  padding-left: 5px;
+  font-size: 1.5rem;
+  font-weight: 400;
+  color: inherit;
+  border-left: 2px solid #878787;
+}
+
+/* Nav: second level (shown on .active) */
+
+nav[data-toggle='toc'] .nav .nav {
+  display: none; /* Hide by default, but at >768px, show it */
+  padding-bottom: 10px;
+}
+
+nav[data-toggle='toc'] .nav .nav > li > a {
+  padding-left: 16px;
+  font-size: 1.35rem;
+}
+
+nav[data-toggle='toc'] .nav .nav > li > a:hover,
+nav[data-toggle='toc'] .nav .nav > li > a:focus {
+  padding-left: 15px;
+}
+
+nav[data-toggle='toc'] .nav .nav > .active > a,
+nav[data-toggle='toc'] .nav .nav > .active:hover > a,
+nav[data-toggle='toc'] .nav .nav > .active:focus > a {
+  padding-left: 15px;
+  font-weight: 500;
+  font-size: 1.35rem;
+}
+
+/* orcid ------------------------------------------------------------------- */
+
 .orcid {
-  height: 16px;
+  font-size: 16px;
+  color: #A6CE39;
   /* margins are required by official ORCID trademark and display guidelines */
   margin-left:4px;
   margin-right:4px;
@@ -133,14 +244,14 @@ a.anchor {
 
 .ref-index th {font-weight: normal;}
 
-.ref-index td {vertical-align: top;}
+.ref-index td {vertical-align: top; min-width: 100px}
 .ref-index .icon {width: 40px;}
 .ref-index .alias {width: 40%;}
 .ref-index-icons .alias {width: calc(40% - 40px);}
 .ref-index .title {width: 60%;}
 
 .ref-arguments th {text-align: right; padding-right: 10px;}
-.ref-arguments th, .ref-arguments td {vertical-align: top;}
+.ref-arguments th, .ref-arguments td {vertical-align: top; min-width: 100px}
 .ref-arguments .name {width: 20%;}
 .ref-arguments .desc {width: 80%;}
 
diff --git a/docs/pkgdown.js b/docs/pkgdown.js
index 087a7622..7e7048fa 100644
--- a/docs/pkgdown.js
+++ b/docs/pkgdown.js
@@ -9,11 +9,6 @@
       $('body').css('padding-top', $('.navbar').height() + 10);
     });
 
-    $('body').scrollspy({
-      target: '#sidebar',
-      offset: 60
-    });
-
     $('[data-toggle="tooltip"]').tooltip();
 
     var cur_path = paths(location.pathname);
diff --git a/docs/pkgdown.yml b/docs/pkgdown.yml
index 77d3565c..85efbfd2 100644
--- a/docs/pkgdown.yml
+++ b/docs/pkgdown.yml
@@ -1,9 +1,12 @@
-pandoc: 1.19.2.1
-pkgdown: 1.4.1
+pandoc: 2.11.2
+pkgdown: 1.6.1
 pkgdown_sha: ~
 articles:
-  customWorkflows: customWorkflows.html
-  shinyUserGuide: shinyUserGuide.html
+  Cookbook: Cookbook.html
+  TechnicalFAQ: TechnicalFAQ.html
+  chartConfiguration: chartConfiguration.html
+  intro: intro.html
+last_built: 2021-09-03T01:15Z
 urls:
   reference: https://pages.github.com/SafetyGraphics/safetyGraphics/reference
   article: https://pages.github.com/SafetyGraphics/safetyGraphics/articles
diff --git a/docs/reference/Rplot001.png b/docs/reference/Rplot001.png
new file mode 100644
index 00000000..17a35806
Binary files /dev/null and b/docs/reference/Rplot001.png differ
diff --git a/docs/reference/SafetyGraphics.html b/docs/reference/SafetyGraphics.html
index 5d827173..4a6f339e 100644
--- a/docs/reference/SafetyGraphics.html
+++ b/docs/reference/SafetyGraphics.html
@@ -6,25 +6,31 @@
 
 
 
-<code>safetyGraphics</code> package — SafetyGraphics • safetyGraphics
+safetyGraphics package — SafetyGraphics • safetyGraphics
+
 
 
-
+
 
-
+
+
+
+
 
-
+
+
+
 
 
-
-
+
+
 
 
-
+
 
 
-
-
+
+
 
 
 
@@ -32,10 +38,10 @@
 
 
 
-
 
+
 
-
+
 
 
 
@@ -52,7 +58,7 @@
 
   
 
-  
+  
     
      
       
      
       
 
@@ -74,33 +80,38 @@
       
-      
       
      
 
     
      
-    
     
      Create Interactive Graphics Related to Clinical Trial Safety
      
-    
     
      
 
-        
+
+
     
      Details
      
 
     
      Learn more on
 CRAN
 or GitHub
      
-    
 
   
      
-  
 
 
       
      
       
      
-  
      Developed by Jeremy Wildfire, Becca Krouse, Preston Burns, Xiao Ni, James Buchanan, Susan Duke, Interactive Safety Graphics Working Group.
      
+  
      Developed by Jeremy Wildfire, Becca Krouse, Preston Burns, Xiao Ni, James Buchanan, Susan Duke.
      
 
      
 
 
      
-  
      Site built with pkgdown 1.4.1.
      
+  
      Site built with pkgdown 1.6.1.
      
 
      
 
       
      
diff --git a/docs/reference/app_startup.html b/docs/reference/app_startup.html
new file mode 100644
index 00000000..0eb19c8b
--- /dev/null
+++ b/docs/reference/app_startup.html
@@ -0,0 +1,225 @@
+
+
+
+  
+  
+
+
+
+Startup code for shiny app — app_startup • safetyGraphics
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+  
+
+  
+    
      
+      
      
+      
+
+      
+
+      
      
+
+
      
+  
      
+    
      
+    
      Startup code for shiny app
      
+    Source: R/app_startup.R
+    
+    
      
+
+    
      
+    
      Prepare inputs for safetyGraphics app - run before app is initialized.
      
+    
      
+
+    
      app_startup(
+  domainData = NULL,
+  meta = NULL,
+  charts = NULL,
+  mapping = NULL,
+  autoMapping = NULL,
+  filterDomain = NULL,
+  chartSettingsPaths = NULL
+)
      
+
+    
      Arguments
      
+    
+    
+    
+      
+      
+    
+    
+      
+      
+    
+    
+      
+      
+    
+    
+      
+      
+    
+    
+      
+      
+    
+    
+      
+      
+    
+    
+      
+      
+    
+    
      domainData
      named list of data.frames to be loaded in to the app. Sample AdAM data from the safetyData package used by default
      meta
      data frame containing the metadata for use in the app. See the preloaded file (?safetyGraphics::meta) for more data specifications and details. Defaults to safetyGraphics::meta.
      charts
      list of charts in the format produced by safetyGraphics::makeChartConfig()
      mapping
      list specifying the initial mapping values for each data mapping for each domain (e.g. list(aes= list(id_col='USUBJID', seq_col='AESEQ')).
      autoMapping
      boolean indicating whether the app should attempt to automatically detect data standards and generate mappings for the data provided. Values specified in the mapping parameter overwrite automatically generated mappings when both are found. Defaults to true.
      filterDomain
      domain used for the data/filter tab. Demographics ("dm") is used by default. Using a domain that is not one record per participant is not recommended.
      chartSettingsPaths
      path(s) where customization functions are saved relative to your working directory. All charts can have itialization (e.g. myChart_Init.R) and static charts can have charting functions (e.g. myGraphic_Chart.R).   All R files in this folder are sourced and files with the correct naming convention are linked to the chart. See the Custom Charts vignette for more details.
      
+
+    
      Value
      
+
+    
      List of elements for used to initialize the shiny app with the following parameters
        
+
      • "meta" List of configuration metadata
        • 
+
      • "charts" List of charts
        • 
+
      • "domainData" List of domain level data sets
        • 
+
      • "mapping" Initial Data Mapping
        • 
+
      • "standards" List of domain level data standards
        • 
+
      
+
+
+  
      
+  
+
      
+
+
+      
      
+      
      
+  
      Developed by Jeremy Wildfire, Becca Krouse, Preston Burns, Xiao Ni, James Buchanan, Susan Duke.
      
+
      
+
+
      
+  
      Site built with pkgdown 1.6.1.
      
+
      
+
+      
      
+   
      
+
+  
+
+
+  
+
+
+
diff --git a/docs/reference/chartsNav.html b/docs/reference/chartsNav.html
new file mode 100644
index 00000000..0db9f9c7
--- /dev/null
+++ b/docs/reference/chartsNav.html
@@ -0,0 +1,187 @@
+
+
+
+  
+  
+
+
+
+Adds a navbar tab that initializes the Chart Module UI — chartsNav • safetyGraphics
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+  
+
+  
+    
      
+      
      
+      
+
+      
+
+      
      
+
+
      
+  
      
+    
      
+    
      Adds a navbar tab that initializes the Chart Module UI
      
+    Source: R/mod_chartsNav.R
+    
+    
      
+
+    
      
+    
      Adds a navbar tab that initializes the Chart Module UI
      
+    
      
+
+    
      chartsNav(chart, ns)
      
+
+    
      Arguments
      
+    
+    
+    
+      
+      
+    
+    
+      
+      
+    
+    
      chart
      chart metadata
      ns
      namespace
      
+
+
+  
      
+  
+
      
+
+
+      
      
+      
      
+  
      Developed by Jeremy Wildfire, Becca Krouse, Preston Burns, Xiao Ni, James Buchanan, Susan Duke.
      
+
      
+
+
      
+  
      Site built with pkgdown 1.6.1.
      
+
      
+
+      
      
+   
      
+
+  
+
+
+  
+
+
+
diff --git a/docs/reference/chartsTab.html b/docs/reference/chartsTab.html
new file mode 100644
index 00000000..0cd37585
--- /dev/null
+++ b/docs/reference/chartsTab.html
@@ -0,0 +1,203 @@
+
+
+
+  
+  
+
+
+
+Server for chart module, designed to be re-used for each chart generated. — chartsTab • safetyGraphics
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+  
+
+  
+    
      
+      
      
+      
+
+      
+
+      
      
+
+
      
+  
      
+    
      
+    
      Server for chart module, designed to be re-used for each chart generated.
      
+    Source: R/mod_chartsTab.R
+    
+    
      
+
+    
      
+    
      Server for chart module, designed to be re-used for each chart generated.
      
+    
      
+
+    
      chartsTab(input, output, session, chart, data, mapping)
      
+
+    
      Arguments
      
+    
+    
+    
+      
+      
+    
+    
+      
+      
+    
+    
+      
+      
+    
+    
+      
+      
+    
+    
+      
+      
+    
+    
+      
+      
+    
+    
      input
      Input objects from module namespace
      output
      Output objects from module namespace
      session
      An environment that can be used to access information and functionality relating to the session
      chart
      list containing a safetyGraphics chart object like those returned by makeChartConfig.
      data
      named list of current data sets (Reactive).
      mapping
      tibble capturing the current data mappings (Reactive).
      
+
+
+  
      
+  
+
      
+
+
+      
      
+      
      
+  
      Developed by Jeremy Wildfire, Becca Krouse, Preston Burns, Xiao Ni, James Buchanan, Susan Duke.
      
+
      
+
+
      
+  
      Site built with pkgdown 1.6.1.
      
+
      
+
+      
      
+   
      
+
+  
+
+
+  
+
+
+
diff --git a/docs/reference/chartsTabUI.html b/docs/reference/chartsTabUI.html
new file mode 100644
index 00000000..35138e28
--- /dev/null
+++ b/docs/reference/chartsTabUI.html
@@ -0,0 +1,187 @@
+
+
+
+  
+  
+
+
+
+UI for chart module, designed to be re-used for each chart generated. — chartsTabUI • safetyGraphics
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+  
+
+  
+    
      
+      
      
+      
+
+      
+
+      
      
+
+
      
+  
      
+    
      
+    
      UI for chart module, designed to be re-used for each chart generated.
      
+    Source: R/mod_chartsTab.R
+    
+    
      
+
+    
      
+    
      UI for chart module, designed to be re-used for each chart generated.
      
+    
      
+
+    
      chartsTabUI(id, chart)
      
+
+    
      Arguments
      
+    
+    
+    
+      
+      
+    
+    
+      
+      
+    
+    
      id
      module id
      chart
      list containing chart specifications like those returned by makeChartConfig.
      
+
+
+  
      
+  
+
      
+
+
+      
      
+      
      
+  
      Developed by Jeremy Wildfire, Becca Krouse, Preston Burns, Xiao Ni, James Buchanan, Susan Duke.
      
+
      
+
+
      
+  
      Site built with pkgdown 1.6.1.
      
+
      
+
+      
      
+   
      
+
+  
+
+
+  
+
+
+
diff --git a/docs/reference/detectStandard.html b/docs/reference/detectStandard.html
index 69bbc0a3..a4353dd4 100644
--- a/docs/reference/detectStandard.html
+++ b/docs/reference/detectStandard.html
@@ -8,23 +8,29 @@
 
 Detect the data standard used for a data set — detectStandard • safetyGraphics
 
+
 
-
+
 
-
+
+
+
+
 
-
+
+
+
 
 
-
-
+
+
 
 
-
+
 
 
-
-
+
+
 
 
 
@@ -32,10 +38,10 @@
 
 
 
-
 
+
 
-
+
 
 
 
@@ -52,7 +58,7 @@
 
   
 
-  
+  
     
      
       
      
       
 
@@ -74,33 +80,38 @@
       
-      
       
      
 
     
      
-    
     
      This function attempts to detect the clinical data standard used in a given R data frame.
      
-    
     
      
 
-    
      detectStandard(data, includeFields = TRUE, domain = "labs")
      
-    
+    
      detectStandard(data, domain = NULL, meta = safetyGraphics::meta)
      
+
     
      Arguments
      
     
-      
+      
-      
-      
+      
+      
-      
-      
+      
+      
      
     
     
      
       data
      A data frame in which to detect the data standard
      A data frame in which to detect the data standard - required.
      		
     
      
     
      includeFields
      specifies whether to check the data set for field level data in addition to columns.  Default: TRUE.
      		domain
      the domain to evaluate - should match a value of meta$domain. Uses the first value in meta$domain if no value is provided.
      		
     
      
     
      domain
      The data domain for the data set provided.  Default: "labs".
      		meta
      the metadata containing the data standards. - default = safetyGraphics::meta
      		
     
      
     
      
-    
+
     
      Value
      
 
-    
      A list containing the matching "standard" from "standardMetadata" and a list of  "details" describing each standard considered.
      
-    
+    
      A data frame describing the detected standard for each "text_key" in the provided metadata. Columns are "domain", "text_key", "column" and "standard".
      
     
      Details
      
 
-    
      This function compares the columns in the provided "data" with the required columns for a given data standard/domain combination. The function is designed to work with the SDTM and ADaM CDISC(<https://www.cdisc.org/>) standards for clinical trial data by default. Additional standards can be added by modifying the "standardMetadata" data set included as part of this package. Currently, "labs" is the only domain supported.
      
-    
+    
      This function compares the columns in the provided "data" with the required columns for a given data standard/domain combination. The function is designed to work with the SDTM and ADaM CDISC(https://www.cdisc.org/) standards for clinical trial data by default. Additional standards can be added by modifying the "meta" data set included as part of this package.
      
 
     
      Examples
      
-    
      detectStandard(adlbc)[["standard"]] #adam
      #> [1] "adam"
      detectStandard(iris)[["standard"]] #none
      #> [1] "none"
      
-if (FALSE) {
-  detectStandard(adlbc,domain="AE") #throws error. AE domain not supported in this release.
-}
      
+    
      detectStandard(data=safetyData::adam_adae)  #aes domain evaluated by default
+
      #> $details
+#> $details$adam
+#> $details$adam$standard
+#> [1] "adam"
+#> 
+#> $details$adam$mapping
+#> # A tibble: 6 × 3
+#> # Rowwise: 
+#>   text_key   current  valid
+#>   <chr>      <chr>    <lgl>
+#> 1 id_col     USUBJID  TRUE 
+#> 2 seq_col    AESEQ    TRUE 
+#> 3 stdy_col   ASTDY    TRUE 
+#> 4 endy_col   AENDY    TRUE 
+#> 5 term_col   AETERM   TRUE 
+#> 6 bodsys_col AEBODSYS TRUE 
+#> 
+#> $details$adam$total_count
+#> [1] 6
+#> 
+#> $details$adam$valid_count
+#> [1] 6
+#> 
+#> $details$adam$invalid_count
+#> [1] 0
+#> 
+#> $details$adam$match_percent
+#> [1] 1
+#> 
+#> $details$adam$match
+#> [1] "full"
+#> 
+#> $details$adam$label
+#> [1] "ADaM"
+#> 
+#> 
+#> $details$sdtm
+#> $details$sdtm$standard
+#> [1] "sdtm"
+#> 
+#> $details$sdtm$mapping
+#> # A tibble: 6 × 3
+#> # Rowwise: 
+#>   text_key   current  valid
+#>   <chr>      <chr>    <lgl>
+#> 1 id_col     USUBJID  TRUE 
+#> 2 seq_col    AESEQ    TRUE 
+#> 3 stdy_col   NA       FALSE
+#> 4 endy_col   NA       FALSE
+#> 5 term_col   AETERM   TRUE 
+#> 6 bodsys_col AEBODSYS TRUE 
+#> 
+#> $details$sdtm$total_count
+#> [1] 6
+#> 
+#> $details$sdtm$valid_count
+#> [1] 4
+#> 
+#> $details$sdtm$invalid_count
+#> [1] 2
+#> 
+#> $details$sdtm$match_percent
+#> [1] 0.6666667
+#> 
+#> $details$sdtm$match
+#> [1] "partial"
+#> 
+#> $details$sdtm$label
+#> [1] "Partial SDTM"
+#> 
+#> $details$sdtm$details
+#> [1] "(4/6 cols/fields matched)"
+#> 
+#> 
+#> 
+#> $standard
+#> [1] "adam"
+#> 
+#> $label
+#> [1] "ADaM"
+#> 
+#> $standard_percent
+#> [1] 1
+#> 
+#> $mapping
+#> # A tibble: 6 × 3
+#> # Rowwise: 
+#>   text_key   current  valid
+#>   <chr>      <chr>    <lgl>
+#> 1 id_col     USUBJID  TRUE 
+#> 2 seq_col    AESEQ    TRUE 
+#> 3 stdy_col   ASTDY    TRUE 
+#> 4 endy_col   AENDY    TRUE 
+#> 5 term_col   AETERM   TRUE 
+#> 6 bodsys_col AEBODSYS TRUE 
+#> 
      detectStandard(data=safetyData::adam_adlbc,domain="labs" ) 
+
      #> $details
+#> $details$adam
+#> $details$adam$standard
+#> [1] "adam"
+#> 
+#> $details$adam$mapping
+#> # A tibble: 12 × 3
+#> # Rowwise: 
+#>    text_key            current                          valid
+#>    <chr>               <chr>                            <lgl>
+#>  1 id_col              USUBJID                          TRUE 
+#>  2 value_col           AVAL                             TRUE 
+#>  3 measure_col         PARAM                            TRUE 
+#>  4 normal_col_low      A1LO                             TRUE 
+#>  5 normal_col_high     A1HI                             TRUE 
+#>  6 studyday_col        ADY                              TRUE 
+#>  7 visit_col           VISIT                            TRUE 
+#>  8 visitn_col          VISITNUM                         TRUE 
+#>  9 measure_values--ALT Alanine Aminotransferase (U/L)   TRUE 
+#> 10 measure_values--AST Aspartate Aminotransferase (U/L) TRUE 
+#> 11 measure_values--TB  Bilirubin (umol/L)               TRUE 
+#> 12 measure_values--ALP Alkaline Phosphatase (U/L)       TRUE 
+#> 
+#> $details$adam$total_count
+#> [1] 12
+#> 
+#> $details$adam$valid_count
+#> [1] 12
+#> 
+#> $details$adam$invalid_count
+#> [1] 0
+#> 
+#> $details$adam$match_percent
+#> [1] 1
+#> 
+#> $details$adam$match
+#> [1] "full"
+#> 
+#> $details$adam$label
+#> [1] "ADaM"
+#> 
+#> 
+#> $details$sdtm
+#> $details$sdtm$standard
+#> [1] "sdtm"
+#> 
+#> $details$sdtm$mapping
+#> # A tibble: 13 × 3
+#> # Rowwise: 
+#>    text_key            current  valid
+#>    <chr>               <chr>    <lgl>
+#>  1 id_col              USUBJID  TRUE 
+#>  2 value_col           LBSTRESN TRUE 
+#>  3 measure_col         NA       FALSE
+#>  4 normal_col_low      NA       FALSE
+#>  5 normal_col_high     NA       FALSE
+#>  6 studyday_col        NA       FALSE
+#>  7 visit_col           VISIT    TRUE 
+#>  8 visitn_col          VISITNUM TRUE 
+#>  9 measure_values--ALT NA       FALSE
+#> 10 measure_values--AST NA       FALSE
+#> 11 measure_values--TB  NA       FALSE
+#> 12 measure_values--ALP NA       FALSE
+#> 13 unit_col            NA       FALSE
+#> 
+#> $details$sdtm$total_count
+#> [1] 13
+#> 
+#> $details$sdtm$valid_count
+#> [1] 4
+#> 
+#> $details$sdtm$invalid_count
+#> [1] 9
+#> 
+#> $details$sdtm$match_percent
+#> [1] 0.3076923
+#> 
+#> $details$sdtm$match
+#> [1] "partial"
+#> 
+#> $details$sdtm$label
+#> [1] "Partial SDTM"
+#> 
+#> $details$sdtm$details
+#> [1] "(4/13 cols/fields matched)"
+#> 
+#> 
+#> 
+#> $standard
+#> [1] "adam"
+#> 
+#> $label
+#> [1] "ADaM"
+#> 
+#> $standard_percent
+#> [1] 1
+#> 
+#> $mapping
+#> # A tibble: 12 × 3
+#> # Rowwise: 
+#>    text_key            current                          valid
+#>    <chr>               <chr>                            <lgl>
+#>  1 id_col              USUBJID                          TRUE 
+#>  2 value_col           AVAL                             TRUE 
+#>  3 measure_col         PARAM                            TRUE 
+#>  4 normal_col_low      A1LO                             TRUE 
+#>  5 normal_col_high     A1HI                             TRUE 
+#>  6 studyday_col        ADY                              TRUE 
+#>  7 visit_col           VISIT                            TRUE 
+#>  8 visitn_col          VISITNUM                         TRUE 
+#>  9 measure_values--ALT Alanine Aminotransferase (U/L)   TRUE 
+#> 10 measure_values--AST Aspartate Aminotransferase (U/L) TRUE 
+#> 11 measure_values--TB  Bilirubin (umol/L)               TRUE 
+#> 12 measure_values--ALP Alkaline Phosphatase (U/L)       TRUE 
+#> 
      
+
      
   
      
-  
 
 
       
      
       
      
-  
      Developed by Jeremy Wildfire, Becca Krouse, Preston Burns, Xiao Ni, James Buchanan, Susan Duke, Interactive Safety Graphics Working Group.
      
+  
      Developed by Jeremy Wildfire, Becca Krouse, Preston Burns, Xiao Ni, James Buchanan, Susan Duke.
      
 
      
 
 
      
-  
      Site built with pkgdown 1.4.1.
      
+  
      Site built with pkgdown 1.6.1.
      
 
      
 
       
      
diff --git a/docs/reference/evaluateStandard.html b/docs/reference/evaluateStandard.html
index aa5d8108..a645811e 100644
--- a/docs/reference/evaluateStandard.html
+++ b/docs/reference/evaluateStandard.html
@@ -8,23 +8,29 @@
 
 Evaluate a data set against a data standard — evaluateStandard • safetyGraphics
 
+
 
-
+
 
-
+
+
+
+
 
-
+
+
+
 
 
-
-
+
+
 
 
-
+
 
 
-
-
+
+
 
 
 
@@ -32,10 +38,10 @@
 
 
 
-
 
+
 
-
+
 
 
 
@@ -52,7 +58,7 @@
 
   
 
-  
+  
     
      
       
      
       
 
@@ -74,33 +80,38 @@
       
-      
       
      
 
     
      
-    
     
      Determines whether the required data elements in a data standard are found in a given data frame
      
-    
     
      
 
-    
      evaluateStandard(data, standard, includeFields = TRUE, domain = "labs")
      
-    
+    
      evaluateStandard(data, meta, domain, standard)
      
+
     
      Arguments
      
     
-      
+      
-      
-      
+      
+      
-      
-      
+      
+      
-      
-      
+      
+      
      
     
     
      
       data
      data.frame to evaluate
      A data frame in which to detect the data standard
      		
     
      
     
      standard
      standard to evaluate
      		meta
      the metadata containing the data standards.
      		
     
      
     
      includeFields
      should field level data be evaluated?
      		domain
      the domain to evaluate - should match a value of meta$domain
      		
     
      
     
      domain
      data domain. "labs" only for now.
      		standard
      standard to evaluate
      		
     
      
     
      
-    
+
     
      Value
      
 
-    
      a list describing to what degree the data set matches the data standard. The "match" property describes compliance with the standard as "full", "partial" or "none". The "checks" property is a list of the data elements expected for the standard and whether they are "valid" in the given data set. "total_checks", "valid_checks" and "invalid_checks" provide counts of the specified checks. "match_percent" is calculated as valid_checks/total_checks.
      
-    
+    
      a list describing to what degree the data set matches the data standard. The "match" property describes compliance with the standard as "full", "partial" or "none". The "checks" property is a list of the data elements expected for the standard and whether they are "valid" in the given data set. "total_checks", "valid_checks" and "invalid_checks" provide counts of the specified checks. "match_percent" is calculated as valid_checks/total_checks.  "mapping" is a data frame describing the detected standard for each "text_key" in the provided metadata. Columns are "text_key", "current" containing the name of the matched column or field value in the data and "match" a boolean indicating whether the data matches the standard.
      
 
     
      Examples
      
-    
      safetyGraphics:::evaluateStandard(data=adlbc, standard="adam") # Match is TRUE
      #> $standard
+    
      # Match is TRUE
+evaluateStandard(
+ data=safetyData::adam_adlbc, 
+ meta=meta, 
+ domain="labs", 
+ standard="adam"
+) 
+
      #> $standard
 #> [1] "adam"
 #> 
-#> $checks
-#> Source: local data frame [12 x 4]
-#> Groups: <by row>
-#> 
-#> # A tibble: 12 x 4
-#>    text_key            standard_val                     type   valid
-#>    <chr>               <chr>                            <chr>  <lgl>
-#>  1 id_col              USUBJID                          column TRUE 
-#>  2 value_col           AVAL                             column TRUE 
-#>  3 measure_col         PARAM                            column TRUE 
-#>  4 measure_values--ALT Alanine Aminotransferase (U/L)   field  TRUE 
-#>  5 measure_values--AST Aspartate Aminotransferase (U/L) field  TRUE 
-#>  6 measure_values--TB  Bilirubin (umol/L)               field  TRUE 
-#>  7 measure_values--ALP Alkaline Phosphatase (U/L)       field  TRUE 
-#>  8 normal_col_low      A1LO                             column TRUE 
-#>  9 normal_col_high     A1HI                             column TRUE 
-#> 10 studyday_col        ADY                              column TRUE 
-#> 11 visit_col           VISIT                            column TRUE 
-#> 12 visitn_col          VISITNUM                         column TRUE 
+#> $mapping
+#> # A tibble: 12 × 3
+#> # Rowwise: 
+#>    text_key            current                          valid
+#>    <chr>               <chr>                            <lgl>
+#>  1 id_col              USUBJID                          TRUE 
+#>  2 value_col           AVAL                             TRUE 
+#>  3 measure_col         PARAM                            TRUE 
+#>  4 normal_col_low      A1LO                             TRUE 
+#>  5 normal_col_high     A1HI                             TRUE 
+#>  6 studyday_col        ADY                              TRUE 
+#>  7 visit_col           VISIT                            TRUE 
+#>  8 visitn_col          VISITNUM                         TRUE 
+#>  9 measure_values--ALT Alanine Aminotransferase (U/L)   TRUE 
+#> 10 measure_values--AST Aspartate Aminotransferase (U/L) TRUE 
+#> 11 measure_values--TB  Bilirubin (umol/L)               TRUE 
+#> 12 measure_values--ALP Alkaline Phosphatase (U/L)       TRUE 
 #> 
 #> $total_count
 #> [1] 12
@@ -198,67 +211,77 @@ 
      Examp
 #> 
 #> $match
 #> [1] "full"
-#> 
      safetyGraphics:::evaluateStandard(data=adlbc, standard="sdtm") # Match is FALSE
      #> $standard
-#> [1] "sdtm"
 #> 
-#> $checks
-#> Source: local data frame [12 x 4]
-#> Groups: <by row>
+#> $label
+#> [1] "ADaM"
+#> 
      
+# Match is FALSE
+evaluateStandard(
+ data=safetyData::adam_adlbc, 
+ meta=meta, 
+ domain="labs", 
+ standard="sdtm"
+) 
+
      #> $standard
+#> [1] "sdtm"
 #> 
-#> # A tibble: 12 x 4
-#>    text_key            standard_val                      type   valid
-#>    <chr>               <chr>                             <chr>  <lgl>
-#>  1 id_col              USUBJID                           column TRUE 
-#>  2 value_col           STRESN                            column FALSE
-#>  3 measure_col         TEST                              column FALSE
-#>  4 measure_values--ALT Aminotransferase, alanine (ALT)   field  FALSE
-#>  5 measure_values--AST Aminotransferase, aspartate (AST) field  FALSE
-#>  6 measure_values--TB  Total Bilirubin                   field  FALSE
-#>  7 measure_values--ALP Alkaline phosphatase (ALP)        field  FALSE
-#>  8 normal_col_low      STNRLO                            column FALSE
-#>  9 normal_col_high     STNRHI                            column FALSE
-#> 10 studyday_col        DY                                column FALSE
-#> 11 visit_col           VISIT                             column TRUE 
-#> 12 visitn_col          VISITNUM                          column TRUE 
+#> $mapping
+#> # A tibble: 13 × 3
+#> # Rowwise: 
+#>    text_key            current  valid
+#>    <chr>               <chr>    <lgl>
+#>  1 id_col              USUBJID  TRUE 
+#>  2 value_col           LBSTRESN TRUE 
+#>  3 measure_col         NA       FALSE
+#>  4 normal_col_low      NA       FALSE
+#>  5 normal_col_high     NA       FALSE
+#>  6 studyday_col        NA       FALSE
+#>  7 visit_col           VISIT    TRUE 
+#>  8 visitn_col          VISITNUM TRUE 
+#>  9 measure_values--ALT NA       FALSE
+#> 10 measure_values--AST NA       FALSE
+#> 11 measure_values--TB  NA       FALSE
+#> 12 measure_values--ALP NA       FALSE
+#> 13 unit_col            NA       FALSE
 #> 
 #> $total_count
-#> [1] 12
+#> [1] 13
 #> 
 #> $valid_count
-#> [1] 3
+#> [1] 4
 #> 
 #> $invalid_count
 #> [1] 9
 #> 
 #> $match_percent
-#> [1] 0.25
+#> [1] 0.3076923
 #> 
 #> $match
 #> [1] "partial"
+#> 
+#> $label
+#> [1] "Partial SDTM"
+#> 
+#> $details
+#> [1] "(4/13 cols/fields matched)"
 #> 
      
-
      
+
      
   
      
-  
 
 
       
      
       
      
-  
      Developed by Jeremy Wildfire, Becca Krouse, Preston Burns, Xiao Ni, James Buchanan, Susan Duke, Interactive Safety Graphics Working Group.
      
+  
      Developed by Jeremy Wildfire, Becca Krouse, Preston Burns, Xiao Ni, James Buchanan, Susan Duke.
      
 
      
 
 
      
-  
      Site built with pkgdown 1.4.1.
      
+  
      Site built with pkgdown 1.6.1.
      
 
      
 
       
      
diff --git a/docs/reference/filterTab.html b/docs/reference/filterTab.html
new file mode 100644
index 00000000..0f35e442
--- /dev/null
+++ b/docs/reference/filterTab.html
@@ -0,0 +1,223 @@
+
+
+
+  
+  
+
+
+
+Server for the filter module in datamods::filter_data_ui — filterTab • safetyGraphics
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+  
+
+  
+    
      
+      
      
+      
+
+      
+
+      
      
+
+
      
+  
      
+    
      
+    
      Server for the filter module in datamods::filter_data_ui
      
+    Source: R/mod_filterTab.R
+    
+    
      
+
+    
      
+    
      Server for the filter module in datamods::filter_data_ui
      
+    
      
+
+    
      filterTab(
+  input,
+  output,
+  session,
+  domainData,
+  filterDomain,
+  current_mapping,
+  tabID = "Filtering",
+  filterVars = NULL
+)
      
+
+    
      Arguments
      
+    
+    
+    
+      
+      
+    
+    
+      
+      
+    
+    
+      
+      
+    
+    
+      
+      
+    
+    
+      
+      
+    
+    
+      
+      
+    
+    
+      
+      
+    
+    
+      
+      
+    
+    
      input
      Shiny input object
      output
      Shiny output object
      session
      Shiny session object
      domainData
      list of data files for each domain
      filterDomain
      domain to use for filtering (typically "dm")
      current_mapping
      current data mapping
      tabID
      ID for the tab containing the filter UI (used for testing)
      filterVars
      Variables to use for filtering (used for testing)
      
+
+    
      Value
      
+
+    
      filtered data set
      
+
+  
      
+  
+
      
+
+
+      
      
+      
      
+  
      Developed by Jeremy Wildfire, Becca Krouse, Preston Burns, Xiao Ni, James Buchanan, Susan Duke.
      
+
      
+
+
      
+  
      Site built with pkgdown 1.6.1.
      
+
      
+
+      
      
+   
      
+
+  
+
+
+  
+
+
+
diff --git a/docs/reference/filterTabChecks.html b/docs/reference/filterTabChecks.html
new file mode 100644
index 00000000..b49ce3b9
--- /dev/null
+++ b/docs/reference/filterTabChecks.html
@@ -0,0 +1,194 @@
+
+
+
+  
+  
+
+
+
+Checks for whether the current data and settings support a filter tab — filterTabChecks • safetyGraphics
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+  
+
+  
+    
      
+      
      
+      
+
+      
+
+      
      
+
+
      
+  
      
+    
      
+    
      Checks for whether the current data and settings support a filter tab
      
+    Source: R/mod_filterTabChecks.R
+    
+    
      
+
+    
      
+    
      Checks for whether the current data and settings support a filter tab
      
+    
      
+
+    
      filterTabChecks(domainData, filterDomain, current_mapping)
      
+
+    
      Arguments
      
+    
+    
+    
+      
+      
+    
+    
+      
+      
+    
+    
+      
+      
+    
+    
      domainData
      list of data files for each domain
      filterDomain
      domain to use for filtering (typically "dm")
      current_mapping
      current data mapping (REACTIVE)
      
+
+    
      Value
      
+
+    
      reactive that returns a boolean indicating whether the checks passed and filtering can be initiailized
      
+
+  
      
+  
+
      
+
+
+      
      
+      
      
+  
      Developed by Jeremy Wildfire, Becca Krouse, Preston Burns, Xiao Ni, James Buchanan, Susan Duke.
      
+
      
+
+
      
+  
      Site built with pkgdown 1.6.1.
      
+
      
+
+      
      
+   
      
+
+  
+
+
+  
+
+
+
diff --git a/docs/reference/filterTabUI.html b/docs/reference/filterTabUI.html
new file mode 100644
index 00000000..345f6c02
--- /dev/null
+++ b/docs/reference/filterTabUI.html
@@ -0,0 +1,183 @@
+
+
+
+  
+  
+
+
+
+UI for the filter module in datamods::filter_data_ui — filterTabUI • safetyGraphics
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+  
+
+  
+    
      
+      
      
+      
+
+      
+
+      
      
+
+
      
+  
      
+    
      
+    
      UI for the filter module in datamods::filter_data_ui
      
+    Source: R/mod_filterTab.R
+    
+    
      
+
+    
      
+    
      UI for the filter module in datamods::filter_data_ui
      
+    
      
+
+    
      filterTabUI(id)
      
+
+    
      Arguments
      
+    
+    
+    
+      
+      
+    
+    
      id
      module id
      
+
+
+  
      
+  
+
      
+
+
+      
      
+      
      
+  
      Developed by Jeremy Wildfire, Becca Krouse, Preston Burns, Xiao Ni, James Buchanan, Susan Duke.
      
+
      
+
+
      
+  
      Site built with pkgdown 1.6.1.
      
+
      
+
+      
      
+   
      
+
+  
+
+
+  
+
+
+
diff --git a/docs/reference/generateMappingList.html b/docs/reference/generateMappingList.html
new file mode 100644
index 00000000..b5d44702
--- /dev/null
+++ b/docs/reference/generateMappingList.html
@@ -0,0 +1,191 @@
+
+
+
+  
+  
+
+
+
+Convert mapping data.frame to a list — generateMappingList • safetyGraphics
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+  
+
+  
+    
      
+      
      
+      
+
+      
+
+      
      
+
+
      
+  
      
+    
      
+    
      Convert mapping data.frame to a list
      
+    Source: R/generateMappingList.R
+    
+    
      
+
+    
      
+    
      Convert mapping data.frame to a list
      
+    
      
+
+    
      generateMappingList(settingsDF, domain = NULL, pull = FALSE)
      
+
+    
      Arguments
      
+    
+    
+    
+      
+      
+    
+    
+      
+      
+    
+    
+      
+      
+    
+    
      settingsDF
      data frame containing current mapping
      domain
      mapping domain to return (returns all domains as a named list by default)
      pull
      call pull() the value for each parameter - needed for testing only. default: FALSE
      
+
+
+  
      
+  
+
      
+
+
+      
      
+      
      
+  
      Developed by Jeremy Wildfire, Becca Krouse, Preston Burns, Xiao Ni, James Buchanan, Susan Duke.
      
+
      
+
+
      
+  
      Site built with pkgdown 1.6.1.
      
+
      
+
+      
      
+   
      
+
+  
+
+
+  
+
+
+
diff --git a/docs/reference/hasColumn.html b/docs/reference/hasColumn.html
index 3ba3db80..6a0d6ed1 100644
--- a/docs/reference/hasColumn.html
+++ b/docs/reference/hasColumn.html
@@ -8,23 +8,29 @@
 
 Check whether a column is found in a data set — hasColumn • safetyGraphics
 
+
 
-
+
 
-
+
+
+
+
 
-
+
+
+
 
 
-
-
+
+
 
 
-
+
 
 
-
-
+
+
 
 
 
@@ -32,10 +38,10 @@
 
 
 
-
 
+
 
-
+
 
 
 
@@ -52,7 +58,7 @@
 
   
 
-  
+  
     
      
       
      
       
 
@@ -74,33 +80,38 @@
       
-      
       
      
 
     
      
-    
     
      Checks whether a specified column is found in a specified data set
      
-    
     
      
 
-    
      hasColumn(columnName, data)
      
-    
+    
      hasColumn(columnName, data)
      
+
     
      Arguments
      
     
@@ -146,37 +155,32 @@ 
      Arg
       
      
     
      the data.frame to search.
      		
     
      
     
      
-    
+
     
      Value
      
 
     
      logical scalar. TRUE if the column is found. FALSE otherwise
      
-    
 
     
      Examples
      
-    
      safetyGraphics:::hasColumn(columnName="PARAM",data=adlbc) #TRUE
      #> [1] TRUE
      safetyGraphics:::hasColumn(columnName="Not_a_column",data=adlbc) #FALSE
      #> [1] FALSE
      
+    
      safetyGraphics:::hasColumn(columnName="PARAM",data=safetyData::adam_adlbc) #TRUE
+
      #> [1] TRUE
      safetyGraphics:::hasColumn(columnName="Not_a_column",data=safetyData::adam_adlbc) #FALSE
+
      #> [1] FALSE
      
 
      
   
      
-  
 
 
       
      
       
      
-  
      Developed by Jeremy Wildfire, Becca Krouse, Preston Burns, Xiao Ni, James Buchanan, Susan Duke, Interactive Safety Graphics Working Group.
      
+  
      Developed by Jeremy Wildfire, Becca Krouse, Preston Burns, Xiao Ni, James Buchanan, Susan Duke.
      
 
      
 
 
      
-  
      Site built with pkgdown 1.4.1.
      
+  
      Site built with pkgdown 1.6.1.
      
 
      
 
       
      
diff --git a/docs/reference/hasField.html b/docs/reference/hasField.html
index ccd6dffe..de95f94c 100644
--- a/docs/reference/hasField.html
+++ b/docs/reference/hasField.html
@@ -8,23 +8,29 @@
 
 Check whether a specified field value is found in a data set — hasField • safetyGraphics
 
+
 
-
+
 
-
+
+
+
+
 
-
+
+
+
 
 
-
-
+
+
 
 
-
+
 
 
-
-
+
+
 
 
 
@@ -32,10 +38,10 @@
 
 
 
-
 
+
 
-
+
 
 
 
@@ -52,7 +58,7 @@
 
   
 
-  
+  
     
      
       
      
       
 
@@ -74,33 +80,38 @@
       
-      
       
      
 
     
      
-    
     
      This checks whether a specific value is found in a specified column in a specified data set
      
-    
     
      
 
-    
      hasField(fieldValue, columnName, data)
      
-    
+    
      hasField(fieldValue, columnName, data)
      
+
     
      Arguments
      
     
@@ -150,37 +159,43 @@ 
      Arg
       
      
     
      the data.frame to search.
      		
     
      
     
      
-    
+
     
      Value
      
 
     
      logical scalar. TRUE if field_value is found. FALSE otherwise
      
-    
 
     
      Examples
      
-    
      safetyGraphics:::hasField(fieldValue="Bilirubin (umol/L)",columnName="PARAM",data=adlbc) #TRUE
      #> [1] TRUE
      safetyGraphics:::hasField(fieldValue="Not_a_real_value",columnName="",data=adlbc) #FALSE
      #> [1] FALSE
      
+    
      #TRUE
+safetyGraphics:::hasField(
+ fieldValue="Bilirubin (umol/L)",
+ columnName="PARAM",
+ data=safetyData::adam_adlbc
+)
+
      #> [1] TRUE
      
+#FALSE
+safetyGraphics:::hasField(
+ fieldValue="Not_a_real_value",
+ columnName="",
+ data=safetyData::adam_adlbc
+)
+
      #> [1] FALSE
      
 
      
   
      
-  
 
 
       
      
       
      
-  
      Developed by Jeremy Wildfire, Becca Krouse, Preston Burns, Xiao Ni, James Buchanan, Susan Duke, Interactive Safety Graphics Working Group.
      
+  
      Developed by Jeremy Wildfire, Becca Krouse, Preston Burns, Xiao Ni, James Buchanan, Susan Duke.
      
 
      
 
 
      
-  
      Site built with pkgdown 1.4.1.
      
+  
      Site built with pkgdown 1.6.1.
      
 
      
 
       
      
diff --git a/docs/reference/homeTab.html b/docs/reference/homeTab.html
new file mode 100644
index 00000000..271b6714
--- /dev/null
+++ b/docs/reference/homeTab.html
@@ -0,0 +1,191 @@
+
+
+
+  
+  
+
+
+
+Server for the filter module in datamods::filter_data_ui — homeTab • safetyGraphics
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+  
+
+  
+    
      
+      
      
+      
+
+      
+
+      
      
+
+
      
+  
      
+    
      
+    
      Server for the filter module in datamods::filter_data_ui
      
+    Source: R/mod_homeTab.R
+    
+    
      
+
+    
      
+    
      Server for the filter module in datamods::filter_data_ui
      
+    
      
+
+    
      homeTab(input, output, session)
      
+
+    
      Arguments
      
+    
+    
+    
+      
+      
+    
+    
+      
+      
+    
+    
+      
+      
+    
+    
      input
      mod input
      output
      mod output
      session
      mod session
      
+
+
+  
      
+  
+
      
+
+
+      
      
+      
      
+  
      Developed by Jeremy Wildfire, Becca Krouse, Preston Burns, Xiao Ni, James Buchanan, Susan Duke.
      
+
      
+
+
      
+  
      Site built with pkgdown 1.6.1.
      
+
      
+
+      
      
+   
      
+
+  
+
+
+  
+
+
+
diff --git a/docs/reference/homeTabUI.html b/docs/reference/homeTabUI.html
new file mode 100644
index 00000000..a0f101f6
--- /dev/null
+++ b/docs/reference/homeTabUI.html
@@ -0,0 +1,183 @@
+
+
+
+  
+  
+
+
+
+UI for the home module — homeTabUI • safetyGraphics
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+  
+
+  
+    
      
+      
      
+      
+
+      
+
+      
      
+
+
      
+  
      
+    
      
+    
      UI for the home module
      
+    Source: R/mod_homeTab.R
+    
+    
      
+
+    
      
+    
      UI for the home module
      
+    
      
+
+    
      homeTabUI(id)
      
+
+    
      Arguments
      
+    
+    
+    
+      
+      
+    
+    
      id
      module id
      
+
+
+  
      
+  
+
      
+
+
+      
      
+      
      
+  
      Developed by Jeremy Wildfire, Becca Krouse, Preston Burns, Xiao Ni, James Buchanan, Susan Duke.
      
+
      
+
+
      
+  
      Site built with pkgdown 1.6.1.
      
+
      
+
+      
      
+   
      
+
+  
+
+
+  
+
+
+
diff --git a/docs/reference/index.html b/docs/reference/index.html
index 1563ad33..d90a48fc 100644
--- a/docs/reference/index.html
+++ b/docs/reference/index.html
@@ -8,23 +8,29 @@
 
 Function reference • safetyGraphics
 
+
 
-
+
 
-
+
+
+
+
 
-
+
+
+
 
 
-
-
+
+
 
 
-
+
 
 
-
-
+
+
 
 
 
@@ -32,10 +38,12 @@
 
 
 
+
 
 
 
 
+
 
 
 
@@ -49,7 +57,7 @@
 
   
 
-  
+  
     
      
       
      
       
 
@@ -71,33 +79,38 @@
       
-      
       
        
         
      • 
   
@@ -132,60 +145,264 @@ 
        Reference
        
     
       
         
-          
        Main Functions
        
+          
        Main Shiny App Functions
        
           
        
         
       
+      
+      
+    
+      
+      
       
         
         
           
        safetyGraphicsApp() 
        
         
-        
        Run the interactive safety graphics builder
        
+        
        Run the core safetyGraphics App
        
+      
+        
+        
+          
        safetyGraphicsInit() 
        
+        
+        
        App to select charts, load data and then initialize the core safetyGraphics app
        
       
     
       
         
-          
        Helper Functions
        
-          
        these functions are used by the main app
        
+          
        Shiny Modules
        
+          
        Reusable Shiny Modules
        
         
       
+      
+      
+    
+      
+      
       
         
         
-          
        addChart() 
        
+          
        safetyGraphicsServer() 
        
+        
+        
        Server for core safetyGraphics app including Home, Mapping, Filter, Charts and Settings modules.
        
+      
+        
+        
+          
        safetyGraphicsUI() 
        
+        
+        
        UI for the core safetyGraphics app including Home, Mapping, Filter, Charts and Settings modules.
        
+      
+        
+        
+          
        chartsTab() 
        
+        
+        
        Server for chart module, designed to be re-used for each chart generated.
        
+      
+        
+        
+          
        chartsTabUI() 
        
+        
+        
        UI for chart module, designed to be re-used for each chart generated.
        
+      
+        
+        
+          
        filterTab() 
        
+        
+        
        Server for the filter module in datamods::filter_data_ui
        
+      
+        
+        
+          
        filterTabUI() 
        
+        
+        
        UI for the filter module in datamods::filter_data_ui
        
+      
+        
+        
+          
        homeTab() 
        
+        
+        
        Server for the filter module in datamods::filter_data_ui
        
+      
+        
+        
+          
        homeTabUI() 
        
+        
+        
        UI for the home module
        
+      
+        
+        
+          
        loadCharts() 
        
+        
+        
        Server for the chart loading module used in safetyGraphicsInit()
        
+      
+        
+        
+          
        loadChartsUI() 
        
+        
+        
        UI for the chart loading module used in safetyGraphicsInit()
        
+      
+        
+        
+          
        loadData() 
        
+        
+        
        Server for the data loading module used in safetyGraphicsInit()
        
+      
+        
+        
+          
        loadDataUI() 
        
+        
+        
        UI for the data loading module used in safetyGraphicsInit()
        
+      
+        
+        
+          
        mappingTab() 
        
+        
+        
        Server for mapping tab covering of all data domains
        
+      
+        
+        
+          
        mappingTabUI() 
        
+        
+        
        UI for mapping tab covering of all data domains
        
+      
+        
+        
+          
        mappingDomain() 
        
+        
+        
        Server that facilitates the mapping of a full data domain
        
+      
+        
+        
+          
        mappingDomainUI() 
        
+        
+        
        UI that facilitates the mapping of a full data domain
        
+      
+        
+        
+          
        mappingColumn() 
        
+        
+        
        Server that facilitates the mapping of a column data (and any associated fields)
        
+      
+        
+        
+          
        mappingColumnUI() 
        
+        
+        
        UI that facilitates the mapping of a column data (and any associated fields)
        
+      
+        
+        
+          
        mappingSelect() 
        
+        
+        
        Server that facilitates the mapping of a single data element (column or field) with a simple select UI
        
+      
+        
+        
+          
        mappingSelectUI() 
        
+        
+        
        UI that facilitates the mapping of a single data element (column or field) with a simple select UI
        
+      
+        
+        
+          
        settingsTab() 
        
+        
+        
        Server for the setting page
        
+      
+        
+        
+          
        settingsTabUI() 
        
+        
+        
        UI for the settings tab
        
+      
+        
+        
+          
        settingsCharts() 
        
+        
+        
        Server for settings tab showing details for the charts loaded in the app
        
+      
+        
+        
+          
        settingsChartsUI() 
        
+        
+        
        UI for settings tab showing details for the charts loaded in the app
        
+      
+        
+        
+          
        settingsData() 
        
         
-        
        Adds a new chart for use in the safetyGraphics shiny app
        
+        
        Server for settings tab showing current data
        
       
         
         
-          
        addSetting() 
        
+          
        settingsDataUI() 
        
         
-        
        Adds a new setting for use in the safetyGraphics shiny app
        
+        
        UI for settings tab showing current data
        
       
         
         
-          
        adlbc 
        
+          
        settingsMapping() 
        
         
-        
        Safety measures sample data
        
+        
        Server for settings tab showing current mapping
        
       
         
         
-          
        output_chartRenderer() render_chartRenderer() 
        
+          
        settingsMappingUI() 
        
         
-        
        Shiny bindings for chartRenderer
        
+        
        UI for settings tab showing current mapping
        
       
         
         
-          
        chartRenderer() 
        
+          
        settingsCode() 
        
+        
+        
        Server for settings tab providing code to re-start the app with current data/settings
        
+      
+        
+        
+          
        settingsCodeUI() 
        
+        
+        
        UI for settings tab providing code to re-start the app with current data/settings
        
+      
+    
+      
+        
+          
        Data
        
+          
        Data sets used in the apps
        
+        
+      
+      
+      
+    
+      
+      
+      
+        
+        
+          
        meta 
        
+        
+        
        Metadata data frame containing information about the data mapping used to configure safetyGraphics charts. One record per unique data mapping
        
+      
+    
+      
+        
+          
        Helper Functions
        
+          
        Utility functions used in the apps
        
+        
+      
+      
+      
+    
+      
+      
+      
+        
+        
+          
        app_startup() 
        
         
-        
        Create an interactive graphics widget
        
+        
        Startup code for shiny app
        
       
         
         
-          
        chartsMetadata 
        
+          
        chartsNav() 
        
         
-        
        Charts Metadata
        
+        
        Adds a navbar tab that initializes the Chart Module UI
        
       
         
         
@@ -195,79 +412,77 @@ 
        generateSettings() 
        
+          
        evaluateStandard() 
        
         
-        
        Generate a settings object based on a data standard
        
+        
        Evaluate a data set against a data standard
        
       
         
         
-          
        getRequiredSettings() 
        
+          
        filterTabChecks() 
        
         
-        
        Get a list of required settings
        
+        
        Checks for whether the current data and settings support a filter tab
        
       
         
         
-          
        getSettingsMetadata() 
        
+          
        generateMappingList() 
        
         
-        
        Get metadata about chart settings
        
+        
        Convert mapping data.frame to a list
        
       
         
         
-          
        removeCharts() 
        
+          
        makeChartConfig() 
        
         
-        
        Remove a chart from the safetyGraphics shiny app
        
+        
        Make Chart Config
        
       
         
         
-          
        removeSettings() 
        
+          
        makeChartExport() 
        
         
-        
        Remove a setting from the safetyGraphics shiny app
        
+        
        Make Chart Export
        
       
         
         
-          
        settingsMetadata 
        
+          
        makeChartParams() 
        
         
-        
        Settings Metadata
        
+        
        Make Chart Parameters
        
       
         
         
-          
        standardsMetadata 
        
+          
        makeChartSummary() 
        
         
-        
        Standards Metadata
        
+        
        html chart summary
        
       
         
         
-          
        trimSettings() 
        
+          
        makeMapping() 
        
         
-        
        Subset a settings object to those relevant for a list of charts
        
+        
        Create data mapping based on data standards and user input
        
       
         
         
-          
        validateSettings() 
        
+          
        prepareChart() 
        
         
-        
        Compare a settings object with a specified data set
        
+        
        Prepare a chart object for safetyGraphcis
        
       
     
     
   
      
 
-  
 
 
       
      
       
      
-  
      Developed by Jeremy Wildfire, Becca Krouse, Preston Burns, Xiao Ni, James Buchanan, Susan Duke, Interactive Safety Graphics Working Group.
      
+  
      Developed by Jeremy Wildfire, Becca Krouse, Preston Burns, Xiao Ni, James Buchanan, Susan Duke.
      
 
      
 
 
      
-  
      Site built with pkgdown 1.4.1.
      
+  
      Site built with pkgdown 1.6.1.
      
 
      
 
       
      
diff --git a/docs/reference/loadCharts.html b/docs/reference/loadCharts.html
new file mode 100644
index 00000000..93fc883a
--- /dev/null
+++ b/docs/reference/loadCharts.html
@@ -0,0 +1,195 @@
+
+
+
+  
+  
+
+
+
+Server for the chart loading module used in safetyGraphicsInit() — loadCharts • safetyGraphics
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+  
+
+  
+    
      
+      
      
+      
+
+      
+
+      
      
+
+
      
+  
      
+    
      
+    
      Server for the chart loading module used in safetyGraphicsInit()
      
+    Source: R/mod_loadCharts.R
+    
+    
      
+
+    
      
+    
      Server for the chart loading module used in safetyGraphicsInit()
      
+    
      
+
+    
      loadCharts(input, output, session, charts = makeChartConfig())
      
+
+    
      Arguments
      
+    
+    
+    
+      
+      
+    
+    
+      
+      
+    
+    
+      
+      
+    
+    
+      
+      
+    
+    
      input
      Shiny input object
      output
      Shiny output object
      session
      Shiny session object
      charts
      list containing chart specifications like those returned by makeChartConfig.
      
+
+
+  
      
+  
+
      
+
+
+      
      
+      
      
+  
      Developed by Jeremy Wildfire, Becca Krouse, Preston Burns, Xiao Ni, James Buchanan, Susan Duke.
      
+
      
+
+
      
+  
      Site built with pkgdown 1.6.1.
      
+
      
+
+      
      
+   
      
+
+  
+
+
+  
+
+
+
diff --git a/docs/reference/loadChartsUI.html b/docs/reference/loadChartsUI.html
new file mode 100644
index 00000000..707ef954
--- /dev/null
+++ b/docs/reference/loadChartsUI.html
@@ -0,0 +1,187 @@
+
+
+
+  
+  
+
+
+
+UI for the chart loading module used in safetyGraphicsInit() — loadChartsUI • safetyGraphics
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+  
+
+  
+    
      
+      
      
+      
+
+      
+
+      
      
+
+
      
+  
      
+    
      
+    
      UI for the chart loading module used in safetyGraphicsInit()
      
+    Source: R/mod_loadCharts.R
+    
+    
      
+
+    
      
+    
      UI for the chart loading module used in safetyGraphicsInit()
      
+    
      
+
+    
      loadChartsUI(id, charts = makeChartConfig())
      
+
+    
      Arguments
      
+    
+    
+    
+      
+      
+    
+    
+      
+      
+    
+    
      id
      module id
      charts
      list containing chart specifications like those returned by makeChartConfig.
      
+
+
+  
      
+  
+
      
+
+
+      
      
+      
      
+  
      Developed by Jeremy Wildfire, Becca Krouse, Preston Burns, Xiao Ni, James Buchanan, Susan Duke.
      
+
      
+
+
      
+  
      Site built with pkgdown 1.6.1.
      
+
      
+
+      
      
+   
      
+
+  
+
+
+  
+
+
+
diff --git a/docs/reference/loadData.html b/docs/reference/loadData.html
new file mode 100644
index 00000000..cdbba372
--- /dev/null
+++ b/docs/reference/loadData.html
@@ -0,0 +1,195 @@
+
+
+
+  
+  
+
+
+
+Server for the data loading module used in safetyGraphicsInit() — loadData • safetyGraphics
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+  
+
+  
+    
      
+      
      
+      
+
+      
+
+      
      
+
+
      
+  
      
+    
      
+    
      Server for the data loading module used in safetyGraphicsInit()
      
+    Source: R/mod_loadData.R
+    
+    
      
+
+    
      
+    
      Server for the data loading module used in safetyGraphicsInit()
      
+    
      
+
+    
      loadData(input, output, session, domain)
      
+
+    
      Arguments
      
+    
+    
+    
+      
+      
+    
+    
+      
+      
+    
+    
+      
+      
+    
+    
+      
+      
+    
+    
      input
      Shiny input object
      output
      Shiny output object
      session
      Shiny session object
      domain
      data domain to be loaded
      
+
+
+  
      
+  
+
      
+
+
+      
      
+      
      
+  
      Developed by Jeremy Wildfire, Becca Krouse, Preston Burns, Xiao Ni, James Buchanan, Susan Duke.
      
+
      
+
+
      
+  
      Site built with pkgdown 1.6.1.
      
+
      
+
+      
      
+   
      
+
+  
+
+
+  
+
+
+
diff --git a/docs/reference/loadDataUI.html b/docs/reference/loadDataUI.html
new file mode 100644
index 00000000..9b93d9e4
--- /dev/null
+++ b/docs/reference/loadDataUI.html
@@ -0,0 +1,187 @@
+
+
+
+  
+  
+
+
+
+UI for the data loading module used in safetyGraphicsInit() — loadDataUI • safetyGraphics
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+  
+
+  
+    
      
+      
      
+      
+
+      
+
+      
      
+
+
      
+  
      
+    
      
+    
      UI for the data loading module used in safetyGraphicsInit()
      
+    Source: R/mod_loadData.R
+    
+    
      
+
+    
      
+    
      UI for the data loading module used in safetyGraphicsInit()
      
+    
      
+
+    
      loadDataUI(id, domain = NULL)
      
+
+    
      Arguments
      
+    
+    
+    
+      
+      
+    
+    
+      
+      
+    
+    
      id
      module id
      domain
      character vector with domains to be loaded
      
+
+
+  
      
+  
+
      
+
+
+      
      
+      
      
+  
      Developed by Jeremy Wildfire, Becca Krouse, Preston Burns, Xiao Ni, James Buchanan, Susan Duke.
      
+
      
+
+
      
+  
      Site built with pkgdown 1.6.1.
      
+
      
+
+      
      
+   
      
+
+  
+
+
+  
+
+
+
diff --git a/docs/reference/makeChartConfig.html b/docs/reference/makeChartConfig.html
new file mode 100644
index 00000000..9dbd58bc
--- /dev/null
+++ b/docs/reference/makeChartConfig.html
@@ -0,0 +1,217 @@
+
+
+
+  
+  
+
+
+
+Make Chart Config — makeChartConfig • safetyGraphics
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+  
+
+  
+    
      
+      
      
+      
+
+      
+
+      
      
+
+
      
+  
      
+    
      
+    
      Make Chart Config
      
+    Source: R/makeChartConfig.R
+    
+    
      
+
+    
      
+    
      Converts YAML chart configuration files to an R list and binds workflow functions. See the vignette about creating custom charts for more details.
      
+    
      
+
+    
      makeChartConfig(
+  dirs,
+  packages = "safetyCharts",
+  packageLocation = "config",
+  sourceFiles = TRUE
+)
      
+
+    
      Arguments
      
+    
+    
+    
+      
+      
+    
+    
+      
+      
+    
+    
+      
+      
+    
+    
+      
+      
+    
+    
      dirs
      path to one or more directories containing yaml config files (relative to working directory)
      packages
      installed packages names containing yaml config files in the /inst/packageLocation folder
      packageLocation
      inst folder where yaml config files (and possibly R functions referenced in yaml workflow) are located in packages
      sourceFiles
      boolean indicating whether to source all R files found in dirs.
      
+
+    
      Value
      
+
+    
      returns a named list of charts derived from YAML files. Each element of the list contains information about a single chart, and has the following parameters:
        
+
      • "env" Environment for the chart. Must be set to "safetyGraphics" or the chart is dropped.
        • 
+
      • "name" Name of the chart. Also the name of the element in the list - e.g. charts$aeExplorer$name is "aeExplorer"
        • 
+
      • "label" Short description of the chart
        • 
+
      • "type" Type of chart; options are: 'htmlwidget', 'module', 'plot', 'table', 'html' or 'plotly'.
        • 
+
      • "domain" Data domain. Should correspond to one or more domains in meta
        • 
+
      • "package" Primary package (if any). Other packages can be loaded directly in workflow functions.
        • 
+
      • "order" Integer order in which to display the chart. If order is a negative number, the chart is dropped.
        • 
+
      • "export" Logical flag indicating whether the chart can be exported to an html report. True by default, except for when type is module.
        • 
+
      • "path" Path to YAML file
        • 
+
      • "links" Named list of link names/urls to be shown in the chart header.
        • 
+
      • "workflow" List of functions names used to render chart. See vignette for details.
        • 
+
      • "functions" List of functions for use in chart renderering. These functions must be located in the global environment or package field of the YAML config. Function names must include either the name or workflow fields of the YAML config.
        • 
+
      
+
+
+  
      
+  
+
      
+
+
+      
      
+      
      
+  
      Developed by Jeremy Wildfire, Becca Krouse, Preston Burns, Xiao Ni, James Buchanan, Susan Duke.
      
+
      
+
+
      
+  
      Site built with pkgdown 1.6.1.
      
+
      
+
+      
      
+   
      
+
+  
+
+
+  
+
+
+
diff --git a/docs/reference/makeChartExport.html b/docs/reference/makeChartExport.html
new file mode 100644
index 00000000..5ba7d6b1
--- /dev/null
+++ b/docs/reference/makeChartExport.html
@@ -0,0 +1,190 @@
+
+
+
+  
+  
+
+
+
+Make Chart Export — makeChartExport • safetyGraphics
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+  
+
+  
+    
      
+      
      
+      
+
+      
+
+      
      
+
+
      
+  
      
+    
      
+    
      Make Chart Export
      
+    Source: R/makeChartExport.R
+    
+    
      
+
+    
      
+    
      Creates R code that allows chart to be exported
      
+    
      
+
+    
      makeChartExport(chart, mapping)
      
+
+    
      Arguments
      
+    
+    
+    
+      
+      
+    
+    
+      
+      
+    
+    
      chart
      chart object like the one generated by makeChartConfig().
      mapping
      mapping object like the one generatedf by makeMapping().
      
+
+    
      Value
      
+
+    
      returns a character vector that can be saved as R code.
      
+
+  
      
+  
+
      
+
+
+      
      
+      
      
+  
      Developed by Jeremy Wildfire, Becca Krouse, Preston Burns, Xiao Ni, James Buchanan, Susan Duke.
      
+
      
+
+
      
+  
      Site built with pkgdown 1.6.1.
      
+
      
+
+      
      
+   
      
+
+  
+
+
+  
+
+
+
diff --git a/docs/reference/makeChartParams.html b/docs/reference/makeChartParams.html
new file mode 100644
index 00000000..2239afbc
--- /dev/null
+++ b/docs/reference/makeChartParams.html
@@ -0,0 +1,191 @@
+
+
+
+  
+  
+
+
+
+Make Chart Parameters — makeChartParams • safetyGraphics
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+  
+
+  
+    
      
+      
      
+      
+
+      
+
+      
      
+
+
      
+  
      
+    
      
+    
      Make Chart Parameters
      
+    Source: R/makeChartParams.R
+    
+    
      
+
+    
      
+    
      Updates raw data and mapping for use with a specific chart
      
+    
      
+
+    
      makeChartParams(data, chart, mapping)
      
+
+    
      Arguments
      
+    
+    
+    
+      
+      
+    
+    
+      
+      
+    
+    
+      
+      
+    
+    
      data
      list of domain-level data
      chart
      list containing chart specifications
      mapping
      data frame with current mapping
      
+
+
+  
      
+  
+
      
+
+
+      
      
+      
      
+  
      Developed by Jeremy Wildfire, Becca Krouse, Preston Burns, Xiao Ni, James Buchanan, Susan Duke.
      
+
      
+
+
      
+  
      Site built with pkgdown 1.6.1.
      
+
      
+
+      
      
+   
      
+
+  
+
+
+  
+
+
+
diff --git a/docs/reference/makeChartSummary.html b/docs/reference/makeChartSummary.html
new file mode 100644
index 00000000..5206d7cd
--- /dev/null
+++ b/docs/reference/makeChartSummary.html
@@ -0,0 +1,191 @@
+
+
+
+  
+  
+
+
+
+html chart summary — makeChartSummary • safetyGraphics
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+  
+
+  
+    
      
+      
      
+      
+
+      
+
+      
      
+
+
      
+  
      
+    
      
+    
      html chart summary
      
+    Source: R/makeChartSummary.R
+    
+    
      
+
+    
      
+    
      makes a nicely formatted html summary for a chart object
      
+    
      
+
+    
      makeChartSummary(chart, showLinks = TRUE, class = "chart-header")
      
+
+    
      Arguments
      
+    
+    
+    
+      
+      
+    
+    
+      
+      
+    
+    
+      
+      
+    
+    
      chart
      list containing chart specifications
      showLinks
      boolean indicating whether to include links
      class
      character to include as class
      
+
+
+  
      
+  
+
      
+
+
+      
      
+      
      
+  
      Developed by Jeremy Wildfire, Becca Krouse, Preston Burns, Xiao Ni, James Buchanan, Susan Duke.
      
+
      
+
+
      
+  
      Site built with pkgdown 1.6.1.
      
+
      
+
+      
      
+   
      
+
+  
+
+
+  
+
+
+
diff --git a/docs/reference/makeMapping.html b/docs/reference/makeMapping.html
new file mode 100644
index 00000000..34aa3e2e
--- /dev/null
+++ b/docs/reference/makeMapping.html
@@ -0,0 +1,202 @@
+
+
+
+  
+  
+
+
+
+Create data mapping based on data standards and user input — makeMapping • safetyGraphics
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+  
+
+  
+    
      
+      
      
+      
+
+      
+
+      
      
+
+
      
+  
      
+    
      
+    
      Create data mapping based on data standards and user input
      
+    Source: R/makeMapping.R
+    
+    
      
+
+    
      
+    
      Create data mapping based on data standards and user input
      
+    
      
+
+    
      makeMapping(domainData, meta, autoMapping, customMapping)
      
+
+    
      Arguments
      
+    
+    
+    
+      
+      
+    
+    
+      
+      
+    
+    
+      
+      
+    
+    
+      
+      
+    
+    
      domainData
      named list of data.frames to be loaded in to the app. Sample AdAM data from the safetyData package used by default
      meta
      data frame containing the metadata for use in the app. See the preloaded file (?safetyGraphics::meta) for more data specifications and details. Defaults to safetyGraphics::meta.
      autoMapping
      boolean indicating whether the app should use safetyGraphics::detectStandard() to detect data standards and automatically generate mappings for the data provided. Values specified in the customMapping parameter overwrite auto-generated mappings when both are found. Defaults to true.
      customMapping
      optional list specifying initial mapping values within each data mapping (e.g. list(aes= list(id_col='USUBJID', seq_col='AESEQ')).
      
+
+    
      Value
      
+
+    
      List containing data standard information and mapping
        
+
      • "mapping" Initial Data Mapping
        • 
+
      • "standards" List of domain level data standards (or NULL if autoMapping is false)
        • 
+
      
+
+
+  
      
+  
+
      
+
+
+      
      
+      
      
+  
      Developed by Jeremy Wildfire, Becca Krouse, Preston Burns, Xiao Ni, James Buchanan, Susan Duke.
      
+
      
+
+
      
+  
      Site built with pkgdown 1.6.1.
      
+
      
+
+      
      
+   
      
+
+  
+
+
+  
+
+
+
diff --git a/docs/reference/mappingColumn.html b/docs/reference/mappingColumn.html
new file mode 100644
index 00000000..a8d4bd7f
--- /dev/null
+++ b/docs/reference/mappingColumn.html
@@ -0,0 +1,202 @@
+
+
+
+  
+  
+
+
+
+Server that facilitates the mapping of a column data (and any associated fields) — mappingColumn • safetyGraphics
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+  
+
+  
+    
      
+      
      
+      
+
+      
+
+      
      
+
+
      
+  
      
+    
      
+    
      Server that facilitates the mapping of a column data (and any associated fields)
      
+    Source: R/mod_mappingColumn.R
+    
+    
      
+
+    
      
+    
      Server that facilitates the mapping of a column data (and any associated fields)
      
+    
      
+
+    
      mappingColumn(input, output, session, meta, data)
      
+
+    
      Arguments
      
+    
+    
+    
+      
+      
+    
+    
+      
+      
+    
+    
+      
+      
+    
+    
+      
+      
+    
+    
+      
+      
+    
+    
      input
      Shiny input object
      output
      Shiny output object
      session
      Shiny session object
      meta
      metadata data frame for the object
      data
      current data file for the domain
      
+
+    
      Value
      
+
+    
      A reactive data.frame providing the current value for text_key associated with the selected column
      
+
+  
      
+  
+
      
+
+
+      
      
+      
      
+  
      Developed by Jeremy Wildfire, Becca Krouse, Preston Burns, Xiao Ni, James Buchanan, Susan Duke.
      
+
      
+
+
      
+  
      Site built with pkgdown 1.6.1.
      
+
      
+
+      
      
+   
      
+
+  
+
+
+  
+
+
+
diff --git a/docs/reference/mappingColumnUI.html b/docs/reference/mappingColumnUI.html
new file mode 100644
index 00000000..9d84936d
--- /dev/null
+++ b/docs/reference/mappingColumnUI.html
@@ -0,0 +1,195 @@
+
+
+
+  
+  
+
+
+
+UI that facilitates the mapping of a column data (and any associated fields) — mappingColumnUI • safetyGraphics
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+  
+
+  
+    
      
+      
      
+      
+
+      
+
+      
      
+
+
      
+  
      
+    
      
+    
      UI that facilitates the mapping of a column data (and any associated fields)
      
+    Source: R/mod_mappingColumn.R
+    
+    
      
+
+    
      
+    
      UI that facilitates the mapping of a column data (and any associated fields)
      
+    
      
+
+    
      mappingColumnUI(id, meta, data, mapping = NULL)
      
+
+    
      Arguments
      
+    
+    
+    
+      
+      
+    
+    
+      
+      
+    
+    
+      
+      
+    
+    
+      
+      
+    
+    
      id
      module id
      meta
      metadata for the column (and related fields)
      data
      current data file for the domain
      mapping
      current data mapping for the column (and related fields)
      
+
+
+  
      
+  
+
      
+
+
+      
      
+      
      
+  
      Developed by Jeremy Wildfire, Becca Krouse, Preston Burns, Xiao Ni, James Buchanan, Susan Duke.
      
+
      
+
+
      
+  
      Site built with pkgdown 1.6.1.
      
+
      
+
+      
      
+   
      
+
+  
+
+
+  
+
+
+
diff --git a/docs/reference/mappingDomain.html b/docs/reference/mappingDomain.html
new file mode 100644
index 00000000..1cf44e69
--- /dev/null
+++ b/docs/reference/mappingDomain.html
@@ -0,0 +1,202 @@
+
+
+
+  
+  
+
+
+
+Server that facilitates the mapping of a full data domain — mappingDomain • safetyGraphics
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+  
+
+  
+    
      
+      
      
+      
+
+      
+
+      
      
+
+
      
+  
      
+    
      
+    
      Server that facilitates the mapping of a full data domain
      
+    Source: R/mod_mappingDomain.R
+    
+    
      
+
+    
      
+    
      Server that facilitates the mapping of a full data domain
      
+    
      
+
+    
      mappingDomain(input, output, session, meta, data)
      
+
+    
      Arguments
      
+    
+    
+    
+      
+      
+    
+    
+      
+      
+    
+    
+      
+      
+    
+    
+      
+      
+    
+    
+      
+      
+    
+    
      input
      Shiny input object
      output
      Shiny output object
      session
      Shiny session object
      meta
      metadata for the domain
      data
      clinical data for the domain
      
+
+    
      Value
      
+
+    
      A reactive data frame containing the mapping for the domain
      
+
+  
      
+  
+
      
+
+
+      
      
+      
      
+  
      Developed by Jeremy Wildfire, Becca Krouse, Preston Burns, Xiao Ni, James Buchanan, Susan Duke.
      
+
      
+
+
      
+  
      Site built with pkgdown 1.6.1.
      
+
      
+
+      
      
+   
      
+
+  
+
+
+  
+
+
+
diff --git a/docs/reference/mappingDomainUI.html b/docs/reference/mappingDomainUI.html
new file mode 100644
index 00000000..3e43c745
--- /dev/null
+++ b/docs/reference/mappingDomainUI.html
@@ -0,0 +1,195 @@
+
+
+
+  
+  
+
+
+
+UI that facilitates the mapping of a full data domain — mappingDomainUI • safetyGraphics
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+  
+
+  
+    
      
+      
      
+      
+
+      
+
+      
      
+
+
      
+  
      
+    
      
+    
      UI that facilitates the mapping of a full data domain
      
+    Source: R/mod_mappingDomain.R
+    
+    
      
+
+    
      
+    
      UI that facilitates the mapping of a full data domain
      
+    
      
+
+    
      mappingDomainUI(id, meta, data, mapping = NULL)
      
+
+    
      Arguments
      
+    
+    
+    
+      
+      
+    
+    
+      
+      
+    
+    
+      
+      
+    
+    
+      
+      
+    
+    
      id
      module id
      meta
      metadata for the domain
      data
      data file for the domain
      mapping
      current data mapping
      
+
+
+  
      
+  
+
      
+
+
+      
      
+      
      
+  
      Developed by Jeremy Wildfire, Becca Krouse, Preston Burns, Xiao Ni, James Buchanan, Susan Duke.
      
+
      
+
+
      
+  
      Site built with pkgdown 1.6.1.
      
+
      
+
+      
      
+   
      
+
+  
+
+
+  
+
+
+
diff --git a/docs/reference/mappingSelect.html b/docs/reference/mappingSelect.html
new file mode 100644
index 00000000..867d045e
--- /dev/null
+++ b/docs/reference/mappingSelect.html
@@ -0,0 +1,194 @@
+
+
+
+  
+  
+
+
+
+Server that facilitates the mapping of a single data element (column or field) with a simple select UI — mappingSelect • safetyGraphics
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+  
+
+  
+    
      
+      
      
+      
+
+      
+
+      
      
+
+
      
+  
      
+    
      
+    
      Server that facilitates the mapping of a single data element (column or field) with a simple select UI
      
+    Source: R/mod_mappingSelect.R
+    
+    
      
+
+    
      
+    
      Server that facilitates the mapping of a single data element (column or field) with a simple select UI
      
+    
      
+
+    
      mappingSelect(input, output, session)
      
+
+    
      Arguments
      
+    
+    
+    
+      
+      
+    
+    
+      
+      
+    
+    
+      
+      
+    
+    
      input
      Shiny input object
      output
      Shiny output object
      session
      Shiny session object
      
+
+    
      Value
      
+
+    
      A reactive containing the selected column
      
+
+  
      
+  
+
      
+
+
+      
      
+      
      
+  
      Developed by Jeremy Wildfire, Becca Krouse, Preston Burns, Xiao Ni, James Buchanan, Susan Duke.
      
+
      
+
+
      
+  
      Site built with pkgdown 1.6.1.
      
+
      
+
+      
      
+   
      
+
+  
+
+
+  
+
+
+
diff --git a/docs/reference/mappingSelectUI.html b/docs/reference/mappingSelectUI.html
new file mode 100644
index 00000000..07506b3d
--- /dev/null
+++ b/docs/reference/mappingSelectUI.html
@@ -0,0 +1,198 @@
+
+
+
+  
+  
+
+
+
+UI that facilitates the mapping of a single data element (column or field) with a simple select UI — mappingSelectUI • safetyGraphics
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+  
+
+  
+    
      
+      
      
+      
+
+      
+
+      
      
+
+
      
+  
      
+    
      
+    
      UI that facilitates the mapping of a single data element (column or field) with a simple select UI
      
+    Source: R/mod_mappingSelect.R
+    
+    
      
+
+    
      
+    
      UI that facilitates the mapping of a single data element (column or field) with a simple select UI
      
+    
      
+
+    
      mappingSelectUI(id, label, choices = NULL, default = NULL)
      
+
+    
      Arguments
      
+    
+    
+    
+      
+      
+    
+    
+      
+      
+    
+    
+      
+      
+    
+    
+      
+      
+    
+    
      id
      unique id for the UI
      label
      label associated with the control
      choices
      a list of options for the control
      default
      default value for the control
      
+
+    
      Value
      
+
+    
      returns the selected value wrapped in a reactive().
      
+
+  
      
+  
+
      
+
+
+      
      
+      
      
+  
      Developed by Jeremy Wildfire, Becca Krouse, Preston Burns, Xiao Ni, James Buchanan, Susan Duke.
      
+
      
+
+
      
+  
      Site built with pkgdown 1.6.1.
      
+
      
+
+      
      
+   
      
+
+  
+
+
+  
+
+
+
diff --git a/docs/reference/mappingTab.html b/docs/reference/mappingTab.html
new file mode 100644
index 00000000..ada00444
--- /dev/null
+++ b/docs/reference/mappingTab.html
@@ -0,0 +1,202 @@
+
+
+
+  
+  
+
+
+
+Server for mapping tab covering of all data domains — mappingTab • safetyGraphics
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+  
+
+  
+    
      
+      
      
+      
+
+      
+
+      
      
+
+
      
+  
      
+    
      
+    
      Server for mapping tab covering of all data domains
      
+    Source: R/mod_mappingTab.R
+    
+    
      
+
+    
      
+    
      Server for mapping tab covering of all data domains
      
+    
      
+
+    
      mappingTab(input, output, session, meta, domainData)
      
+
+    
      Arguments
      
+    
+    
+    
+      
+      
+    
+    
+      
+      
+    
+    
+      
+      
+    
+    
+      
+      
+    
+    
+      
+      
+    
+    
      input
      Shiny input object
      output
      Shiny output object
      session
      Shiny session object
      meta
      metadata for all domains
      domainData
      clinical data for all domains
      
+
+    
      Value
      
+
+    
      list of mappings for all domains
      
+
+  
      
+  
+
      
+
+
+      
      
+      
      
+  
      Developed by Jeremy Wildfire, Becca Krouse, Preston Burns, Xiao Ni, James Buchanan, Susan Duke.
      
+
      
+
+
      
+  
      Site built with pkgdown 1.6.1.
      
+
      
+
+      
      
+   
      
+
+  
+
+
+  
+
+
+
diff --git a/docs/reference/mappingTabUI.html b/docs/reference/mappingTabUI.html
new file mode 100644
index 00000000..7ff3bf36
--- /dev/null
+++ b/docs/reference/mappingTabUI.html
@@ -0,0 +1,199 @@
+
+
+
+  
+  
+
+
+
+UI for mapping tab covering of all data domains — mappingTabUI • safetyGraphics
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+  
+
+  
+    
      
+      
      
+      
+
+      
+
+      
      
+
+
      
+  
      
+    
      
+    
      UI for mapping tab covering of all data domains
      
+    Source: R/mod_mappingTab.R
+    
+    
      
+
+    
      
+    
      UI for mapping tab covering of all data domains
      
+    
      
+
+    
      mappingTabUI(id, meta, domainData, mappings = NULL, standards = NULL)
      
+
+    
      Arguments
      
+    
+    
+    
+      
+      
+    
+    
+      
+      
+    
+    
+      
+      
+    
+    
+      
+      
+    
+    
+      
+      
+    
+    
      id
      module id
      meta
      metadata for all domains
      domainData
      list of data files for each domain
      mappings
      optional data frame containing stacked mappings for all domains
      standards
      optional list of data standards like the ones generated by detectStandard()
      
+
+
+  
      
+  
+
      
+
+
+      
      
+      
      
+  
      Developed by Jeremy Wildfire, Becca Krouse, Preston Burns, Xiao Ni, James Buchanan, Susan Duke.
      
+
      
+
+
      
+  
      Site built with pkgdown 1.6.1.
      
+
      
+
+      
      
+   
      
+
+  
+
+
+  
+
+
+
diff --git a/docs/reference/meta.html b/docs/reference/meta.html
new file mode 100644
index 00000000..083f97ae
--- /dev/null
+++ b/docs/reference/meta.html
@@ -0,0 +1,194 @@
+
+
+
+  
+  
+
+
+
+Metadata data frame containing information about the data mapping used to configure safetyGraphics charts. One record per unique data mapping — meta • safetyGraphics
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+  
+
+  
+    
      
+      
      
+      
+
+      
+
+      
      
+
+
      
+  
      
+    
      
+    
      Metadata data frame containing information about the data mapping used to configure safetyGraphics charts. One record per unique data mapping
      
+    Source: R/meta.R
+    
+    
      
+
+    
      
+    
      Metadata data frame containing information about the data mapping used to configure safetyGraphics charts. One record per unique data mapping
      
+    
      
+
+    
      meta
      
+
+
+    
      Format
      
+
+    
      A data frame with 31 rows and 7 columns
      
+
      domain
      Data domain
      
+
      text_key
      Text key indicating the setting name. '--' delimiter indicates a field level data mapping
      
+
      col_key
      Key for the column mapping
      
+
      field_key
      Key for the field mapping (if any)
      
+
      type
      type of mapping - "field" or "column"
      
+
      label
      Label
      
+
      description
      Description
      
+
      multiple
      Mapping supports multiple columns/fields
      
+
      standard_adam
      Default values for the ADaM data standard
      
+
      standard_sdtm
      Default values for the SDTM data standard
      
+
+
      
+
+    
      Source
      
+
+    
      Created for this package
      
+
+  
      
+  
+
      
+
+
+      
      
+      
      
+  
      Developed by Jeremy Wildfire, Becca Krouse, Preston Burns, Xiao Ni, James Buchanan, Susan Duke.
      
+
      
+
+
      
+  
      Site built with pkgdown 1.6.1.
      
+
      
+
+      
      
+   
      
+
+  
+
+
+  
+
+
+
diff --git a/docs/reference/prepareChart.html b/docs/reference/prepareChart.html
new file mode 100644
index 00000000..1175ab68
--- /dev/null
+++ b/docs/reference/prepareChart.html
@@ -0,0 +1,186 @@
+
+
+
+  
+  
+
+
+
+Prepare a chart object for safetyGraphcis — prepareChart • safetyGraphics
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+  
+
+  
+    
      
+      
      
+      
+
+      
+
+      
      
+
+
      
+  
      
+    
      
+    
      Prepare a chart object for safetyGraphcis
      
+    Source: R/prepareChart.R
+    
+    
      
+
+    
      
+    
      Sets default values and binds needed functions to a chart object based on chart type.
      
+    
      
+
+    
      prepareChart(chart)
      
+
+    
      Arguments
      
+    
+    
+    
+      
+      
+    
+    
      chart
      chart object like the one generated by makeChartConfig().
      
+
+    
      Value
      
+
+    
      returns the chart object with a new functions object added.
      
+
+  
      
+  
+
      
+
+
+      
      
+      
      
+  
      Developed by Jeremy Wildfire, Becca Krouse, Preston Burns, Xiao Ni, James Buchanan, Susan Duke.
      
+
      
+
+
      
+  
      Site built with pkgdown 1.6.1.
      
+
      
+
+      
      
+   
      
+
+  
+
+
+  
+
+
+
diff --git a/docs/reference/safetyGraphicsApp.html b/docs/reference/safetyGraphicsApp.html
index 4cdd80d8..78bdf351 100644
--- a/docs/reference/safetyGraphicsApp.html
+++ b/docs/reference/safetyGraphicsApp.html
@@ -6,25 +6,31 @@
 
 
 
-Run the interactive safety graphics builder — safetyGraphicsApp • safetyGraphics
+Run the core safetyGraphics App — safetyGraphicsApp • safetyGraphics
+
 
 
-
+
 
-
+
+
+
+
 
-
+
+
+
 
 
-
-
+
+
 
 
-
+
 
 
-
-
+
+
 
 
 
@@ -32,10 +38,10 @@
 
 
 
-
 
-
-
+
+
+
 
 
 
@@ -52,7 +58,7 @@
 
   
 
-  
+  
     
      
       
      
       
 
@@ -74,33 +80,38 @@
       
-      
       
        
         
      • 
   
@@ -121,65 +132,76 @@
 
        
   
        
     
        
-    
        Run the interactive safety graphics builder
        
+    
        Run the core safetyGraphics App
        
     Source:         R/safetyGraphicsApp.R
     
     
        
 
     
        
-    
-    
        Run the interactive safety graphics builder
        
-    
+    
        Run the core safetyGraphics App
        
     
        
 
-    
        safetyGraphicsApp(charts = NULL, maxFileSize = NULL,
-  settingsLocation = ".", customSettings = "customSettings.R",
-  loadData = FALSE)
        
-    
+    
        safetyGraphicsApp(
+  domainData = list(labs = safetyData::adam_adlbc, aes = safetyData::adam_adae, dm =
+    safetyData::adam_adsl),
+  meta = safetyGraphics::meta,
+  charts = NULL,
+  mapping = NULL,
+  autoMapping = TRUE,
+  filterDomain = "dm",
+  chartSettingsPaths = NULL
+)
        
+
     
        Arguments
        
     
+    
+      
+      
+    
+    
+      
+      
+    
-      
+      
-      
-      
+      
+      
-      
-      
+      
+      
-      
-      
+      
+      
-      
-      
+      
+      
        
     
        domainData
        named list of data.frames to be loaded in to the app. Sample AdAM data from the safetyData package used by default
        meta
        data frame containing the metadata for use in the app. See the preloaded file (?safetyGraphics::meta) for more data specifications and details. Defaults to safetyGraphics::meta.
        
     
        
       charts
        Character vector of charts to include
        list of charts in the format produced by safetyGraphics::makeChartConfig()
        		
     
        
     
        maxFileSize
        maximum file size in MB allowed for file upload
        		mapping
        list specifying the initial mapping values for each data mapping for each domain (e.g. list(aes= list(id_col='USUBJID', seq_col='AESEQ')).
        		
     
        
     
        settingsLocation
        folder location of user-defined settings metadata. Files should be named settingsMetadata.rda, chartsMetadata.rda and standardsMetadata.rda and use the same structure established in the /data folder. Defaults to current working directory.
        		autoMapping
        boolean indicating whether the app should attempt to automatically detect data standards and generate mappings for the data provided. Values specified in the mapping parameter overwrite automatically generated mappings when both are found. Defaults to true.
        		
     
        
     
        customSettings
        Name of R script containing settings customizations to be run before the app is initialized. This is the recommended way to add additional charts (via addChart()), settings (addSetting()) and data standards (addStandard()). default = 'settingsLocation/customSettings.R'
        		filterDomain
        domain used for the data/filter tab. Demographics ("dm") is used by default. Using a domain that is not one record per participant is not recommended.
        		
     
        
     
        loadData
        Option to pre-load data into the app. Defaults to FALSE.
        		chartSettingsPaths
        path(s) where customization functions are saved relative to your working directory. All charts can have itialization (e.g. myChart_Init.R) and static charts can have charting functions (e.g. myGraphic_Chart.R).   All R files in this folder are sourced and files with the correct naming convention are linked to the chart. See the Custom Charts vignette for more details.
        		
     
        
     
        
-    
 
-  
        
-  
+  
 
        
 
 
       
        
       
        
-  
        Developed by Jeremy Wildfire, Becca Krouse, Preston Burns, Xiao Ni, James Buchanan, Susan Duke, Interactive Safety Graphics Working Group.
        
+  
        Developed by Jeremy Wildfire, Becca Krouse, Preston Burns, Xiao Ni, James Buchanan, Susan Duke.
        
 
        
 
 
        
-  
        Site built with pkgdown 1.4.1.
        
+  
        Site built with pkgdown 1.6.1.
        
 
        
 
       
        
diff --git a/docs/reference/safetyGraphicsInit.html b/docs/reference/safetyGraphicsInit.html
new file mode 100644
index 00000000..4e13b67c
--- /dev/null
+++ b/docs/reference/safetyGraphicsInit.html
@@ -0,0 +1,195 @@
+
+
+
+  
+  
+
+
+
+App to select charts, load data and then initialize the core safetyGraphics app — safetyGraphicsInit • safetyGraphics
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+  
+
+  
+    
        
+      
        
+      
+
+      
+
+      
        
+
+
        
+  
        
+    
        
+    
        App to select charts, load data and then initialize the core safetyGraphics app
        
+    Source: R/safetyGraphicsInit.R
+    
+    
        
+
+    
        
+    
        App to select charts, load data and then initialize the core safetyGraphics app
        
+    
        
+
+    
        safetyGraphicsInit(
+  charts = makeChartConfig(),
+  delayTime = 1000,
+  maxFileSize = NULL
+)
        
+
+    
        Arguments
        
+    
+    
+    
+      
+      
+    
+    
+      
+      
+    
+    
+      
+      
+    
+    
        charts
        chart object
        delayTime
        time (in ms) between drawing app UI and starting server. Default set to 1000 (1 second), but could need to be higher on slow machine.
        maxFileSize
        maximum file size in MB allowed for file upload
        
+
+
+  
        
+  
+
        
+
+
+      
        
+      
        
+  
        Developed by Jeremy Wildfire, Becca Krouse, Preston Burns, Xiao Ni, James Buchanan, Susan Duke.
        
+
        
+
+
        
+  
        Site built with pkgdown 1.6.1.
        
+
        
+
+      
        
+   
        
+
+  
+
+
+  
+
+
+
diff --git a/docs/reference/safetyGraphicsServer.html b/docs/reference/safetyGraphicsServer.html
new file mode 100644
index 00000000..5ecd0eea
--- /dev/null
+++ b/docs/reference/safetyGraphicsServer.html
@@ -0,0 +1,220 @@
+
+
+
+  
+  
+
+
+
+Server for core safetyGraphics app including Home, Mapping, Filter, Charts and Settings modules. — safetyGraphicsServer • safetyGraphics
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+  
+
+  
+    
        
+      
        
+      
+
+      
+
+      
        
+
+
        
+  
        
+    
        
+    
        Server for core safetyGraphics app including Home, Mapping, Filter, Charts and Settings modules.
        
+    Source: R/mod_safetyGraphicsServer.R
+    
+    
        
+
+    
        
+    
        This function returns a server function suitable for use in shiny::runApp()
        
+    
        
+
+    
        safetyGraphicsServer(
+  input,
+  output,
+  session,
+  meta,
+  mapping,
+  domainData,
+  charts,
+  filterDomain
+)
        
+
+    
        Arguments
        
+    
+    
+    
+      
+      
+    
+    
+      
+      
+    
+    
+      
+      
+    
+    
+      
+      
+    
+    
+      
+      
+    
+    
+      
+      
+    
+    
+      
+      
+    
+    
+      
+      
+    
+    
        input
        Shiny input object
        output
        Shiny output object
        session
        Shiny session object
        meta
        data frame containing the metadata for use in the app. See the preloaded file (?safetyGraphics::meta) for more data specifications and details. Defaults to safetyGraphics::meta.
        mapping
        current mapping
        domainData
        named list of data.frames to be loaded in to the app.
        charts
        list of charts to include in the app
        filterDomain
        domain used for the data/filter tab. Demographics ("dm") is used by default. Using a domain that is not one record per participant is not recommended.
        
+
+
+  
        
+  
+
        
+
+
+      
        
+      
        
+  
        Developed by Jeremy Wildfire, Becca Krouse, Preston Burns, Xiao Ni, James Buchanan, Susan Duke.
        
+
        
+
+
        
+  
        Site built with pkgdown 1.6.1.
        
+
        
+
+      
        
+   
        
+
+  
+
+
+  
+
+
+
diff --git a/docs/reference/safetyGraphicsUI.html b/docs/reference/safetyGraphicsUI.html
new file mode 100644
index 00000000..8df0e044
--- /dev/null
+++ b/docs/reference/safetyGraphicsUI.html
@@ -0,0 +1,199 @@
+
+
+
+  
+  
+
+
+
+UI for the core safetyGraphics app including Home, Mapping, Filter, Charts and Settings modules. — safetyGraphicsUI • safetyGraphics
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+  
+
+  
+    
        
+      
        
+      
+
+      
+
+      
        
+
+
        
+  
        
+    
        
+    
        UI for the core safetyGraphics app including Home, Mapping, Filter, Charts and Settings modules.
        
+    Source: R/mod_safetyGraphicsUI.R
+    
+    
        
+
+    
        
+    
        UI for the core safetyGraphics app including Home, Mapping, Filter, Charts and Settings modules.
        
+    
        
+
+    
        safetyGraphicsUI(id, meta, domainData, mapping, standards)
        
+
+    
        Arguments
        
+    
+    
+    
+      
+      
+    
+    
+      
+      
+    
+    
+      
+      
+    
+    
+      
+      
+    
+    
+      
+      
+    
+    
        id
        module ID
        meta
        data frame containing the metadata for use in the app. See the preloaded file (?safetyGraphics::meta) for more data specifications and details. Defaults to safetyGraphics::meta.
        domainData
        named list of data.frames to be loaded in to the app.
        mapping
        data.frame specifying the initial values for each data mapping. If no mapping is provided, the app will attempt to generate one via detectStandard()
        standards
        a list of information regarding data standards. Each list item should use the format returned by safetyGraphics::detectStandard.
        
+
+
+  
        
+  
+
        
+
+
+      
        
+      
        
+  
        Developed by Jeremy Wildfire, Becca Krouse, Preston Burns, Xiao Ni, James Buchanan, Susan Duke.
        
+
        
+
+
        
+  
        Site built with pkgdown 1.6.1.
        
+
        
+
+      
        
+   
        
+
+  
+
+
+  
+
+
+
diff --git a/docs/reference/setMappingListValue.html b/docs/reference/setMappingListValue.html
new file mode 100644
index 00000000..2a64a5a7
--- /dev/null
+++ b/docs/reference/setMappingListValue.html
@@ -0,0 +1,208 @@
+
+
+
+  
+  
+
+
+
+Set the value for a given named parameter — setMappingListValue • safetyGraphics
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+  
+
+  
+    
        
+      
        
+      
+
+      
+
+      
        
+
+
        
+  
        
+    
        
+    
        Set the value for a given named parameter
        
+    Source: R/setMappingListValue.R
+    
+    
        
+
+    
        
+    
        Sets the value for a named parameter (key) to given value in a list (settings)
        
+    
        
+
+    
        setMappingListValue(key, value, settings, forceCreate = FALSE)
        
+
+    
        Arguments
        
+    
+    
+    
+      
+      
+    
+    
+      
+      
+    
+    
+      
+      
+    
+    
+      
+      
+    
+    
        key
        a list defining the position of parameter in the settings object.
        value
        the value to set
        settings
        The settings list used to generate a chart like eDISH()
        forceCreate
        Specifies whether the function should create a new list() when none exisits. This most commonly occurs when deeply nested objects.
        
+
+    
        Value
        
+
+    
        the updated settings object
        
+
+    
        Examples
        
+    
        testSet<-list(a=list(b="myValue"))
+safetyGraphics:::setMappingListValue(key=list("a","b"), value="notMyValue", settings=testSet) 
+
        #> $a
+#> $a$b
+#> [1] "notMyValue"
+#> 
+#> 
        #returns list(a=list(b="notMyValue")))
+
+
        
+  
        
+  
+
        
+
+
+      
        
+      
        
+  
        Developed by Jeremy Wildfire, Becca Krouse, Preston Burns, Xiao Ni, James Buchanan, Susan Duke.
        
+
        
+
+
        
+  
        Site built with pkgdown 1.6.1.
        
+
        
+
+      
        
+   
        
+
+  
+
+
+  
+
+
+
diff --git a/docs/reference/settingsCharts.html b/docs/reference/settingsCharts.html
new file mode 100644
index 00000000..0eb8c4cb
--- /dev/null
+++ b/docs/reference/settingsCharts.html
@@ -0,0 +1,195 @@
+
+
+
+  
+  
+
+
+
+Server for settings tab showing details for the charts loaded in the app — settingsCharts • safetyGraphics
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+  
+
+  
+    
        
+      
        
+      
+
+      
+
+      
        
+
+
        
+  
        
+    
        
+    
        Server for settings tab showing details for the charts loaded in the app
        
+    Source: R/mod_settingsCharts.R
+    
+    
        
+
+    
        
+    
        Server for settings tab showing details for the charts loaded in the app
        
+    
        
+
+    
        settingsCharts(input, output, session, charts)
        
+
+    
        Arguments
        
+    
+    
+    
+      
+      
+    
+    
+      
+      
+    
+    
+      
+      
+    
+    
+      
+      
+    
+    
        input
        Shiny input object
        output
        Shiny output object
        session
        Shiny session object
        charts
        list data frame summarizing the charts
        
+
+
+  
        
+  
+
        
+
+
+      
        
+      
        
+  
        Developed by Jeremy Wildfire, Becca Krouse, Preston Burns, Xiao Ni, James Buchanan, Susan Duke.
        
+
        
+
+
        
+  
        Site built with pkgdown 1.6.1.
        
+
        
+
+      
        
+   
        
+
+  
+
+
+  
+
+
+
diff --git a/docs/reference/settingsChartsUI.html b/docs/reference/settingsChartsUI.html
new file mode 100644
index 00000000..f039166c
--- /dev/null
+++ b/docs/reference/settingsChartsUI.html
@@ -0,0 +1,183 @@
+
+
+
+  
+  
+
+
+
+UI for settings tab showing details for the charts loaded in the app — settingsChartsUI • safetyGraphics
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+  
+
+  
+    
        
+      
        
+      
+
+      
+
+      
        
+
+
        
+  
        
+    
        
+    
        UI for settings tab showing details for the charts loaded in the app
        
+    Source: R/mod_settingsCharts.R
+    
+    
        
+
+    
        
+    
        UI for settings tab showing details for the charts loaded in the app
        
+    
        
+
+    
        settingsChartsUI(id)
        
+
+    
        Arguments
        
+    
+    
+    
+      
+      
+    
+    
        id
        module id
        
+
+
+  
        
+  
+
        
+
+
+      
        
+      
        
+  
        Developed by Jeremy Wildfire, Becca Krouse, Preston Burns, Xiao Ni, James Buchanan, Susan Duke.
        
+
        
+
+
        
+  
        Site built with pkgdown 1.6.1.
        
+
        
+
+      
        
+   
        
+
+  
+
+
+  
+
+
+
diff --git a/docs/reference/settingsCode.html b/docs/reference/settingsCode.html
new file mode 100644
index 00000000..80c0c235
--- /dev/null
+++ b/docs/reference/settingsCode.html
@@ -0,0 +1,203 @@
+
+
+
+  
+  
+
+
+
+Server for settings tab providing code to re-start the app with current data/settings — settingsCode • safetyGraphics
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+  
+
+  
+    
        
+      
        
+      
+
+      
+
+      
        
+
+
        
+  
        
+    
        
+    
        Server for settings tab providing code to re-start the app with current data/settings
        
+    Source: R/mod_settingsCode.R
+    
+    
        
+
+    
        
+    
        Server for settings tab providing code to re-start the app with current data/settings
        
+    
        
+
+    
        settingsCode(input, output, session, mapping, charts, domainData)
        
+
+    
        Arguments
        
+    
+    
+    
+      
+      
+    
+    
+      
+      
+    
+    
+      
+      
+    
+    
+      
+      
+    
+    
+      
+      
+    
+    
+      
+      
+    
+    
        input
        Shiny input object
        output
        Shiny output object
        session
        Shiny session object
        mapping
        mapping
        charts
        charts
        domainData
        data list
        
+
+
+  
        
+  
+
        
+
+
+      
        
+      
        
+  
        Developed by Jeremy Wildfire, Becca Krouse, Preston Burns, Xiao Ni, James Buchanan, Susan Duke.
        
+
        
+
+
        
+  
        Site built with pkgdown 1.6.1.
        
+
        
+
+      
        
+   
        
+
+  
+
+
+  
+
+
+
diff --git a/docs/reference/settingsCodeUI.html b/docs/reference/settingsCodeUI.html
new file mode 100644
index 00000000..543ec4f7
--- /dev/null
+++ b/docs/reference/settingsCodeUI.html
@@ -0,0 +1,183 @@
+
+
+
+  
+  
+
+
+
+UI for settings tab providing code to re-start the app with current data/settings — settingsCodeUI • safetyGraphics
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+  
+
+  
+    
        
+      
        
+      
+
+      
+
+      
        
+
+
        
+  
        
+    
        
+    
        UI for settings tab providing code to re-start the app with current data/settings
        
+    Source: R/mod_settingsCode.R
+    
+    
        
+
+    
        
+    
        UI for settings tab providing code to re-start the app with current data/settings
        
+    
        
+
+    
        settingsCodeUI(id)
        
+
+    
        Arguments
        
+    
+    
+    
+      
+      
+    
+    
        id
        module ID
        
+
+
+  
        
+  
+
        
+
+
+      
        
+      
        
+  
        Developed by Jeremy Wildfire, Becca Krouse, Preston Burns, Xiao Ni, James Buchanan, Susan Duke.
        
+
        
+
+
        
+  
        Site built with pkgdown 1.6.1.
        
+
        
+
+      
        
+   
        
+
+  
+
+
+  
+
+
+
diff --git a/docs/reference/settingsData.html b/docs/reference/settingsData.html
new file mode 100644
index 00000000..fd0b7f86
--- /dev/null
+++ b/docs/reference/settingsData.html
@@ -0,0 +1,195 @@
+
+
+
+  
+  
+
+
+
+Server for settings tab showing current data — settingsData • safetyGraphics
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+  
+
+  
+    
        
+      
        
+      
+
+      
+
+      
        
+
+
        
+  
        
+    
        
+    
        Server for settings tab showing current data
        
+    Source: R/mod_settingsData.R
+    
+    
        
+
+    
        
+    
        Server for settings tab showing current data
        
+    
        
+
+    
        settingsData(input, output, session, domains)
        
+
+    
        Arguments
        
+    
+    
+    
+      
+      
+    
+    
+      
+      
+    
+    
+      
+      
+    
+    
+      
+      
+    
+    
        input
        Shiny input object
        output
        Shiny output object
        session
        Shiny session object
        domains
        named list of the data.frames for each domain
        
+
+
+  
        
+  
+
        
+
+
+      
        
+      
        
+  
        Developed by Jeremy Wildfire, Becca Krouse, Preston Burns, Xiao Ni, James Buchanan, Susan Duke.
        
+
        
+
+
        
+  
        Site built with pkgdown 1.6.1.
        
+
        
+
+      
        
+   
        
+
+  
+
+
+  
+
+
+
diff --git a/docs/reference/settingsDataUI.html b/docs/reference/settingsDataUI.html
new file mode 100644
index 00000000..675a0629
--- /dev/null
+++ b/docs/reference/settingsDataUI.html
@@ -0,0 +1,183 @@
+
+
+
+  
+  
+
+
+
+UI for settings tab showing current data — settingsDataUI • safetyGraphics
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+  
+
+  
+    
        
+      
        
+      
+
+      
+
+      
        
+
+
        
+  
        
+    
        
+    
        UI for settings tab showing current data
        
+    Source: R/mod_settingsData.R
+    
+    
        
+
+    
        
+    
        UI for settings tab showing current data
        
+    
        
+
+    
        settingsDataUI(id)
        
+
+    
        Arguments
        
+    
+    
+    
+      
+      
+    
+    
        id
        module id
        
+
+
+  
        
+  
+
        
+
+
+      
        
+      
        
+  
        Developed by Jeremy Wildfire, Becca Krouse, Preston Burns, Xiao Ni, James Buchanan, Susan Duke.
        
+
        
+
+
        
+  
        Site built with pkgdown 1.6.1.
        
+
        
+
+      
        
+   
        
+
+  
+
+
+  
+
+
+
diff --git a/docs/reference/settingsMapping.html b/docs/reference/settingsMapping.html
new file mode 100644
index 00000000..71d4a20b
--- /dev/null
+++ b/docs/reference/settingsMapping.html
@@ -0,0 +1,199 @@
+
+
+
+  
+  
+
+
+
+Server for settings tab showing current mapping — settingsMapping • safetyGraphics
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+  
+
+  
+    
        
+      
        
+      
+
+      
+
+      
        
+
+
        
+  
        
+    
        
+    
        Server for settings tab showing current mapping
        
+    Source: R/mod_settingsMapping.R
+    
+    
        
+
+    
        
+    
        Server for settings tab showing current mapping
        
+    
        
+
+    
        settingsMapping(input, output, session, metadata, mapping)
        
+
+    
        Arguments
        
+    
+    
+    
+      
+      
+    
+    
+      
+      
+    
+    
+      
+      
+    
+    
+      
+      
+    
+    
+      
+      
+    
+    
        input
        Shiny input object
        output
        Shiny output object
        session
        Shiny session object
        metadata
        Data mapping metadata used for initial loading of app
        mapping
        reactive data frame representing the current metadata mapping. columns = "domain", "text_id" and "current"
        
+
+
+  
        
+  
+
        
+
+
+      
        
+      
        
+  
        Developed by Jeremy Wildfire, Becca Krouse, Preston Burns, Xiao Ni, James Buchanan, Susan Duke.
        
+
        
+
+
        
+  
        Site built with pkgdown 1.6.1.
        
+
        
+
+      
        
+   
        
+
+  
+
+
+  
+
+
+
diff --git a/docs/reference/settingsMappingUI.html b/docs/reference/settingsMappingUI.html
new file mode 100644
index 00000000..ac16a70b
--- /dev/null
+++ b/docs/reference/settingsMappingUI.html
@@ -0,0 +1,183 @@
+
+
+
+  
+  
+
+
+
+UI for settings tab showing current mapping — settingsMappingUI • safetyGraphics
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+  
+
+  
+    
        
+      
        
+      
+
+      
+
+      
        
+
+
        
+  
        
+    
        
+    
        UI for settings tab showing current mapping
        
+    Source: R/mod_settingsMapping.R
+    
+    
        
+
+    
        
+    
        UI for settings tab showing current mapping
        
+    
        
+
+    
        settingsMappingUI(id)
        
+
+    
        Arguments
        
+    
+    
+    
+      
+      
+    
+    
        id
        module id
        
+
+
+  
        
+  
+
        
+
+
+      
        
+      
        
+  
        Developed by Jeremy Wildfire, Becca Krouse, Preston Burns, Xiao Ni, James Buchanan, Susan Duke.
        
+
        
+
+
        
+  
        Site built with pkgdown 1.6.1.
        
+
        
+
+      
        
+   
        
+
+  
+
+
+  
+
+
+
diff --git a/docs/reference/settingsTab.html b/docs/reference/settingsTab.html
new file mode 100644
index 00000000..6e7d3907
--- /dev/null
+++ b/docs/reference/settingsTab.html
@@ -0,0 +1,207 @@
+
+
+
+  
+  
+
+
+
+Server for the setting page — settingsTab • safetyGraphics
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+  
+
+  
+    
        
+      
        
+      
+
+      
+
+      
        
+
+
        
+  
        
+    
        
+    
        Server for the setting page
        
+    Source: R/mod_settingsTab.R
+    
+    
        
+
+    
        
+    
        Server for the setting page
        
+    
        
+
+    
        settingsTab(input, output, session, domains, metadata, mapping, charts)
        
+
+    
        Arguments
        
+    
+    
+    
+      
+      
+    
+    
+      
+      
+    
+    
+      
+      
+    
+    
+      
+      
+    
+    
+      
+      
+    
+    
+      
+      
+    
+    
+      
+      
+    
+    
        input
        Shiny input object
        output
        Shiny output object
        session
        Shiny session object
        domains
        domains
        metadata
        metadata
        mapping
        mapping
        charts
        charts
        
+
+
+  
        
+  
+
        
+
+
+      
        
+      
        
+  
        Developed by Jeremy Wildfire, Becca Krouse, Preston Burns, Xiao Ni, James Buchanan, Susan Duke.
        
+
        
+
+
        
+  
        Site built with pkgdown 1.6.1.
        
+
        
+
+      
        
+   
        
+
+  
+
+
+  
+
+
+
diff --git a/docs/reference/settingsTabUI.html b/docs/reference/settingsTabUI.html
new file mode 100644
index 00000000..0f54bae1
--- /dev/null
+++ b/docs/reference/settingsTabUI.html
@@ -0,0 +1,183 @@
+
+
+
+  
+  
+
+
+
+UI for the settings tab — settingsTabUI • safetyGraphics
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+  
+
+  
+    
        
+      
        
+      
+
+      
+
+      
        
+
+
        
+  
        
+    
        
+    
        UI for the settings tab
        
+    Source: R/mod_settingsTab.R
+    
+    
        
+
+    
        
+    
        UI for the settings tab
        
+    
        
+
+    
        settingsTabUI(id)
        
+
+    
        Arguments
        
+    
+    
+    
+      
+      
+    
+    
        id
        module ID
        
+
+
+  
        
+  
+
        
+
+
+      
        
+      
        
+  
        Developed by Jeremy Wildfire, Becca Krouse, Preston Burns, Xiao Ni, James Buchanan, Susan Duke.
        
+
        
+
+
        
+  
        Site built with pkgdown 1.6.1.
        
+
        
+
+      
        
+   
        
+
+  
+
+
+  
+
+
+
diff --git a/docs/reference/textKeysToList.html b/docs/reference/textKeysToList.html
index 1a43f4cb..0d2ef132 100644
--- a/docs/reference/textKeysToList.html
+++ b/docs/reference/textKeysToList.html
@@ -8,23 +8,29 @@
 
 Helper function to convert keys from text to nested lists — textKeysToList • safetyGraphics
 
+
 
-
+
 
-
+
+
+
+
 
-
+
+
+
 
 
-
-
+
+
 
 
-
+
 
 
-
-
+
+
 
 
 
@@ -32,10 +38,10 @@
 
 
 
-
 
+
 
-
+
 
 
 
@@ -52,7 +58,7 @@
 
   
 
-  
+  
     
        
       
        
       
 
@@ -74,33 +80,38 @@
       
-      
       
        
 
     
        
-    
     
        Convert settings keys from text vectors (using the "--" delimiter) to a list of lists
        
-    
     
        
 
-    
        textKeysToList(textKeys)
        
-    
+    
        textKeysToList(textKeys)
        
+
     
        Arguments
        
     
@@ -142,21 +151,22 @@ 
        Arg
       
        
     
        a list (or vector) of character keys using the "--" delimiter to indicate hierarchy
        		
     
        
     
        
-    
+
     
        Value
        
 
     
        A list of unnamed lists, with position in the nested list indicating hierarchy
        
-    
 
     
        Examples
        
-    
        safetyGraphics:::textKeysToList("id_col")
        #> [[1]]
+    
        safetyGraphics:::textKeysToList("id_col") 
+
        #> [[1]]
 #> [[1]][[1]]
 #> [1] "id_col"
 #> 
 #> 
        #list(list("id_col"))
 
 #list(list("id_col"),list("measure_col","label"))
-safetyGraphics:::textKeysToList(c("id_col","measure_col--label"))
        #> [[1]]
+safetyGraphics:::textKeysToList(c("id_col","measure_col--label")) 
+
        #> [[1]]
 #> [[1]][[1]]
 #> [1] "id_col"
 #> 
@@ -171,27 +181,21 @@ 
        Examp
 #> 
        
 
        
   
        
-  
 
 
       
        
       
        
-  
        Developed by Jeremy Wildfire, Becca Krouse, Preston Burns, Xiao Ni, James Buchanan, Susan Duke, Interactive Safety Graphics Working Group.
        
+  
        Developed by Jeremy Wildfire, Becca Krouse, Preston Burns, Xiao Ni, James Buchanan, Susan Duke.
        
 
        
 
 
        
-  
        Site built with pkgdown 1.4.1.
        
+  
        Site built with pkgdown 1.6.1.
        
 
        
 
       
        
diff --git a/docs/sitemap.xml b/docs/sitemap.xml
index 9a4c6e06..6760540d 100644
--- a/docs/sitemap.xml
+++ b/docs/sitemap.xml
@@ -7,102 +7,162 @@
     https://pages.github.com/SafetyGraphics/safetyGraphics/reference/SafetyGraphics.html
   
   
-    https://pages.github.com/SafetyGraphics/safetyGraphics/reference/addChart.html
+    https://pages.github.com/SafetyGraphics/safetyGraphics/reference/app_startup.html
   
   
-    https://pages.github.com/SafetyGraphics/safetyGraphics/reference/addSetting.html
+    https://pages.github.com/SafetyGraphics/safetyGraphics/reference/chartsNav.html
   
   
-    https://pages.github.com/SafetyGraphics/safetyGraphics/reference/adlbc.html
+    https://pages.github.com/SafetyGraphics/safetyGraphics/reference/chartsTab.html
   
   
-    https://pages.github.com/SafetyGraphics/safetyGraphics/reference/chartRenderer-shiny.html
+    https://pages.github.com/SafetyGraphics/safetyGraphics/reference/chartsTabUI.html
   
   
-    https://pages.github.com/SafetyGraphics/safetyGraphics/reference/chartRenderer.html
+    https://pages.github.com/SafetyGraphics/safetyGraphics/reference/detectStandard.html
   
   
-    https://pages.github.com/SafetyGraphics/safetyGraphics/reference/chartsMetadata.html
+    https://pages.github.com/SafetyGraphics/safetyGraphics/reference/evaluateStandard.html
   
   
-    https://pages.github.com/SafetyGraphics/safetyGraphics/reference/checkColumn.html
+    https://pages.github.com/SafetyGraphics/safetyGraphics/reference/filterTab.html
   
   
-    https://pages.github.com/SafetyGraphics/safetyGraphics/reference/checkField.html
+    https://pages.github.com/SafetyGraphics/safetyGraphics/reference/filterTabChecks.html
   
   
-    https://pages.github.com/SafetyGraphics/safetyGraphics/reference/checkNumeric.html
+    https://pages.github.com/SafetyGraphics/safetyGraphics/reference/filterTabUI.html
   
   
-    https://pages.github.com/SafetyGraphics/safetyGraphics/reference/checkRequired.html
+    https://pages.github.com/SafetyGraphics/safetyGraphics/reference/generateMappingList.html
   
   
-    https://pages.github.com/SafetyGraphics/safetyGraphics/reference/createChart.html
+    https://pages.github.com/SafetyGraphics/safetyGraphics/reference/hasColumn.html
   
   
-    https://pages.github.com/SafetyGraphics/safetyGraphics/reference/detectStandard.html
+    https://pages.github.com/SafetyGraphics/safetyGraphics/reference/hasField.html
   
   
-    https://pages.github.com/SafetyGraphics/safetyGraphics/reference/evaluateStandard.html
+    https://pages.github.com/SafetyGraphics/safetyGraphics/reference/homeTab.html
   
   
-    https://pages.github.com/SafetyGraphics/safetyGraphics/reference/generateSettings.html
+    https://pages.github.com/SafetyGraphics/safetyGraphics/reference/homeTabUI.html
   
   
-    https://pages.github.com/SafetyGraphics/safetyGraphics/reference/generateShell.html
+    https://pages.github.com/SafetyGraphics/safetyGraphics/reference/loadCharts.html
   
   
-    https://pages.github.com/SafetyGraphics/safetyGraphics/reference/getRequiredSettings.html
+    https://pages.github.com/SafetyGraphics/safetyGraphics/reference/loadChartsUI.html
   
   
-    https://pages.github.com/SafetyGraphics/safetyGraphics/reference/getSettingKeys.html
+    https://pages.github.com/SafetyGraphics/safetyGraphics/reference/loadData.html
   
   
-    https://pages.github.com/SafetyGraphics/safetyGraphics/reference/getSettingValue.html
+    https://pages.github.com/SafetyGraphics/safetyGraphics/reference/loadDataUI.html
   
   
-    https://pages.github.com/SafetyGraphics/safetyGraphics/reference/getSettingsMetadata.html
+    https://pages.github.com/SafetyGraphics/safetyGraphics/reference/makeChartConfig.html
   
   
-    https://pages.github.com/SafetyGraphics/safetyGraphics/reference/hasColumn.html
+    https://pages.github.com/SafetyGraphics/safetyGraphics/reference/makeChartExport.html
   
   
-    https://pages.github.com/SafetyGraphics/safetyGraphics/reference/hasField.html
+    https://pages.github.com/SafetyGraphics/safetyGraphics/reference/makeChartParams.html
+  
+  
+    https://pages.github.com/SafetyGraphics/safetyGraphics/reference/makeChartSummary.html
+  
+  
+    https://pages.github.com/SafetyGraphics/safetyGraphics/reference/makeMapping.html
+  
+  
+    https://pages.github.com/SafetyGraphics/safetyGraphics/reference/mappingColumn.html
+  
+  
+    https://pages.github.com/SafetyGraphics/safetyGraphics/reference/mappingColumnUI.html
+  
+  
+    https://pages.github.com/SafetyGraphics/safetyGraphics/reference/mappingDomain.html
+  
+  
+    https://pages.github.com/SafetyGraphics/safetyGraphics/reference/mappingDomainUI.html
+  
+  
+    https://pages.github.com/SafetyGraphics/safetyGraphics/reference/mappingSelect.html
+  
+  
+    https://pages.github.com/SafetyGraphics/safetyGraphics/reference/mappingSelectUI.html
+  
+  
+    https://pages.github.com/SafetyGraphics/safetyGraphics/reference/mappingTab.html
+  
+  
+    https://pages.github.com/SafetyGraphics/safetyGraphics/reference/mappingTabUI.html
   
   
-    https://pages.github.com/SafetyGraphics/safetyGraphics/reference/removeCharts.html
+    https://pages.github.com/SafetyGraphics/safetyGraphics/reference/meta.html
   
   
-    https://pages.github.com/SafetyGraphics/safetyGraphics/reference/removeSettings.html
+    https://pages.github.com/SafetyGraphics/safetyGraphics/reference/prepareChart.html
   
   
     https://pages.github.com/SafetyGraphics/safetyGraphics/reference/safetyGraphicsApp.html
   
   
-    https://pages.github.com/SafetyGraphics/safetyGraphics/reference/setSettingsValue.html
+    https://pages.github.com/SafetyGraphics/safetyGraphics/reference/safetyGraphicsInit.html
   
   
-    https://pages.github.com/SafetyGraphics/safetyGraphics/reference/settingsMetadata.html
+    https://pages.github.com/SafetyGraphics/safetyGraphics/reference/safetyGraphicsServer.html
   
   
-    https://pages.github.com/SafetyGraphics/safetyGraphics/reference/standardsMetadata.html
+    https://pages.github.com/SafetyGraphics/safetyGraphics/reference/safetyGraphicsUI.html
   
   
-    https://pages.github.com/SafetyGraphics/safetyGraphics/reference/textKeysToList.html
+    https://pages.github.com/SafetyGraphics/safetyGraphics/reference/setMappingListValue.html
   
   
-    https://pages.github.com/SafetyGraphics/safetyGraphics/reference/trimData.html
+    https://pages.github.com/SafetyGraphics/safetyGraphics/reference/settingsCharts.html
+  
+  
+    https://pages.github.com/SafetyGraphics/safetyGraphics/reference/settingsChartsUI.html
+  
+  
+    https://pages.github.com/SafetyGraphics/safetyGraphics/reference/settingsCode.html
+  
+  
+    https://pages.github.com/SafetyGraphics/safetyGraphics/reference/settingsCodeUI.html
+  
+  
+    https://pages.github.com/SafetyGraphics/safetyGraphics/reference/settingsData.html
+  
+  
+    https://pages.github.com/SafetyGraphics/safetyGraphics/reference/settingsDataUI.html
+  
+  
+    https://pages.github.com/SafetyGraphics/safetyGraphics/reference/settingsMapping.html
+  
+  
+    https://pages.github.com/SafetyGraphics/safetyGraphics/reference/settingsMappingUI.html
+  
+  
+    https://pages.github.com/SafetyGraphics/safetyGraphics/reference/settingsTab.html
+  
+  
+    https://pages.github.com/SafetyGraphics/safetyGraphics/reference/settingsTabUI.html
+  
+  
+    https://pages.github.com/SafetyGraphics/safetyGraphics/reference/textKeysToList.html
   
   
-    https://pages.github.com/SafetyGraphics/safetyGraphics/reference/trimSettings.html
+    https://pages.github.com/SafetyGraphics/safetyGraphics/articles/Cookbook.html
   
   
-    https://pages.github.com/SafetyGraphics/safetyGraphics/reference/validateSettings.html
+    https://pages.github.com/SafetyGraphics/safetyGraphics/articles/TechnicalFAQ.html
   
   
-    https://pages.github.com/SafetyGraphics/safetyGraphics/articles/customWorkflows.html
+    https://pages.github.com/SafetyGraphics/safetyGraphics/articles/chartConfiguration.html
   
   
-    https://pages.github.com/SafetyGraphics/safetyGraphics/articles/shinyUserGuide.html
+    https://pages.github.com/SafetyGraphics/safetyGraphics/articles/intro.html
   
 
diff --git a/man/chartsNav.Rd b/man/chartsNav.Rd
index f01c3961..d0197e34 100644
--- a/man/chartsNav.Rd
+++ b/man/chartsNav.Rd
@@ -2,7 +2,7 @@
 % Please edit documentation in R/mod_chartsNav.R
 \name{chartsNav}
 \alias{chartsNav}
-\title{Add a navbar tab that initializes the Chart Module UI}
+\title{Adds a navbar tab that initializes the Chart Module UI}
 \usage{
 chartsNav(chart, ns)
 }
@@ -12,5 +12,5 @@ chartsNav(chart, ns)
 \item{ns}{namespace}
 }
 \description{
-Add a navbar tab that initializes the Chart Module UI
+Adds a navbar tab that initializes the Chart Module UI
 }
diff --git a/man/chartsTab.Rd b/man/chartsTab.Rd
index 92d5daee..090efb6c 100644
--- a/man/chartsTab.Rd
+++ b/man/chartsTab.Rd
@@ -2,7 +2,7 @@
 % Please edit documentation in R/mod_chartsTab.R
 \name{chartsTab}
 \alias{chartsTab}
-\title{home tab - server}
+\title{Server for chart module, designed to be re-used for each chart generated.}
 \usage{
 chartsTab(input, output, session, chart, data, mapping)
 }
@@ -13,12 +13,12 @@ chartsTab(input, output, session, chart, data, mapping)
 
 \item{session}{An environment that can be used to access information and functionality relating to the session}
 
-\item{chart}{list containing a safetyGraphics chart object. see custom chart vignette for details.}
+\item{chart}{list containing a safetyGraphics chart object like those returned by \link{makeChartConfig}.}
 
 \item{data}{named list of current data sets (Reactive).}
 
 \item{mapping}{tibble capturing the current data mappings (Reactive).}
 }
 \description{
-server for the display of the chart tab
+Server for chart module, designed to be re-used for each chart generated.
 }
diff --git a/man/chartsTabUI.Rd b/man/chartsTabUI.Rd
index f2e3685a..f27a9aea 100644
--- a/man/chartsTabUI.Rd
+++ b/man/chartsTabUI.Rd
@@ -2,15 +2,15 @@
 % Please edit documentation in R/mod_chartsTab.R
 \name{chartsTabUI}
 \alias{chartsTabUI}
-\title{Charts Tab}
+\title{UI for chart module, designed to be re-used for each chart generated.}
 \usage{
 chartsTabUI(id, chart)
 }
 \arguments{
 \item{id}{module id}
 
-\item{chart}{list containing chart specifications}
+\item{chart}{list containing chart specifications like those returned by \link{makeChartConfig}.}
 }
 \description{
-Charting module
+UI for chart module, designed to be re-used for each chart generated.
 }
diff --git a/man/filterTab.Rd b/man/filterTab.Rd
index b643f2f2..0f82a09c 100644
--- a/man/filterTab.Rd
+++ b/man/filterTab.Rd
@@ -2,7 +2,7 @@
 % Please edit documentation in R/mod_filterTab.R
 \name{filterTab}
 \alias{filterTab}
-\title{filter module server}
+\title{Server for the filter module in datamods::filter_data_ui}
 \usage{
 filterTab(
   input,
@@ -36,5 +36,5 @@ filterTab(
 filtered data set
 }
 \description{
-server function that facilitates the data filtering with the datamods::filter_data_server module
+Server for the filter module in datamods::filter_data_ui
 }
diff --git a/man/filterTabChecks.Rd b/man/filterTabChecks.Rd
index 8734945a..247c462b 100644
--- a/man/filterTabChecks.Rd
+++ b/man/filterTabChecks.Rd
@@ -2,7 +2,7 @@
 % Please edit documentation in R/mod_filterTabChecks.R
 \name{filterTabChecks}
 \alias{filterTabChecks}
-\title{filter module checks}
+\title{Checks for whether the current data and settings support a filter tab}
 \usage{
 filterTabChecks(domainData, filterDomain, current_mapping)
 }
@@ -17,5 +17,5 @@ filterTabChecks(domainData, filterDomain, current_mapping)
 reactive that returns a boolean indicating whether the checks passed and filtering can be initiailized
 }
 \description{
-function that checks whether the current data and settings are appropriate for the filter tab
+Checks for whether the current data and settings support a filter tab
 }
diff --git a/man/filterTabUI.Rd b/man/filterTabUI.Rd
index 0f57f5ad..9c0841d5 100644
--- a/man/filterTabUI.Rd
+++ b/man/filterTabUI.Rd
@@ -2,7 +2,7 @@
 % Please edit documentation in R/mod_filterTab.R
 \name{filterTabUI}
 \alias{filterTabUI}
-\title{filterTabUI}
+\title{UI for the filter module in datamods::filter_data_ui}
 \usage{
 filterTabUI(id)
 }
@@ -10,5 +10,5 @@ filterTabUI(id)
 \item{id}{module id}
 }
 \description{
-UI that facilitates the filtering data with datamods::filter_data_ui
+UI for the filter module in datamods::filter_data_ui
 }
diff --git a/man/homeTab.Rd b/man/homeTab.Rd
index 5446e62e..17447951 100644
--- a/man/homeTab.Rd
+++ b/man/homeTab.Rd
@@ -2,7 +2,7 @@
 % Please edit documentation in R/mod_homeTab.R
 \name{homeTab}
 \alias{homeTab}
-\title{home tab - server}
+\title{Server for the filter module in datamods::filter_data_ui}
 \usage{
 homeTab(input, output, session)
 }
@@ -14,5 +14,5 @@ homeTab(input, output, session)
 \item{session}{mod session}
 }
 \description{
-server for the display of the home tab
+Server for the filter module in datamods::filter_data_ui
 }
diff --git a/man/homeTabUI.Rd b/man/homeTabUI.Rd
index 523e6efb..eb271cfd 100644
--- a/man/homeTabUI.Rd
+++ b/man/homeTabUI.Rd
@@ -2,7 +2,7 @@
 % Please edit documentation in R/mod_homeTab.R
 \name{homeTabUI}
 \alias{homeTabUI}
-\title{Home Tab}
+\title{UI for the home module}
 \usage{
 homeTabUI(id)
 }
@@ -10,5 +10,5 @@ homeTabUI(id)
 \item{id}{module id}
 }
 \description{
-Home Tab - sub-module showing details for the data loaded in the app - UI
+UI for the home module
 }
diff --git a/man/loadCharts.Rd b/man/loadCharts.Rd
index 020a279a..f05f3d70 100644
--- a/man/loadCharts.Rd
+++ b/man/loadCharts.Rd
@@ -2,7 +2,7 @@
 % Please edit documentation in R/mod_loadCharts.R
 \name{loadCharts}
 \alias{loadCharts}
-\title{loadCharts}
+\title{Server for the chart loading module used in safetyGraphicsInit()}
 \usage{
 loadCharts(input, output, session, charts = makeChartConfig())
 }
@@ -13,8 +13,8 @@ loadCharts(input, output, session, charts = makeChartConfig())
 
 \item{session}{Shiny session object}
 
-\item{charts}{Initial list of charts}
+\item{charts}{list containing chart specifications like those returned by \link{makeChartConfig}.}
 }
 \description{
-server that facilitates selection of charts for safetyGraphicsApp
+Server for the chart loading module used in safetyGraphicsInit()
 }
diff --git a/man/loadChartsUI.Rd b/man/loadChartsUI.Rd
index 745579c8..174e180e 100644
--- a/man/loadChartsUI.Rd
+++ b/man/loadChartsUI.Rd
@@ -2,15 +2,15 @@
 % Please edit documentation in R/mod_loadCharts.R
 \name{loadChartsUI}
 \alias{loadChartsUI}
-\title{loadChartsUI}
+\title{UI for the chart loading module used in safetyGraphicsInit()}
 \usage{
 loadChartsUI(id, charts = makeChartConfig())
 }
 \arguments{
 \item{id}{module id}
 
-\item{charts}{list of charts}
+\item{charts}{list containing chart specifications like those returned by \link{makeChartConfig}.}
 }
 \description{
-UI that helps users pick charts
+UI for the chart loading module used in safetyGraphicsInit()
 }
diff --git a/man/loadData.Rd b/man/loadData.Rd
index 7cc7cc18..d47020a7 100644
--- a/man/loadData.Rd
+++ b/man/loadData.Rd
@@ -2,7 +2,7 @@
 % Please edit documentation in R/mod_loadData.R
 \name{loadData}
 \alias{loadData}
-\title{loadDataServer}
+\title{Server for the data loading module used in safetyGraphicsInit()}
 \usage{
 loadData(input, output, session, domain)
 }
@@ -16,5 +16,5 @@ loadData(input, output, session, domain)
 \item{domain}{data domain to be loaded}
 }
 \description{
-UI that facilitates the mapping of a column data domain
+Server for the data loading module used in safetyGraphicsInit()
 }
diff --git a/man/loadDataUI.Rd b/man/loadDataUI.Rd
index 9d9341d5..2ed708d8 100644
--- a/man/loadDataUI.Rd
+++ b/man/loadDataUI.Rd
@@ -2,7 +2,7 @@
 % Please edit documentation in R/mod_loadData.R
 \name{loadDataUI}
 \alias{loadDataUI}
-\title{loadDataUI}
+\title{UI for the data loading module used in safetyGraphicsInit()}
 \usage{
 loadDataUI(id, domain = NULL)
 }
@@ -12,5 +12,5 @@ loadDataUI(id, domain = NULL)
 \item{domain}{character vector with domains to be loaded}
 }
 \description{
-UI that facilitates the mapping of a column data domain
+UI for the data loading module used in safetyGraphicsInit()
 }
diff --git a/man/mappingColumn.Rd b/man/mappingColumn.Rd
index 2a843a0f..f878fc8d 100644
--- a/man/mappingColumn.Rd
+++ b/man/mappingColumn.Rd
@@ -2,7 +2,7 @@
 % Please edit documentation in R/mod_mappingColumn.R
 \name{mappingColumn}
 \alias{mappingColumn}
-\title{mappingColumn}
+\title{Server that facilitates the mapping of a column data (and any associated fields)}
 \usage{
 mappingColumn(input, output, session, meta, data)
 }
@@ -21,5 +21,5 @@ mappingColumn(input, output, session, meta, data)
 A reactive data.frame providing the current value for text_key associated with the selected column
 }
 \description{
-server function that facilitates the mapping of a single data element (column of field) with a simple select UI
+Server that facilitates the mapping of a column data (and any associated fields)
 }
diff --git a/man/mappingColumnUI.Rd b/man/mappingColumnUI.Rd
index 27b7eb02..d195c9c0 100644
--- a/man/mappingColumnUI.Rd
+++ b/man/mappingColumnUI.Rd
@@ -2,7 +2,7 @@
 % Please edit documentation in R/mod_mappingColumn.R
 \name{mappingColumnUI}
 \alias{mappingColumnUI}
-\title{mappingColumnUI}
+\title{UI that facilitates the mapping of a column data (and any associated fields)}
 \usage{
 mappingColumnUI(id, meta, data, mapping = NULL)
 }
@@ -16,5 +16,5 @@ mappingColumnUI(id, meta, data, mapping = NULL)
 \item{mapping}{current data mapping for the column (and related fields)}
 }
 \description{
-UI that facilitates the mapping of a column data domain
+UI that facilitates the mapping of a column data (and any associated fields)
 }
diff --git a/man/mappingDomain.Rd b/man/mappingDomain.Rd
index 4c44b996..b6665d2d 100644
--- a/man/mappingDomain.Rd
+++ b/man/mappingDomain.Rd
@@ -2,7 +2,7 @@
 % Please edit documentation in R/mod_mappingDomain.R
 \name{mappingDomain}
 \alias{mappingDomain}
-\title{mappingDomain}
+\title{Server that facilitates the mapping of a full data domain}
 \usage{
 mappingDomain(input, output, session, meta, data)
 }
@@ -21,5 +21,5 @@ mappingDomain(input, output, session, meta, data)
 A reactive data frame containing the mapping for the domain
 }
 \description{
-server function that facilitates the mapping of a single data domain
+Server that facilitates the mapping of a full data domain
 }
diff --git a/man/mappingDomainUI.Rd b/man/mappingDomainUI.Rd
index 5101da83..960372ce 100644
--- a/man/mappingDomainUI.Rd
+++ b/man/mappingDomainUI.Rd
@@ -2,7 +2,7 @@
 % Please edit documentation in R/mod_mappingDomain.R
 \name{mappingDomainUI}
 \alias{mappingDomainUI}
-\title{mappingDomainUI}
+\title{UI that facilitates the mapping of a full data domain}
 \usage{
 mappingDomainUI(id, meta, data, mapping = NULL)
 }
diff --git a/man/mappingSelect.Rd b/man/mappingSelect.Rd
index f63bf4d7..609b1005 100644
--- a/man/mappingSelect.Rd
+++ b/man/mappingSelect.Rd
@@ -2,7 +2,7 @@
 % Please edit documentation in R/mod_mappingSelect.R
 \name{mappingSelect}
 \alias{mappingSelect}
-\title{mappingSelect}
+\title{Server that facilitates the mapping of a single data element (column or field) with a simple select UI}
 \usage{
 mappingSelect(input, output, session)
 }
@@ -17,5 +17,5 @@ mappingSelect(input, output, session)
 A reactive containing the selected column
 }
 \description{
-server function that facilitates the mapping of a single data element (column of field) with a simple select UI
+Server that facilitates the mapping of a single data element (column or field) with a simple select UI
 }
diff --git a/man/mappingSelectUI.Rd b/man/mappingSelectUI.Rd
index 72001fa1..7d37aab8 100644
--- a/man/mappingSelectUI.Rd
+++ b/man/mappingSelectUI.Rd
@@ -2,7 +2,7 @@
 % Please edit documentation in R/mod_mappingSelect.R
 \name{mappingSelectUI}
 \alias{mappingSelectUI}
-\title{Mapping Select UI}
+\title{UI that facilitates the mapping of a single data element (column or field) with a simple select UI}
 \usage{
 mappingSelectUI(id, label, choices = NULL, default = NULL)
 }
diff --git a/man/mappingTab.Rd b/man/mappingTab.Rd
index d01de71f..6b1ebe49 100644
--- a/man/mappingTab.Rd
+++ b/man/mappingTab.Rd
@@ -2,7 +2,7 @@
 % Please edit documentation in R/mod_mappingTab.R
 \name{mappingTab}
 \alias{mappingTab}
-\title{mapping module server}
+\title{Server for mapping tab covering of all data domains}
 \usage{
 mappingTab(input, output, session, meta, domainData)
 }
@@ -21,5 +21,5 @@ mappingTab(input, output, session, meta, domainData)
 list of mappings for all domains
 }
 \description{
-server function that facilitates the mapping of a single data domain
+Server for mapping tab covering of all data domains
 }
diff --git a/man/mappingTabUI.Rd b/man/mappingTabUI.Rd
index ddd5ff75..08fec487 100644
--- a/man/mappingTabUI.Rd
+++ b/man/mappingTabUI.Rd
@@ -2,7 +2,7 @@
 % Please edit documentation in R/mod_mappingTab.R
 \name{mappingTabUI}
 \alias{mappingTabUI}
-\title{mappingTabUI}
+\title{UI for mapping tab covering of all data domains}
 \usage{
 mappingTabUI(id, meta, domainData, mappings = NULL, standards = NULL)
 }
@@ -18,5 +18,5 @@ mappingTabUI(id, meta, domainData, mappings = NULL, standards = NULL)
 \item{standards}{optional list of data standards like the ones generated by \code{detectStandard()}}
 }
 \description{
-UI that facilitates the mapping of all data domain
+UI for mapping tab covering of all data domains
 }
diff --git a/man/meta.Rd b/man/meta.Rd
index 801bfebe..d38e7f71 100644
--- a/man/meta.Rd
+++ b/man/meta.Rd
@@ -3,7 +3,7 @@
 \docType{data}
 \name{meta}
 \alias{meta}
-\title{meta}
+\title{Metadata data frame containing information about the data mapping used to configure safetyGraphics charts. One record per unique data mapping}
 \format{
 A data frame with 31 rows and 7 columns
 \describe{
diff --git a/man/safetyGraphicsApp.Rd b/man/safetyGraphicsApp.Rd
index 85610cb0..eec37703 100644
--- a/man/safetyGraphicsApp.Rd
+++ b/man/safetyGraphicsApp.Rd
@@ -2,7 +2,7 @@
 % Please edit documentation in R/safetyGraphicsApp.R
 \name{safetyGraphicsApp}
 \alias{safetyGraphicsApp}
-\title{Run the interactive safety graphics app}
+\title{Run the core safetyGraphics App}
 \usage{
 safetyGraphicsApp(
   domainData = list(labs = safetyData::adam_adlbc, aes = safetyData::adam_adae, dm =
@@ -31,5 +31,5 @@ safetyGraphicsApp(
 \item{chartSettingsPaths}{path(s) where customization functions are saved relative to your working directory. All charts can have itialization (e.g. myChart_Init.R) and static charts can have charting functions (e.g. myGraphic_Chart.R).   All R files in this folder are sourced and files with the correct naming convention are linked to the chart. See the Custom Charts vignette for more details.}
 }
 \description{
-Run the interactive safety graphics app
+Run the core safetyGraphics App
 }
diff --git a/man/safetyGraphicsInit.Rd b/man/safetyGraphicsInit.Rd
index b8d86c0f..b4ac65b1 100644
--- a/man/safetyGraphicsInit.Rd
+++ b/man/safetyGraphicsInit.Rd
@@ -2,7 +2,7 @@
 % Please edit documentation in R/safetyGraphicsInit.R
 \name{safetyGraphicsInit}
 \alias{safetyGraphicsInit}
-\title{Run the interactive safety graphics app}
+\title{App to select charts, load data and then initialize the core safetyGraphics app}
 \usage{
 safetyGraphicsInit(
   charts = makeChartConfig(),
@@ -18,5 +18,5 @@ safetyGraphicsInit(
 \item{maxFileSize}{maximum file size in MB allowed for file upload}
 }
 \description{
-Run the interactive safety graphics app
+App to select charts, load data and then initialize the core safetyGraphics app
 }
diff --git a/man/safetyGraphicsServer.Rd b/man/safetyGraphicsServer.Rd
index 807fda9b..9ec00b23 100644
--- a/man/safetyGraphicsServer.Rd
+++ b/man/safetyGraphicsServer.Rd
@@ -2,7 +2,7 @@
 % Please edit documentation in R/mod_safetyGraphicsServer.R
 \name{safetyGraphicsServer}
 \alias{safetyGraphicsServer}
-\title{Server for the default safetyGraphics shiny app}
+\title{Server for core safetyGraphics app including Home, Mapping, Filter, Charts and Settings modules.}
 \usage{
 safetyGraphicsServer(
   input,
diff --git a/man/safetyGraphicsUI.Rd b/man/safetyGraphicsUI.Rd
index b8f7c0c5..ab47189a 100644
--- a/man/safetyGraphicsUI.Rd
+++ b/man/safetyGraphicsUI.Rd
@@ -2,7 +2,7 @@
 % Please edit documentation in R/mod_safetyGraphicsUI.R
 \name{safetyGraphicsUI}
 \alias{safetyGraphicsUI}
-\title{UI for the default safetyGraphics shiny app}
+\title{UI for the core safetyGraphics app including Home, Mapping, Filter, Charts and Settings modules.}
 \usage{
 safetyGraphicsUI(id, meta, domainData, mapping, standards)
 }
@@ -18,5 +18,5 @@ safetyGraphicsUI(id, meta, domainData, mapping, standards)
 \item{standards}{a list of information regarding data standards. Each list item should use the format returned by safetyGraphics::detectStandard.}
 }
 \description{
-UI for the default safetyGraphics shiny app
+UI for the core safetyGraphics app including Home, Mapping, Filter, Charts and Settings modules.
 }
diff --git a/man/settingsCharts.Rd b/man/settingsCharts.Rd
index 7c404535..f9ed6d3f 100644
--- a/man/settingsCharts.Rd
+++ b/man/settingsCharts.Rd
@@ -2,7 +2,7 @@
 % Please edit documentation in R/mod_settingsCharts.R
 \name{settingsCharts}
 \alias{settingsCharts}
-\title{Settings Module - charts details - server}
+\title{Server for settings tab showing details for the charts loaded in the app}
 \usage{
 settingsCharts(input, output, session, charts)
 }
@@ -16,5 +16,5 @@ settingsCharts(input, output, session, charts)
 \item{charts}{list data frame summarizing the charts}
 }
 \description{
-server for the display of the charts
+Server for settings tab showing details for the charts loaded in the app
 }
diff --git a/man/settingsChartsUI.Rd b/man/settingsChartsUI.Rd
index 5941125d..ff68aac0 100644
--- a/man/settingsChartsUI.Rd
+++ b/man/settingsChartsUI.Rd
@@ -2,7 +2,7 @@
 % Please edit documentation in R/mod_settingsCharts.R
 \name{settingsChartsUI}
 \alias{settingsChartsUI}
-\title{Settings Module - chart details}
+\title{UI for settings tab showing details for the charts loaded in the app}
 \usage{
 settingsChartsUI(id)
 }
@@ -10,5 +10,5 @@ settingsChartsUI(id)
 \item{id}{module id}
 }
 \description{
-Settings Module - sub-module showing details for the charts loaded in the app - UI
+UI for settings tab showing details for the charts loaded in the app
 }
diff --git a/man/settingsCode.Rd b/man/settingsCode.Rd
index d713e6d5..960f3465 100644
--- a/man/settingsCode.Rd
+++ b/man/settingsCode.Rd
@@ -2,7 +2,7 @@
 % Please edit documentation in R/mod_settingsCode.R
 \name{settingsCode}
 \alias{settingsCode}
-\title{Server for the setting code page}
+\title{Server for settings tab providing code to re-start the app with current data/settings}
 \usage{
 settingsCode(input, output, session, mapping, charts, domainData)
 }
@@ -20,5 +20,5 @@ settingsCode(input, output, session, mapping, charts, domainData)
 \item{domainData}{data list}
 }
 \description{
-Server for the setting code page
+Server for settings tab providing code to re-start the app with current data/settings
 }
diff --git a/man/settingsCodeUI.Rd b/man/settingsCodeUI.Rd
index cc956c1f..7b54f1bc 100644
--- a/man/settingsCodeUI.Rd
+++ b/man/settingsCodeUI.Rd
@@ -2,7 +2,7 @@
 % Please edit documentation in R/mod_settingsCode.R
 \name{settingsCodeUI}
 \alias{settingsCodeUI}
-\title{UI for the settings page}
+\title{UI for settings tab providing code to re-start the app with current data/settings}
 \usage{
 settingsCodeUI(id)
 }
@@ -10,5 +10,5 @@ settingsCodeUI(id)
 \item{id}{module ID}
 }
 \description{
-UI for the settings page
+UI for settings tab providing code to re-start the app with current data/settings
 }
diff --git a/man/settingsData.Rd b/man/settingsData.Rd
index bc434b88..745b953a 100644
--- a/man/settingsData.Rd
+++ b/man/settingsData.Rd
@@ -2,7 +2,7 @@
 % Please edit documentation in R/mod_settingsData.R
 \name{settingsData}
 \alias{settingsData}
-\title{Settings Module - data details - server}
+\title{Server for settings tab showing current data}
 \usage{
 settingsData(input, output, session, domains)
 }
@@ -16,5 +16,5 @@ settingsData(input, output, session, domains)
 \item{domains}{named list of the data.frames for each domain}
 }
 \description{
-server for the display of the loaded data
+Server for settings tab showing current data
 }
diff --git a/man/settingsDataUI.Rd b/man/settingsDataUI.Rd
index 09a0ba63..5a814d50 100644
--- a/man/settingsDataUI.Rd
+++ b/man/settingsDataUI.Rd
@@ -2,7 +2,7 @@
 % Please edit documentation in R/mod_settingsData.R
 \name{settingsDataUI}
 \alias{settingsDataUI}
-\title{Settings Module - data details}
+\title{UI for settings tab showing current data}
 \usage{
 settingsDataUI(id)
 }
@@ -10,5 +10,5 @@ settingsDataUI(id)
 \item{id}{module id}
 }
 \description{
-Settings Module - sub-module showing details for the data loaded in the app - UI
+UI for settings tab showing current data
 }
diff --git a/man/settingsMapping.Rd b/man/settingsMapping.Rd
index 256d8eab..bff64b23 100644
--- a/man/settingsMapping.Rd
+++ b/man/settingsMapping.Rd
@@ -2,7 +2,7 @@
 % Please edit documentation in R/mod_settingsMapping.R
 \name{settingsMapping}
 \alias{settingsMapping}
-\title{Settings view of Metadata/Mapping - server}
+\title{Server for settings tab showing current mapping}
 \usage{
 settingsMapping(input, output, session, metadata, mapping)
 }
@@ -18,5 +18,5 @@ settingsMapping(input, output, session, metadata, mapping)
 \item{mapping}{reactive data frame representing the current metadata mapping. columns = "domain", "text_id" and "current"}
 }
 \description{
-server for the display of the data mapping metadata.
+Server for settings tab showing current mapping
 }
diff --git a/man/settingsMappingUI.Rd b/man/settingsMappingUI.Rd
index 2d97a448..3ee17585 100644
--- a/man/settingsMappingUI.Rd
+++ b/man/settingsMappingUI.Rd
@@ -2,7 +2,7 @@
 % Please edit documentation in R/mod_settingsMapping.R
 \name{settingsMappingUI}
 \alias{settingsMappingUI}
-\title{Settings view of Metadata/Mapping - UI}
+\title{UI for settings tab showing current mapping}
 \usage{
 settingsMappingUI(id)
 }
@@ -10,5 +10,5 @@ settingsMappingUI(id)
 \item{id}{module id}
 }
 \description{
-UI that displays the data mapping metadata.
+UI for settings tab showing current mapping
 }
diff --git a/man/settingsTabUI.Rd b/man/settingsTabUI.Rd
index 7ec01647..33df0d70 100644
--- a/man/settingsTabUI.Rd
+++ b/man/settingsTabUI.Rd
@@ -2,7 +2,7 @@
 % Please edit documentation in R/mod_settingsTab.R
 \name{settingsTabUI}
 \alias{settingsTabUI}
-\title{UI for the settings page}
+\title{UI for the settings tab}
 \usage{
 settingsTabUI(id)
 }
@@ -10,5 +10,5 @@ settingsTabUI(id)
 \item{id}{module ID}
 }
 \description{
-UI for the settings page
+UI for the settings tab
 }
diff --git a/vignettes/Cookbook.Rmd b/vignettes/Cookbook.Rmd
new file mode 100644
index 00000000..bd7a8116
--- /dev/null
+++ b/vignettes/Cookbook.Rmd
@@ -0,0 +1,145 @@
+---
+title: "Cookbook"
+author: "Jeremy Wildfire"
+date: "`r Sys.Date()`"
+output: rmarkdown::html_vignette
+vignette: >
+  %\VignetteIndexEntry{Cookbook}
+  %\VignetteEngine{knitr::rmarkdown}
+  %\VignetteEncoding{UTF-8}
+---
+
+# Cookbook Vignette
+
+This vignette contains a series of examples showing how to initialize the safetyGraphics Shiny app in different scenarios. For a general overview of the app see [this vignette](Intro). For more details about adding custom charts, see [this vignette](chartConfiguration).
+
+##  Setup and installation
+
+safetyGraphics requires R v4 or higher. These examples have been tested using RStudio v1.4, but should work on other platforms with proper configuration. 
+
+You can install `{safetyGraphics}` from CRAN like any other R package: 
+
+```
+install.packages("safetyGraphics")
+library("safetyGraphics")
+```
+
+Or to use the most recent development version from GitHub, call:
+
+``` 
+devtools::install_github("safetyGraphics/safetyCharts", ref="dev")
+library(safetyCharts)
+devtools::install_github("safetyGraphics/safetyGraphics", ref="dev")
+library(safetyGraphics)
+safetyGraphics::safetyGraphicsApp()
+```
+
+## Example 1 - Default App
+
+To run the app with no customizations using sample AdAM data from the {safetyData} package, install the package and run:
+
+```
+safetyGraphics::safetyGraphicsApp()
+```
+
+## Example 2 - SDTM Data
+
+The data passed in to the safetyGraphics app can be customized using the `data` parameter in `safetyGraphicsApp()`. For example, to run the app with SDTM data saved in `{safetyData}`, call: 
+
+```
+sdtm <- list(
+    dm=safetyData::sdtm_dm,
+    aes=safetyData::sdtm_ae,
+    labs=safetyData::sdtm_lb
+)
+
+safetyGraphics::safetyGraphicsApp(domainData=sdtm)
+```
+
+## Example 3 - Single Data Domain
+
+Running the app for a single data domain, is similar: 
+
+```
+justLabs <- list(labs=safetyData::adam_adlbc)
+safetyGraphics::safetyGraphicsApp(domainData=justLabs)
+```
+
+Note that charts with missing data are automatically dropped and the filtering tab is not present since it requires demographics data by default. 
+
+## Example 4 - Drop Unwanted Charts
+
+Users can also generate a list of charts and then drop charts that they don't want to include. For example, if you wanted to drop charts with `type` of "htmlwidgets" you could run this code.
+
+```
+library(purrr)
+charts <- makeChartConfig() #gets charts from safetyCharts pacakge by default
+notWidgets <- charts %>% purrr::keep(~.x$type != "htmlwidget")
+safetyGraphicsApp(charts=notWidgets)
+```
+
+## Example 6 - Add a chart
+
+The code below adds a new simple chart showing participants' age distribution by sex. 
+
+```
+ageDist <- function(data, settings){
+    p<-ggplot(data = data, aes_(x=as.name(settings$age_col))) +
+        geom_histogram() + 
+        facet_wrap(as.name(settings$sex_col))
+    return(p)
+}
+ageDist_chart<-list(
+    env="safetyGraphics",
+    name="ageDist",
+    label="Age Distribution",
+    type="plot",
+    domain="dm",
+    workflow=list(
+        main="ageDist"
+    )
+)
+charts <- makeChartConfig() 
+charts$ageDist<-ageDist_chart
+safetyGraphicsApp(charts=charts)
+```
+  
+For extensive details on adding and customizing different types of charts, see this [vignette](chartConfiguration).
+
+## Example 7 - Non-standard data
+
+Next, let's initialize the the app with non-standard data. {safetyGraphics} automatically detects AdAM and SDTM data when possible, but for non-standard data, the user must provide a data mapping. This can be done in the app using the data/mapping tab, or can be done when the app is initialized by passing a `mapping` list to `safetyGraphicsApp()`. For example:
+
+```
+notAdAM <- list(labs=safetyData::adam_adlbc %>% rename(id = USUBJID))
+idMapping<- list(labs=list(id_col="id"))
+safetyGraphicsApp(domainData=notAdAM, mapping=idMapping)
+```
+
+## Example 8 - Non-standard data #2
+
+For a more realistic example, consider [this labs data set (csv)](https://raw.githubusercontent.com/SafetyGraphics/SafetyGraphics.github.io/master/pilot/SampleData_NoStandard.csv). The data can be loaded in to safetyGraphics with the code below, but several items in the mapping page need to be filled in:
+
+```
+labs <- read.csv("https://raw.githubusercontent.com/SafetyGraphics/SafetyGraphics.github.io/master/pilot/SampleData_NoStandard.csv")
+safetyGraphics::safetyGraphicsApp(domainData=list(labs=labs))
+```
+
+drawing
+
+Fortunately there is no need to re-enter this mapping information in every time you re-start the app. After filling in these values once, you can export code to restart the app *with the specified settings pre-populated*. First, click on the setting icon in the header and then on "code" to see this page: 
+
+
+
+The YAML code provided here captures the updates you've made on the mapping page. To re-start the app with those settings, just save these YAML code in a new file called `customSettings.yaml` in your working directory, and then call: 
+
+```
+labs <- read.csv("https://raw.githubusercontent.com/SafetyGraphics/SafetyGraphics.github.io/master/pilot/SampleData_NoStandard.csv")
+customMapping <- read_yaml("customSettings.yaml")
+safetyGraphics::safetyGraphicsApp(
+    domainData=list(labs=labs),
+    mapping=customMapping   
+)
+``` 
+
+Note, that for more complex customizations, the setting page also provides a `.zip` file with a fully re-usable version of the app. 
diff --git a/vignettes/TechnicalFAQ.Rmd b/vignettes/TechnicalFAQ.Rmd
new file mode 100644
index 00000000..f249c87a
--- /dev/null
+++ b/vignettes/TechnicalFAQ.Rmd
@@ -0,0 +1,114 @@
+---
+title: "Technical FAQ"
+author: "Jeremy Wildfire"
+date: "`r Sys.Date()`"
+output: rmarkdown::html_vignette
+vignette: >
+  %\VignetteIndexEntry{Technical FAQ}
+  %\VignetteEngine{knitr::rmarkdown}
+  %\VignetteEncoding{UTF-8}
+---
+
+# Technical FAQ Vignette
+
+This vignette answers frequently asked technical questions about {safetyGraphics}. It addressees questions on a variety of technical topics including Qualification and Validation status, Common Data Pipelines and Security. 
+
+Whenever new questions come in, we'll update the version of [this FAQ in our wiki](https://github.com/SafetyGraphics/safetyGraphics/wiki/TechnicalFAQ/) - so check there first if you have a question. We'll update the vignette on CRAN whenever a new version of the package is released. 
+
+# Validation, Quality Control and Testing
+
+## Q: Is the safetyGraphics package validated? 
+**A**: As of the version 2 release, the safetyGraphics package is intended for exploratory use only and is not validated or qualified per [21 CFR Part 11](https://www.fda.gov/regulatory-information/search-fda-guidance-documents/part-11-electronic-records-electronic-signatures-scope-and-application). No warranty or guarantees are included as part of the package. Further, any formal validation should be fit for purpose and follow your organization's procedures. That said, extensive quality checks are built in to the package (see the question below for details) and in to many of charts that are included by default. We follow the work of [R Validation hub](https://www.pharmar.org/) closely, and may release validation guidance based on the approach described in their [white paper](https://www.pharmar.org/white-paper/) at a future date. 
+
+## Q: Can I validate charts created by safetyGraphics? 
+**A**: Study-specific instances of most safetyGraphics charts can be exported either as an R script or as a standalone html report. It may be possible to treat those outputs as standard TLFs (Tables, Listings and Figures) and conduct QC/Validation on them using standard statistical SOPs. Consult with your companies procedures to confirm. 
+
+## Q: What testing/QC process for safetyGraphics? 
+**A**: Several layers of quality control are included in our standard development workflow including: 
+- Over 200 automated unit tests with `{testthat}` that run automatically via Continuous integration with GitHub actions. 
+- Automated unit tests for shiny modules run via a headless browser using `{shinytest}`.
+- Pass all standard R checks in `R cmd check`
+- Full code review of all new functionality documented in GitHub PR. 
+- Issue tracking in GitHub
+- Formal Alpha/Beta user testing before major releases
+- Basic user tests conducted before minor release
+
+# Use Cases, Data Sources and Deployment
+## Q: What are some common use cases for safetyGraphics? 
+
+**A**: safetyGraphics graphics has been used in a variety of ways. Some of the most common use cases thus far are:
+- Analysts exploring safety data 
+- Clinicians monitoring ongoing studies
+- Analysts and Clinicians evaluating safety signals in completed studies
+
+As an open source tool with a flexible data pipeline, many other use cases have been discussed: 
+- Data review by Data Safety Monitoring Boards ([link](https://www.ncbi.nlm.nih.gov/pmc/articles/PMC7833551/pdf/main.pdf))
+- Submissions to FDA ([link](https://phuse.s3.eu-central-1.amazonaws.com/Advance/Data+Visualisation+and+Open+Source+Technology/Interactive+Data+Visualizations+for+Decision+Making+in+Submissions+%E2%80%93%C2%A0PHUSE+Webinar.pdf))
+- Visualizing Analysis results data ([link](https://github.com/phuse-org/aesummaries))
+- Risk based monitoring
+
+## Q: Do I have to use a certain data standard with safetyGraphics? 
+
+**A**: No. Any standard (or non-standard) data can be loaded as long as it meets the [minimum data requirements](Intro#appendix-2---minimum-data-requirements) for the selected data domain. Metadata capturing default CDISC standards are included with the app (see `?safetyGraphics::meta`) so that data mappings can be automatically populated when AdAM and SDTM data are loaded. Other data standards require the user to manually complete the data mapping in the mapping tab - see the [cookbook vignette](cookbook) for examples. 
+
+## Q: What data sources does safetyGraphics support? How do I load custom data? 
+
+**A**: This topic is covered in detail in the [Loading data section of the Introductory vignette](Intro#loading-study-data)`safetyGraphics` is designed to support a flexible data pipeline that supports many data types.  In short, data can be loaded using the the `dataDomains` parameter in the `safetyGraphicsApp()` function or via the `safetyGraphicsInit()` graphical user interface. 
+
+`safetyGraphicsApp()` - custom data can be loaded via the `dataDomains` parameter, which should be a list containing `dataframes` or `tibbles` for each clinical domain; that list can be populated by importing data from any number of sources including databases, sas files or [any number of other sources](https://r4ds.had.co.nz/data-import.html). See the [cookbook vignette](cookbook) for some basic examples of loading custom data.
+
+`safetyGraphicsInit()` - allows users to load tabular data from a variety of sources using the point-and-click interface provided in the {datamods} package. 
+
+More detail is provided in the [Loading data section of the Introductory vignette](Intro#loading-study-data)
+
+## Q: How can the safetyGraphics app be shared? 
+
+**A**: The safetyGraphics app can be shared using [standard shiny methodology](https://shiny.rstudio.com/tutorial/written-tutorial/lesson7/). More details for a specific use cases are given in the next few questions. Charts created by safetyGraphics can also be exported and re-used. Charts created with [htmlwidgets](https://www.htmlwidgets.org/) are especially flexible and can be used in many contexts  - including in web applications outside of R.
+
+## Q: Can I deploy `safetyGraphics` to shinyapps.io to explore trial data from my organization? 
+
+**A**: No, we advise against loading non-authorized, private, or non-deidentified patient data outside of your organization's firewall. Consult with your IT and QA first. There is huge risk associated with confidentiality, IP, and patient privacy. Also refer to [ShinyApps.io Chapter 8 Security and Compliance](https://docs.rstudio.com/shinyapps.io/security-and-compliance.html). 
+
+## **Q**: Can I deploy `safetyGraphics` to an internal [rsconnect](https://www.rstudio.com/products/connect/) server?
+
+**A**: Yes - the easiest way to do this is likely to deploy a customized app using shiny modules. In general, you'll want to use wrap `safetyGraphicsServer()`, `safetyGraphicsUI()` and `app_startup()` in the context of `shiny_app` and then call rsconnect::deployApp(). The script below shows the code for the app deployed at [https://jwildfire.shinyapps.io/safetyGraphics/](https://jwildfire.shinyapps.io/safetyGraphics/) using demo data.
+
+```
+library(safetyGraphics)
+library(shiny)
+
+domainData<-list(
+    labs=safetyData::adam_adlbc, 
+    aes=safetyData::adam_adae, 
+    dm=safetyData::adam_adsl
+)
+
+config <- app_startup(
+    domainData=domainData, 
+    meta=safetyGraphics::meta, 
+    autoMapping = TRUE, 
+    filterDomain="dm" 
+)
+
+shinyApp(
+    ui =  safetyGraphicsUI("sg",config$meta, config$domainData, config$mapping, config$standards),
+    server = function(input,output,session){
+        callModule(
+            safetyGraphicsServer,
+            "sg",
+            config$meta, 
+            config$mapping, 
+            config$domainData, 
+            config$charts, 
+            config$filterDomain
+        )
+    }
+)
+
+```
+
+# Misc. 
+
+## Q: How do I avoid R not choking on the huge volume of lab data? (from @AlbrechtDurer)
+**A**: This is a very good question @AlbrechtDurer, and in my experience the answer is complex and varies for different use cases. Focusing on specific toxicities helps, but probably isn't enough in really big studies. In those cases, I think the most important thing is to design a good data pipeline that includes both a database backend (as opposed to loading all of your study data each time you initialize the app) and visualizations that summarize the data in a reasonable way (as opposed to just plotting every single data point in a scatter plot no matter what). Fortunately this is all doable in R, and improvements in this area are our radar for safetyGraphics after v2 goes live.
+
diff --git a/vignettes/chartConfiguration.Rmd b/vignettes/chartConfiguration.Rmd
new file mode 100644
index 00000000..72aba17f
--- /dev/null
+++ b/vignettes/chartConfiguration.Rmd
@@ -0,0 +1,319 @@
+---
+title: "Chart Configuration"
+author: "Jeremy Wildfire"
+date: "`r Sys.Date()`"
+output: rmarkdown::html_vignette
+vignette: >
+  %\VignetteIndexEntry{Chart Configuration}
+  %\VignetteEngine{knitr::rmarkdown}
+  %\VignetteEncoding{UTF-8}
+---
+
+# Chart Configuration Vignette
+
+The {safetyGraphics} shiny app can be used to display a wide variety of charts. This vignette provides details about the charting process including step-by-step instructions for adding new charts and technical specifications, but first we need to talk about a 2nd package ...
+
+# Introducing {safetyCharts}
+
+While this is technically a vignette for {safetyGraphics}, the {safetyCharts} package is just as important here. The roles of the packages can be summarized in just a few words: 
+
+ **The {safetyGraphics} platform displays charts from {safetyCharts}.**
+ 
+This relationship is central to the technical framework for the safetyGraphics app. By itself, the `safetyGraphics` **platform** really doesn't do much! In fact, none of the content on the Charts tab is actually found in the `safetyGraphics` package; it's all imported from elsewhere! As you've probably guessed, the default charts live in the `safetyCharts` package. `safetyCharts` has over a dozen charts that are configured to work with {safetyGraphics}, but can also easily be used independently. 
+
+While {safetyGraphics} and {safetyCharts} are designed to work seamlessly together, users can also add charts from other packages. In fact, several charts in {safetyCharts} are just wrappers that load charts from other packages for use in {safetyGraphics}. The rest of this vignette provides a series of step-by-step examples detailing how this process works for different types of charts. 
+
+# {safetyGraphics} Chart Components
+
+To add a chart to safetyGraphics, two components are required: 
+
+1. A Configuration Object 
+2. A Chart Function 
+
+The configuration file captures metadata about the chart for use in the app and is typically saved as a YAML file. Several example configuration files are provided in the examples below, and YAML Configuration files for {safetyCharts} are saved [here](https://github.com/SafetyGraphics/safetyCharts/tree/dev/inst/config). 
+
+The chart function typically takes a list of `settings` and a list of `data` as inputs and returns a chart object ready to be displayed in the app. Details of charting functions vary somewhat for different chart types, as explained in the examples below. 
+
+A full technical specification of this chart configuration framework is provided in Appendix 1. 
+
+# Example 1 - Hello World
+
+Once you've created the configuration and chart functions, the chart can be added to the app via the `charts` parameter in `safetyGraphicsApp()`. Consider this simple "Hello World" example: 
+
+```
+# Chart Function
+helloWorld <- function(data, settings){
+    plot(-1:1, -1:1)
+    text(runif(20, -1,1),runif(20, -1,1),"Hello World")
+}
+
+# Chart Configuration
+helloworld_chart<-list(
+    env="safetyGraphics",
+    name="HelloWorld",
+    label="Hello World!",
+    type="plot",
+    domain="aes",
+    workflow=list(
+        main="helloWorld"
+    )
+)
+
+safetyGraphicsApp(charts=list(helloworld_chart))
+```
+
+It's also easy to add a custom chart to the default charts provided in {safetyCharts} using the `makeChartConfig()` function: 
+
+```
+charts <- makeChartConfig(packages="safetyCharts") # or just makeChartConfig() since safetyCharts is included by default
+charts$helloworld<-helloworld_chart
+safetyGraphicsApp(charts=charts)
+```
+
+Here's our Hello World the chart running in the app: 
+
+
+
+# Example 2 - Static Outlier Explorer 
+
+Now let's consider a more complex example that makes use of the `data` and `settings` provided in `safetyGraphics`. In this section, we use {ggplot2} to create a spaghetti plot for tracking outliers in lab data. First, consider the following code which creates a stand-alone plot for a single data set:
+
+```
+# Use sample clinical trial data sets from the {safetyData} package
+library(safetyData) 
+library(ggplot2)
+library(dplyr)
+
+# Define data mapping using a format similar to a reactive safetyGraphics mapping 
+settings <- list(
+    id_col="USUBJID",
+    value_col="LBSTRESN",
+    measure_col="LBTEST",
+    studyday_col="LBDY"
+)
+
+# Define a plotting function that takes data and settings as inputs 
+spaghettiPlot <- function( data, settings ){
+    # define plot aes - note use of standard evaluation! 
+    plot_aes <- aes_(
+        x=as.name(settings$studyday_col), 
+        y=as.name(settings$value_col), 
+        group=as.name(settings$id_col)
+    )
+
+    #create the plot
+    p<-ggplot(data = data, plot_aes) +
+        geom_path(alpha=0.15) + 
+        facet_wrap(
+            as.name(settings$measure_col),
+            scales="free_y"
+        )
+    return(p)
+}
+
+spaghettiPlot(
+    safetyData::sdtm_lb %>% 
+        filter(LBTEST %in% c("Albumin","Bilirubin","Calcium","Chloride")), 
+    settings
+)
+```
+
+Running the code above should create a plot with 4 panels:
+
+
+
+With minor modifications, this chart can be added to the {safetyGraphics} shiny app, which allows us to create the chart with any mappings/data combination loaded in the app. The `spaghettiPlot()` function above is already written to work with safetyGraphics, so we just need to create the chart configuration object. This time we'll capture the configuration in a [YAML](https://yaml.org/) file.
+
+```
+env: safetyGraphics
+label: Spaghetti Plot
+type: plot
+domain: 
+  - labs
+workflow:
+  main: spaghettiPlot
+links:
+  safetyCharts: https://github.com/SafetyGraphics/safetycharts
+```
+
+With the charting function loaded in to our session and the configuration file saved in our working directory as `spaghetti.yaml`, we can add the chart to the app as follows: 
+
+```
+library(yaml)
+charts <- makeChartConfig()
+charts$spaghetti<-prepareChart(read_yaml('spaghetti.yaml'))
+safetyGraphicsApp(charts=charts)
+```
+Under the charts tab, you'll see: 
+
+
+
+If you look closely at the `spaghettiPlot()` code above, you'll noticed some details that make the chart work in the app:  
+
+ - The chart function is written as a function taking `data` and `settings` as inputs. This is the expected parameterization for most charts in {safetyGraphics}. 
+- The references to `settings` use parameters that are defined on the mapping tab. Behind the scenes, these are defined in the `safetyGraphics::meta`.
+- The `spaghettiPlot` function is referenced in the `main` item the YAML `workflow`. This tells the app which function to use to draw the chart.
+
+These details allow users to dynamically define data attributes for any labs data set, allowing the chart to be reused across many different types of data. 
+
+This example is inspired by `safetyCharts::safety_outlier_explorer` - the [charting function](https://github.com/SafetyGraphics/safetyCharts/blob/dev/R/safety_outlier_explorer.R) and [yaml configuration file](https://github.com/SafetyGraphics/safetyCharts/blob/dev/inst/config/safetyOutlierExplorerStatic.yaml) on are GitHub.
+
+# Example 3 - Shiny Module
+
+{safetyGraphics} also supports defining charts as Shiny Modules. Once you're [familiar](https://shiny.rstudio.com/articles/modules.html) [with](https://mastering-shiny.org/scaling-modules.html) [modules](https://emilyriederer.netlify.app/post/shiny-modules/), they are relatively straightforward to use with safetyGraphics. 
+
+Let's take a look at a simple module that extends the functionality of the static chart from the example above. Once again, this example is based upon `safetyCharts`, and you can see the [code](https://github.com/SafetyGraphics/safetyCharts/blob/dev/R/mod_safetyOutlierExplorer.R) and [config](https://github.com/SafetyGraphics/safetyCharts/blob/dev/inst/config/safetyOutlierExplorerModule.yaml) on GitHub. 
+
+The config object for a module differs from a static chart is that the workflow section of the YAML file must specify `ui` and `server` functions instead of a `main` charting function.  This example defines a simple UI function that allows users to select which lab measurements should be included in the spaghetti plot from example 1: 
+
+``` 
+safetyOutlierExplorer_ui <- function(id) {
+    ns <- NS(id) 
+    sidebar<-sidebarPanel(
+        selectizeInput(
+            ns("measures"), 
+            "Select Measures", 
+            multiple=TRUE, 
+            choices=c("")
+        )
+    )
+    main<-mainPanel(plotOutput(ns("outlierExplorer")))
+    ui<-fluidPage(
+        sidebarLayout(
+            sidebar,
+            main,
+            position = c("right"),
+            fluid=TRUE
+        )
+    )
+    return(ui)
+}
+``` 
+
+Next we define a server function that populates the control for selecting measurements and then draws the plot using [`safetyCharts::safety_outlier_explorer()`](https://github.com/SafetyGraphics/safetyCharts/blob/dev/R/safety_outlier_explorer.R) charting function - which is based on the `spaghetti()` function ! Note that the server function takes a single reactive `params` object containing the data (`params$data`) and settings (`param$settings`) as input. 
+
+``` 
+safetyOutlierExplorer_server <- function(input, output, session, params) {
+
+    ns <- session$ns
+    # Populate control with measures and select all by default
+    observe({
+        measure_col <- params()$settings$measure_col
+        measures <- unique(params()$data[[measure_col]])
+        updateSelectizeInput(
+            session, 
+            "measures",
+            choices = measures,
+            selected = measures
+        )
+    })
+
+    # customize selected measures based on input
+    settingsR <- reactive({
+        settings <- params()$settings
+        settings$measure_values <- input$measures
+        return(settings)
+    })
+
+    #draw the chart
+    output$outlierExplorer <- renderPlot({safety_outlier_explorer(params()$data, settingsR())})
+}
+```
+
+Finally, the YAML configuration file looks like this  - just the workflow and label changes from Example 1: 
+
+```
+env: safetyGraphics
+label: Outlier Explorer - Module
+type: module
+package: safetyCharts
+domain: 
+  - labs
+workflow:
+  ui: safetyOutlierExplorer_ui
+  server: safetyOutlierExplorer_server
+links:
+  safetyCharts: https://github.com/SafetyGraphics/safetycharts
+``` 
+
+Initializing the app as usual by adding it to the chart list: 
+`charts$outlierMod<-prepareChart(read_yaml('outlierMod.yaml'))`
+
+Unselecting a few measures gives the following display: 
+
+
+# Example 4 - htmlwidgets and init functions
+
+You can also add custom htmlwidgets to safetyGraphics. In fact, many of the [default charts](https://github.com/SafetyGraphics/safetyCharts/tree/dev/inst/htmlwidgets) imported from safetyCharts are javascript libraries that are imported as htmlwidgets. Like shiny modules, htmlwidgets are relatively simple to use once you are [familiar with the basics](https://www.htmlwidgets.org/). 
+
+The biggest differences between widgets and other charts in safetyGraphics are: 
+
+1. The widget must be contained in a package, which must be specified in the YAML file. 
+2. The widget expects a `widget` item giving the name of the widget in the YAML workflow. 
+3. By default, the data and settings for a widget are passed in a list (`list(data=data, settings=settings)`) to the `x` parameter in `htmlwidget::createWidget`.  
+
+Items 1 and 2 above are simple enough, but #3 is likely to create problems unless the widget is designed specifically for usage with safetyGraphics. That is, if the widget isn't expecting `x$settings` to be a list that it uses to configure the chart, it probably isn't going to work as expected. 
+
+Fortunately, there's a workaround built in to safetyGraphics in the form of `init` workflow functions. Init functions run before the chart is drawn, and can be used to create custom parameterizations. The init function should take `data` and `settings` as inputs and return `params` which should be a list which is then provided to the chart (see the appendix for more details). The [init function](https://github.com/SafetyGraphics/safetyCharts/blob/dev/R/init_aeExplorer.R) for the the interactive [AE Explorer](https://github.com/RhoInc/aeexplorer) is a good example. It starts by [merging demographics and adverse event data](https://github.com/SafetyGraphics/safetyCharts/blob/c37f3ac7883b15ab3d8a36e597dec85728657fd7/R/init_aeExplorer.R#L16-L18) and then proceeds to [create a customized settings object](https://github.com/SafetyGraphics/safetyCharts/blob/c37f3ac7883b15ab3d8a36e597dec85728657fd7/R/init_aeExplorer.R#L20-L43) to match [the configuration requirements](https://github.com/RhoInc/aeexplorer/wiki/Configuration) of the javascript chart renderer. This init function is then saved under `workflow$init` in the chart config object. 
+
+The rest of the [chart configuration YAML](https://github.com/SafetyGraphics/safetyCharts/blob/dev/inst/config/aeExplorer.yaml) is similar to the examples above, and the chart is once again by passing the chart config object to `safetyGraphicsApp()`
+ 
+# Appendix #1 - Chart Framework Technical Specifications 
+
+## Configuration Overview
+
+
+
+The diagram above summarizes the various components of the safetyGraphics charting framework: 
+- The `safetyGraphicsApp()` function allows users to specify which charts to include in the shiny app via the `charts` parameter, which expects a `list` of charts. 
+- Each item in `charts` is itself defined as a `list` that provides configuration details for a single chart. These configuration lists have several required parameters, which are described in the technical specification below. 
+- Configuration lists are typically saved as YAML files, but can be also be loaded directly as list objects as shown in the Hello World example above. 
+- Needed functions are bound to the chart object via the prepareChart() function. See the documentation for `chart$functions` below for full details. 
+
+## Chart Specification
+
+Each item in the `charts` list should be a list() with the following parameters: 
+- `env`: Environment for the chart. Must be set to "safetyGraphics" or the chart is dropped. Type: *character*. **Required**
+- `name`: Name of the chart. Type: *character*. **Required**
+- `type:`: Type of chart. Valid options are: "plot","htmlwidget","html","table" and "module". Type: *character*. **Required**
+- `label`: A short description of the chart. chart$name is used if not provided. Type: *character*. *Optional*
+- `domain`: The data domain(s) used in the chart. Type: *character*. **Required**
+- `package`: The package where the {htmlwidget} is saved. Type: *character*. **Required** when `chart$type` is "htmlwidget"
+- `order`: Order in which to display the chart. If order is a negative number, the chart is dropped. Defaults to 999999. Type: *Integer*. *Optional*
+- `links`:  Named list of link names/urls to be shown in the chart header. Type: *list of character*. *Optional*
+- `path`: Full path of the YAML file. Auto-generated by `makeChartConfig()` Type: *character* *optional*
+- `workflow`: Names of functions used to create the chart. Should be loaded in global environment or included in `chart$package` before calling `prepareChart()`. Supported parameters are listed below. Type: *list of character*. **Required**
+   - `workflow$main`: name of the function to draw the chart. The function should take `data` and `settings` parameters unless the input parameters are customized by an `init` function. **Required**, unless `chart$type` is "htmlwidget" or "module")
+   - `workflow$init: name of initialization function that runs before chart is drawn via the `main` function. Should take `data` and `settings` as input and return a list of parameters accepted by the `main` function. *Optional*
+   - `workflow$widget`: name or widget saved in `chart$package` to be passed to `htmlwidgets::createWidget` **Required** when `chart$type` is "htmlwidget"
+   - `workflow$ui` and `workflow$server`: names of functions to render shiny ui and server. Automatically generated in `prepareChart()` unless `chart$type` is "module". **Required** when `chart$type` is 'module'
+- `functions`: a list of functions used to create the chart. Typically generated at runtime by `prepareChart()` using information in `chart$workflow`, `chart$type` and `chart$package`. Not recommended to generate manually. Type: *list of functions*. **Required**
+ 
+## Default Technical workflow
+
+This appendix describe the technical process used to render a chart when safetyGraphicsApp() is called with the default parameters. 
+
+1. `safetyGraphicsApp()` is called with `charts` and `chartSettingsPath` as NULL (the default).
+2. `app_startup` is called, which then immediately calls `makeChartConfig()`. 
+3.  `makeChartConfig()` looks for charts in the safetyCharts package (the default) since no path was specified. The function looks for the package in all current `.libPaths()` and then looks in the `inst/config` folder once the package is found. 
+4. `makeChartConfig` loads YAML configuration files in the specified directories and saves them to a list. `name` and `path` parameters are added. 
+5. `makeChartConfig` calls `prepareChart` for each chart configuration. `prepareChart` sets default values for `order`, `name` and `export`, and then binds relevant functions to a `chart$functions` list based on the chart's `type`, `workflow` and `package`.
+6. That list of charts is then returned to `app_startup()` which runs a few actions on each chart: 
+   - If `chart$functions` is missing, `prepareChart` is called (not relevant in the default workflow, but useful for adding custom charts)
+   - If `chart$order` is negative, the chart is dropped with a message.
+   - If `chart$env` is not "safetyGraphics", the chart is dropped with a message. 
+   - If `chart$domains` has elements not found in the `dataDomains` passed to `app_startup(), the chart is dropped with a message.
+   - `charts` are re-ordered based on `chart$order`
+7. `app_startup` returns the list of charts to `safetyGraphicsApp` which then then passes them along to `safetyGraphicsServer` as the `charts` parameter. 
+8. `safetyGraphicsServer` then creates modules for each chart.  First, `UIs` are created via `chartsNav()` which then calls:
+    -  `makeChartSummary` to create the chart header with links and metadata and ...
+    -  `ChartsTabUI` which then calls `chart$functions$ui` to create the proper UI element based on `chart$type`. 
+8. Next, `safetyGraphicsServer` draws the charts using `chartsTab()` which: 
+    - Creates a reactive `params` object containing mappings and data using `makeChartParams()` which:
+        - Subsets `domainData` based on `chart$domain`
+        - Calls `charts$functions$init` if provided
+        - Does custom formatting for `chart$type` of "htmlwidget"
+    - Chart is drawn using `chart$functions$server` and `chart$functions$main`
+    - Button to download R script is added to header. Script is created by `makeChartExport()`
+    - Button to download html report is added to header unless type="module". Report template is at "inst/reports/safetyGraphicsReport.Rmd"
+9. Finally, `safetyGraphicsServer` passes the charts to `settingsTab`, which uses them to help populate the `charts` and `code` subtabs. 
diff --git a/vignettes/customWorkflows.Rmd b/vignettes/customWorkflows.Rmd
deleted file mode 100644
index ef80cab8..00000000
--- a/vignettes/customWorkflows.Rmd
+++ /dev/null
@@ -1,461 +0,0 @@
----
-title: "safetyGraphics Shiny App - Custom Workflows"
-author: "Jeremy Wildfire"
-date: "`r Sys.Date()`"
-output: rmarkdown::html_vignette
-vignette: >
-  %\VignetteIndexEntry{safetyGraphics Shiny App - Custom Workflows}
-  %\VignetteEngine{knitr::rmarkdown}
-  %\VignetteEncoding{UTF-8}
----
-
-```{r setup, include = FALSE}
-knitr::opts_chunk$set(
-  collapse = TRUE,
-  comment = "#>"
-)
-```
-# Overview
-The safetyGraphics package is designed to serve as a flexible and extensible platform for analyzing clinical trial safety. This vignette shows how users can configure the safetyGraphics shiny app with workflows using customized charts and data.
-
-Version 1.1 of the package allows users to  preload their own charts and data sets for use in the safetyGraphics Shiny Application. Many types of clinical trial lab data are supported in conjunction with 4 types of charts - Static charts, Plotly charts, Shiny Modules and HTML widgets. As shown in the next section, loading data is simple, but adding custom charts is slightly more complex. Behind the scenes, all 4 chart types have two major technical components: **code** and **metadata**. As such, making a custom chart requires the user to create an R script that defines the chart's code and metadata. We provide several examples below that describe the step-by-step process for creating a chart.
-
-# Adding Custom Data
-
-Run `safetyGraphicsApp(loadData=TRUE)` to preload all data.frames from your current R session in a new instance of the safetyGraphics Shiny app. While users can still manually load additional `.csv` or `.sas7bdat` files in the app as needed, this programatic alternative allows for more flexibility for loading other data sources, and can help to automate situations where users want to load multiple files. For example, running the code below will preload several example data sets saved on our GitHub site. 
-
-```
-#Load in data sets with different data standards
-data_url <- 'https://raw.githubusercontent.com/SafetyGraphics/SafetyGraphics.github.io/master/pilot/'
-SDTM<-read.csv(paste0(data_url,'SampleData_SDTM.csv'))
-SDTM_Partial<-read.csv(paste0(data_url,'SampleData_PartialSDTM.csv'))
-AdAM_Partial<-read.csv(paste0(data_url,'SampleData_PartialADaM.csv'))
-NoStandard<-read.csv (paste0(data_url,'SampleData_NoStandard.csv'))
-AdAM <- adlbc #loadData=TRUE overrides the default behavior where adlbc is automatically preloaded into the app
-
-#Initialize the app with data from the session
-safetyGraphicsApp(loadData=TRUE)
-
-```
-
-Clicking on the data tab shows the 5 pre-loaded data sets with their different data standards. 
-
-
-
-This data load process can easily be combined with the chart workflow described below (including `customSettings.R` programs) to create easily reusable, custom workflows. 
-
-# Steps to Create a Custom Chart
-
-There are 4 steps required to create a custom chart for use in `safetyGraphics`:
-
-1. Create custom chart code
-2. Add new settings to the app (if needed)
-3. Add the chart to the app
-4. Initialize the app
-
-The remainder of this vignette is dedicated to 4 examples that describe the process for creating custom charts in more detail. Note that full code for all examples are available in Appendix 3 at the end of this vignette. 
-
-# Example 1 - Hello World
-
-To create a trivially simple custom chart, make a file called `customSettings.R` with the following code: 
-
-```
-# Step 1 - Write custom chart code 
-helloWorld <- function(data,settings){
-  plot(-1:1, -1:1)
-  text(runif(20, -1,1),runif(20, -1,1),"Hello World")
-}
-
-# Step 2 - Initialize Custom Settings 
-# Not Applicable!
-
-# Step 3 - Initialize the custom chart 
-addChart( 
-  chart=”hello_world”,
-  main=”helloWorld",
-  label=”Hello World”, 
-)
-```
-
-Then initialize the app (Step 4) by running: 
-
-```
-setwd('/path/to/the/file/above')
-safetyGraphicsApp()
-```
-
-Once the app opens, click the charts tab to view the new custom "hello_world" chart. 
-
-
-
-# Example 2 - Detailed Walkthrough
-
-Our second example goes through the chart creation process step-by-step for a more realistic example. An understanding of the underlying infrastructure for safetyGraphics will help here, so we recommend reviewing the first [introductory vignette](https://github.com/SafetyGraphics/safetyGraphics/wiki/Vignette:-Shiny-User-Guide) before diving in. 
-
-## Step 1 - Create custom chart code
-
-The first, and most complicated, step is to write the code for the custom chart. It's easiest to break this process down in to 3 smaller steps.  
-
-1. Create customSettings.R file
-2. Make static code using sample data
-3. Covert static chart code to Function
-
-### Step 1.1 - Create customSettings.R file
-
-First, create a file called customSettings.R and save it in a designated directory. All of the code in the following steps goes in this file. Note that when you run the app, custom medatadata files will be saved in the same directory as the customSettings.R file. 
-
-### Step 1.2 - Make Static Code Using Sample Data
-
-Next, write code that creates your chart using a sample data set (the `adlbc` data set included with safetyGraphics is a good option). Note that all common charting packages are supported including `ggplot2`, `lattice` and base R graphics.  Our example makes a histogram showing the distribution of lab values: 
-
-```
-library(safetyGraphics)
-library(ggplot2)
-ggplot(
-	data = adlbc, 
-	aes(x = PARAM, y = AVAL)
-) +
- geom_boxplot(fill =‘blue’) +
- scale_y_log10() +
- theme_bw() +
- theme(
-  axis.text.x = element_text(angle = 25, hjust = 1), 	
-  axis.text = element_text(size = 12), 
-  axis.title = element_text(size = 12)
-)
-```
-
-As expected, running this code creates a simple box plot. 
-
-
-
-### Step 1.3 - Convert Static Chart Code to a Function
-
-After the chart is working using the sample data, you need to update it to a function that will work with any data set that the user loads in the shiny app.  Replace hard coded parameters with references to the settings defined in the safetyGraphics settings object as shown below. 
-
-
-
-This is the hardest part of creating a custom chart, so we've provided some additional notes about this process below. There is also a technical appendix at the end of this document that provides more details about the metadata/settings objects used in this step. Finally, feel free to ask [ask us questions](https://github.com/SafetyGraphics/safetyGraphics/issues) if you run in to problems. 
-
- - The code to create the chart must be wrapped in a function that takes 2 parameters as inputs: `data` and `settings` as shown in line 1 above. When the chart function is called by Shiny, these parameters are generated dynamically within the app; `data` represents the user selection in the Data module, and `settings` represents the selections in the Settings Module.
-  - The `data` parameter is saved as a `data.frame`, and a preview of the current data is conveniently available in the data tab.  
-  - The `settings` parameter is saved as a `list` and is slightly more complex. Each setting shown on the settings page has a unique ID (called a `text_key` in the package) that gives its position in the settings `list`. In our example, the "Measure column" setting has the ID `measure_col` and is accessed in the charting function via `settings$measure_col`. Additional technical documentation about the `settings` list is provided in Appendix 1.
-- Lines 2-7 above create a new data frame called `mapped_data`. This isn't required, but it simplifies the code somewhat and helps to avoid non-standard evaluation in the chart function. 
-- Note that we dynamically identify the `Value` and `Measure` columns in lines 4 and 5 by referencing the `settings` object.  This code, as opposed to directly specifying a column name like `data$PARAM`, allows the chart to work with any data standard.
-- Line 9 initializes the chart using `ggplot()` with the newly derived `mapped_data`.
-- Line 13 introduces a custom setting - `settings[["boxcolor"]]` - so that the user can specify a color for the bars in the shiny app if desired. All custom settings must be initialized using the `addSetting()` function; this process is described in Step 2 below. 
-- Finally, note that the process for defining custom "htmlwidget" and "shiny module" charts is slightly different than the sample code above; example 3 provides basic example for a shiny module, and htmlwidgets are discussed in Appendix 2. 
-
-## Step 2 - Add custom settings to the App
-
-Next, we'll add any new settings to the app by calling the `addSetting()` function in our `customSettings.R` function.  
-
-First, we need to determine which settings are already defined. As noted above, our chart uses 3 settings: `value_col`, `measure_col` and `box_color`. In most cases you can just examine the  `settingsMetadata` data frame, which contains all settings available in safetyGraphics, along with details about each. Either view it with view(settingsMetadata) or use code like this:
- 
-
-
-In some complex cases, it might be easier to examine an example settings object directly (rather than the data frame representation). To do this, you can create a shell settings object and then check to see if the settings exist:
-
-
-
-As shown in the output above, our example uses 2 pre-loaded settings (`measure_col` and `value_col`) and one new setting (`boxcolor`). We add boxcolor to the metadata using the `addSetting()` function as shown below. 
-
-```
-addSetting( 
-  text_key="boxcolor", 
-  label="Box Plot Color", 
-  description="The color of the boxes",
-  setting_type="character",
-  setting_cat="appearance", 
-  default="gray"
-) 
-```
-
-You could repeat as needed for multiple settings. For full details about each parameter see `?addSetting`, which matches up with the column names in `?settingsMetadata`.
-
-## Step 3 - Add the chart to the App
-
-Next, we need to add the chart itself to the app using `addChart()`. We'd add the example above as follows:
-
-```
-addChart( 
-  chart="labdist", 
-  main="labdist", 
-  label="Lab Distribution - static", 
-  requiredSettings=c("boxcolor","value_col","measure_col"),
-  type="static”
- )
-```
-
-For full details about each parameter see `?addChart`, which matches up with the column names in `?chartMetadata`.
-
-## Step 4 - Initialize the app
-
-Finally, make sure your working directory is set to the location of you customSettings.R and call safetyGraphicsApp(). The settings page for the new “Lab Distribution – Static” chart will look like this:
-
-
-
-And here is the chart: 
-
-
-
-There are options that will let you save the custom code in other locations and/or automatically add a chart each time you run the app. See ?safetyGraphicsApp, ?addChart and ?addSettings for details. 
- 
-# Example 3 - Interactive Histogram
-
-We can expand on our static boxplot from Example 2 by adding some interactivity.  Placing our boxplot in a Shiny module will allow the user to make chart-specific aesthetic adjustments on the fly.  In this example, we've added the ability to add/remove individual data points, transform the y-axis scale, and show/hide outliers:
-
-
-
-This example expands on the static boxplot example in the following ways:
-- Most of the underlying code for manipulating the dataset and creating the `ggplot2` figure is identical to the static boxplot example. However, we've added some conditional statements to modify the boxplot based on the user selections.
-- Instead of a single chart function, we now have two: the module UI function, and the module server function. The UI function has the same name as the server function, with `_UI` appended. These functions should be specified (or sourced from an external file) within customSettings.R.
-- `data` and `settings` are passed to the module server function as reactive objects.
-
-The full code for the custom script is saved in Appendix 3. 
-
-# Example 4 - Custom htmlwidget (Coming soon!)
-
-Custom `htmlwidgets` are not currently supported via `addChart()` and addSetting()`, but we plan to add support in future release. 
-
-For now, please contact the package development team or [file an issue on GitHub](https://github.com/SafetyGraphics/safetyGraphics/issues) if you would like to add a custom `htmlwidget` to safetyGraphics, and we can discuss technical details.  
-
-# Appendix 1 - Technical Details
-
-This appendix provides a detailed technical description of the settings framework used in the application. As described in the [introductory vignette](https://github.com/SafetyGraphics/safetyGraphics/wiki/Vignette:-Shiny-User-Guide#update-settings), the settings Shiny module allows users to make a [wide](https://github.com/SafetyGraphics/safetyGraphics/wiki/Vignette:-Shiny-User-Guide#case-study-1---mapping-non-standard-data) [range](https://github.com/SafetyGraphics/safetyGraphics/wiki/Vignette:-Shiny-User-Guide#case-study-2---adding-customizations) of customizations to the charts for any given study. Understanding the underlying technical details of this settings customization process is perhaps the most complicated aspect of designing custom charts for `safetyGraphics`. This appendix is broken in to 2 sections, the first describes the structure of the settings themselves, the second describes the metadata used to generate the settings when the package is built. 
-
-## Settings Structure
-
-Behind the scenes, the settings are stored as a `list`, which is updated in real time as the user makes changes in the Shiny settings module. A small chunk of a typical settings `list` is shown below. Note that this was generated using `generateSettings(standard="adam")`. More details on this and other functions related to settings is provided below. 
-
-
-
-As described in the examples above, the current settings `list` is passed directly to the chart function whenever a user views a chart in the shiny app. Each control in the settings module is tied to a single component in the setting `list` using a unique key. That unique key defines the setting's position in the list. You can see the unique key for any setting by hovering over the title for the control in the shiny app. As an example, the "ID column" control has a unique key of "id_col", which is accessible in the settings `list` via `settings$id_col`, which would resolve to "USUBJID", the default value for the ADaM data standard, in our sample settings above. The settings framework also supports nested settings. A double dash "--" indicates a level of nesting in the `list`, so a setting ID of "measure_values--ALT" would be accessed as `settings[["measure_values"]][["ALT"]]`, which would resolve to "Alanine Aminotransferase (U/L)" in our sample settings. 
-
-You can see additional details about pre-loaded settings by viewing the safetyGraphics::settingsMetadata data file that contains the default settings for the shiny app. ?settingsMetadata provides detailed data specifications for the metadata file, which also match the options available in the addSetting() function used in the examples above.
-
-The `safetyGraphics` package includes several functions specifically designed for use with settings objects. As mentioned above, you can generate a default settings list for a data standard using the `generateSettings()` function:
-
-```
-safetyGraphics::generateSettings()  # no standard
-safetyGraphics::generateSettings(standard="ADaM") # ADaM standard
-```
-
-Other functions for working with settings (all used liberally by the shiny app) include: `getRequiredSettings()`, `generateShell()`, `getSettingKeys()`, `getSettingValue()`, `getSettingsMetadata()`, `setSettingsValue()`, `trimSettings()` and `validateSettings()`. The R documentation for each of these functions provides technical details and examples for common use cases. Note also that all of the charts included with the application have detailed standalone documentation referenced in the `repo_url` and `settings_url` fields found in the `chartsMetadata` file; for example, the `hep-explorer`'s configuration page is [here](https://github.com/SafetyGraphics/hep-explorer/wiki/Configuration) and provides a lot of additional context about how each setting is used by the chart.
-
-Finally, note that for htmlwidgets the settings `list` is converted to a json object with the following code: 
-
-```
-settings_list <- list(...)
-jsonlite::toJSON(
-      settings_list,
-      auto_unbox = TRUE,
-      null = "null"
-    )
-```
-
-## Metadata framework
-
-In general, there are 3 primary types of metadata used in the shiny app: chart metadata, setting metadata and data standard metadata. The metadata files that provide key information to the Shiny app and allow for the app to automatically be updated with new charts, settings, and standards. 
-
-The underlying technical framework for the metadata is somewhat complex. In general, we follow the recommendations from the [Data chapter](http://r-pkgs.had.co.nz/data.html) in Hadley Wickham's R Packages book. Using that workflow, we combine 5 "raw" metadata files (saved in `data-raw\`) in to 3 data files that are available as part of the package (saved in `data\` with documentation in `R\`). An R script to convert the 5 "raw" files to the 3 files in the package is saved as `data-raw\csv-to-rda.R`, which is re-run whenever the metadata framework is updated. 
-
-The `addChart()` and  `addSetting()` functions (and their evil twins `removeCharts()` and `removeSettings()`) allow users to customize these metadata files without actually rebuilding the entire package. These functions simply edit, add or remove rows from the `settingsMetadata` and `chartsMetadata` files saved in `data\` and then save local copies of the files that are used in place of the default versions. This customization is likely enough for most users, but developers looking to make permanent changes to the apps default must go a level deeper and edit the files saved in `data-raw/`. More detail about those raw files is provided below, and step-by-step instructions for creating a new default chart are provided in Appendix 2. 
-
-- **Charts Metadata (chartsMetadata.csv)**: This file informs the Shiny app about all of the chart modules that should be made available to the user. The structure of this file is 1 row per chart. Columns contain chart-specific details such as chart name, type, and size. 
-
-- **Settings Metadata for Charts (settingsMetadataCharts.csv)**: This file helps the Shiny app understand which settings are needed for the different charts. This information is incorporated in the Settings configuration and Reporting modules. The structure of this file is 1 row per unique setting and 1 column per chart.  `TRUE`/`FALSE` values are used to indicate whether the setting is relevant to a given chart.
-    
-- **Settings Metadata (settingsMetadata.csv)**:  This file informs the Shiny app about all of the possible settings across all of the charts.  Specifically, the file helps to populate the Settings tab of the app, and it also ensures that settings are successfully handed off to the charts. The structure is 1 row per setting and the columns contain information such as a description of the setting, type of setting (e.g. data mapping), and whether the setting is optional or required.  
-
-- **Settings Defaults (generateSettingsMetadataDefaults.R)**: Ths file contains information about the default values for the settings (specifically for non-data mapping settings).  A `.R` file is used in place of a `.csv` to preserve the R value type (numeric, string, list, etc) of the defaults. While all settings are represented (structure of 1 row per setting), all data mapping defaults should be set to `NULL` and handled in the Standards metadata file.
-
-- **Standards Metadata (standardsMetadata.csv)**: This file contains information about the default values for the settings for each data standard (specifically for data mapping settings). The file helps the Shiny app automatically detect data standards in uploaded files and automate settings configuration if the data is in a standard format. The structure of the file is 1 row per setting and 1 column per data standard. While all settings are represented, all rows corresponding to non-data mapping settings should be left blank.
-
-# Appendix 2 - Step-by-Step Process for Contributing a New Default Chart to safetyGraphics Package
-
-1. Make a new branch of the safetyGraphics master [repository](https://github.com/SafetyGraphics/safetyGraphics).
-
-2. Create a new charting function using the guidelines in the examples above
-
-3. Drop the file containing the charting function in the `inst/custom` directory, under the subfolder that matches the chart type (static, plotly, or Shiny module).
-
-4. Update metadata
-   - Update metadata files:
-      - For all custom charts:
-         - Add a row for the new chart to `data-raw/chartsMetadata.csv`
-         - Add a column for the new chart to `data-raw/settingsMetadataCharts.csv`.
-      - For charts that contain new settings: 
-         - Add rows for new settings to `data-raw/settingsMetadata.csv` 
-         - Add defaults for new settings in `data-raw/generateSettingsMetadataDefaults.R` and re-run the file.
-         - Add rows for new settings in `data-raw/settingsMetadataCharts.csv`.
-         - Add rows for new settings in the data standard mappings in `data_raw/standardsMetaData.csv`
-   - Run `data-raw/csv_to_rda.R` to save the files to `data/`.
-   - Add chart to documentation file for settingsMetadata: `R/settingsMetadata.R`. Append `chart_` to the name of your chart function/file and add it as an item in the list.
-
-5. Update package dependencies.
-If you've added a plotly chart:
-   - Add plotly to DESCRIPTION file Imports
-   - Add `library(plotly)` to top of `global.R` file under `inst/safetyGraphics_app`
- 
-6. Update package documentation with `devtools::document()`.  
-
-7. Rebuild the R package, test out the Shiny app, and make a PR to the safetyGraphics repo.
-
-# Appendix 3 - Full Custom Scripts for Examples
-
-## Full Code for Example 1 - Hello World
-
-```
-# Step 1 - Write custom chart code 
-helloWorld <- function(data,settings){
-  plot(-1:1, -1:1)
-  text(runif(20, -1,1),runif(20, -1,1),"Hello World")
-}
-
-# Step 2 - Initialize Custom Settings 
-# Not Applicable!
-
-# Step 3 - Initialize the custom chart 
-addChart( 
-  chart=”hello_world”,
-  main=”helloWorld",
-  label=”Hello World”, 
-)
-```
-
-## Full Code for Example 2 - Static Histogram
-
-```
-custom_location<-"customBoxplot/"
-
-#####################################################################
-# Step 1 - Write custom chart code
-#####################################################################
-labdist<-function(data,settings){
-  mapped_data <- data %>%
-    select(Value = settings[["value_col"]], Measure = settings[["measure_col"]])%>%
-    filter(!is.na(Value))
-  
-  ggplot(data = mapped_data, aes(x = Measure, y = Value)) + 
-    geom_boxplot(fill = settings[["boxcolor"]]) +
-    scale_y_log10() +
-    theme_bw() + 
-    theme(axis.text.x = element_text(angle = 25, hjust = 1),
-          axis.text = element_text(size = 12),
-          axis.title = element_text(size = 12))
-}
-
-#####################################################################
-# Step 2 - Initialize Custom Settings
-#####################################################################
-addSetting(
-  text_key="boxcolor", 
-  label="Box Plot Color", 
-  description="The color of the boxes", 
-  setting_type="character", 
-  setting_cat="appearance", 
-  default="gray", 
-  settingsLocation=custom_location
-)
-
-
-#####################################################################
-# Step 3 - Initialize the custom chart
-#####################################################################
-addChart(
-  chart="labdist",
-  main="labdist", 
-  label="Lab Distribution - static",
-  settingsLocation = custom_location,
-  requiredSettings=c("boxcolor","value_col","measure_col"),
-  type="static"
-)
-```
-
-## Full Code for Example 3 - Interactive Histogram
-
-```
-custom_location<-"customBoxplot/"
-
-#####################################################################
-# Step 1 - Write custom chart module code
-#####################################################################
-labdist_module_UI <- function(id) {
-  ns <- NS(id) 
-  tagList(
-    checkboxInput(ns("show_points"), "Show points?", value=FALSE),
-    checkboxInput(ns("show_outliers"), "Show outliers?", value=TRUE),
-    selectInput(ns("scale"), "Scale Transform", choices=c("Log-10","None")),
-    plotOutput(ns("labdist"), width = "1000px")
-  )
-}
-
-labdist_module <- function(input, output, session, data, settings) {
-  
-  ns <- session$ns
-  
-  mapped_data <- reactive({
-    data() %>%
-      select(Value = settings()[["value_col"]],
-             Measure = settings()[["measure_col"]])%>%
-      filter(!is.na(Value)) 
-  })
-  
-  output$labdist <- renderPlot({
-    
-    req(mapped_data())
-    
-    # set up the plot
-    p <- ggplot(data = mapped_data(), aes(x = Measure, y = Value)) +
-      theme_bw() +
-      theme(axis.text.x = element_text(angle = 25, hjust = 1),
-            axis.text=element_text(size=12),
-            axis.title = element_text(size = 12))
-    
-    # add/remove outliers
-    if (input$show_outliers){
-      p <- p + geom_boxplot(fill = settings()[["boxcolor"]]) 
-    } else {
-      p <- p + geom_boxplot(fill = settings()[["boxcolor"]], outlier.shape = NA) 
-    }
-    
-    # log-transform scale
-    if (input$scale=="Log-10"){
-      p <- p + scale_y_log10()
-    }
-    
-    # show individual data points
-    if (input$show_points){
-      p <- p + geom_jitter(width = 0.2)
-    }  
- 
-    p
-  })
-}
-
-#####################################################################
-# Step 2 - Initialize Custom Settings
-#####################################################################
-addSetting(
-  text_key="boxcolor", 
-  label="Box Plot Color", 
-  description="The color of the boxes", 
-  setting_type="character", 
-  setting_cat="appearance", 
-  default="gray", 
-  settingsLocation=custom_location
-)
-
-#####################################################################
-# Step 3 - Initialize the custom chart
-#####################################################################
-addChart(
-  chart="labdist_module",
-  main="labdist_module", 
-  label="Lab Distribution - shiny module",
-  settingsLocation = custom_location,
-  requiredSettings=c("boxcolor","value_col","measure_col"),
-  type="module"
-)
-```
\ No newline at end of file
diff --git a/vignettes/intro.Rmd b/vignettes/intro.Rmd
new file mode 100644
index 00000000..b7bcb53d
--- /dev/null
+++ b/vignettes/intro.Rmd
@@ -0,0 +1,139 @@
+---
+title: "Intro to Shiny App"
+author: "Jeremy Wildfire"
+date: "`r Sys.Date()`"
+output: rmarkdown::html_vignette
+vignette: >
+  %\VignetteIndexEntry{Intro to Shiny App}
+  %\VignetteEngine{knitr::rmarkdown}
+  %\VignetteEncoding{UTF-8}
+---
+
+# Intro Vignette
+
+The `safetyGraphics` shiny app provides an easy-to-use shiny interface for creating shareable safety graphics for any study. This vignette provides an overview of the app's functionality, shows how to initialize the app with your own study data, and provides links to technical resources explaining how to customize the app.  
+
+# safetyGraphics Demo
+
+A demo of shiny application using data from the [{safetyData} package](https://github.com/SafetyGraphics/safetyData) is hosted [here](https://jwildfire.shinyapps.io/safetyGraphics/). The app can also be initialized with the `safetyGraphicsApp()` function in the R console - see Appendix 1 for details. 
+
+Let's take a quick look at the various pages in the app.
+
+## Home Tab
+
+A home page has a basic overview of the app.
+
+
+
+## Mapping Tab
+
+The Mapping tab is used to tell charts which data columns and fields to use for various chart components. 
+
+
+
+This mapping process makes it easy to re-use charts across many different studies. You can see previews of the loaded data using the checkbox at the top of the page. The demo data has 3 data domains (labs, adverse events (aes) and demographics (dm)), but others can be added as well. The mapping tab is automatically filled in for common data standards, like the ADaM data shown here, but can also be filled in manually for non-standard data. 
+
+## Filtering Tab
+
+The Filtering tab allows users to interactively select which participants to include in charts. 
+
+
+
+This tab is created using the filter functionality included in the [{datamods} package](https://github.com/dreamRs/datamods#filter). Whenever data is filtered in this tab, those filtered data are used in all charts (across all data domains). Note that the number of participants selected is always shown in the upper right hand corner of the app. 
+
+## Charts Tab
+
+Clicking the Charts tab opens a dropdown menu containing a series of charts related to clinical trial safety. Clicking the [Hepatic Safety Explorer](https://github.com/safetyGraphics/hep-explorer) opens this page:
+
+
+
+safetyGraphics supports many different kinds of charts including web-based interactive graphics using {htmlwidgets} (like the chart shown above), static plots, plotly plots and custom shiny modules. Each chart has a header that provides details about the chart, links to chart-specific resources and buttons that allow users to download a stand-alone html report or a .R file that reproduces the chart. See the [Chart Configuration Vignette](ChartConfiguration) for more detail about the safetyGraphics charting framework. 
+
+## ⚙️ (Settings) Tab
+
+Finally, the Settings tab - shown as a gear icon ⚙️ -  contains technical details that can be used to customize/troubleshoot the app. Clicking on the "Code" sub-tab (shown below) allows you to download a zip file that can be used to re-open the app with with any customizations that have been made during your current session. 
+
+
+
+# Loading Study Data
+
+There are 2 primary ways to load your study data in to the safetyGraphics shiny app: 
+
+1. Using `safetyGraphicsInit()` shiny interface
+2. Passing data directly to `safetyGraphicsApp()`
+
+## Loading data with `safetyGraphicsInit()` 
+
+The `safetyGraphicsInit()` function starts a simple app that allows users to select charts and then load the data required via a point-and-click interface as shown below:
+
+
+
+The app dynamically determines which data sets are required for the selected charts and updates the "Data Loader" UI when the charts selection changes. Below, we've selected 2 charts from the labs domain - so the other data domains are automatically hidden. 
+
+
+
+Once you've picked charts, click the "Load" buttons in the "Data Loader" section to select data files for each domain.  Data is loaded using the import functionality from the [`{datamods}` package](https://github.com/dreamRs/datamods#import) which allows you to select data  loaded in your R session or load data files directly from your file system. `{datamods}` supports any file format that [{rio}](https://cran.r-project.org/web/packages/rio/index.html) can handle including text files, Excel, SAS and SPSS format. 
+
+Once you've loaded files for all of the active data domains, the "Run App" button will become active. Click it to initialize the app. 
+
+## Passing data to `safetyGraphicsApp()`
+ 
+You can also initialize the app with custom data directly from the R console. The basic workflow is as follows: 
+
+1. Load your data in to the R session
+2. Save your data as a named list. The name of each list item should correspond to a safetyGraphics data domain. 
+3. Run `safetyGraphicsApp()` using the `domainData` to pass the list of data frames. 
+
+Here is a simple example that starts the app with SDTM data from the safetyData library: 
+
+```
+library(safetyData)
+sdtm <- list(
+    dm=safetyData::sdtm_dm,
+    aes=safetyData::sdtm_ae,
+    labs=safetyData::sdtm_lb
+)
+
+safetyGraphics::safetyGraphicsApp(domainData=sdtm)
+```
+
+This example and other use cases are described in the `safetyGraphics Cookbook - Advanced Examples` Vignette.  
+
+# Additional Resources
+
+Several additional vignettes are available for more advanced topics: 
+- [Chart Configuration Vignette](ChartConfiguration) - details about the charting process including technical specifications and step-by-step instructions
+- [Cookbook Vignette](Cookbook) - a series of examples showing how to initialize the safetyGraphics Shiny app in different scenarios
+- [Technical FAQ Vignette](TechnicalFAQ) Vignette - vignette discussing security, validation and other technical issues
+
+The {safetyGraphics} app is maintained by the Interactive Safety Graphics (ISG) subteam of the ASA Biopharm-DIA Safety Working Group. You can learn more about the team and find links to recent presentations and publications at our [home page](https://safetygraphics.github.io/).  
+
+# Appendix 1 - Initialization code
+
+We suggest running the app in RStudio with R version 4.0 or higher. The following code installs the {safetyGraphics} package and initializes the app demo: 
+
+```
+install.packages('safetyGraphics')
+library(safetyGraphics)
+safetyGraphicsApp() 
+```
+
+Or to use the initialization workflow: 
+
+```
+install.packages('safetyGraphics')
+library(safetyGraphics)
+safetyGraphicsInit() 
+```
+
+Or you can install the most recent development version of {safetyGraphics} and the companion package {safetyCharts} directly from GitHub:
+
+```
+install.packages("devtools")
+library(devtools)
+devtools::install_github("safetyGraphics/safetyGraphics") 
+library(safetyGraphics)
+devtools::install_github("safetyGraphics/safetyCharts") 
+library(safetyCharts)
+safetyGraphicsApp() #or safetyGraphicsInit()
+```
diff --git a/vignettes/shinyUserGuide.Rmd b/vignettes/shinyUserGuide.Rmd
deleted file mode 100644
index 8efc3030..00000000
--- a/vignettes/shinyUserGuide.Rmd
+++ /dev/null
@@ -1,237 +0,0 @@
----
-title: "safetyGraphics Shiny App - User Guide"
-author: "Jeremy Wildfire"
-date: "`r Sys.Date()`"
-output: rmarkdown::html_vignette
-vignette: >
-  %\VignetteIndexEntry{safetyGraphics Shiny App - User Guide}
-  %\VignetteEngine{knitr::rmarkdown}
-  %\VignetteEncoding{UTF-8}
----
-
-```{r setup, include = FALSE}
-knitr::opts_chunk$set(
-  collapse = TRUE,
-  comment = "#>"
-)
-```
-
-# Overview
-
-The `safetyGraphics` Shiny app provides an easy-to-use point-and-click interface to create shareable safety graphics for any study.
-
-# Starting the Shiny App
-
-After opening RStudio and making sure you are running R version 3.5 or higher, the application can be started with just a few lines of code. In general, you'll want to load the latest stable release from CRAN:
-
-```
-install.packages("safetyGraphics")
-library("safetyGraphics")
-safetyGraphicsApp()
-```
-
-To load the latest development release from GitHub with `devtools`:
-
-```
-install.packages("devtools")
-library("devtools")
-devtools::install_github("SafetyGraphics/safetyGraphics")
-library("safetyGraphics")
-safetyGraphicsApp()
-```
-
-## Loading Large Files
-
-By default, Shiny only allows users to load files smaller than 5mb. If you want to load a larger file, use the maxFileSize setting when calling the app:
-
-```
-safetyGraphicsApp(maxFileSize = 100)
-```
-
-# Typical Workflow
-
-After opening the app, you will typically follow the workflow below. In short, you will load data (once), tweak settings and view charts (maybe more than once), and then export a snapshot of the charts for other users.
-
-
-
-This workflow lines up with the items in the toolbar for the App.
-
-
-
-More information about each step in the process is shown below.
-
-## Load Data
-
-When you open the app, you are taken to the Home Tab which contains some general information about the app and links to helpful documentation. Click on the Data Tab and you should see the "Data Upload" and "Data Preview" panels. The preview for the pre-loaded "Example data" dataset is shown by default.
-
-
-
-To load your own data, simply click the browse button and select a `.csv` or `.sas7bdat` data set. Once the file is loaded, select it in the list at the bottom of the "Data Upload Panel". Once selected, the "Data Preview" panel will update automatically (along with the Settings, Charts, and Reports tabs).
-
-The charts in the safetyGraphics app are specifically designed for clinical trial safety monitoring, and require laboratory datasets that contain one row per participant per time point per measure. Data mappings for two common [CDISC](https://www.cdisc.org/) data standards - [SDTM](https://www.cdisc.org/standards/foundational/sdtm) and [ADaM](https://www.cdisc.org/standards/foundational/adam) - are pre-loaded in the application. As described below, the app can automatically generate charts for data sets using these standards; other data sets require some user configuration.  
-
-## Update Settings
-
-After loading your data, navigate to the Settings tab to customize the behavior of the charts. This tab includes a Charts panel for selecting the charts you want to visualize and other panels for different types of chart settings. For example, the "Data Mappings" panel (shown below for the "Example Data" ADaM data set) can be used to specify the column that contains the unique subject ID, and on the more general "Appearance Settings" panel, there is an option to specify a warning message to be displayed when the chart loads. You can hover the mouse over any setting label to get more details. The small numbers to the right of the settings labels indicate the number of charts that use the relevant setting. Mousing over them presents a list of these charts.
-
-
-
-When possible, items on the settings tab are pre-populated based on the data standard of the selected data set. If a SAS data set with labels is provided, the relevant column labels will appear within brackets [] next to their variable names. You can see this in the Data Mappings screenshot above. See the Case Studies below for more details regarding working with non-standard data and adding customizations to the charts.
-
-## View Chart
-
-Once the settings configuration is complete, click on the Charts tab to view a drop-down of the available charts. A green check will display by charts that are ready to be visualized and a red X will indicate that settings need to be changed in order to render the chart. Simply click one of the options to view it. The chart tab updates automatically when settings are changed or new data is loaded.
-More details about chart functionality will be documented in separate vignettes.  
-
-
-
-## Export Results
-
-Navigate to the Reports tab to choose reports for export and click the "Export Chart(s)" button at the bottom to create a standalone copy of the charts using the current configuration. The export functionality combines the data, code, and settings for the charts in to a single file. In addition to the charts themselves, the export includes a summary of the tool, and code to recreate the customized charts in R.
-
-
-
-# Case Study #1 - Mapping Non-Standard data
-
-## Overview
-
-When a new data file is loaded, the app will detect whether the dataset is formatted according to ADaM or SDTM data standards.  If the uploaded dataset matches one of these standards, the settings tab will be pre-populated accordingly, and little or no custom user customization will be needed to generate a basic chart. However, no data standard is strictly required; the app also works with data in other formats. The specific data columns required varies between charts. For example, the only firm data requirements for the Hepatic Explorer chart are:
-
-- The data must have one record per participant per timepoint per lab test. That is, the data should be long, not wide.
-- The data must have columns for:
-    - Unique Subject Identifier (ID Column)
-    - Name of Measure or Test (Measure Column)
-    - Numeric finding or result (Value Column)
-    - Numeric upper limit of normal for the test
-    - Numeric lower limit of normal for the test
-    - Numeric study day
-- The following values must be present in the column corresponding to Measure or Test:
-    - Aminotransferase, alanine (ALT)
-    - Aminotransferase, aspartate (AST)
-    - Alkaline phosphatase (ALP)
-    - Total Bilirubin
-
-The app also supports data sets that partially match the pre-loaded data standards. The step-by-step instructions below outline how to create a chart for one such data set.
-
-## Step-by-step
-
-### 1. Open the App
-
-Paste the following code into RStudio:
-
-```
-#Code to initialize shiny application
-install.packages("safetyGraphics")
-library("safetyGraphics")
-safetyGraphicsApp()
-```
-
-### 2. Load Data
-
-Use the "Browse.." button on the data upload section of the data tab to load a non-standard data set. We'll use the `.csv` saved [here](https://github.com/SafetyGraphics/safetyGraphics/tree/master/inst/safetyGraphics_app/tests/partialSDTM.csv), but the process is similar for other data sets. Notice that once the data is loaded, the app will detect whether the data matches one of those pre-loaded standards, and a note is added to indicate whether a match is found. Our sample data is a partial match for the SDTM standard. Once you select the newly loaded data set, the app should look like the screen capture below. Click on the Charts tab and note the red X's in the drop-down indicating that user customization is needed.
-
-
-
-### 3. Select Columns
-
-Next, click the "Settings" tab in the nav bar at the top of the page. The page should look something like this:
-
-
-
-Behind the scenes, a validation process is run to check if the selected settings match up with the selected data set to create a valid chart. Green (for valid) and red (for invalid) status messages are shown after each label in the Settings tab - you can hover the mouse over the status to get more details.
-
-As you can see, we've got several invalid settings with red status messages. We now need to go through and update each invalid setting and turn its status icon into a green check. Once all of the individual settings are valid, the red Xs in the Charts drop-down will turn to green checks, and the chart will be created. Let's hover over the red X by the Measure Column Setting to see the detailed description of the failed check:
-
-
-
-As you might've guessed from the empty select box, the check failed because no value is specified for the setting. Choosing the measure column is simple. Click the select box to see pre-populated options corresponding to the columns in the data.
-
-
-
-Now select ID for the ID column, LBTEST for the Measure Column,  and LBDY for the Study Day Column option. Your setting page should look something like this:
-
-
-
-Now we need to fill in the 4 inputs beneath Measure Column. You may have noticed that there were no options available for these inputs when the page loaded. This is because these options are field level data that depend on the Measure Column option. Once you selected a Measure Column, the options for these inputs were populated using the unique values found in that data column. To fill them in, just type the first few letters of the lab measure in the text box. For example, type "Alan" for the Alanine Aminotransferase value input and select the correct option.
-
-
-
-Repeat the process for the other 3 "value" inputs and viola, the red X changes to a green check, and the Hepatic Explorer chart is ready.
-
-
-
-### 4. View Chart
-
-Now that we've got the data mapping complete, just select "Hepatic Explorer" from the Chart tab drop-down.
-
-
-
-The chart has lots of useful interactive features built in, but we'll cover those in a separate vignette.
-
-### 5. Export Chart
-
-To export the chart, click the Reports Tab, make sure that the Hepatic Explorer has a check by it, and click the "Export Chart(s)" button. Your chart, along with the other valid charts, will be saved in an `.html` file and downloaded to your machine.
-
-Open the downloaded file in a new tab in your browser and you'll see tabs for each of the charts and an "Info" tab. The Hepatic Explorer tab will be identical to the chart shown above, with all of your customizations intact. The "Info" tab, shown below, has a brief description of the safetyGraphics package and source code that you can use to recreate the charts in R.
-
-
-
-The html file contains all of the data and code for the charts and is easy to share. Just send the file to the person you're sharing with, and tell them to open it in their web browser (just double-click the file) - they don't even need R.
-
-## Summary
-
-This case study shows how to create a shareable chart created using custom settings in just a few clicks. Continue reading to find out how to add customizations to your chart.
-
-# Case Study #2 - Adding Customizations
-
-## Overview
-
-Only the most basic settings used by the `safetyGraphics` displays are populated by default, but users can also add a wide variety of additional customization. We'll walk through a few common customizations for the Hepatic Explorer chart in this case study including:
-
-- Adding grouping variables
-- Adding filter variables
-- Defining which rows should be included in the analyses using the Analysis Flag options
-- Defining the baseline measurement using the Baseline options
-
-## Step-by-Step
-
-### 1. Open the App
-
-Just paste this code in to RStudio:
-
-```
-#Code to initialize shiny application
-install.packages("safetyGraphics")
-library("safetyGraphics")
-safetyGraphicsApp()
-```
-
-We'll use the pre-loaded example data for this case study, so there is no need to load your own data file.
-
-### 2. Add Filters and Groups
-
-The `SafetyGraphics` Hepatic Explorer chart offers native support for data-driven groups and filtering. Any data column can be used to add filter and grouping controls to the chart. One common use case is to add grouping by treatment arm and filtering by site, race and sex. All of this can be done with just a few clicks. As you might have guessed, you just update the "Filter columns" and "Group columns" inputs as shown:
-
-
-
-Select "Hepatic Explorer" from the Charts drop-down tab to see the following chart (with orange boxes added around the newly created filters and groups for emphasis):
-
-
-
-A word of warning - both grouping and filtering work best using categorical variables with a relatively small number of groups (less than 10 or so). With that said, there is no official limit on the number of unique values to include in a group or filter, so if you followed the example above but chose "AGE" (with over a dozen unique integer values) instead of "AGEGR1" (with 3 categorical levels), you might not love the functionality in the chart. Fortunately, it's easy to go back and update the chart to use the categorized variable instead - just go back to the settings tab and update the corresponding setting.
-
-### 3. Flag Rows of Special Interest
-
-You can also use the settings page to identify important values in the data. For the Hepatic Explorer chart, you can flag baseline values (using the "Baseline column" and "Baseline values" inputs) and values included in the analysis population (using "Analysis Flag column" and "Analysis Flag values" inputs). In both cases, you need to choose the "column" first, and then choose 1 or more corresponding "values".  Here are some suggested settings using our sample data:
-
-
-
-In the Hepatic Explorer chart, adding a baseline flag enables the users to view a baseline-adjusted version of the chart. Click the chart tab, and then change the "Display Type" control to "Baseline Adjusted (mDish)".
-
-
-
-We're following ADaM conventions and using "flag" columns ending in "FL" and "Y" values for the configuration here, but any column/value combination is allowed. For example, you could use study day 0 to define baseline by setting baseline column to "ADY" and baseline value to "0".
-
-### Summary
-
-This case study shows how to add some basic customizations to your Hepatic Explorer chart with a few clicks in the shiny application. Note that not all customizations are available in the shiny app. You can access more granular settings by looking at the documentation for the underlying [hep-explorer github repo](https://github.com/SafetyGraphics/hep-explorer) javascript library.