Terminology is often treated as a static lookup file. In a clinical data pipeline, it is a dependency that can affect mappings, validation, metadata, and interpretation. Updating it without examining those relationships can create unexplained differences between otherwise similar study packages.
CDISC controlled terminology is maintained through published releases. The NCI CDISC vocabulary resources provide an authoritative route to the terminology content. The operational practices below are recommendations for managing a study’s selected version.
1. Record the version explicitly
A specification that says “use current terminology” is difficult to reproduce months later. Record the selected release, applicable codelists, approved extensions, and study-specific decisions. Keep the actual reference material or a recoverable controlled reference, rather than depending on an unversioned link alone.
A hypothetical laboratory category may remain clinically unchanged while its permissible representation evolves. A later validator can report a difference that reflects version alignment rather than a new data defect. Reviewers need enough context to distinguish those situations.
2. Separate update types
A correction to an incorrectly assigned term differs from adopting a new vocabulary release. One addresses study data quality; the other changes a dependency. Both may affect outputs, but their approvals and impact assessments need not be identical.
Compare releases at the codelist and term level. Identify additions, retirements, definition changes, and changes relevant to the study’s actual content. Do not rerun a broad migration merely because a newer release exists without first evaluating why it is needed.
3. Trace downstream consequences
Terminology can affect grouping and presentation as well as conformance. Examine mappings, derived categories, table labels, and metadata that reference an affected term. A cosmetic-looking change may split categories or alter sorting in a downstream report.
Define-XML is useful additional reading for the metadata layer. Our recommendation is to maintain one shared terminology decision record across specifications, datasets, and metadata, with checks that identify disagreement between those artifacts.
4. Preserve justified exceptions
Where an extension is permitted, document its meaning and why an existing term does not represent the collected concept. Involve the appropriate standards reviewer. Avoid repurposing a superficially similar term simply to eliminate a validation message.
For a practical release review, select a few affected concepts and verify their representation from collection through output. Include one extension and one corrected assignment, if present. Confirm that the package’s metadata identifies the intended version and that reviewers can understand any differences from earlier transfers.
Consistency does not mean forcing every study onto the newest vocabulary immediately. It means applying an explicit, justified version policy and retaining enough evidence to explain what changed and why.
