Longitudinal Patient Data Platform for Secure Clinical Trial Matching

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing systems for patient engagement and clinical trial participation are inefficient, requiring excessive processing cycles, memory utilization, and network communication resources, with limited patient control over medical information and insecure data handling.

Innovation Solution

A patient engagement platform utilizing a patient database for longitudinal data storage, modular components, and customizable dashboards to enhance patient control, reduce navigation operations, and improve data security, enabling efficient clinical study matching and patient outreach.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If a traditional patient engagement system is used, then patients can access medical information, but the system requires excessive navigation and processing resources

Engineering Contradiction:
Improvenavigation efficiencyVSAvoidprocessing cycles
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The system pre-generates and stores longitudinal patient data summaries and clinical trial matching results before they are requested. When a patient logs in, their profile page instantly displays pre-computed information about their medical history, treatment outcomes, and compatible clinical trials without requiring real-time processing or multiple navigation steps through complex menus.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patient engagement platform is divided into modular components: a longitudinal data management module, a clinical trial matching module, and a patient interface module. Each module handles specific tasks independently, allowing the system to retrieve and display only the relevant segment of data needed for each patient interaction, reducing overall processing complexity.

Inventive Principle:
Principle #1Segmentation

2Reliability

If comprehensive patient data is stored and processed, then better clinical trial matching can be achieved, but data security risks increase

Engineering Contradiction:
Improveclinical trial matching accuracyVSAvoiddata security
Core Design Contradiction:
ReliabilityVSObject-affected harmful factors

Solution Approach 1:

The system introduces a security intermediary layer that sits between the comprehensive longitudinal patient data storage and the clinical trial matching algorithms. This intermediary layer uses encryption and access control mechanisms to protect sensitive patient information while still allowing the matching algorithms to process and analyze the data for improved clinical trial compatibility assessments.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Adaptability or versatility

If patients have full control over their health information, then patient engagement improves, but system operations become more complex

Engineering Contradiction:
Improvepatient controlVSAvoidsystem operations
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patient interface includes self-service controls that allow patients to independently manage their own health information preferences, data sharing permissions, and clinical trial enrollment choices. The system provides pre-configured templates and automated workflows that guide patients through these decisions without requiring complex system administration or manual configuration by healthcare providers.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS12614614B2Systems, methods, and apparatus to provide longitudinal patient data
Publication Date: 2026.04.28 PROSCIENTO INC
  • US12614614B2 patent drawing
  • US12614614B2 patent drawing
  • US12614614B2 patent drawing

AI summary

A patient portal system may include a patient database module to interpret a patient profile value and a clinical database module to interpret a clinical study description. The patient database module may also interpret patient clinical data in response to the patient profile value and the clinical study description, and include at least a portion of the patient clinical data as longitudinal data of a patient corresponding to the patient profile value. The system may also include a patient interface module to implement a patient engagement interface and to interpret a patient medical event value in response to patient interactions with the patient engagement interface. The patient database may also adjust the longitudinal data in response to the patient medical event value.