Signals Clinical: Can I change the configuration of Line Listing Review (LLR) in Signals Clinical 3.x after Study data exists?

Problem:

My organization has a Signals Clinical tenant along with Line Listing Review (LLR), and we want to understand ramifications caused by changes to the configuration of Line Listing Review (LLR) in Signals Clinical 3.x after Study data exists. What about creation of cohorts based on tables that have gone through Spotfire transformations?

Background:

The Quick Start Guide (Revvity Signals Clinical 3.1 Quick Start Guide.pdf) is not meant to be fully inclusive, as its name implies.  This document is available as a download item from the Revvity Signals Download Center.

When you are logged into a Signals Clinical Review (SCL) tenant, you have access to many Help pages, per the following site address: https://<tenant_name>.revvitycloud.com/guide/Content/Home_Clinical.htm.

When this page renders, click on Capabilities > Line Listing Review. Review the "Line Listing Review" page in order to provide context to the below questions and answers.

Note that in SCL configuration a set of Key columns are declared, which SCL uses to uniquely identify records in Signals Clinical, to facilitate tracking. The values in these columns are usually meta-data associated with the record and typically do not change. The configuration of SCL also declares a set of Monitoring columns, which define the data that gets collected/observed as part of the review process. This is the data most likely to be modified at the source in response to edit checks/queries etc.

Solutions:

Impact of Changing the set of Key Columns After LLR Enablement
Question: If the Administrator changes the designation of key columns after LLR has been enabled for a Study, will all rows be marked as New, as in (classic) SLLR?

Answer: Yes, all rows will be reset and marked as New. Review history will be lost when the Administrator modifies the set of key columns. This makes changing key column designations potentially dangerous once the review process has begun.

Impact of Adding/Removing Monitored Columns After LLR Enablement
Question: If the Administrator adds or removes monitored columns after LLR has been enabled for a Study, will all rows be marked as Amended, as in (classic) SLLR?

Answer: The behavior depends on the current status of rows:
1. Rows with "New" status will remain "New".
2. Rows with "Amended" status will remain "Amended" and retain all review history.
3. Rows with "Reviewed" status:
- Will change to "Amended" if any monitoring column data changes.
- Will remain "Reviewed" if no monitoring column data changes.

The amended status calculation in SC differs from the old (classic) SLLR:
- old (classic) SLLR used row-level calculation by concatenating all monitoring column data into a hash value
- SC uses cell-level calculation, comparing each monitoring column value directly

Adding or removing monitored columns does not automatically change row status if the data in existing monitored columns remains unchanged.

The amended status calculation is cell level. For every monitoring column, SCL compares the values directly:
If column data is changed, then one history record is added for this change. 
The row status changed to Amended if any monitoring column data changed. 
If all monitoring column data does not change, then status will keep as it was.

Example: Monitoring columns A, B, C, and data changed in A, B. Then
1. Row status changed to Amended (If it has been reviewed).
2. One history record added for column A data change with original data and new data.
3. One history record added for column B data change with original data and new data.

Cohort Creation from Transformed Tables
Question: Can cohorts be created from tables that have gone through transformations?

Answer: No, cohorts can only be created from tables that exist directly in Signals Clinical. The cohort menu is only available for tables with SC as the data source. SC's strategy is to develop transformation capabilities directly within SC rather than supporting integration of externally transformed data. When creating cohorts, the system needs the original row keys from SC.