Special Characters in FDA Study Data Variables and Datasets
FDA’s June 2026 conformance guide addresses character encoding for study-data variable names, dataset names, labels, and values and warns that unsupported or inconsistent characters can create review or processing problems. These requirements are current FDA technical-conformance guidance for electronic study-data submissions and should be rechecked when FDA guidance, supported standards, or eCTD specifications change.
ReviewedEvidence1 sourceSectionWriting & Style
Quick answer
Use the character encoding and supported-character conventions required by the current FDA study-data guidance and applicable standard.
Key details
Core IssueFDA’s June 2026 conformance guide addresses character encoding for study-data variable names, dataset names, labels, and values and warns that unsupported or inconsistent characters can create review or processing problems.
Registerscholarly, professional, or research/report writing
Important caveats
Scope Boundary
These requirements are current FDA technical-conformance guidance for electronic study-data submissions and should be rechecked when FDA guidance, supported standards, or eCTD specifications change.
Further guidance
Content
Check names, labels, and values separately because the permitted character behavior and downstream processing risks are not identical across all fields.
Purpose
Use the character encoding and supported-character conventions required by the current FDA study-data guidance and applicable standard.
Sources and evidence
Sources are shown with the role they play in this guide. Historical or style-sensitive claims are kept within the evidence boundary described above.
FDA’s June 2026 conformance guide sets maximum descriptor lengths of 8 characters for variable names and 40 characters for variable descriptive labels and dataset labels in the specified study-data exchange context. These numeric limits are current FDA technical-conformance specifications and should be rechecked when the guide or supported exchange format changes.
FDA’s June 2026 Study Data Technical Conformance Guide gives specific conventions for variable descriptive labels and dataset labels, including avoiding certain unbalanced punctuation that can interfere with processing. These requirements are current FDA technical-conformance guidance for electronic study-data submissions and should be rechecked when FDA guidance, supported standards, or eCTD specifications change.
FDA’s June 2026 conformance guide requires variable and dataset names to follow the applicable standards-development-organization technical specifications and gives SAS naming-option guidance for submitted datasets. These requirements are current FDA technical-conformance guidance for electronic study-data submissions and should be rechecked when FDA guidance, supported standards, or eCTD specifications change.
FDA’s June 2026 conformance guide specifies .xml for XML files used in the covered study-data submission context and states that define.xml should not be compressed.
FDA’s June 2026 conformance guide notes that there is no single standard or best practice for all adjudication data and directs sponsors to document where adjudication data reside and how adjudicated values can be distinguished from original values.
FDA’s June 2026 guide says the AE domain should include all adverse events unless an indication-specific technical specification says otherwise and asks for the criterion supporting a serious-event flag.
