Overview

Life Science Analytics Cloud (LSAC) is the leading AI-powered clinical analytics platform from Saama that seamlessly integrates clinical trial data, delivering more actionable insights for faster decision making. 

Saama’s suite of cloud-based applications in LSAC offer powerful data aggregation, monitoring, analytics, and collaboration capabilities, so sponsors and CROs can optimize study planning, enrollment, compliance, productivity, and oversight.

This document contains important information on new features and updates for LSAC v4.1.

New Features/Enhancements

This section gives a list of new features and/or updates for each module worked upon or improved.

1

  • Enhancements in Clinical Insights

    COM-4802: New X-axis parameter – Study Days for widgets


The addition of the X-axis parameter, namely, Study Days, to widgets represents subject data in correlation to relative study days. The chart starts from the first dosing date of the subjects selected. The Study Days parameter has been implemented in the following dashboards: 

  • For Lab Spaghetti Plot – Baseline Deviation - Study Days are plotted according to Lab Days.
  • For Safety Summary – Study Days are plotted as 0, 30, 60, 90 and so on, in the interval of 30 study days. 
  • For Subject Progression and Subject Event Log, the relative study days calculation is as follows:
  • Relative Study Days for AE = AE Date – Subject Start Date
  • Relative Study Days for CM = CM Date – Subject Start Date
  • Relative Study Days for Dosing = Dosing Date – Subject Start Date
  • Relative Study Days for Disposition = Disposition Date – Subject Start Date

Subject Start Date Calculation: Based upon the ‘First Event’ setup on Disposition Event Configuration dashboard, the start disposition is picked and accordingly the minimum date is calculated for each study-site-subject combination as Subject Start Date as per the Start Disposition Event setup.

Note: 

  • If any disposition is earlier than the Subject Enrollment Date, then relative study days will be in negative.
  • If an AE date is earlier than the Subject Start Date, then that AE is plotted/counted for relative Study Day 0 (zero).

                             


COM-4136: GPP Enhancements 2.0

1

The Graphical Patient Profile dashboard has been enhanced to include the following:

  • AE Severity Grading Over Time

The horizontal bar will depict AE severity over time through color-coded labels and indicators that have been specified in the configurable GPP template.

Note: If AE Severity Date is not mentioned, then AE will be plotted from the AE Start Date until the AE End Date.

 

  • Configurable Subject Metadata

Metadata visibility in GPP can be customized from the Data tab in the GPP template, except for the following infographics that would always be present whenever the dashboard is rendered. These are, i) Study Name, ii) Study ID, iii) Site Name, iv) Site ID, and v) Subject ID

By default, GPP metadata comprising of all the infographics will be visible when subject data is rendered. These are, i) Study Name, ii) Study ID, iii) Site Name, iv) Site ID, v) Subject ID, vi) Therapeutic Area, vii) Medical Indication, viii) Phase, ix) Gender, x) Age, xi) Date of First Dose, xii) Date of Last Dose, xiii) Discontinuation Date, xiv) Discontinuation Reason, xv) Cause of Death, xvi) Date of Death

Additionally, as an admin user, you can also select the following infographics to be made visible, if required. These are i) Subject Info Query, and ii) Subject Info Query Labels

If data is not available for any infographic, then ‘’–--‘’ will be displayed.

  • Addition of ‘Discontinuation Details’ in GPP Metadata

Two new withdrawn details, namely, Cause of Death and Date of Death, will be visible in the metadata/summary card section of GPP. These two metadata elements will only be seen if the discontinuation cause is Death.

  • 5-point interval for Y-axis

Subject Exposure data can be distributed into intervals of 5, for better data consumption. The admin user can enable this setting in the Options tab of the GPP template.

  • Addition of the Date Range filter

The addition of the dashboard-level date range filter allows the user to view widget data, based on the time period specified in the date range filter. By default, the time period selection rendered on the date range filter is from the start date of the subject’s lab result to the end date of the subject’s lab result or the current date (whichever is earlier).

s1

COM-4840: Change of source table to capture Drug Response

1

Drug Response data as seen on the Subject Progression dashboard will be captured from the source table, namely, RS table – Disease Response and Clin Classification table and not from the EX table as was done earlier.


COM-5098: Subject Data plotted against Lab Assessment Date

1

Subject data markers will be plotted at actual lab assessment dates, irrespective of visit date, in the dashboards Lab Spaghetti Plot – Baseline Deviation and Lab Spaghetti Plot – Absolute Value. A lab assessment date can fall between 2 consecutive subject visits and the corresponding logic for the calculation is as follows:

Lab Assessment Date = Visit Number for Visit 1 + [(Lab assessment date – previous visit date)/total number of days between previous and next visit]

1

  • Enhancements in Operations Insights


COM-4803:  Redesigned – Site Performance dashboard

1

The Site Performance dashboard – Study has been redesigned with additional filters and a more effective and user-friendly UI that aids in better data consumption. KPI performance is gauged through the charts, with one chart for one KPI. The 10 most highest/lowest performing sites, based on the KPI selected can be viewed in tabular form. These enhancements are listed below:

  • Global filter selection can most easily render data on this dashboard without the need to select dashboard-level filters. 
  • Newly added dashboard level filters, namely, Country, and Study Name enable the user to see a more focused analysis.  
  • Additional site performance parameter, namely, %SDV Completion has been added to draw out analysis on the same.

1

COM-4801: Enrollment Rate calculation stops when LPLD is achieved 

1

The enrollment rate measured over a period of time, will stop being calculated, when the milestone LPLD (Last Patient Last Dose) is achieved. If the LPLD is not available, then the LPLV milestone will be considered at the site and study level. The details of the milestones, LPLD or LPLV, in the tooltip of the following widgets will be a good indication to know when the enrollment rate calculation has stopped. These are:

  • Enrollment Rate KPI – Portfolio Summary dashboard - Portfolio
  • Site Activation and Enrollment Over Time – Study Summary Dashboard – Study
  • Site Activation and Enrollment Over Time – Site Activation dashboard – Study
  • Protocol Deviations, View By: Month & Year – Quality Measures dashboard – Study
  • Enrollment Rate KPI – Site Summary dashboard – Site
  • Enrollment Rate KPI – Cross Study Performance dashboard – Site
  • Enrollment Rate – Site Performance dashboard – Study
  • Subject Enrollment Rate – Study/Country/Site

 

COM-4781, COM-4738: Newly added attributes – Site Status, Site FPFV, and PI Email

1

The attributes, namely, Site Status, FPFV (First Patient First Visit), and PI Email have been added to the following dashboards and listing:

  • Oversight Scorecard – Site Status, Site FPFV, and PI Email details can be seen in tooltips on hovering over the Site ID/Name and over the oversight scorecard. New added columns, namely, Site Status, Site FPFV, and PI Email are visible in the tabular view of the oversight scorecard.
  • Cross Study Performance – Site Status, Site FPFV, and PI Email are visible when the user clicks Site Details to flip the tile. 
  • Site Summary – Site Status, Site FPFV, and PI Email are visible when the Site ID is expanded.
  • Listing – Site – Newly added column, namely, PI Email has been added.

1

COM-4820: Active Global filter in Site Summary dashboard

1

Data can be rendered on the Site Summary dashboard – Study, through study selection made in the Global filter that appears in the Top Navigation Bar without selecting any parameter values in the dashboard-level filters.

Note: Study selection in Global filter is based on the study-access defined for every user.



COM-4792: Enhanced UX with respect to Data Unavailability

1

Based on data availability, site names/ID and KPI name will be greyed to indicate that no data is present, on these specific sites or for these specific KPIs, for analysis. The dashboard, Cross Study Performance, displays the message below the filters as follows:

For grayed out KPI, no data available to display in dashboard

1

COM-4814: Widget – ‘Study Site Progress Status’ is now configurable 

1

The funnel widget, namely, Study Site Progress Status in Site Activation dashboard – Study, is configurable from source so as to show only those milestones that are applicable. The applied milestones are arranged in the sequence in which they would occur on an active site.

Additionally, three new site statuses have been added and these would be visible in alphabetical order in the funnel widget. These are:

  • Active
  • Enrollment Open
  • Active – No Longer Recruiting

1

COM-4982: Lazy Data Loading in Portfolio Summary dashboard

1

Lazy loading of data has been implemented on the Portfolio Summary dashboard – Study that allows data to be rendered in smaller chunks to enable a quick data response.

1

COM-4993: Correction on AE Category labels

1

AE Category labels that are perceived as a combination have been corrected to be read as follows:

  • Serious & Related
  • Serious & Not Related
  • Not Serious & Related
  • Not Serious & Not Related

The dashboards & KPIs that reflect the new AE Category labels are, i) Safety Summary dashboard – Study, ii) AE Rate per Subject Days KPI at study, country, and site level.

1

COM-4914: Newly added filters in Site Summary dashboard

1

New dashboard level filters, namely Country and Site, have been added to the Site Summary dashboard – Study to enable a more focused rendering of data for better analysis. The filters appear in hierarchy order where the prior filter selection dictates the values seen in the filter that appears next. These filters are:

  • Country – Multi-select, non-mandatory filter
  •  Site – Multi-select, non-mandatory filter

  • Enhancements in Smart Search powered by DaLIA*

     

    COM-3970, COM-4248: Entity addition to all DaLIA intents/queries

    The following entities will be recognized in all of DaLIA queries that are submitted at study level and at site level. These entities are:

    • Study-level recognized entities: TA | Study Phase | Study Sponsor | Study Status |Investigator Name |  CRO
    • Site-level recognized entities: TA | Study Phase | Study Sponsor | Study Status | Investigator Name | Investigator | CRA | CRO 

    Additionally, the entity Site Name will be recognized by DaLIA when querying. The auto-suggestive approach will help the user to select the site name as he/she types the initial letters (of site name) in the DaLIA search bar. The site names will be suggested as per the study selections done in the Master Study Filter (MSF). Study select options in the MSF are determined as per the study access defined for each user.

    1

    COM-3712: Newly added intent – Subject intent

    Subject-level queries related to i) Adverse Events, ii) Concomitant Medications, and iii) Lab Results can be submitted to DaLIA to gain insights at subject-level or for a specific subject ID. 

    1

    COM-4029, COM-4380, COM-4329: Customized Listing Views & Multi-level Sorting of Output

    • Freeze columns

    In any listing obtained as a DaLIA response, the first three columns will be ‘Freezed’ by default – that is, they would remain visible even when the user scrolls to the right. The user can choose to freeze 3 or more than 3 columns, as best as it would be to his/her advantage. Columns that are ‘freezed’ will appear to the left of the listing. 

    The top row in the listing will always remain ‘freezed’ and will be visible even when the user scrolls to the bottom of the listing.

    • Show/Hide Columns

    The user can also choose to show/hide columns that appear in the listing output. By default, all columns will be visible in the listing and the user can then configure the selection through the Settings icon.

    • Sorting of Output

    Users can select multiple columns to sort the listing output. All listing columns will be available to apply sorting to. Sorting can be done in ascending or descending order. Columns such as Country, Site ID, Region, CRA Name, Investigator Name, Milestone, and so on.

    1

    COM-4488, COM-4569: Introduction to Pie Charts & High Charts in DaLIA

                    Visualizations of DaLIA output will be seen on queries related to Adverse Events. These are as follows:

     

    • Queries related to the trend of adverse events over a period of time (weekly, monthly, and so on) will be answered as a high chart. The high chart will be rendered as a stacked column chart (depending on the query), and legend key. Hovering over the stacked column will reveal relevant AE data. The three stacked columns are described below: 
      1. Three columns will be rendered for queries containing all the parameters (refer to the DaLIA Pre-trained Intents table), namely, i) Seriousness (Serious & Not Serious) -2 Stack Columns, ii) Relatedness to IP (Related & Not Related, Incomplete Data) - 3 Stack Columns, and iii) Combination of Seriousness & Relatedness to IP - 5 Stack Columns.
      2. A baseline/reference line will run through the graph, at specific points that indicate the average number of adverse events for that specific week/month/year. This baseline will be visible for AE trends related to the site/country/region and will not be visible for AE trends related to studies.
      3. Time depiction on X-axis will be presented as such: For Weekly – week 1/month, Monthly – MMM-YYYY (default selection), Yearly – YYYY.
    • Queries related to the count or percentage count of adverse events will be answered as a pie/donut chart and a listing. The pie/donut chart may, at the maximum, 5 segments since the count of adverse events will be presented in 5 combinations, that is, Serious & Related, Serious & Not Related, Not Serious & Related, Not Serious & Not Related, and Incomplete Data (when relatedness is unknown or if data is incomplete). Hovering over the pie/donut chart will give more relevant details.

    Users can switch over to the listing view, if needed.

    1

    COM-4842: Newly added Subject Disposition Events in DaLIA

    The following Subject Disposition events will be recognized by DaLIA and can be queried upon. The new subject disposition events are applicable to Study/Country/Site/Region. These are:

    • Follow up agreed
    • Follow up not agreed
    • Treatment initiated
    • Treatment not initiated
    • Discontinued before treatment
    • Discontinued after treatment
    • Withdrawal of Consent
    • Screened

    1

    COM-4793: Intents can be combined using the ‘AND’ & ‘OR’ operators

    All disposition events can be queried upon, either one-at-a-time or by clubbing two or more of them by using the AND & OR operators except for the dispositions events, namely, Screening and Enrollment that cannot be clubbed with other disposition events for querying. 

    Additionally, time frames such as, a date range, month, year, are not considered when two disposition events are clubbed together for querying.

     

    COM-3970, COM-4248, COM-3712, COM-4029, COM-4380, COM-4329, COM-4488, COM-4569, COM-4842, COM-4793: Scope & Calculations of New Intents

    Type 

    Intent 

    Calculation 

    Entity

    Trend of Adverse Events 

    (High chart)

    Adverse Events over Timeframe for seriousness 

    For serious AE: count of all AE which fulfills all of the following criteria: 

    • AE start date is same or later than the date taken as first date (timeframe or no timeframe)

    • AE start date not null Serious/Yes in “aeser” column

    For Non Serious AE: count of all AE which fulfills all of the following criteria: 

    • AE start date is same or later than the date taken as first date (timeframe or no timeframe)

    • AE start date not null

    • All values except “serious” and “yes” will be considered in the non serious category. 

    For Total AE: count of total AE = count of severe AE + count of non serious AE

    Study, Region,  

    Country, and Site

    Trend of Adverse Events 

    (High chart)

    Adverse Events over Timeframe for relatedness 

    For related AE: count of all AE which fulfills all of the following criteria: 

    • AE start date is same or later than the date taken as first date (timeframe or no timeframe)

    • AE start date not null Yes/Definitely related/ Probably related/possibly related in “aerelnst” column

         For Not related AE: count of all AE which fulfills all of the following criteria: 

    • AE start date is same or later than the date taken as first date (timeframe or no timeframe)

    • AE start date not null 

    • No in “aerelnst” column

          Incomplete data: count of all AE which fulfills all of the following criteria: 

    • AE start date is same or later than the date taken as first date (timeframe or no timeframe)

    • AE start date not null Blank/null value in “aerelnst” column

        For Total AE: count of total AE = count of related AE + count of not related AE+ count of AE with incomplete data

    Study, Region,  

    Country, and Site

    Trend of Adverse Events 

    (High chart)

    Adverse Events over Timeframe for combination of seriousness and relatedness 

    For serious- related AE: count of all AE which fulfills all of the following criteria: 

    • AE start date is same or later than the date taken as first date (timeframe or no timeframe)

    • AE start date not null Serious/Yes in “aeser” column

    • Yes/Definitely related/probably related/possibly related in “aerelnst” column

          For serious- not related AE: count of all AE which fulfills all of the following criteria: 

    • AE start date is same or later than the date taken as first date (timeframe or no timeframe)

    • AE start date not null Serious/Yes in “aeser” column

    • No in “aerelnst” column

          For Non- serious- related AE: count of all AE which fulfills all of the following criteria: 

    • AE start date is same or later than the date taken as first date (timeframe or no timeframe)

    • AE start date not null 

    •  All values except “serious” and “yes” will be considered in non serious category. Yes/Definitely related/probably related/possibly related in “aerelnst” column

          For Non- serious- Not-related AE: count of all AE which fulfills all of the following criteria: 

    • AE start date is same or later than the date taken as first date (timeframe or no timeframe)

    • AE start date not null 

    •  All values except “serious” and “yes” will be considered in non serious category. 

    • No in “aerelnst” column

          For AE with incomplete data: count of all AE which fulfills all of the following criteria: 

    • AE start date is same or later than the date taken as first date (timeframe or no timeframe)

    • AE start date not null and AE end date null

    • Blank in “aerelnst” column irrespective of what is there in Seriousness. 

     count of total AEs= count of serious-related AEs + count of serious-not related AEs + count of Non- serious-related AEs + count of Non- serious-related AEs + count of AEs with incomplete data

    Baseline: The average AE count per site= Total AE count for that week for that study across sites/ count of sites for that study.

    Study, Region,  

    Country, and Site

    Adverse event count and percentage distribution (Pie Chart) 

    Adverse event count and percentage of various categories


    For serious- related AE: count of all AE which fulfills all of the following criteria:

    • AE start date is same or later than the date taken as first date (timeframe or no timeframe)

    • AE start date not null

    • Serious/Yes in “aeser” column 

    • Yes/Definitely related/probably related/possibly related in “aerelnst” column

    For serious- not related AE: count of all AE which fulfills all of the following criteria:

    • AE start date is same or later than the date taken as first date (timeframe or no timeframe)

    • AE start date not null

    • Serious/Yes in “aeser” column 

    • No in “aerelnst” column

    For Non- serious- related AE: count of all AE which fulfills all of the following criteria:

    • AE start date is same or later than the date taken as first date (timeframe or no timeframe)

    • AE start date not null

    • All values except “serious” and “yes” will be considered in non serious category. 

    • Yes/Definitely related/probably related/possibly related in “aerelnst” column

    For Non- serious- Not-related AE: count of all AE which fulfills all of the following criteria:

    • AE start date is same or later than the date taken as first date (timeframe or no timeframe)

    • AE start date not null

    • All values except “serious” and “yes” will be considered in non serious category. (updated on 03/09/2021)

    • No in “aerelnst” column

    For AE with incomplete data: count of all AE which fulfills all of the following criteria:

    • AE start date is same or later than the date taken as first date (timeframe or no timeframe)

    • AE start date not null

    • Blank in “aerelnst” column irrespective of what is there in Seriousness.

    count of total AEs= count of serious-related AEs + count of serious-not related AEs + count of Non- serious-related AEs + count of Non- serious-related AEs + count of AEs with incomplete data.

    %Calculations:

    For Serious related= (count of AEs for serious-relatedness/ count of all AEs)*100

    Similarly %share of other combinations can be calculated. The same calculations are applied for site, country, region level queries. Sum of all %values should be equal to 100 (for verification)

     


    Subject Disposition (Handling Multiple Intents without Timeframe)

    Multiple Intents for all  Disposition events except Enrollment & Screening (without timeframe) 

    Count of Disposition events  (dsevent column) with respect to dsstdtc as described in DaLIA  query.

    Study, Region,  

    Country, and Site.

    Subject Disposition (Addition of new disposition events)

    Disposition Events count and listings (in time frame)

    Count of Disposition events  (dsevent column) with respect to dsstdtc as described in DaLIA  query.

    Study, Region,  

    Country, and Site.

    All Intents

    Adding TA, Indication, Program and  Site Name, CRO columns

    -


    Study, Region,  

    Country, and Site.

    Site Name

    Queries with Site Name  

    -

    Site

    Adverse Event Count

    Subject Level Intent

    Count of Subject ID column with respect to AE Term (aeterm)

    Study, Cohort, Region,  Country, Site and  

    Subject

    Adverse Event Count

    AE Count as per Severity at Subject level

    -count of Subject ID (usubjid) column with respect to Severity column

    Study, Cohort, Region,  Country, Site and  

    Subject

    Adverse Event Count

    AE Count as per Seriousness at Subject level

    Count of subject having the queried seriousness column.

    Study, Cohort, Region,  Country, Site and  

    Subject

    Adverse Event Count

    Relatedness to Study Drug

    -count of subjects with respect to the relatedness (aerelnst) column as queried in DaLIA

    Study, Cohort, Region,  Country, Site Subject

    Subject Intent

    Subject wrt Study/Region/Country/Site

    count of subjects column with respect to study/region/country/site as per the question asked in DaLIA

    Study, Region,  

    Country, Site

    Concomitant Medication

    Subject level queries for CM Indication

    count of subject column with respect to Concomitant medication

    Study, Region,  

    Country, Site

    Concomitant Medication

    Standardized Medication Name

    count of Subject ID column with respect to cmdecod column 

    Study, Region,  

    Country, Site

    Concomitant Medication

    CM Route

    count of Subject ID column with respect to cmroute column

    Study, Region,  

    Country, Site

    Concomitant Medication

    Ongoing CM

    count of Subject ID where cm start date  is not null and cm end date is null with respect to the queried intent (if any)

    Study, Region,  

    Country, Site

    Concomitant Medication

    Completed CM

    count of usubjid column wherecm start date is not null and cm end date is not null with respect to the queried intent (if any)

    Study, Region,  

    Country, Site

    Lab Results

    Subject Level Intent for Test name or short name


    count of subject ID column with respect to the test name or short name whichever is asked by the user in DaLIA.

    Study, Region,  

    Country, Site

    Lab Results

    Subject level intent based on the reference ranges

    count of subject ID column with respect to Lab Result Original column

    Study, Region,  

    Country, Site

    Lab Results

    Subject level intent based on Test Category and Sub Category

    Count of subject ID column with respect to the Test Category or Subcategory whichever is asked by the user in DaLIA. Filter to be applied on Test Category or Test Subcategory as queried in DaLIA

    Study, Region,  

    Country, Site

    Lab Results

    Subject level intent based on visit type

    count of Subject ID columns with respect to the Visit column and Test name/short name as asked in DaLIA.

    Study, Region,  

    Country, Site

            

    *DaLIA's responses or answers to queries are determined by the data present in the USDM (Unified Study Data Model) and by the underlying data that is processed to draw out the various OOB KPI analytics. DaLIA is not trained to respond to any query based on custom configurations or to any query based on the OOB KPI Studio Reports; response to such a query will be inaccurate or null.


    • Enhancements in LSAC Platform App

     

    LSPT-927: Configurable LSAC Login Page

    The LSAC Login page is now configurable from source and will render the various events, news and application updates as suited, irrespective of any release cycle or deployment. As a user you will be able to see all application-related & company related updates as and when they are posted by the LSAC team. The content heading would contain links to take the user to the main article.

    1

    LSPT-481: Un-Publish/Delete an App

    A published third-party/stand-alone app that appears in Marketplace can be un-published or can be deleted by the LSAC App Admin user. Un-publishing an app restricts the visibility of the app temporarily until it is published at a later time after the app has been modified by the LSAC Admin user. Deleting the app removes or deletes the app from the LSAC application. Once the app is deleted, the App Admin will not be able to see the app in App Registration Module and the LSAC users can no longer see the app in the Marketplace App showcase.
    A confirmation message will be sent to the LSAC App Admin user before he/she decides to un-publish or delete the app.
    1
    Bug Fixes
    There are no fixed issues for this release.
    Open Issues
    There are no known issues for this release.
    Technical Support
    Customers can submit issues via our support portal (support.saama.com) or calling the support line (866) 619-9995 during normal business hours. For any other query customers can contact us on the email address: support@saama.com