Report Builder (Ad-hoc Reports)

Setting Up and Running Ad-hoc Reports

The Report Builder tool provides a means of pulling specific variables or measured outcomes together into targeted listings for a quick view of data that needs to be reviewed, tracked, or made available to specific user roles - including study Participants. This is an alternative to exporting all the data and then needing to filter or report on it outside of the system.

Table of Contents:

Running Reports

Creating and Modifying Reports

Role targeting/Report Visibility

Accessing and Running Reports

Prerequisite: User role has Access to Report Builder

 

Web Browser:

 

 

 

Mobile App:

RBaccessmob1

 

 

If your user role has been given access to one or more reports, they will display in the table of reports. From there, they can each be run.

Web Browser:

Mobile App:

Tap on a report to highlight it, and then use the Execute function at the top right:

Running Reports for a Given Participant

The same reports can be found from within each Participant's casebook, but with an added capability of automatically filtering the data for the respective Participant. 

From the Participant’s casebook screen, access the reports from the right side (web browser only):

ReportSubexecute1

 


Creating and Modifying Reports

Prerequisite: User has Access to Report Builder and access to Create or Setup a Report

The creation of a new report first involves defining the basic parameters:

  • The forms from which data is to be included in the report
  • The user roles that will have access to view the report 

Web Browser:

RBsetupmain1

1. Name the report and choose what type of data to include.  The name can be any name with a maximum of 100 characters. The report name is displayed when the report is executed so the name should be representative of the data in the report as closely as possible. Options of what to include:
  • Use Label Header - Use reporting label instead of the field name, as defined in the form builder
  • Include Draft Records  - Include records saved as a draft (not applicable if the study does not include draft saving)
  • Exclude Admin sites - By default, reports include both Provider and Admin site data. Check this option to only include Provider site data.

2. Choose which form type to build a report from.  Participant forms (data collected in the Subject Manager) or Site forms (data collected in site documents).

3. Select which role(s) to make the report visible to. This assumes the selected role(s) also has access to the report builder. User roles that don’t have the ability to define their own reports will need reports created for them and deployed to their role.

4. Save the report to populate the table. Now the report can be set up with specific data and filters as described below.

Blinded fields are supported in the report builder when reports are run. If a report includes variables that are blinded to certain roles in the study, and if those same roles are given access to run the report, they will not see the blinded data.

 

Mobile App:

RBsetupapp1

Defining the Report Variables

RBsetupweb2

Clicking the Setup link will display the Report Setup page. From the top, select which form to work with. From the list of available fields, add them to the 'Included' column. Do this for each form that was included in the report. Holding down the shift key on the web will allow for selecting/moving multiple variables at a time.


RBsetupweb3

The same can be done for filters that need to be made available within the report.

Mobile App:

Tap and drag fields from one table to the other.

RBsetupapp2

Joining data from multiple tables can cause confusion if the user building the report is not considering the relationships of data and how they should be joined together.

TrialKit uses a Left Outer Join method. This is opposite of the Standard Join in that a table row will still be included in the report even if the joined table has no matching row. for example if Participant ID from Demographics is being joined to the Heart rate value on the Vitals form, and the vitals does not exist for a given Participant, The Demographic data will still display as a row in the report. Alternatively if multiple Vitals have been entered for a given Participant, the report will repeat the single Demographics data for each row so that it can show the multiple vitals records.

Report Configuration

Because of the longitudinal nature of clinical trial data, it is very important to understand the relationship between the forms. Imagine a typical trial. The central entity is the Participant. Case Report Form data is captured concerning the Participant. How that CRF data relates to that Participant is very important.
The form can have 3 types of relationships:

  • One to One
  • One to Many
  • Many to Many

One to One

This is the simplest of all relationships. It means there is exactly one record per Participant per form. A good example might be the demographics form. Normally, there is only a single demographics form to complete per Participant. If the enrollment or Registration data is the master Participant record, then the demographics record can be joined right alongside it.

 

One to Many

An example here is when wanting to view something like Demographics (collected once) to Adverse Events (collected many times). When joining variables from both tables, it should be expected that for a given subject, the Demographics data will show repeated down each row based on the number of rows of Adverse Event records that also need to display.

 

Many to Many

Things get a little more complicated when relating data from two forms containing many records per Participant. A good example of a "Many to Many" relationship is when comparing Medications to Adverse events.


Here's an example of a subject with two AEs and 2 related CMs:

Building a report without setting up the form configuration, the output ends up giving four rows of data (one for each record):

From the above, it's hard to see which CM each AE is related to. This is where the form configuration comes in. It can be updated to this:

With the above, the system is being told that each CM is related to an AE if it occurred within four days of the AE. 

The Form's visit date field is how the report determines the Days Before/After

Now the output makes more sense:

 

Basic Rules when using the Form Configuration

  • The sequence in which forms appear is determined by the order designated in the Form Configuration Table.
  • If required is not checked for a form, the Participant will appear in the report with empty columns if the given form does not exist for the Participant. If required is checked for a form and the form does not exist, the Participant will not appear in the report.
  • Relate one form to another and use the Days Before and Days After to select which forms are related.

Modifying Existing Reports

With access to setup reports, existing ones can also be modified via the "Edit" option on each report in the table. This can be used to update the basic parameters of the report: 

  • Forms included
  • Report properties
  • Roles that the report is available to

To only modify the variables shown in the report, use the "Setup" option.

 


Role Targeting/Report Visibility

Users will only be able to access reports if the reports have been made available to their role within the report configuration as described in the section above.

Points Regarding Report Visibility for a Given Role

  • If a role is given access to a report be sure that role also has access to the report builder
  • If the role is a site type role, the user will only see data for the site(s) in which they belong
  • Field blinding is enforced on reports - so if a user is blinded to a field that is included in the report, that data will not display when they run the report
  • Users with reports targeted to their role will also be able to access them in both the Report Builder and within the Participant's casebook screen
  • If a report is targeted to a Participant user role, the Participant will have access within the Participant web portal on the web browser.