We have the SNOMED dataset installed onto our platform for the apps we provide - as the dataset is regularly updated, we are wondering what the most effective way of automating the process - I get emails notifying me that the dataset has been updated - should I use these email alerts to trigger an agent to update the dataset on our platform, or is there another way that you would recommend?
While triggering an agent via email alerts is a creative approach, it is not recommended for a production clinical environment due to the risk of missed emails, parsing failures, and a lack of predictable version control.
Instead, the industry-standard method to automate SNOMED CT dataset updates is to pull directly from official terminological release APIs using structured scripts or orchestration tools.
Why Email Triggers Fall Short
The Recommended Alternative: API & Orchestration
Depending on your jurisdiction, you should leverage programmatic endpoints provided by the official SNOMED distribution bodies.
Instead of waiting for a push notification (email), switch to a pull architecture using a cron job or an orchestrator (like Apache Airflow, AWS Step Functions, or GitHub Actions).
[ Scheduled Orchestrator ]
│ (e.g., Monthly Poll)
▼
[ Query SNOMED API ] ──► (New Version Found?) ──► No ──► [ End ]
│
▼ Yes
[ Download RF2 files & Verify Checksums ]
│
▼
[ Run Database Migrations in Staging ]
│
▼
[ Run Automated Validation Tests ]
│
▼
[ Zero-Downtime Swap to Production ]
Steps for a Best-Practice Automation Pipeline
20261001). If it matches your platform's active version, the pipeline stops. If it is newer, it triggers the download.To give you the most tailored implementation advice, could you let me know:
I've found the appropriate url for the dataset: https://termbrowser.nhs.uk/?perspective=full&conceptId1=404684003&edition=uk-edition&release=v20260923&server=https://termbrowser.nhs.uk/sct-browser-api/snomed&langRefset=999001261000000100,999000691000001104 - do you know how we would be alerted to any update without using email notifications?
The URL you provided belongs to the NHS Digital SNOMED CT Browser. While the browser is perfect for looking up specific clinical terms, the underlying REST API used by that interface is strictly prohibited for use in automated production systems.
To bypass email alerts safely and alert your platform to updates programmatically, you should use NHS England's Technology Reference Update Distribution (TRUD) API. TRUD is the official, secure platform where the SNOMED CT UK Edition data files are legally hosted and distributed. [1, 2, 3]
Instead of an email trigger, you can configure your automation pipeline to use a programmatic "pull" model via the TRUD API.
Step-by-Step Alert Automation via TRUD API
Log into your organization’s account on the NHS TRUD service. On your account page, you will find a unique API Key generated for your account. [1, 2]
Every asset on TRUD has an assigned item number visible in the URL of its release page. For example, the primary SNOMED CT UK Edition typically maps to its own specific item ID in the TRUD catalogue. [1]
Instead of relying on email triggers, write a lightweight script (e.g., in Python or Bash) hosted on your server or an orchestrator (like a monthly AWS Lambda function or a Cron job).
Your script will make an HTTP GET request to the TRUD Release List Endpoint, appending ?latest to check only the most recent version: [1]
http
GET https://isd.digital.nhs.uk/trud/api/v1/keys/{YOUR_API_KEY}/items/{ITEM_NUMBER}/releases?latest
Use code with caution.
(Replace {YOUR_API_KEY} with your token and {ITEM_NUMBER} with the SNOMED UK release item ID). [1]
The API will return a structured JSON response containing the latest version metadata. Your script should: [1]
releaseDate or version string (e.g., v20260923) against the version currently running on your app platform.Alternative: Syndication via the NHS Terminology Server
If your application leverages a clinical terminology server (such as Ontoserver) rather than raw file parsing, you can set up a Syndication Feed. The NHS England Terminology Server allows you to create a system-to-system account. Your local server can then talk directly to the NHS downstream feed to automatically detect and synchronize new expansions and concept maps as soon as they are approved. [1, 2]
Would you like assistance drafting a Python or Bash script to poll the TRUD API and compare the version strings, or would you prefer guidance on setting up an Ontoserver syndication stream?
Measured, not assumed. The platform's existing TRUD key already returns item 101, SNOMED CT UK Clinical
Edition, RF2: Full, Snapshot & Delta — HTTP 200, latest release SNOMEDCT2_43.0.0_20260923000001
(2026-10-06, 990,865,460 bytes) — while the UK Drug Extension (105) and UK Monolith Edition (1799) are not
subscribed (HTTP 404). So there is no email route to build and no new subscription to obtain: the central reference
routine already pulls from TRUD on a schedule (dm+d, weekly) with a release register, a per-release licence record and
staleness alerts, and SNOMED is being wired in as its sixth source (note L of the
Hermes→OpenCode inbox).
Two corrections worth keeping in the record. (1) The SNOMED CT UK Edition is not open data — dm+d is Open
Government Licence, SNOMED CT is licence-gated, which is exactly why TRUD issues a per-account credential for it. (2)
TRUD's credential is derived from the account's email address and password, it travels in the request path
(/trud/api/v1/keys/<key>/items/<id>/releases) and in every archive URL, and TRUD's own error bodies echo it back —
so a response must never be stored or logged verbatim, which is note (K).
And the update itself is done. The corpus is now the International RF2 Snapshot 20260801 (from TRUD release
SNOMEDCT2_43.0.0_20260923000001): concepts 535,233, descriptions 1,716,441, relationships 3,580,370, with
the previous load's defect repaid — it had swallowed ~127,627 descriptions (8% of the table) through PostgreSQL's
default CSV quoting. heart attack now leads with Myocardial infarction (disorder) [22298006]. The full record,
including the rollback tables and the UK Clinical Extension question, is on the
SNOMED page.