FDA Updates on Standardized Study Data Submissions and E2B(R3) Electronic Safety Reporting
The US Food and Drug Administration (FDA) has published updated technical guidance documents addressing standardized electronic study data submissions and the electronic transmission of Individual Case Safety Reports (ICSRs). The Study Data Technical Conformance Guide – Technical Specifications Document and the E2B(R3) Electronic Transmission of Individual Case Safety Reports Implementation Guide provide technical recommendations to support consistent data structures, electronic submission quality and reliable exchange of safety information.
Together, these documents address two important areas of regulatory operations: the submission of clinical and nonclinical study data for product review and the electronic reporting of individual safety cases. The updated documents are dated October 2026 and are relevant to regulatory affairs, clinical data management, pharmacovigilance, regulatory operations and submission technology teams.
The Study Data Technical Conformance Guide provides specifications and recommendations for submitting standardized human and animal study data to FDA’s Center for Drug Evaluation and Research (CDER) and Center for Biologics Evaluation and Research (CBER). It supplements FDA’s guidance on electronic submissions of standardized study data and supports submissions including investigational new drug applications (INDs), new drug applications (NDAs), abbreviated new drug applications (ANDAs) and certain biologics license applications (BLAs).
Planning and Standardized Data Preparation
Sponsors are advised to prepare a Study Data Standardization Plan (SDSP) during product development and update it as the development programme expands. Early discussions with the relevant FDA review division can help identify data requirements, dataset structures and potential standardization issues. Study Data Reviewer’s Guides and Analysis Data Reviewer’s Guides should also support the explanation and interpretation of submitted datasets.
Clinical and Nonclinical Data Standards
The guide covers FDA-supported standards, including the Study Data Tabulation Model (SDTM) for clinical tabulation data, the Analysis Data Model (ADaM) for clinical analysis datasets and the Standard for Exchange of Nonclinical Data (SEND) for nonclinical toxicology data. Sponsors should use the versions listed in the FDA Data Standards Catalog.
Complete metadata, appropriate dataset documentation and traceability are important for helping reviewers understand the submitted data and how study results were derived. Where a standard does not clearly address a particular implementation issue, sponsors should discuss their approach with the review division and provide supporting documentation.
Electronic Formats, Terminology and Validation
The guide addresses electronic exchange formats, dataset naming and structure, controlled terminology, eCTD submission organization, validation and data traceability. It also describes technical rejection criteria for applicable study-data submissions, including checks associated with XPT-formatted datasets and trial summary information.
Sponsors should validate datasets before submission and ensure that data conform to the applicable FDA-supported standards. Legacy data conversions should preserve traceability to the original study information, and any remaining nonconformance should be appropriately explained.
The guide also includes recommendations for reviewing SEND data before submission. This helps sponsors assess whether nonclinical datasets accurately represent the study design, remain traceable to source data and study reports, and support analyses consistent with reported results.
The E2B(R3) Implementation Guide describes the data elements and message specifications used for electronic transmission of ICSRs. It was developed through the International Council for Harmonisation (ICH) process and provides a standardized structure for exchanging individual safety case information between organizations and regulatory authorities.
The October 2026 FDA document is identified as Revision 2 and incorporates technical updates made to the ICH ICSR Implementation Guide in 2025. The guide supports consistent electronic reporting for drug and biological products.
Standardized ICSR Data Elements
The implementation guide defines the information included in an electronic safety case. This covers case identification, reporting sources, sender details, study information, patient characteristics, reactions or events, relevant medical history, drug information, investigation results and the case narrative.
Structured data elements and defined terminologies help ensure that safety information is represented consistently. The guide also addresses report amendments and nullifications, linked reports, additional documents and information needed to identify and evaluate individual safety cases.
Message Structure and Electronic Transmission
E2B(R3) specifies the structure of ICSR messages and the associated transmission information. It includes message and batch identifiers, sender and receiver details, transmission dates and acknowledgement messages. These components support the identification, processing and tracking of electronic safety reports.
The guide also describes acknowledgements, including transmission status, validation errors and message-level warnings or comments. Organizations should ensure that their systems can create, transmit, receive and process messages in accordance with the applicable specifications.
Compatibility and Technical Implementation
The guide includes appendices covering ICSR schemas, schema files, reference message examples, code lists, technical information and backwards and forwards compatibility. These resources support implementation and help organizations assess how electronic messages are handled across compatible system versions.
The document also covers date and time representation, time zones and ISO 8601-compliant XML examples. Consistent formatting and appropriate use of the defined data elements are important for successful electronic exchange and accurate interpretation of safety information.
FDA notes that a separate regional technical specifications document is associated with the implementation guide. Organizations should therefore check the relevant FDA guidance webpage to confirm that they are using the latest applicable technical specifications.
What These Updates Mean for Regulatory and Pharmacovigilance Teams
The two documents address different submission needs but share a common objective: improving the consistency, quality and usability of regulatory data.
For clinical and nonclinical submissions, sponsors should focus on supported standards, complete metadata, validation, reviewer documentation and data traceability. For pharmacovigilance submissions, organizations should focus on accurate ICSR data, correct message structures, compatible schemas, acknowledgement handling and reliable electronic transmission.
Regulatory affairs and regulatory operations teams should coordinate with clinical data management, submission publishing, safety systems and IT teams to assess the impact of these documents on existing processes. Teams should review applicable standards and technical specifications, update procedures where necessary, and incorporate appropriate validation checks into submission workflows.
References
Comments