SNOMED CT in Vietnam: localized content and FHIR integration

1. What is SNOMED CT

SNOMED CT stands for Systematized Nomenclature of Medicine — Clinical Terms, an international, logic-based, polyhierarchical clinical reference terminology governed by the non-profit organization SNOMED International. The International Edition is versioned; the latest production release at this page's content snapshot is the July 2026 edition, released through MLDS on 1 July 2026.

SNOMED International is a non-profit registered in England and Wales and headquartered in London. The terminology content originated in 2002 from the convergence of SNOMED RT, developed by the College of American Pathologists, and Clinical Terms Version 3 from the UK NHS. The governing organization was established as the International Health Terminology Standards Development Organisation (IHTSDO) in 2007 and began trading as SNOMED International in 2017.

Official technical documentation describes SNOMED CT as an international, logic-based reference terminology for representing clinically relevant information. The International Edition, national extensions, translations, and reference sets are separately versioned artifacts; implementations should record the edition, version, and module rather than storing an SCTID without provenance.

2. Concept structure and hierarchies

Each SNOMED CT concept is identified by a SCTID, a unique integer — for example, 38341003 corresponds to "Hypertensive disorder". Each concept comes with a set of descriptions (Fully Specified Name and Synonyms), a set of relationships defining its links to other concepts, and module metadata identifying the publishing source.

Concept 38341003 |Hypertensive disorder|
  description[]
    FSN     "Hypertensive disorder, systemic arterial (disorder)"
    Synonym "Hypertension"
    Synonym "HTN"
  relationship[]
    IS-A             → 64572001  |Disease|
    Finding site     → 113257007 |Cardiovascular system structure|
  module
    900000000000207008 |SNOMED CT core|

The IS-A relationship forms a multi-inheritance tree, allowing a concept to belong to several parent branches. In addition, attributes such as Finding site, Causative agent, and Associated morphology form a post-coordination model with rich semantics — far beyond any linear classification scheme.

The international edition divides the concept space into 19 top-level hierarchies: Body Structure, Clinical Finding, Procedure, Substance, Pharmaceutical / Biologic Product, Observable Entity, Specimen, Physical Object, Physical Force, Event, Environment / Geographical Location, Social Context, Situation with Explicit Context, Staging and Scales, Qualifier Value, Record Artifact, SNOMED CT Model Component, Special Concept, and Organism. Note that "Disorder" is not a top-level hierarchy on its own; disorder and diagnosis concepts form a sub-tree within Clinical Finding.

3. SNOMED CT versus ICD-10

ICD-10 and SNOMED CT serve two different but complementary purposes — they are not interchangeable. ICD-10 is a classification used for disease statistics, epidemiological reporting, and insurance billing. SNOMED CT is a clinical terminology used to record medical events with high precision.

The recommended practice in FHIR VN Core is to send both codings inside the same CodeableConcept. ICD-10 satisfies the BHYT billing obligation under Decision 4469/QĐ-BYT, while SNOMED CT preserves rich clinical semantics for decision support and downstream analytics.

{
  "resourceType": "Condition",
  "subject": { "reference": "Patient/example" },
  "code": {
    "coding": [
      {
        "system": "http://snomed.info/sct",
        "code": "38341003",
        "display": "Hypertensive disorder"
      },
      {
        "system": "http://hl7.org/fhir/sid/icd-10",
        "code": "I10",
        "display": "Essential (primary) hypertension"
      },
      {
        "system": "http://fhir.hl7.org.vn/core/CodeSystem/vn-icd10-cs",
        "code": "I10",
        "display": "Tăng huyết áp vô căn (nguyên phát)"
      }
    ]
  }
}

4. Membership and licensing

Under SNOMED International's official licensing guidance, a Member is a national government agency or another body endorsed by the appropriate national authority. SNOMED International does not charge for use in Member territories; registration is handled through a National Release Center or MLDS, depending on the country.

The snapshot on the official Member page (map dated 1 June 2026) names 53 Members and does not include Vietnam. SNOMED International states that deployment in a non-Member territory requires an annual MLDS license; charges may apply, and fee exemptions require an application. Vietnam's three 2025 Decisions do not automatically replace the terms governing the International Edition. Implementers should record edition, version, content source, and license scope.

SNOMED CT IPS Terminology is a separate open product published under CC BY 4.0. Its current implementation guide describes more than 15,000 concepts for the International Patient Summary scope; it is not a substitute for the complete International Edition across all clinical use cases.

5. Vietnamese content releases issued to date

The Ministry of Health laid the legal foundation through Decision 1928/QĐ-BYT (2023) on the Health e-Government Architecture version 2.1, which designates SNOMED CT as one of the national standard terminologies. The year 2025 marked real momentum, with three consecutive release waves.

Each source row carries four core fields: vn_code — a Ministry of Health management code, snomed_ct_id — the international SCTID, name_vn — the Vietnamese term, and name_en — the source English term. A total of 1,327 SCTIDs occur in more than one source scope; the pipeline retains the relevant designations but creates one concept per SCTID, producing 76,066 unique concepts in the full artifact.

The three Decisions establish the scope published to date. The primary Vietnamese corpus cited on this page does not contain an instrument confirming the order of future hierarchies, a date for establishing a National Release Center, or a timetable for Vietnam to become a Member. Any proposed expansion should therefore be labeled as a technical option and updated only when the competent authority publishes a new instrument.

6. Localized scope

VN Core declares VNSNOMEDSubsetCS at http://fhir.hl7.org.vn/core/CodeSystem/vn-snomed-subset-cs as a CodeSystem supplement: content = #supplement and supplements = http://snomed.info/sct. The public IG page carries metadata only; the full JSON artifact in hl7.fhir.vn.terminology.clinical contains 76,066 unique concepts and adds Vietnamese designations plus a vn-code property for SCTIDs sourced from the 77,393 rows.

VN Core ships companion ValueSets for context-aware bindings: vn-body-site-vs for Procedure.bodySite and Condition.bodySite, vn-condition-code-vs for Condition.code, and vn-allergy-code-vs for AllergyIntolerance.code. A separate erratum page for the SNOMED CT VN translation is published in the IG so that the community can flag corrections.

7. Integration with FHIR VN Core

The VNCoreCondition profile binds code to vn-condition-code-vs at extensible strength, allowing ICD-10 and SNOMED CT codings within the published binding scope. The VNCoreAllergyIntolerance profile uses SNOMED CT IPS Terminology for code, also at extensible strength. IPS Terminology is a separate open product with a defined scope; concepts outside that scope require the appropriate SNOMED CT edition and licensing basis.

// VNCoreCondition.fsh — extract
* code 1..1 MS
* code from $vn-condition-code-vs (extensible)

// VNCoreAllergyIntolerance.fsh — extract
* code 1..1 MS
* code from $vn-allergy-code-vs (extensible)

// VN Body Site for Condition.bodySite
* bodySite from $vn-body-site-vs (preferred)

Extensible bindings let systems fall back to ICD-10 or text descriptions when no suitable SNOMED concept exists yet, while still reporting conformance once one is available. For systems that need parallel coding for BHYT reporting, the VNCoreConditionDiagnosis profile extends VNCoreCondition by making ICD-10 mandatory and SNOMED CT optional but recommended.

When representing a concept from the published set, the SNOMED CT coding uses system = http://snomed.info/sct and one of the artifact's 76,066 unique SCTIDs; the supplement only supplies additional designations and properties. For diagnoses used in BHYT billing, add Vietnamese ICD-10 according to the applicable profile and workflow. If multiple codings are present, record terminology versions and the mapping relationship, and test equivalence rather than assuming the codings are synonymous because they share a CodeableConcept.

8. ECL — the query language

Expression Constraint Language (ECL) is the official query language of SNOMED International. It defines concept subsets based on relationships in the terminology graph. ECL is used to build dynamic ValueSets, filter concepts by attribute, and write semantic validation rules.

// ECL examples
< 38341003 |Hypertensive disorder|
   // all descendant concepts (excluding the concept itself)

<< 38341003 |Hypertensive disorder|
   // descendants including the concept itself

< 64572001 |Disease| : 363698007 |Finding site| = << 80891009 |Heart structure|
   // Diseases whose Finding site is Heart or any descendant of Heart

In FHIR R4, ECL is embedded inside ValueSets through filter operators. VN Core uses the standard FHIR syntax with descendent-of or is-a — note the FHIR R4 spelling (descendent, not descendant).

ValueSet: VNHypertensionVS
Id: vn-hypertension-vs
* include codes from system http://snomed.info/sct
    where concept descendent-of #38341003

When the terminology server supports native ECL (both Snowstorm and Ontoserver do), you can pass complex ECL expressions through the filter parameter on $expand — for example filter=<<233604007|Pneumonia|. This pattern is widely used by clinical data-entry applications to surface context-appropriate concepts.

9. Snowstorm and Ontoserver tooling

Two terminology servers commonly turn up in SNOMED CT FHIR deployments: Snowstorm and Ontoserver. Snowstorm is built by SNOMED International and released as open source under Apache 2.0 on GitHub at github.com/IHTSDO/snowstorm. Snowstorm has full ECL support, FHIR Terminology Service operations $lookup, $validate-code, $expand, and $translate, and is the engine that powers the public SNOMED Browser.

Ontoserver is developed by Australia's CSIRO and offered commercially. Its product documentation describes support for multiple terminologies, including SNOMED CT, LOINC, and classifications; verify capabilities, editions, ECL/FHIR operations, licensing, and the operating model for the deployed version.

For open-source projects or early stages, HAPI FHIR provides a JPA-backed terminology service implementation with partial SNOMED CT support (basic lookup and validation, but no native ECL). If your use case requires complex ECL, the safe choice is to run Snowstorm as a sidecar and have HAPI delegate to it via the FHIR Terminology Service.

For VN Core, the practical way to verify SNOMED-backed ValueSets is to stand up an ECL-capable terminology server and load the JSON artifact from the hl7.fhir.vn.terminology.clinical package, which tracks the three Ministry of Health Decisions — expansions can then be checked against exactly the content the Ministry has released. The IG build itself currently relies on a public terminology server and still hits timeouts when validating SNOMED CT codes; that is precisely why a dedicated instance is recommended for serious test environments.

10. Frequently asked questions

Is SNOMED CT free to use in Vietnam?

The three 2025 Decisions define Vietnamese content catalogs, but they do not automatically grant rights to the complete International Edition. Under the official guidance, deployment in a non-Member territory requires licensing through MLDS; charges may apply, and some uses may qualify for a fee exemption. Implementers must check the terms for the specific product, version, and use case.

Is ICD-10 enough for VN Core?

Where a reporting, statistics, or payment workflow requires Vietnamese ICD-10 under its applicable instrument or contract, retain the required classification and version. SNOMED CT may add detail in Condition.code, AllergyIntolerance.code, or suitable observation elements; Observation.code commonly uses LOINC or a laboratory code under the profile binding and must not be replaced by SNOMED CT by default.

When will VN Core require SNOMED CT?

There is no published date for VN Core to require SNOMED CT. The current release uses the binding strengths stated in each profile. Any move to preferred or required must go through IG governance, coverage and backward-compatibility analysis, and licensing review, then appear in a versioned release.

Can we test SNOMED CT before membership?

The SNOMED Browser can be used to inspect content, but browser access does not itself grant deployment rights. For the International Edition in a non-Member territory, SNOMED International requires MLDS registration and charges may apply; research or public-good projects may apply for a fee exemption. If the use case is limited to IPS, the IPS Terminology can be evaluated under its CC BY 4.0 license and product-specific guidance.