How do I set up mirrored table rows from scheduled events to (S)AEs?

Available with version 4.10.0.

Learn how to configure mirrored table rows functionality that enables structured mirroring/linking of data - particularly table rows such as Concomitant Medications or lab data - from scheduled event forms into (S)AE forms. 

TABLE OF CONTENTS

• 1. Understanding the basics
  • 1.1. Prerequisites and availability
  • 1.2. Supported source types
  • 1.3. Data mirroring specifications
• 2. Creating the source and destination table in forms (Step 3)
  • 2.1. Creating the source table in Step 3
  • 2.2. Using "Save as reusable" option for compatibility
  • 2.3. Creating the destination table in (S)AE forms
  • 2.4. Destination table compatibility requirements
• 3. Setting up the mirrored table rows tab
• 4. Data behaviour and integration
• 5. Access rights and permissions
• 6. Amendments and sandbox considerations

Mirrored table rows functionality allows you to automatically transfer data from entire table rows from scheduled events to (S)AE forms. This feature provides structured mirroring where users can select which rows to mirror, navigate between source and destination, and manage updates via a secure, validated workflow.

Unlike manual linking or passive pre-filled fields, mirrored data becomes a true part of the (S)AE form: auditable, exportable, and governed by standard form behaviors like progress tracking, signature, SDV, and notifications. This feature ensures that critical information - like ConMeds or lab data linked to an adverse event - is fully integrated into the safety documentation and operational workflow.

1. Understanding the basics

1.1. Prerequisites and availability

Mirrored table rows functionality is only available when the (S)AE module is activated for the study. This feature creates a close connection between scheduled events and adverse event reporting, ensuring seamless data flow within your safety workflow.

Before setting up mirrored table rows, ensure that:

• Your study has the (S)AE module enabled.
• Source tables in scheduled events are properly structured and contain relevant data (see section 2.1. Creating the source table in Step 3 and 2.2. Using "Save as reusable" option for compatibility).
• Destination tables in (S)AE forms are configured to receive the mirrored data (see section 2.3. Creating the destination table in (S)AE forms and 2.4. Destination table compatibility requirements)

1.2. Supported source types

Supported sources:

• Regular tables from scheduled events
• Repeating fields from scheduled events
• All standard input field/column types within tables

Excluded sources:

• Matrix fields (not supported as source tables)
• ePRO forms (cannot be used as source for mirroring)
• (S)AE forms (can only serve as destinations, not sources)

1.3. Data mirroring specifications

What gets mirrored: Complete selected table row data with all entered field values.

What does not get mirrored: Queries from source data, source form signatures, SDV, or locking status.

2. Creating the source and destination table in forms (Step 3)

Before you can configure mirrored table rows in Step 5, you must first create the appropriate source and destination tables in Step 3 - Forms. This foundational step ensures that your tables are properly structured and compatible for mirroring functionality.

2.1. Creating the source table in Step 3

Navigate to Step 3 (Forms) in your study configuration. Select the scheduled event form where you want to create the source table. Add a new table or repeating field to your form, then

1. Configure the table structure with the appropriate columns and input field types.
2. Set up field configurations such as choice options, date formats, and any other field-specific settings.
3. Complete the table setup with appropriate labels, descriptions, and any required dependencies.

2.2. Using "Save as reusable" option for compatibility

Activate the "Save as reusable" flag in the source table when it is fully configured. This is a best practice that ensures perfect compatibility when creating the destination table. This approach eliminates configuration mismatches and reduces setup errors.

2.3. Creating the destination table in (S)AE forms

Navigate to the (S)AE form in Step 3 (Form Design). Instead of creating a new table from scratch, use the reusable field you saved from the source table from the list "Existing fields". Insert the reusable table component into your (S)AE form.

2.4. Destination table compatibility requirements

3. Setting up the mirrored table rows tab

Navigate to your study's Trigger Events configuration in Step 5 of the study configuration. Locate the "Mirrored table rows" tab next to the existing "Mirrored fields" tab. Click on it to access the configuration interface. 

	Click the "Configure table row mirroring" button to start a new configuration.
	Give the new mirrored table configuration a descriptive name to help identify its purpose. ⚠️ Important: There is no option to save incomplete mirrored table configurations as drafts. You must complete the entire setup before saving. Fortunately, this only takes a few clicks.
	In the Source dropdown, select the input form from your scheduled events. Choose the specific table or repeating field you want to mirror from the available options. ⭐️ Refer to 1.2. Supported source types for more information.
	In the Destinationdropdown, select the (S)AE form where you want to mirror the data. Choose the destination table that will receive the mirrored data. The system will only show compatible destination tables based on your source selection ⭐️ Refer to 2.4. Destination table compatibility requirements for more information.
	Save the mirrored table rows configuration.
	Once you've created mirrored table configurations, you can activate/deactivate, duplicate, delete, or expand/collapse it.

4. Data behaviour and integration

For a comprehensive overview of the data entry and mirroring experience from the site user perspective, refer to the companion article 

That article provides detailed guidance on the practical aspects of working with mirrored table rows, including:

• How the mirroring process works during data collection
• How mirrored table functionality integrates seamlessly into the (S)AE workflow
• Understanding that mirrored data becomes actual (S)AE data with full form integration
• Important considerations regarding the impact on signatures, SDV status, and form locking
• Step-by-step instructions for selecting, managing, and updating mirrored data

5. Access rights and permissions

The system implements specific access rights behavior based on:

1. Scheduled events read/update rights: Controls source data access
2. (S)AE read/update rights: Controls destination data access
3. Combined permissions: Determines overall mirroring capabilities

View the related role-based rights in the overview: All Climedo role rights and their explanation.

6. Amendments and sandbox considerations

Once your study is active, mirrored table rows configurations become read-only to protect data integrity. You can view existing configurations but cannot modify, add, or remove them.

To make changes in active studies, use the sandbox environment where you can activate/deactivate, duplicate, delete, add, or update mirrored table configurations. After testing thoroughly, publish the sandbox to apply changes to the active study.