ediverse Explore the platform

Spotlight PEPPOL BIS Billing 3.0 The EU e-invoicing mandate is here — France Sept 2026, Belgium Jan 2026, Germany 2025.

NamingSystem — Address book of identifiers and codings

The registry of systems used in FHIR Identifiers and Codings: OID, URI, UUID, their owners, their descriptions, their synonyms.

Purpose of the resource

NamingSystem documents a system used to qualify an Identifier (e.g. urn:oid:1.2.250.1.213.1.4.8 for France's INS-NIR) or a Coding (e.g. http://loinc.org). It declares the owner, the type (code system or identifier system), the known UniqueIds (OID, URI, UUID, other), and their preference.

It plays a critical role in the national ecosystem: the French OID registry, HL7 International's OID Registry, IHE PIX, all publish their data as NamingSystems.

Key fields

FieldTypeCardinalityRole
urluri0..1Canonical URL.
identifierIdentifier[]0..*Business identifiers.
versionstring0..1Version.
namestring1..1Short name.
titlestring0..1Human-readable title.
statuscode1..1draft | active | retired | unknown.
kindcode1..1codesystem | identifier | root.
datedateTime1..1Registration date.
publisherstring0..1Publisher.
responsiblestring0..1Operationally responsible entity.
typeCodeableConcept0..1Identifier type (HL7 v2-0203 or local).
descriptionmarkdown0..1Description.
usagestring0..1Usage context description.
uniqueIdBackboneElement[]1..*Known unique identifiers (OID, URI, UUID, other). Has a preferred.

JSON example

json namingsystem-example.json
{
  "resourceType": "NamingSystem",
  "id": "loinc",
  "name": "LOINC",
  "status": "active",
  "kind": "codesystem",
  "date": "2026-05-15",
  "publisher": "Regenstrief Institute",
  "responsible": "Regenstrief Institute, Inc.",
  "type": {
    "coding": [{
      "system": "http://terminology.hl7.org/CodeSystem/v2-0203",
      "code": "LN"
    }]
  },
  "description": "Logical Observation Identifiers Names and Codes — observation identifiers.",
  "usage": "LOINC is used to identify laboratory observations and clinical measurements.",
  "uniqueId": [{
    "type": "oid",
    "value": "2.16.840.1.113883.6.1",
    "preferred": false
  }, {
    "type": "uri",
    "value": "http://loinc.org",
    "preferred": true
  }]
}

Common pitfalls

  • No preferred=true — leaves consumers puzzled.
  • Non-normalised OID — always store without prefix (the urn:oid: prefix is added on use).
  • Mixing identifier / codesystem — a code system and an identifier system are not declared the same way.