In the world of drug development, the journey from a laboratory bench to a patient’s bedside is notoriously long and fragmented. Historically, the early stages of research, known as nonclinical or preclinical testing, and the later stages of human clinical trials operated in completely different universes. Researchers used entirely different terminology, tracking methods, and data structures.
When regulatory bodies like the United States Food and Drug Administration began demanding standardized electronic submissions, this fragmentation became a massive operational bottleneck. To bridge the gap, the Clinical Data Interchange Standards Consortium created two foundational data models: SEND and SDTM.
While one focuses on animal models and the other on human subjects, they are actually two sides of the same coin. Understanding the intricate relationship between SEND and SDTM is essential for any biopharmaceutical company looking to build a unified, compliant, and efficient drug development pipeline.
The Shared DNA of CDISC Standards
To truly understand how SEND and SDTM interact, it helps to look at their origin. SDTM, which stands for Study Data Tabulation Model, was developed first. It was designed to standardize the structure of human clinical trial data, organizing millions of disparate data points into uniform domains such as demographics, vital signs, and adverse events.
As global health authorities realized the immense efficiency of reviewing standardized clinical data, they requested a similar framework for nonclinical toxicology and pharmacology studies. Instead of reinventing the wheel from scratch, the consortium built SEND, which stands for Standard for the Exchange of Nonclinical Data, directly upon the architecture of SDTM.
Because SEND is an extension of the SDTM framework, they share the exact same underlying logic. They use identical variable naming conventions, data structures, and controlled terminologies. If you know how to navigate an SDTM clinical dataset, the structure of a SEND nonclinical dataset will feel instantly familiar.
Mapping the Nonclinical to Clinical Relationship
The structural harmony between SEND and SDTM allows for direct cross-study comparisons that were nearly impossible in the past. This structural relationship manifests across several core areas.
1. Identical Domain Structures
Both standards group data into logical categories called domains. For example, the domain used to capture laboratory test results is called LB in both SEND and SDTM. Vital signs data is stored in the VS domain across both models. This means a toxicologist reviewing animal liver enzyme data in a SEND dataset and a clinical investigator reviewing human liver function in an SDTM dataset are looking at files organized with the exact same variables and columns.
2. Controlled Terminology
A major challenge in data integration is inconsistent naming. One researcher might write “high blood pressure,” another might type “hypertension,” and an early-stage lab report might use a complex physiological description. Both SEND and SDTM enforce a shared dictionary of controlled terminology. This ensures that medical and scientific concepts are described using identical, standardized terms throughout the entire lifecycle of the drug asset.
3. Translational Science Insights
The true value of the SEND and SDTM relationship lies in translational science, which is the ability to predict human outcomes based on nonclinical observations. Because the datasets are structured identically, data scientists can use automated tools to map toxicology findings from animal studies directly against adverse events observed during Phase I and Phase II clinical trials. If a specific safety signal emerges in humans, researchers can easily query the legacy SEND datasets to see if early indicators were present during animal testing.
Why the Relationship Matters for Regulatory Success
For regulatory affairs teams, looking at SEND and SDTM as a continuous data spectrum rather than two isolated requirements is a strategic advantage.
The FDA requires electronic data submissions to be completely standardized. When a company submits an Investigational New Drug application or a Biologics License Application, reviewers do not want to waste weeks deciphering custom spreadsheets. A seamless transition from SEND compliant nonclinical packages to SDTM compliant clinical packages ensures that regulators can navigate, review, and validate your safety and efficacy data without administrative delays.
Moreover, managing data under a unified CDISC framework prevents data loss and minimizes errors when transferring a candidate molecule from preclinical teams to clinical operations.
Bridging the Data Gap
Navigating the nuances of nonclinical and clinical data mapping requires a deep understanding of both biological science and complex data architecture. Minor misalignments in domain mapping or controlled terminology can lead to submission warnings or costly validation failures.
If your team is preparing a regulatory package, you do not have to navigate these intricate standards alone. Ensure total alignment across your development lifecycle and streamline your regulatory path by partnering with the expert CDISC Standard for Exchange of Nonclinical Data (SEND) services by MakroCare. Our dedicated compliance specialists will help you transform raw laboratory data into pristine, submission ready datasets that meet the highest global standards.
