Clinical Trial Data Management Snapshot Reporting

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current data management systems for clinical trials face challenges in handling data from diverse geographical locations and varying formats, which can compromise data integrity and efficiency, especially when dealing with large volumes of clinical response and workflow data.

Innovation Solution

A clinical trial data management system that synchronizes clinical data management application servers and workflow servers to generate simultaneous displays and perform data entry, cleaning, and reporting, using a snapshot process to copy and merge data from databases into temporary files for report generation, while integrating with online data input systems and thesaurus applications for term matching and quality control.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If data is accessed directly from live databases for report generation, then report generation is fast and direct, but data integrity is compromised due to frequent database accesses

Engineering Contradiction:
Improvereport generation speedVSAvoiddata integrity
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent creates snapshot copies of clinical response data and workflow data from the live databases into temporary files. These snapshots are then used for report generation, eliminating the need to access live databases during reporting. This copying mechanism preserves data integrity while enabling efficient report generation from the static snapshot data.

Inventive Principle:
Principle #26Copying

2Adaptability or versatility

If the system handles data from diverse geographical locations and varying formats, then data versatility is improved, but data integrity and management complexity worsen

Engineering Contradiction:
Improvedata format compatibilityVSAvoiddata integrity
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent introduces a thesaurus application as an intermediary layer between the diverse input data formats and the internal data processing system. The thesaurus standardizes clinical terms and codes from various sources, enabling the system to handle diverse geographical locations and formats while maintaining data integrity through consistent term mapping and validation.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The snapshot mechanism serves multiple functions: it preserves data integrity by eliminating live database access, enables efficient report generation, and provides a unified interface for handling diverse data formats. The temporary snapshot files act as a universal intermediary that can process various data types without compromising the source databases.

Inventive Principle:
Principle #6Universality (Multi-functionality)

3Manufacturing precision

If the system performs iterative data entry and cleaning operations, then data quality is improved, but processing time increases

Engineering Contradiction:
Improvedata qualityVSAvoidprocessing time
Core Design Contradiction:
Manufacturing precisionVSLoss of time

Solution Approach 1:

The patent performs data cleaning and validation operations on the snapshot copies rather than on live database data. This preliminary action on copied data allows iterative cleaning processes to occur without impacting the timing of critical database operations, thereby improving data quality while minimizing time loss in the overall system workflow.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentEP1903752B8A data management system and method
Publication Date: 2009.03.25 SHELBOURNE DATA MANAGEMENT

AI summary

A clinical trial data management system (1) receives clinical trial data in Case Record Forms (CRFs), which are scanned by a document management system (3) to provide an indexed image file. Client workstations and the document management system (3) communicate via a local area network (LAN) 4 with clinical data management application servers (5) in turn linked with database servers (7) which manage a clinical data database (8) in a storage area network (SAN). There is a separate path for work flow data, namely from the document management system and workstations (3) via LANs (4, 6, 9) to a cluster of work flow engine application and database servers 10. The work flow servers (10) perform work flow processing and manage work flow databases (11) in a second SAN. The work servers (10) execute a snapshot process comprising copying a portion of each of the clinical response data and of the work flow data from their respective databases (8, 11) to a temporary file in which said data is merged, and automatically generate reports exclusively from the temporary file without accesses to the clinical data or work flow databases (8, 11). The data is copied according to dynamically-set criteria, including metric requirements, and the data is copied from the full databases (8, 11) irrespective of data age. The snapshot process is executed only be applications on the work flow servers (10).