Managing Missing Remote Data in Clinical Trials: A Compliance-First Approach

Introduction: The Challenge of Missing Data in Decentralized Trials

Decentralized and hybrid clinical trial models have introduced new complexities in data capture. With participants reporting data via eConsent platforms, wearable devices, mobile apps, or portals, the risk of missing data has increased. Missing data may arise from technical issues, patient non-compliance, data sync failures, or platform errors. Regardless of the cause, such gaps can pose serious threats to data integrity, endpoint reliability, and regulatory compliance.

This article outlines a compliance checklist approach to proactively manage missing remote data in accordance with FDA, EMA, and ICH GCP expectations. It also highlights CAPA planning, documentation standards, and how to prepare for audit scrutiny on this critical issue.

Types of Missing Data in Remote Capture Systems

Understanding the nature of missing data is the first step in building robust controls. Common scenarios include:

• Intermittent Dropouts: Data is missing for certain days or time points (e.g., patient forgot to log daily diary)
• Persistent Gaps: Entire data blocks missing over long periods, possibly indicating technology or compliance failure
• Platform Failures: Errors during sync or data upload that result in unrecorded entries
• Subject Discontinuation: Final records may be incomplete or unavailable
• ePRO or Device Malfunction: Sensor or application failure prevents data entry

Missing data must be flagged early to prevent protocol deviations or statistical impact on trial endpoints.

Regulatory Expectations on Missing Data Management

Agencies like the FDA and EMA expect sponsors to predefine how missing data will be handled in the protocol, SAP, and SOPs. The ICH E9 addendum specifically emphasizes estimands and sensitivity analyses for missing data scenarios. Key expectations include:

• Documented procedures for detecting and tracking missing data
• Real-time visibility for CRAs and site staff
• Query generation and reconciliation processes
• Clear documentation of cause: technical error vs. patient issue
• Plans for imputing or statistically managing missing data

Failure to adequately address missing data during a regulatory inspection can lead to audit findings, delays, or even trial rejection.

Checklist: Handling Missing Remote Data – From Detection to Resolution

Case Study: FDA Audit on Missing Data in a Remote Oncology Trial

In a 2022 inspection of a remote oncology study using patient-reported outcomes (PROs) via a mobile app, the FDA noted significant issues with missing symptom diary entries. The sponsor had not implemented a protocol to review data completeness regularly.

Observations included:

• Delayed recognition of over 20% missed entries across a two-week period
• Lack of documented site follow-up with subjects
• Failure to classify missing data as deviations

As part of CAPA, the sponsor:

• Implemented a real-time alert system
• Retrospectively reclassified missing entries and updated deviation logs
• Trained site personnel on missing data escalation SOPs

Documentation and Filing Expectations

Thorough documentation is the foundation of regulatory compliance when managing missing remote data. Essential documents include:

• Missing Data Log: Central log of all missing or incomplete data entries with timestamps and reasons
• Deviation Forms: Where applicable, filed deviation reports with CAPA linkage
• Query Reports: Evidence of data reconciliation actions between site and sponsor
• Monitoring Reports: CRA notes identifying patterns or trends in missing data
• Updated eCRFs: With clarifications or imputation notes as per the statistical analysis plan

These should be filed in the TMF and accessible during audits. FDA and EMA auditors often request random subject data files to confirm how missing entries were handled.

CAPA Planning for Missing Remote Data

CAPA processes should not only address root causes but aim to prevent future occurrences. Preventive actions might include:

• Enhanced subject training at enrollment
• Device usability testing and interface simplification
• Redundant data sync methods or backup storage
• Frequent interim data review meetings across functional teams

CAPA timelines and responsibilities should be tracked, with follow-up audits verifying effectiveness.

Integrating Data Integrity with Risk-Based Monitoring (RBM)

Risk-Based Monitoring plans should highlight missing remote data as a critical risk factor. Specific Key Risk Indicators (KRIs) may include:

• % of missed entries per patient per week
• Sites with >10% subject data incompleteness
• Recurrent technical failures per device or application

KRIs should trigger alerts for early intervention and inspection readiness adjustments.

Reference Resource

For global studies involving remote data capture tools, refer to:
EU Clinical Trials Register – ePRO and Remote Data Capture Studies

Conclusion: Making Remote Data Integrity Audit-Proof

As remote technologies become integral to clinical trials, managing missing data is no longer optional—it is a regulatory imperative. By proactively identifying risks, implementing layered detection and resolution workflows, and thoroughly documenting every step, sponsors and CROs can protect both their data and their trial outcomes from audit challenges. A structured, compliance-driven checklist can make the difference between regulatory success and inspection failure.