SEND Data Validation and Reconciliation for Clinical Pathology

– A Pharma Case Study

Summary

send data validation and reconciliation for clinical pathology

A $130 billion pharmaceutical company, responsible for the safety evaluation of a new drug, faced inefficiencies in validating clinical pathology data.
For in vivo studies, clinical pathology data (e.g., hematology, clinical chemistry, urinalysis) must be mapped to SEND domains such as LB (Laboratory Test Results), CL (Clinical Observations), MI (Microscopic Findings) and submitted to FDA.
The data, originating from the in vivo studies, was dispersed across multiple Electronic Health Record (EHR) systems, requiring consolidation and submission to the FDA to secure approval for subsequent phases.

Why It Matters: Any errors in the underlying data or mistakes during submission could significantly delay FDA approval. To mitigate this risk, rigorous validation of the data prior to submission is critical.

The Issue: However, the team encountered substantial challenges in delivery of timely and accurate data.

1. Inefficient manual processes hindered timely analysis and strained resources:

  • Scientists spent 3–5 hours per study reconciling data manually, amounting to 1,200 hours annually.
  • This repetitive effort delayed critical project milestones and diverted attention from higher-value analysis.

2. Potential validation gaps threatened FDA approval timelines:

  • Labor-intensive workflows increased the risk of errors in SEND submissions.
  • These vulnerabilities posed a risk of costly delays, with potential multi-billion-dollar business implications.

To address the need for automation while ensuring compliance and consistency with FDA standards, the company implemented iceDQ, a data reliability platform that automated data reconciliation, validation, and exception handling across the entire pipeline.

Results with iceDQ:

  • Validation timelines were reduced by over 95%
  • Resource requirements for validation dropped by 60%
  • Maintained FDA submission requirements by 100%

 

This case study highlights how a major pharmaceutical company successfully transitioned from manual validation and reconciliation to an automated, reliable data pipeline using iceDQ.

The SEND Data Collection and Submission System

The pharmaceutical company’s clinical data pipeline was structured to ensure that clinical pathology data spanning various Electronic Health Record (EHR) platforms, Oracle systems (Staging & Cerner), and SAVANTE, were consistently collected, processed, validated, and prepared for regulatory submission to the FDA.

iceDQ's Implementation

Fig 1: The SEND Data System

1. Data captured from EHR systems Clinical pathology data from in vivo studies was captured across multiple Electronic Health Record (EHR) systems and sent to the Oracle Staging Database, which served as the central collection point.
2. Data transmission to Cerner Study-specific details (including drug details, sample types, and test parameters) were created from the staging database and then the data was sent to Cerner (Oracle Health) via HL7 messages. The samples were then processed through lab instruments, and results were reviewed against historical averages for quality checks.
3. Return of validated data to Oracle Once the lab results passed quality checks, validated data was sent back to the Oracle Staging Database.
4. SEND package generation in SAVANTE The validated data was picked up by SAVANTE, which generated SEND (Standard for Exchange of Nonclinical Data) packages in the required CDISC format.
5. Validation using Pinnacle 21 The SEND packages were validated using Pinnacle 21 to ensure compliance with CDISC standards and to identify any structural or data quality issues.
6. Regulatory submission and internal review Finalized SEND packages were submitted to the FDA for approval and shared internally for comparison with original records in Oracle, ensuring consistency and traceability.

Challenges in Validating & Reconciling SEND Data

The manual data validation and reconciliation of data between systems created bottlenecks affecting study timelines and regulatory compliance:

  • Manual Data Validation Was Time-Consuming: Scientists spent thousands of hours annually verifying HL7 message accuracy between Oracle and Cerner, often relying on random sampling due to data volume, diverting time from critical analysis.

“One of the challenges we had as a business was making sure that all data processing & reconciliation worked properly and business rules were validated and checked before submitting to the FDA. Often, we’d have to do random sampling because of the sheer volume of that data” – Director of Data Platforms

  • No Real-Time Reconciliation with SAVANTE: Lack of automated validation between Oracle and SAVANTE created regulatory risks and potential FDA approval delays.
  • Manual Business Rule Check Before FDA Submission: Scientists manually applied business rules before submission. While Pinnacle 21 ensured CDISC compliance, it couldn’t catch missing or mismatched records, leading to critical gaps and potential delays in drug approvals.

These validation and reconciliation pain points collectively introduced delays in FDA submission timelines, risking incomplete or rejected data packages, and ultimately causing drug approvals to be delayed by months, resulting in a commercial impact totaling billions of dollars.

Scientists spent 3–5 hours per study reconciling data manually, amounting to 1,200 hours annually.

Enter iceDQ: Automated Data Validation Testing

To eliminate these inefficiencies and reduce regulatory risk, the pharmaceutical company implemented iceDQ, an automated data reliability platform built to streamline validation, enforce business rules, and reconcile critical study data across systems.

iceDQ’s implementation within the clinical data pipeline

Fig 2: iceDQ’s implementation within the clinical data pipeline

Automated Reconciliation Across Platforms
A. Oracle Staging Database ↔ Oracle Cerner: iceDQ reconciled the data between the Oracle Staging Database and Cerner, confirming whether all HL7-generated messages had been generated successfully or not. Reconciliation between Oracle Staging Database and Cerner using iceDQ

Fig 3: Reconciliation between Oracle Staging Database and Cerner using iceDQ

B. Oracle Staging Database ↔ SAVANTE: Before FDA submission, iceDQ reconciled SEND package content against source datasets in the Oracle Staging Database, flagging any missing or mismatched values. Reconciliation between Oracle Staging Database and SAVANTE using iceDQ

Fig 4: Reconciliation between Oracle Staging Database and SAVANTE using iceDQ

Business Validation across SAVANTE
C. Verifying Savante Values: iceDQ automated FDA-readiness checks by verifying valid units for numeric values, ensuring required fields were complete, and enforcing logical, referential, and format validations aligned with SEND guidelines. Business Validation at SAVANTE using iceDQ

Fig 5: Business Validation at SAVANTE using iceDQ

How iceDQ Supports SEND-Readiness

Here’s how iceDQ can be strategically applied across the SEND lifecycle:

1. Automated Data Validation

  • iceDQ enables rule-based validation of raw and transformed data against SEND Implementation Guide (SENDIG) standards.
  • You can define custom rules to check for:
    • Domain-specific constraints (e.g., LBTESTCD values in LB domain)
    • Cross-domain consistency (e.g., matching subject IDs across TS and DM)
    • Controlled terminology compliance

2. Data Reconciliation Across Systems

  • Clinical pathology data often originates from multiple EHRs, LIMS, and lab systems.
  • iceDQ automates reconciliation logic to ensure consistency across these sources before mapping to SEND domains.

3. Exception Handling and Audit Trails

  • iceDQ flags anomalies and exceptions in real time, allowing teams to troubleshoot and resolve issues before submission.
  • Every validation run is logged, creating a traceable audit trail–a key requirement for regulatory inspections.

4. Integration with SEND Tools

  • iceDQ can be integrated upstream of SEND dataset generation tools (e.g., Pinnacle 21, SENDIG mappers).
  • This ensures that only clean, validated data enters the SEND packaging process, reducing rework and submission delays.

5. Continuous Monitoring

Business Impact & Conclusion

The implementation of iceDQ transformed the pharmaceutical company’s clinical pathology data validation workflows and delivered measurable operational and regulatory benefits:

Value Proposition using iceDQ

Fig 6: Value Proposition using iceDQ

Reduces manual QC effort | Accelerates validation timelines | Minimizes risk of FDA technical rejection due to SEND non-compliance| Accelerated data validation | Enhanced data quality | Minimized manual QA effort | Reliable FDA submissions

  • 95% Reduction in Validation & Reconciliation Time: Manual validation and reconciliation dropped from ~1,200 to 60 hours annually, a 95% reduction.
  • 60% Reduction in FTE reliance: iceDQ cut FTE QA needs by 60% across ~250 studies per year.
  • 100% Compliance with FDA Submission Requirements: iceDQ improved FDA SEND submission readiness by automating validations, standardizing checks, reducing errors, and enabling non-technical teams to manage data quality independently.

By implementing iceDQ, the pharmaceutical company eliminated bottlenecks associated with manual clinical pathology data validation across disparate systems. Automated reconciliation, FDA-compliant rule enforcement, and real-time dashboards enabled a seamless validation process.

This transformation in the data workflow ensured compliance and safeguarded drug development timelines, ultimately protecting billions in potential revenue from costly regulatory delays.

About the author

Sandesh Gawande

Sandesh Gawande is the Founder and CEO of iceDQ, a unified Data Reliability Platform for automated data testing, monitoring, and observability. With over 25 years of experience in data engineering and architecture, Sandesh has led large-scale data initiatives for Fortune 500 companies across banking, insurance, and healthcare, including Deutsche Bank, JPMorgan Chase, and MetLife.

Know More

Sandesh Gawande - CTO iceDQ

Sandesh Gawande

CEO and Founder at iceDQ.
First to introduce automated data testing. Advocate for data reliability engineering.

Share this article