Terminology releases stop being a fire drill
SNOMED CT moved to monthly International Edition releases. RxNorm has always been monthly. MedDRA lands twice a year and LOINC goes monthly in 2027. Every one of those releases retires concepts your mappings point at. TopQuadrant governs the terminologies, the crosswalks between them, and your local extensions, so a release is a diff to review rather than a project to run.
Trusted to govern the data behind the world's most regulated decisions.
Your process was designed for a biannual release cadence that no longer exists
Most terminology governance in pharma was built when SNOMED CT shipped in January and July. It now ships monthly, and LOINC follows in 2027. The teams feeling this first are the ones whose safety, RWE, and lab pipelines depend on mappings nobody has re-validated since the last release. Version-aware mapping management is the fix, and it is a governance capability rather than a script.
SNOMED CT International Edition releases per year as of 2026, up from two, each carrying inactivations your mappings have to absorb.
Prebuilt ontologies and vocabularies available out of the box, including the standards this sector runs on.
One governed home for external standards, internal extensions, and every crosswalk between them.
Release ingestion
Absorb a release as a reviewable diff
Load each new release of SNOMED CT, MedDRA, LOINC, RxNorm, ICD-11, or CDISC controlled terminology and see precisely what changed: new concepts, inactivations, relabels, and hierarchy moves, with every one of your mappings and tagged assets that touches them.
- Concept-level diffs. New, retired, relabelled, and moved concepts listed against the prior release.
- Affected-asset report. Every internal mapping, codelist, and dataset referencing a changed concept.
- Release history retained. Prior versions stay queryable, so historical data still resolves correctly.
Version-aware crosswalks
Mappings that record which version they were asserted against
SNOMED CT to MedDRA, MedDRA to WHODrug, SNOMED CT to ICD-10 and ICD-11: the published crosswalks are partial, maintained by different bodies on different cycles, and nothing flags it when they break. Here each correspondence records its source version, its basis, and whether it is exact or approximate.
- Version stamps on both sides. Know which release of each terminology a mapping was validated against.
- Exact and approximate flagged. Compositional mismatches are recorded rather than assumed away.
- Break detection. After a release, see which correspondences now point at inactive concepts.
Local extensions
Extend a standard without forking it
Internal codes, sponsor-specific terms, and legacy dictionaries live alongside the published standards, related to them explicitly. You keep your extensions separable, so the next release of the standard updates cleanly underneath them.
- Separable extensions. Local concepts are yours, related to standard concepts rather than mixed into them.
- Legacy dictionary retirement. Map an old internal dictionary to a standard with a documented migration path.
- Governed submission codelists. CDISC controlled terminology and your divergences from it, held together.
Impact on downstream data
Know what a recode does to your historical numbers
Upgrading a safety database to a new MedDRA version can change historical event frequencies if terms merged or split. Because the terminology and the data that references it live in one graph, you can see the affected records before the upgrade rather than explaining the shift afterwards.
- Pre-upgrade impact. Records and analyses affected by a merge, split, or relabel, before you commit.
- Point-in-time resolution. Reproduce a historical analysis against the terminology version in force then.
- Deprecated code sweep. Find every place a retired LOINC or RxNorm code is still in use.