top of page
Search

How should a US regulated company localize XML files such as SPL labeling and Define-XML while keeping them valid, controlled and audit-ready?

11 hours ago
6 min read

Regulatory team reviewing localized XML files



Table of Contents

 

 

What is the direct answer?

 

A US regulated company should extract only the translatable text from the XML, translate it with the markup protected, merge it back, and validate the result against the schema and the FDA rules before submission. Each step needs a named owner, access control, an audit trail and QA. Submitted content must meet FDA language and format rules. AD VERBUM provides AI+HUMAN hybrid translation for this work.

 

What does XML localization in regulated industries mean?

 

Localization makes content linguistically and culturally appropriate for a target locale. The OASIS XLIFF Technical Committee FAQ quotes this definition and describes translation as rendering text into another language. Localization is a kind of translation that also accounts for the culture of the target location.

 

XML localization applies this to structured files. The text sits inside tags, attributes and placeholders. Only the text may change. The structure must stay intact.

 

The scope for a US regulated company usually includes:

 

  • Structured Product Labeling (SPL) files for drug and biologic labeling.

  • Define-XML files describing study dataset metadata.

  • Technical documentation and software strings stored as XML.

 

This differs from translating a regulatory document in a word processor. A document translation is judged on language accuracy. An XML translation is judged on language accuracy and on whether the file still validates.

 

Which US rules shape XML localization?

 

The rules depend on the file type and the submission.

 

Language. Under 21 CFR Part 207 Subpart E, establishment registration and listing information must be sent in electronic format, comply with 21 CFR part 11 with specified exemptions, and be in English. Where foreign-language-only labeling is permitted under 201.15©, the labeling content is submitted in that language with an accurate English translation.

 

Format. FDA guidance on providing regulatory submissions in electronic format states that the agency adopts the XML-based SPL standard for content of labeling, including all text, tables and figures, in NDAs, ANDAs and BLAs. This covers original submissions, supplements and annual reports.

 

Study data. Define-XML describes tabular dataset metadata for SDTM, SEND and ADaM datasets. FDA and PMDA require it for every study in an electronic submission.

 

File handling. The Study Data Technical Conformance Guide (October 2026 edition) states that XML files use the .xml extension and that define.xml is not compressed.

 

Regulatory Affairs owns the interpretation of these rules. Localization executes within them.

 

What are the steps, owners and controls?

 

1. Classify the file and the target use

 

Owner: Regulatory Affairs. Determine whether the file is SPL, Define-XML or other XML, and whether English is the submission language. Control: a written scope record listing file type, languages and the governing rule.

 

2. Extract the translatable content

 

Owner: Localization. The XLIFF FAQ explains that localization data is extracted from the original format and merged back later, while non-localizable parts are kept in a skeleton. Control: a defined filter that lists which elements and attributes are translatable. Elements such as identifiers, codes and namespaces are excluded.

 

3. Protect tags and placeholders

 

Owner: Localization engineering. The XLIFF 1.0 specification describes generic placeholders that replace inline code. The XLIFF 2.0 specification describes protected formatting codes and variable placeholders such as {0} in a Java string. Control: automated checks that every placeholder in the source appears in the target, in a valid position.

 

4. Translate with terminology governance

 

Owner: Translation Manager. Load approved Translation Memories and Term Bases. Subject-matter experts review medical, legal or technical wording. Control: a locked term base, QA against ISO 17100 and, where machine output is post-edited, ISO 18587.

 

5. Merge back and rebuild the file

 

Owner: Localization engineering. Control: the rebuilt file keeps the original structure. Under the XLIFF 2.1 draft, a processing agent must preserve XLIFF-defined elements and attributes it cannot handle.

 

6. Validate

 

Owner: Regulatory Operations. See the validation section below. Control: a recorded validation report attached to the batch.

 

7. Approve and archive

 

Owner: Regulatory Affairs. Control: a signed approval, version history and an audit trail showing who changed which segment and when. Access control limits who can open the files.

 

How is XML validated before submission?

 

The FDA SPL Validation Rules (December 2023) describe SPL as an HL7 standard based on the Clinical Document Architecture. They require files to be well formed and valid against the schema, with no additional data elements or attributes beyond those described. They also require an XML 1.0 declaration with UTF-8 encoding, a reference to the FDA spl.xsl stylesheet and a schemaLocation for the urn:hl7-org:v3 namespace pointing to spl.xsd.

 

For Define-XML, the CDISC USDM Handbook 3 describes a sequence from syntactic to semantic checks:

 

  1. Schema compliance.

  2. Conformance against the published Define-XML conformance rules.

  3. Consistency with the SDTMIG and the actual datasets.

  4. Controlled terminology validation of codelists against the correct package and NCI codes.

 

It also describes a presubmission gate before the file enters a submission package. A CDISC paper on upversioning states that FDA requires Define-XML 2.1 for studies starting on or after March 15, 2023. It recommends validating define.xml alone and with the data.

 

What are the decision criteria for a vendor?

 

Criterion

What to require

File handling

Documented extraction filters, placeholder protection, post-merge validation

Subject expertise

Linguists with medical, legal or engineering backgrounds

Quality standards

ISO 17100, ISO 18587, and ISO 13485 for medical devices

Security

ISO 27001, defined hosting location, access control

Data protection

GDPR and HIPAA alignment where data categories apply

Terminology

Use of your Translation Memories and Term Bases

Traceability

Audit trail per file and per segment

Independent audit

Certificates verified by an external body

A vendor that cannot show the validation report format for your file type is not ready for regulated XML.

 

What are some examples?

 

Drug labeling. A sponsor holds an SPL file for a product with foreign-language-only labeling permitted under 201.15©. The submission needs the original-language content and an accurate English translation. The team translates only the text nodes, keeps coded elements unchanged, validates both files and files the pair.

 

Device software strings. A medical device maker stores interface text in XML with placeholders such as {0}. The team protects each placeholder, translates the surrounding sentence for word order, and runs a placeholder-parity check.


What are some examples?

Study metadata. A sponsor needs descriptive labels in define.xml reviewed for terminology. Only label text is edited. Codelists and identifiers stay fixed, and the file goes through the conformance rule check.

 

What are the failure modes and mitigations?

 

Failure mode

Mitigation

Translated tag names or attribute values break the schema

Extraction filter that excludes markup and coded values

Placeholders moved or deleted

Placeholder parity check and protected-tag handling

Encoding corruption of special characters

UTF-8 declaration check as required by SPL rules

Extra elements added by tools

Schema validation against the FDA rules, which bar additional elements

Inconsistent terminology across files

Locked term base and Translation Memory reuse

Compressed define.xml

Packaging check against the Study Data Technical Conformance Guide

Unauthorized file access

Access control, encrypted transfer, audit trail

Sensitive data exposed to public tools

Private hosting with documented data residency

Where does AD VERBUM fit?

 

AD VERBUM is a language service provider with 25+ years of experience. It runs a proprietary LangOps System on EU-hosted servers and works with a network of 3,500+ subject-matter expert linguists. Its AI+HUMAN hybrid translation covers 150+ languages and integrates client Translation Memories and Term Bases. It holds ISO 9001, 17100, 18587, 13485, 27001, 42001 and 14001 certifications and AQAP2110, audited by Bureau Veritas. It aligns to GDPR and HIPAA. See the translation and localization services.


AD VERBUM

What is our perspective?

 

Regulated XML fails on small errors. A moved placeholder or a changed attribute can invalidate a file that a linguist judged correct.   We treat the language and the file as one deliverable. Subject-matter experts review the text, and the markup stays protected. Your terminology assets govern the wording.   Hosting matters as much as accuracy. Our LangOps System runs on private EU infrastructure, so core processing does not depend on outsourced public cloud tooling.   The result is a file that your Regulatory Affairs team can validate and defend in an audit.   Eric Brown

 

FAQ

 

Does the FDA accept translated XML labeling?

 

Submissions must generally be in English. Where foreign-language-only labeling is permitted under 201.15©, the content is submitted in that language with an accurate English translation, per 21 CFR Part 207 Subpart E.

 

Should tag names and attributes be translated?

 

No. The SPL rules require files valid against the schema with no additional elements or attributes. Only the text content is translated.

 

Is define.xml compressed for submission?

 

No. The Study Data Technical Conformance Guide states that define.xml should not be compressed.

 

What does XLIFF do?

 

XLIFF carries extracted translatable data between tools and merges it back, keeping non-localizable parts in a skeleton, per the OASIS FAQ.

 

Key points

 

  • Translate text nodes only. Protect markup, codes and namespaces.

  • Assign a named owner and control to every step.

  • Validate against the schema and FDA rules before submission.

  • English is the required submission language, with limited exceptions.

  • Define-XML 2.1 applies to studies starting on or after March 15, 2023.

  • Keep define.xml uncompressed.

  • Record an audit trail for each file and segment.

  • Choose vendors on certifications, hosting and subject expertise.

 

Sources

 

 
 
bottom of page