Interoperability · SNOMED CT

Clinically safe, comparable, computable data

Every diagnosis, problem, and procedure is captured as a coded SNOMED CT concept, searchable in everyday clinical language, mapped to ICD-10, and scoped by specialty.

Clinically safe, computable data

SNOMED CT turns clinical language into structured data that can be searched, compared, and analysed.

Coded Problems & Diagnoses

Every problem and diagnosis is captured as a SNOMED CT concept, not a free-text description.

Procedures & Findings

Clinical procedures, findings, and observations are coded consistently across every module.

Hierarchical Concept Model

Concepts sit within a clinical hierarchy, so a coded diagnosis can be queried at any level of specificity.

Cross-Mapping to ICD-10

Coded concepts map to ICD-10 for reporting and reimbursement workflows that require it.

Specialty Refsets

Reference sets scope the relevant subset of SNOMED CT to each specialty, keeping search results relevant.

Terminology Search

Clinicians search using everyday clinical language; the platform resolves it to the correct coded concept.

One concept, precisely placed

An illustrative example of how a single diagnosis sits within the SNOMED CT concept hierarchy.

  1. Clinical finding
  2. Disease
  3. Metabolic disease
  4. Diabetes mellitus
  5. Type 2 diabetes mellitus

A concept lookup, in practice

Illustrative example. Actual concept identifiers depend on your terminology server configuration.

GET /terminology/concept/example-id
200 OK
{
  "conceptId": "example-id",
  "term": "Type 2 diabetes mellitus",
  "active": true,
  "hierarchy": [
    "Clinical finding",
    "Disease",
    "Metabolic disease",
    "Diabetes mellitus"
  ],
  "synonyms": ["Type 2 diabetes", "NIDDM"],
  "mappings": {
    "icd10": "E11"
  }
}
0

Globally recognised clinical terminology

0+

Years of coded clinical documentation

0%

Diagnoses & problems coded, not free text

0

Terminology systems cross-mapped

SNOMED CT questions, answered

Talk to us about clinical coding in your deployment

Book a session with our team to review terminology scope, refsets, and mapping requirements.