Terminology Code Management and Read-to-SNOMED Mapping
This page is the wiki anchor for Read Version 2 / CTV3 retirement, NHS SNOMED CT UK Edition and dm+d management, and local terminology-service handling of non-standard, local, or extension codes.
Boundary
This is standards and terminology-model evidence. It does not prove that any InterSystems product or deployment has loaded the NHS Terminology Server, implemented a specific SNOMED CT UK Edition or dm+d release, converted historical Read-coded data, maintained local ConceptMaps, or completed clinical-safety / information-governance assurance. Treat it as the model to test against product and deployment artefacts.
Current Reading
The safe reading is:
- New NHS England clinical recording should use SNOMED CT for clinical terms, and medicines / devices should use dm+d where medicines information is transferred electronically.
- Read Version 2 and CTV3 are retired or deprecated for active content management. Official Read-to-SNOMED migration products exist, but the generic Read Version 2 to SNOMED CT mapping tables are static after the final April 2020 release and should be treated as migration / analytics aids, not automatic clinical equivalence.
- SNOMED CT UK Edition is managed through NHS England standards, TRUD releases, UK extensions, request routes, browser/reference tools, and the NHS England Terminology Server.
- Local or non-standard codes should be handled as governed terminology resources: local CodeSystems, ValueSets, ConceptMaps, versioned imports from national terminology, clinical review, unmapped/no-map handling, audit, and safety governance. They should not become informal cross-organisation standards unless the local governance, licence, mapping purpose, and receiver agreement are explicit.
- Practical examples include the NHS England Terminology Server, NHS England's route for buying a local/federated terminology server, OneLondon, NHS Scotland, Australia's National Clinical Terminology Service, and OpenCodelists / OpenSAFELY codelist management.
Read Version 2 / CTV3 To SNOMED CT Mapping
| Evidence | What it supports | Boundary |
|---|---|---|
| NHS England Read Codes guidance | Read Version 2 final update in April 2016; CTV3 no further updates after April 2018; change requests now route to SNOMED CT; use dm+d for medicines and SNOMED CT for clinical content. | Retirement / transition policy, not evidence that every historical Read-coded item has a clinically safe replacement in a local record. |
| NHS TRUD Data Migration crossmaps | Official many-to-one forward crossmaps include Read Version 2 to SNOMED CT and CTV3 to SNOMED CT; the final generic mapping release was April 2020 and is now unmaintained static data. | Strong migration artefact evidence, but not a bidirectional equivalence guarantee or deployment-specific clinical-validation pack. |
| NHS Data Migration Workbench | Current TRUD workbench releases are preloaded with SNOMED CT, CTV3, READ, OPCS-4, ICD-10 and crossmaps, supporting migration and analysis workflows. | Tool availability does not prove local migration quality, clinical sign-off, or source-record provenance handling. |
| PBCL Read Code to SNOMED Code Translation Table | Supported map tables translate Read Codes in the PBCL EDIFACT primary-care pathology message into SNOMED CT. | Domain-specific primary-care pathology support; do not generalise it to all Read-coded record content. |
| Primary-care SNOMED subsets | NHS England's primary-care implementation material says initial primary-care SNOMED subsets were based on Read-to-SNOMED mappings and then expanded with early-adopter feedback. | Supports the migration pathway history, not complete or current equivalence for every legacy code. |
How Standard Codes Are Managed Now
| Layer | Managed by | Current mechanism | Evidence |
|---|---|---|---|
| SNOMED CT UK Edition | NHS England as UK National Release Centre / standards owner. | UK Edition releases through TRUD, including International Edition plus UK clinical extensions, refsets, maps, and added-value content; request portal for changes; browser/reference access; Terminology Server API access. | SRC-280, SRC-281 |
| dm+d | NHSBSA with NHS England terminology governance. | dm+d standard SCCI0052, weekly refresh, Content Committee governance, SNOMED CT identifiers, and UK Medicines Terminology Futures alignment with SNOMED CT UK Drug Extension. | SRC-282 |
| NHS England Terminology Server | NHS England. | Live cloud FHIR-compliant terminology service exposing CodeSystem, ValueSet, and ConceptMap resources; supports current and previous versions, APIs, syndication, Snapper authoring/mapping, and sharing locally authored terminology. | SRC-281 |
| Local or extension content | Local organisation, regional programme, or terminology producer under SNOMED/FHIR governance. | Local CodeSystems, ValueSets, and ConceptMaps; SNOMED extension namespace and maintenance controls where extension content is created; $expand, $validate-code, $lookup, and $translate operations for use in systems. |
SRC-281, SRC-283, SRC-284 |
| Implementation assurance | Supplier plus care organisation. | Source terminology versions, mapping purpose, mapping equivalence, clinical review, no-map handling, inactive-code handling, provenance, release cadence, audit, DCB0129/DCB0160 where clinical workflow is affected, and local operating RACI. | SRC-283, SRC-284 |
Local, Non-Standard, And Extension Code Handling
Use a terminology-service model when local codes are unavoidable.
| Requirement | Practical handling |
|---|---|
| Prefer national standards | If a required or extensible binding has an applicable SNOMED CT or dm+d code, use that standard code. A local code may be carried as an additional coding only where the profile and receiver agreement allow it. |
| Preserve source provenance | Historical Read-coded entries should retain original code, term, source system, date, author/source organisation where available, and map-version metadata if converted or dual-coded. |
| Define local codes explicitly | Use a local CodeSystem for local code definitions and ownership, not undocumented app-table values. |
| Control permitted sets | Use ValueSets for the subset allowed in a workflow, form, interface, report, or extraction. |
| Map with purpose and review | Use ConceptMaps for local-to-standard or Read-to-SNOMED mappings. Record mapping purpose, equivalence, mapper/reviewer, date, source and target versions, unmapped items, and review cycle. |
| Validate at runtime or release time | Use terminology operations such as $validate-code, $lookup, $expand, and $translate, or an approved local mirror/syndicated terminology service where real-time calls are not appropriate. |
| Govern change | Treat terminology releases as versioned inputs. Inactive SNOMED concepts, inactive-but-valid dm+d identifiers, superseded local codes, and mapping changes need release notes, reprocessing policy, clinical sign-off, and rollback/error handling. |
Examples
| Example | What it shows | Boundary |
|---|---|---|
| NHS England Terminology Server | A live national cloud FHIR terminology service containing SNOMED CT, dm+d, ICD-10, OPCS-4, Read Codes, and other content; NHS England describes local-code mapping, authoring, syndication, and system-to-system FHIR APIs. | National service model, not proof that a named supplier deployment uses it. |
| NHS England local / federated server route | NHS England describes buying an Ontoserver-based terminology server, loading local codes, mapping national to local codes, and federating with the national ecosystem. | Procurement/model evidence; local implementation still needs contract, governance, and deployment proof. |
| OneLondon terminology server | OneLondon describes tailoring terminology-server work to London priorities, consistent mapping for London Data Service needs, and a Dedalus / CSIRO Ontoserver route. | Regional implementation signal, not an InterSystems or national NHS England deployment claim. |
| NHS Scotland terminology service | Public NHS Scotland / partner material shows a terminology-service route using browser, authoring, mapping, and FHIR endpoint patterns. | Scotland-specific example; do not import NHS England DSIC or DUAA labels without local evidence. |
| Australia National Clinical Terminology Service | National tooling for release, distribution, terminology server access, syndication, browser, mapping platform, SNOMED CT-AU, and Australian Medicines Terminology. | International national-service example, not UK supplier proof. |
| OpenCodelists / OpenSAFELY | Practical management of research codelists across SNOMED CT, CTV3, dm+d, BNF, ICD-10 and related schemes. | Research / analytics codelist governance example, not a clinical operational terminology service. |
InterSystems Due-Diligence Reading
If an InterSystems product, partner, or customer deployment claims Read-to-SNOMED migration, SNOMED CT UK Edition use, dm+d support, local-code mapping, or terminology-service integration, ask for:
| Proof area | Evidence to request |
|---|---|
| Source packages | SNOMED CT UK Edition, dm+d, Read/CTV3 map, ICD/OPCS, local-code package names, release dates, source authority, licence route, and ingestion method. |
| Terminology architecture | NHS Terminology Server, local Ontoserver/Snowstorm/Snow Owl/Hermes, internal terminology tables, or hybrid pattern; FHIR CodeSystem / ValueSet / ConceptMap support; cache/syndication policy. |
| Mapping design | Map purpose, direction, equivalence categories, many-to-one handling, no-map list, inactive concept handling, local-code retirement, clinical review, and test cases. |
| Record provenance | Preservation of original Read/local code, display term, source system, author/source organisation, coded-date, migration-date, and map version. |
| Safety and governance | DCB0129/DCB0160 where clinical workflow is affected, clinical-safety officer roles, hazard log, residual-risk acceptance, data-quality controls, rollback/reprocessing, and operating RACI. |
| Deployment proof | Customer-approved architecture, interface catalogue, onboarding records, DSA/DPIA where relevant, audit design, release/change controls, go-live status, and operational support model. |
What This Page Proves And Does Not Prove
What it proves:
- Read Version 2 and CTV3 are no longer active clinical terminology authoring routes for new NHS England clinical content.
- Official Read-to-SNOMED mapping artefacts and tooling exist, with important static/unmaintained boundaries for generic maps.
- SNOMED CT UK Edition, dm+d, and the NHS England Terminology Server are the current standards-management frame for coded clinical and medicines data in England.
- Local and non-standard codes should be handled through governed terminology resources and services, not undocumented local values.
What it does not prove:
- It does not prove any InterSystems product is currently configured with NHS Terminology Server, SNOMED CT UK Edition, dm+d, TRUD map files, or local ConceptMaps.
- It does not prove a local Read-to-SNOMED migration is clinically safe, complete, current, or deployment-approved.
- It does not replace product/version evidence, customer architecture, clinical-safety cases, information-governance artefacts, or local terminology-governance documentation.