📊
ACUITY Training Documentation
  • ACUITY
    • Introduction
    • Background
    • System Components
    • Why is it useful?
    • Where can you use it?
    • User group
  • Granting access
    • VA Security Overview
    • User access
      • Adding new users
      • User roles and access
      • Granting access to drug programmes and datasets
      • Controlling views in VA HUB
        • Views available for REACT Packages
  • Data Loading
    • Data Loading Overview
      • ADMIN UI overview
        • ADMIN UI user guide
      • General overview
  • Creating a study
    • Configuring a drug programme
    • Configuring a dataset
  • Creating a dataset
    • Mapping mandatory data files
    • Loading mandatory data files
    • Reviewing data load success in ADMIN UI
      • Checking mandatory data load
      • Access to data load report
      • Data load statuses
      • Data load error classifications
      • Data load reports
    • Reviewing data quality in VA HUB
  • Data Loading Exercise
  • Loading Specific Data Types
    • Adverse Events
      • Adverse Events data
      • Mandatory data mappings
      • Mandatory data load
      • Reviewing mandatory data load in ADMIN UI
      • Reviewing mandatory data quality in VA HUB
      • Non-mandatory data mappings
      • Non-mandatory data load & reviewing load success in ADMIN UI
      • Reviewing non-mandatory data quality in VA HUB
      • Adverse events loading exercise
    • Labs
      • Labs data
      • Mapping Labs data
      • Loading Labs data and reviewing success in ADMIN UI
      • Reviewing Labs data quality in VA HUB
      • Labs loading exercise
    • Dosing & Exposure (PK)
      • PK data
      • PK concentration data
      • Specimen collection data
      • Stacked PK results data
      • Reviewing PK data quality in VA HUB
      • Dosing & Exposure (PK) loading exercise
    • Tumour Response (RECIST)
      • Tumour response data
      • Recist target lesion assessments (recist1) data
      • Recist non-target lesion assessments (recist1) data
      • Recist assessment summarised (recist2)
      • Recist data loading and review in ADMIN UI
      • Recist 1 & 2 data mapping, loading and reviewing
      • Reviewing tumour response (RECIST) data quality in VA HUB
      • Tumour Response (RECIST) loading exercise
        • Recist 1 and Recist 2 loading exercise
Powered by GitBook
On this page
  1. Loading Specific Data Types
  2. Adverse Events

Non-mandatory data mappings

Non-mandatory fields can also be mapped into ADMIN UI to build out the visualisations in the Adverse Events view.

PreviousReviewing mandatory data quality in VA HUBNextNon-mandatory data load & reviewing load success in ADMIN UI

Last updated 3 years ago

As with mapping mandatory data fields in the Adverse Events (AEs) mappings table what is represented in the Source data column from the source data file and play a key role in successful loading of data

AE Mapping table

When mapping source data columns to the mapping table ensuring the fields are populated with the correct data and that the data is in the format required for the mapping field - text, numeric, date or time is important

Data fields requiring dates - from the aggregation functions select the date format that is represented in the source data file

*Date format exception* - The data field AE severity change dates must be populated with date format MM/DD/YYYY - the source data file must represent dates for this field in this format

AE severity grade changes for this field the source data column will contain multiple column names from the source data file.

All the columns in the source data file containing AE severity grade changes must be mapped.

NOTE: the column which contains the starting severity grade is NOT required in this field

Note: when adding multiple column names in a Source data column field each column name is followed by a comma and space - example: AE_SGC1, AESGC2, AESGC3,

Aggregation functions: Multiple AE severity grade changes must be selected for the data field AE severity grade changes - this allows the information to be collected from all the columns

AE severity change dates field is populated with all the source data columns with the dates associated with the severity grade changes - remember these should be in the format MM/DD/YYYY in the source data file

Aggregation functions: Multiple AE severity grade changes must be selected for the data field AE severity change dates -- this allows the information to be collected from all the columns

Action taken due to severity grade changes for investigational drugs this field is populated with all source data columns which contain information on the action taken due to severity grade changes.

The initial action taken source data column does not need to be populated in this field because it has already been captured as a separate data field

Populating this column will allow this to be selected as an option in the event filters in the AE visualisation

Aggregation functions: Array must be selected for the data field Action taken due to severity grade changes for investigational drugs - this allows the information to be collected from all the columns

Remember: not all the non-mandatory fields need to be populated it depends on your source data files and what data you capture, what data is entered will impact what is seen in the visualisations

TRAINING VIDEO: This video walks through an example of mapping non-mandatory AE data, highlighting the areas above

Aggregation functions
LogoACUITY_docs/Adverse Event Table_v1.0.docx at main · digital-ECMT/ACUITY_docsGitHub
Adverse Events Mapping Table
Adverse Events: Non-Mandatory Data Mappings