Codes instead of free text Always the current release Via the National Terminology Server

Custom SNOMED CT integration development

SNOMED CT is the international medical terminology system that healthcare professionals use to record diagnoses, complaints, procedures and findings unambiguously. In the Netherlands, Nictiz manages the system via the SNOMED National Release Center, and a licence can be requested there free of charge. If you want your own software to code with SNOMED, search it and keep up with the latest releases, you need an integration. Appfront builds that integration.

What is a SNOMED CT integration?

A SNOMED CT integration makes your software record medical concepts as codes instead of free text. SNOMED CT contains a large collection of medical terms with their synonyms and the relationships between them. Each concept has a unique, numeric ID that carries no meaning in itself, with descriptions in several languages. According to Nictiz, the terms are used to record diagnoses, complaints, symptoms, interventions and results. The structure is polyhierarchical: a concept has more general parent concepts and more specific child concepts, so you can later search on a whole group as well. SNOMED International maintains the system, and the part relevant to the Netherlands has been translated into Dutch.

The Netherlands has been a member of SNOMED International since 2007. The Nictiz terminology centre manages SNOMED in the Netherlands on behalf of the Ministry of Health, Welfare and Sport (VWS), via the SNOMED National Release Center (NRC). Hospitals, ICT suppliers and other organisations can apply for a licence there free of charge, and once the licence is accepted they download the Dutch and international editions through the MLDS portal. According to Nictiz, the Dutch edition has been released every month since September 2024, except in July and December. A licence holder may grant sublicences to users of their systems and is then responsible for distributing new releases to them.

We build custom software because, according to SNOMED International, SNOMED does nothing on its own: it has to be used in an application. You can load the release files yourself, run SNOMED International's open source terminology server Snowstorm, or query Nictiz's National Terminology Server, which makes SNOMED available via the FHIR standard and which Nictiz keeps up to date. The integration enables searching on synonyms, limits the choice to the reference set that belongs to a field, such as the Diagnosis Thesaurus, and uses the mappings to ICD-10, among others, where you need them. We map existing local lists to SNOMED, so old and new data can be used together.

Coded

Concepts recorded unambiguously.

Up to date

Every new release processed.

Mapped

Local lists mapped to SNOMED.

How we build your SNOMED CT integration

We start with your data: which fields currently contain free text or a custom list, who records them and what they are used for later. Then, for each field, we choose the reference set or part of the hierarchy that fits, and how to make it available: loading it yourself, your own terminology server or the National Terminology Server. We first build one field completely, with searching, selecting and saving, and let healthcare professionals try it in practice. The remaining fields follow, along with the mapping of your old lists and updating with every release.

1
Mapping your data

Fields, usage, reuse.

2
Choice per field

Reference set and delivery.

3
First field

Search, select, save.

4
Go-live and maintenance

Mapping, and every new release.

What a SNOMED CT integration actually does

The components below appear in almost every SNOMED CT integration. Which ones you need depends on whether your focus is on recording, exchanging or analysing data.

Search

On terms and synonyms.

Reference sets

The right choice per field.

Releases

New editions loaded.

Terminology server

Queried via FHIR.

Mapping

Local lists and ICD-10.

Log

Every change traceable.

Who we build a SNOMED CT integration for

The integration is intended for organisations that want to record or reuse data unambiguously, and for suppliers that want to support SNOMED in their software.

Healthcare organisations

Less free text in the record.

Software builders

SNOMED in your healthcare software.

Data teams

Analysis of coded data.

Records

Unambiguous data submission.

Technology and integrations

This page is about using SNOMED CT as the terminology in your software. Which code systems belong to which care concept is defined in the health and care information models (zibs); read about that under the zibs integration. For medicines, there is the G-Standaard integration. If you want to share coded data with patients, see the MedMij integration, and for the handover set between care providers, the BgZ integration. You can read about our approach at building software.

SNOMED CT Dutch edition MLDS portal RF2 release files National Terminology Server Snowstorm FHIR terminology services Reference sets Mapping to ICD-10 Changelog

Why Appfront for your SNOMED CT integration?

A free-text diagnosis, a custom list that nobody maintains any more, or a code list that lags months behind the release all make exchanging and analysing data difficult. We build on that: codes that fit the field, releases that are kept up to date and old lists that are mapped traceably.

Unambiguous

No confusion over meaning.

Up to date

New concepts on time.

Traceable

Old lists mapped.

Security and privacy in a SNOMED CT integration

SNOMED itself contains no patient data, but the fields in which you code do. The integration stores only the code and the selected term in your system, and queries an external terminology server without sending any data about the patient. Changes to mappings and reference sets are recorded with a timestamp and user, so you can check why an old record was given a particular code.

The integration runs in a European data centre or in your own environment, with encrypted connections and storage. Access credentials for the MLDS portal and the terminology server are kept secured. For sublicences, the integration keeps track of which users have received which release, so you can provide the overview if Nictiz asks for it.

Frequently asked questions about a SNOMED CT integration

Questions asked by information managers, application administrators and healthcare software vendors before they start with SNOMED.

An international medical terminology system with a large collection of terms, their synonyms and the relationships between them. Healthcare professionals use it to record diagnoses, symptoms, procedures and findings, among other things, in an unambiguous way.

Yes. In the Netherlands you apply for it free of charge from the SNOMED National Release Center at Nictiz, because the Netherlands is a member of SNOMED International. Once you have accepted the licence, you can download the editions via the MLDS portal.

According to Nictiz, the Dutch edition has been published every month since September 2024, except in July and December. Many EHRs expect you to import a new release yourself in good time; an integration can do that for you.

A Nictiz server on which SNOMED, LOINC, the Dutch Lab Code Set and UCUM, among others, can be queried via the FHIR standard. You do need a licence for the code systems you use, but you don't have to download the release files yourself.

A selection of concepts from SNOMED for a specific purpose or domain, such as the Diagnosis Thesaurus. By basing a field on a reference set, a healthcare professional can only choose from the concepts that fit there.

You can submit a change request to the NRC via the Nictiz Service Desk, stating the purpose for which you want to use SNOMED. The NRC assesses the request and takes the necessary action.

For organisations with their own software, old local lists or plans to analyse data, and for vendors who want to include SNOMED in their package. If your standard package already fully supports SNOMED for your fields, a custom integration is usually not needed.

SNOMED CT in your own software?

Tell us what data you currently record in free text or your own lists. We'll show you how an integration can code it with SNOMED.

Edit content