DOM-004 · Domains changed

Domain code is not in the SDTMIG v3.4 or v4.0 domain tables

All 47 rules · Catalogue 0.15.2 targeting SDTMIG v4.0 (public-review)

Rule
DOM-004
Category
Domains changed
Basis
Confirmed Traceable to the published specification text cited below.
Detectability
External context required The Define-XML cannot settle this. Answering it needs a decision or a fact held outside the submission metadata.
Finding type
Question
Applies to
SDTMIG 3.2, 3.3, 3.4

What changes in v4.0

Each SDTMIG release absorbs content that sponsors previously carried in custom domains. v4.0 adds DC, GI and EA, and restates that "sponsors may not add any variables other than those described here" and "standard variables must not be renamed or modified for novel usage". What this finding reports is narrower than "this is a custom domain": the domain code is not among the 67 domains defined by the SDTMIG v3.4 and v4.0 specification tables, nor among the companion-IG domains this report also checks. Those tables are a snapshot, not the registry. Section 4.1.6, Dataset Naming, points at the registry — "see the CDISC Controlled Terminology SDTM Domain Abbreviation codelist (DOMAIN) for standard domain codes" — which is versioned, published quarterly, and includes domains from Therapeutic Area User Guides and companion IGs that this report does not check against. A domain from one of those will appear here and is not sponsor-defined.

What to do about it

First establish which kind of dataset this is, because a Define-XML alone cannot. Check the domain code against the current CDISC Controlled Terminology DOMAIN codelist and against the Therapeutic Area User Guides in use on the study. If it is there, this finding tells you only that the code sits outside the SDTMIG's own tables. If it is not, it is a sponsor-defined custom domain: check it against the v4.0 domain list, since retiring a custom domain in favour of a standard one removes a permanent conformance-explanation burden. Section 4.1.6 also notes that domain codes beginning with X, Y or Z are reserved for custom domains, so a code starting with one of those is a custom domain with no further checking needed.

What the scan can and cannot see

That the domain code is absent from the SDTMIG's own domain tables is a fact about those tables. Section 4.1.6 names the CDISC Controlled Terminology DOMAIN codelist as the registry, and that codelist plus the study's Therapeutic Area User Guides decide whether the code is standard or sponsor-defined.

Sources

Every claim above rests on one of these. Where a line is from the public-review draft it says so, because a draft can still move.

  1. SDTMIG v4.0 public-review draft (exported 2026-02-09), Section 3.2, Data to be Included in SDTM Datasets for Human Clinical Trials — 'Sponsors may not add any variables other than those described here'; 'Standard variables must not be renamed or modified for novel usage' (draft specification text)
  2. SDTMIG v4.0 public-review draft (exported 2026-02-09), Section 4.1.6, Dataset Naming — 'See the CDISC Controlled Terminology SDTM Domain Abbreviation codelist (DOMAIN) for standard domain codes'; NS, SA, AP, AD and AX are reserved prefixes; 'domain codes beginning with the letters X, Y, and Z have been reserved for the creation of custom domains' (draft specification text)
  3. SDTMIG v4.0 public-review draft (exported 2026-02-09), Appendix E, New Domains for SDTMIG v4.0 — DC, GI, EA
  4. Mechanically observed specification tables, SDTMIG v3.4 (2022-07-21) and SDTMIG v4.0 public-review draft (2026-02-09) — 67 domains across both versions, carried in the versioned standards registry (packages/core/src/standards); this is what the rule compares against, and it is not the CDISC CT DOMAIN codelist

Does this one apply to your studies?

Open the scanner, then select or drop in a Define-XML file. It checks this rule and the other 46 in your browser; the file is never uploaded.

Open the scanner