SAS transport files have served clinical submissions for decades, but their limits are well known: 8-character names, 200-byte text values and no room for metadata. Dataset-JSON is CDISC's answer, and in 2025 it moved from an idea to something regulators are actively testing.
Where things stand
- CDISC published Dataset-JSON v1.1 on 5 December 2024, together with a compressed format and an API specification.
- In April 2025 FDA published a Federal Register notice asking for comments on Dataset-JSON v1.1 as a possible future replacement for XPT v5. The notice set no date and said current requirements do not change.
- FDA describes its testing so far as indicating potential use as a replacement, with more testing planned.
- The R Consortium's fifth submissions pilot sent FDA a package with Dataset-JSON in place of every XPT file.
- FDA's October 2026 Technical Conformance Guide and its Data Standards Catalog still name XPT v5 as the exchange format.
So the short answer is: not yet. Every submission today still goes in as XPT.
What actually changes for programmers
Very little in the datasets themselves. SDTM and ADaM do not change; what changes is the container. The real gains are longer names and values, proper metadata in the file, and data that modern tools can read without a SAS licence. The risks are the usual ones with a new format: tool support and validation engines catching up.
How to prepare without wasting effort
- Keep your metadata (names, labels, lengths, origins) in one specification that drives both the datasets and define.xml. Whatever the container, that is what reviewers rely on.
- Avoid designs that only work because of XPT limits, such as values deliberately split across variables, unless the standard requires it.
- Try a round trip on a finished study: export to Dataset-JSON, read it back, compare. It shows quickly where your tools are ready and where they are not.
- Do not change a live submission plan for it. Until FDA says otherwise, XPT v5 is the requirement.
Our view
Dataset-JSON is coming, but on a regulator's timetable, not a vendor's. Teams that keep clean, specification-driven metadata will switch with little more than a new export step. We are watching it closely and will update this article when FDA sets a date.