Every few months someone predicts the end of the SAS transport file. In October 2026 FDA published version 6.3 of its Study Data Technical Conformance Guide, and XPT v5 is still "the file format for the submission of all electronic datasets." If you are planning a submission in the next year or two, that is the format you are building for.
The guide changes in smaller ways almost every release, though, and some of those changes land directly on the programming team. Here is what to check before your next package goes out.
Lab data now needs two ADaM datasets
The guide now asks for two lab analysis datasets in clinical studies: ADLB with results in SI units, and ADLC built the same way with results in conventional units. If your lab ADaM was designed around one unit system, plan the second dataset early. It is not just a copy: units, normal ranges, toxicity grades and any derived flags have to be consistent in both.
The limits that still catch people out
- Dataset and variable names of up to 8 characters, labels of up to 40, character values of up to 200 bytes.
- Datasets larger than 5 GB have to be split, and the split has to be explained in the reviewer's guide.
- Values should use plain ASCII. A single accented character in a free-text field can fail validation late in the process.
- Define-XML 2.0 or later is strongly preferred, and FDA's Data Standards Catalog lists Define-XML 2.1 as required for studies starting after March 2022.
Reviewer's guides carry more weight
The clinical study data reviewer's guide (cSDRG) and the analysis data reviewer's guide (ADRG) are where you explain everything the datasets cannot. The ADRG must state the software used, with its version and operating system, which matters more now that teams mix SAS and R. Treat both guides as living documents during the study, not as a write-up at the end.
Check your versions against the catalog
FDA's Data Standards Catalog (version 11.0) lists SDTMIG 3.4 as required for studies starting from March 2025, and ADaMIG 1.2 or 1.3 as required from March 2024. A study that started before those dates can usually keep the version it began with. Write the version decision into the study's data standards plan so nobody has to reconstruct it at submission time.
What we do before every package goes out
We run the transport limits, conformance checks and define.xml review as a routine step weeks before the deadline, not the night before. If you would like a second pair of eyes on a package, we are happy to help. Our free e-Submission readiness checklist covers the same ground.