Real-World Insights into Managing Queries During Reconciliation Cycles

Introduction: The Central Role of Queries in Reconciliation

Laboratory and EDC reconciliation is a vital quality assurance function in clinical trials. One of the key outputs of reconciliation cycles is the generation of queries—requests for clarification or correction of discrepancies between laboratory data and the data captured in the Electronic Data Capture (EDC) system. These queries can stem from inconsistencies in subject ID, visit date, test values, units, or missing results.

Effective query management ensures data consistency and integrity, supports GCP compliance, and enables timely database lock. Regulatory authorities such as the FDA and EMA pay close attention to the timeliness, traceability, and resolution of these queries during sponsor inspections.

Types of Queries Generated During Reconciliation

The classification of queries is important for tracking resolution timelines and assigning ownership. Typically, queries during reconciliation cycles fall into the following categories:

• Missing Data: Lab results not available in EDC or missing visit records
• Value Mismatches: Differing lab values between vendor reports and EDC entries
• Incorrect Units: Lab results entered with wrong units requiring clarification
• Visit Window Deviations: Sample collected outside allowed protocol window
• Duplicate Entries: Same subject data appearing multiple times
• Specimen Status: Results reported for unscheduled or uncollected samples

Each type must be mapped to standard discrepancy codes for automated reconciliation tools and downstream metrics reporting.

Case Study 1: Oncology Trial – Value Discrepancy Across Systems

In a multicenter Phase II oncology trial, a periodic reconciliation cycle revealed consistent mismatches in neutrophil count between the central lab database and the EDC for Visit 5 in 18 subjects across 4 sites. Root cause analysis showed:

• The EDC system was configured to auto-convert neutrophil count from % to absolute value using a deprecated formula.
• Site users were unaware of this configuration and overrode system suggestions based on printed lab reports.

The queries generated were initially categorized as “value mismatch,” but were escalated to protocol deviation due to systematic occurrence. CAPA included EDC reconfiguration, site retraining, and query category enhancement for future cycles.

Query Lifecycle in Reconciliation

A well-managed query lifecycle enhances compliance and reduces cycle times. A typical flow includes:

1. Generation: Triggered manually or through automated reconciliation scripts
2. Logging: Assigned a unique ID, category, and priority
3. Assignment: Routed to the responsible function—lab vendor, CRA, data manager
4. Response: Clarification or data correction provided with timestamp and rationale
5. Closure: Verified by the initiator and archived in audit trail
6. Trend Analysis: Monthly or quarterly query trends reviewed by quality teams

Case Study 2: Endocrine Trial – Missing Results from Courier Delays

A global endocrine study observed recurring queries for missing TSH values for Week 12. Investigation showed samples were delayed in transit due to courier disruptions in South Asia, leading to sample degradation and invalid results.

These queries were initially assigned to the central lab vendor, but upon investigation, a cross-functional RCA attributed the issue to vendor SOP non-compliance. A corrective action plan involved:

• Switching to temperature-stable collection tubes
• Courier qualification updates
• Pre-alert mechanisms for holiday/weekend shipping plans

The reconciliation process was enhanced with flags for “expected but not received” results to proactively detect transit issues in future cycles.

Timelines and Escalation Protocols for Queries

Regulatory guidance does not define specific timelines for query resolution, but sponsors are expected to implement risk-based targets. Best practices include:

Quality Oversight and Metrics Tracking

Oversight dashboards should include real-time visibility into query backlogs, overdue resolutions, category-wise breakdown, and site/vendor-wise performance. Key metrics to monitor include:

• Total queries generated per cycle
• % queries resolved within SLA
• % escalated queries
• Repeat queries for same subject
• Top 3 frequent query categories

Sponsors can benchmark these KPIs against historical trials or internal SOP targets.

For more on reconciliation expectations, refer to the NIHR Clinical Trials Oversight Guidelines.

Conclusion

Query management during reconciliation is a multi-stakeholder responsibility requiring tight coordination between vendors, sites, data managers, and sponsors. Proactive classification, clear resolution timelines, automated audit trails, and oversight dashboards are essential to maintain data integrity and inspection readiness. Real-world case studies demonstrate that timely RCA and CAPA application improve query efficiency and minimize repeat errors. Investing in intelligent reconciliation tools and SOP-driven workflows ensures better outcomes for future clinical trials.