Home / Insights / Connectivity

LOINC and SNOMED CT coding for lab results: a practical guide

ConnectivityPublished 2026-11-189 min readInternational

An analyser calls a test "TSH" or "Ch 14". Your EHR wants a code. The patient's other provider wants a different one. Standard codes are how results stay meaningful when they leave the lab. This guide explains LOINC and SNOMED CT for lab results, where each is used, and how to map your tests without breaking your interfaces.

Written and reviewed by the Catenix team. How these guides are written and checked.

In brief

  • LOINC codes identify what was measured: the analyte, property, timing, specimen, scale and method. It is widely used for lab results in the US.
  • SNOMED CT is a clinical terminology used across the NHS, including for pathology tests and results in the UK.
  • Codes must be mapped per test, per analyser and per receiving system; the analyser's own code is never enough.
  • Common mistakes: wrong specimen type, wrong units, one code for several methods, and panels coded as a single result.
  • Catenix maps each analyser's codes to tests in its test library, where each test can carry a LOINC and a SNOMED CT code. Each destination is set to receive local or LOINC codes, and on a feed agreed as LOINC-coded, a result without a LOINC code is not sent.

Take it with you: POCT connectivity buyer's guide · POCT readiness checklist (PDF, no form).

Why lab results need codes

Inside one lab, a test name is enough. Outside it, names fail: "Glucose" could be serum, plasma, whole blood or urine, fasting or random, in mmol/L or mg/dL. When results go into an EHR, a regional record, a research dataset or a patient's app, the receiving system needs to know exactly what was measured to display trends, run alerts and avoid comparing unlike things. Standard codes carry that meaning.

LOINC

LOINC (Logical Observation Identifiers Names and Codes) is maintained by the Regenstrief Institute and is free to use. Each LOINC code is defined by six parts: the component (what is measured), the property (such as mass concentration), the timing, the system (specimen type), the scale (quantitative, ordinal, nominal) and, where it matters, the method. Two tests that differ in any of these get different codes.

In the US, LOINC is the expected code for lab results in many EHRs and public health reporting. When an EHR asks for "LOINC-coded results", it wants the OBX observation identifier in HL7 v2, or the Observation code in FHIR, populated with the right LOINC code.

SNOMED CT in the UK

SNOMED CT is a comprehensive clinical terminology, and it is the standard terminology for clinical records across the NHS. For pathology, the NHS uses SNOMED CT content for test requests and results, so a UK lab sending results into NHS systems should expect to code them in SNOMED CT. Private clinic systems in the UK vary; some use SNOMED CT, some LOINC, some their own codes. Ask each receiving system what it expects.

Mapping your tests

  1. List every test on every analyser with its analyser code, specimen type, units and method.
  2. For each receiving system, find what code it expects: LOINC, SNOMED CT or a local code.
  3. Map each test, checking the specimen type, property and units match the code's definition.
  4. Map panels as a set of individual results, each with its own code, plus a panel or order code if the receiver uses one.
  5. Have a second person check the mappings, and keep them under change control.
  6. Test with real messages and confirm the receiving system displays and trends each result correctly.

A worked example: one analyte, several codes

The same analyte can need different LOINC codes, depending on the specimen and the units. A few common examples:

Test as the lab reports itSpecimenUnitsLOINCWhy it differs
GlucoseSerum or plasmamg/dL2345-7Mass concentration
GlucoseSerum or plasmammol/L14749-6Molar concentration
PotassiumSerum or plasmammol/L2823-3Serum or plasma specimen
PotassiumWhole bloodmmol/L6298-4Whole blood specimen, as on many blood gas analysers
CreatinineSerum or plasmamg/dL2160-0Mass concentration
CreatinineSerum or plasmaumol/L14682-9Molar concentration
HbA1cWhole blood%4548-4NGSP percentage
HbA1cWhole bloodmmol/mol59261-8IFCC units

A UK lab reporting glucose in mmol/L that copies a US mapping table would send 2345-7 with mmol/L values, and the receiving system would read 5.4 as 5.4 mg/dL. That is why units and code must be checked together. Treat this table as an illustration of the reasoning: check every code against the current LOINC release and your own method before use.

How codes appear in messages

In HL7 v2, the code goes in OBX-3 as code, text and coding system, for example 3016-3^TSH^LN for TSH coded in LOINC. The same field can carry an alternate code in components four to six, such as the lab's local code: 3016-3^TSH^LN^TSH^Thyroid stimulating hormone^L. In FHIR, Observation.code holds a list of codings, so one result can carry a LOINC coding and a local coding side by side. See our HL7, ASTM and POCT1-A2 sample messages for complete examples.

Mistakes that break interfaces

MistakeWhat happens
Wrong specimen type, such as serum code for whole bloodResults trend against the wrong history
Units that do not match the code's propertyValues look wrong or fail validation
One code used for two methods with different rangesResults are compared that should not be
A panel coded as one resultIndividual values cannot be displayed or trended
Calculated results left uncodedDerived values such as ratios disappear in the receiver
Mapping changed without telling the receiverTrend lines break silently

Coding for UK pathology

For NHS work, test requests and results are coded in SNOMED CT using NHS England's pathology test content, published as the Unified Test List. A private lab sending results into GP systems or NHS records should expect each result to need a SNOMED CT code from that list, alongside units that match it. Private clinic EHRs in the UK vary more: some accept SNOMED CT, some accept LOINC, and some only display the test name. Ask each receiver before you map, and keep one mapping per destination rather than a single code per test.

Who owns which part of the mapping

PartyResponsible for
The labChoosing and approving each code, keeping mappings under change control, telling receivers about changes
The lab software vendorHolding codes per test and per destination, sending them in the right fields, recording changes
The receiving systemStating which code system and units it expects, and displaying and trending coded results correctly
The analyser manufacturerDocumenting the analyser's own test codes, and often suggesting LOINC codes through LIVD files

Keeping mappings right over time

Mappings change when you add a test, change an analyser or method, or change units. Treat every mapping change like any other change to a validated system: record why, check it, test it, and tell the receiving systems. Review mappings when LOINC or SNOMED CT releases updates relevant to your tests. Keep a dated copy of each version of the mapping, so you can show which code any result carried on the day it was sent, and why.

Questions to ask any lab software vendor about coding

  1. Where are LOINC and SNOMED CT codes held, and who can change them?
  2. Can each destination receive a different code system?
  3. What happens to a result that has no code for a destination that requires one?
  4. Are code changes recorded with before and after values?
  5. Can you show the coded message exactly as it was sent?

To see which analysers already have connection guides, use our analyser connection guides or the open connectivity dataset, and see our integrations for record system routes.

Where Catenix fits

Catenix keeps a test library with units, clinic-authored reference ranges and, for each test, a LOINC and a SNOMED CT code where your lab has assigned them. Each analyser's own codes map to tests in that library. Each destination is configured to receive either your local codes or LOINC, so the same result can go with a LOINC code to a US EHR and with a local code, clearly marked as local, to a system that expects one. On a feed agreed as LOINC-coded, a result without a LOINC code is not sent and is listed for someone to fix. Changes to codes are recorded in the audit trail with the before and after values. Analyser not on the list? We build the driver, usually within a couple of days. Catenix is connectivity, workflow and record-keeping software; it does not interpret results and is not marketed as a medical device. See our glossary and POCT message samples.

Questions people ask

Is LOINC required for lab results?

It depends on the receiving system and the reporting route. Many US EHRs and public health systems expect LOINC. In the NHS, SNOMED CT is the standard terminology.

Is LOINC free?

Yes. LOINC is free to use under its licence from the Regenstrief Institute.

Can one result carry both a LOINC and a local code?

Yes. HL7 v2 and FHIR both allow a result to carry more than one code, which helps when receivers expect different code systems.

Who is responsible for the mappings?

The lab. Software holds and applies the mappings, but the lab approves them and keeps them under change control.

Does the same test always have the same LOINC code?

No. The code depends on the specimen, the property measured and sometimes the method. Glucose in mmol/L and in mg/dL, or potassium in serum and in whole blood, have different LOINC codes.

Where do I find the right LOINC code for a test?

Search the LOINC database published by the Regenstrief Institute using the analyte, specimen and units. Many IVD manufacturers also publish LIVD files that suggest LOINC codes for their assays; check them against your own method and units.

Does a private lab in the UK need SNOMED CT codes?

Only for receivers that expect them, which includes NHS systems. Many private clinic EHRs accept local codes or LOINC. Map per destination, and add SNOMED CT when you start sending results into NHS records.

What happens if a result is sent with the wrong code?

The receiver may file it under the wrong test, chart it against the wrong history or reject it. Correct the mapping under change control, resend affected results as corrections where the receiver supports it, and tell the receiver what changed.

Sources and further reading

Take it with you

The buyer's guide, in your inbox.

Nine pages on what POCT connectivity is, the standards in plain English, the cost of doing it by hand and eight questions to ask any supplier.

Get the POCT connectivity buyer's guide

Nine pages, vendor-neutral: what connectivity is, the standards in plain English, the cost of doing it by hand and eight questions to ask any supplier. The PDF also opens directly from the downloads page; leave an email only if you want it in your inbox.

We use your email only to send the guide and, if you ask, to follow up once. No newsletter unless you tick the box. See our privacy notice.

Thank you. The guide is on its way. You can also open it now.
That did not send. Open the guide directly or email contact@catenix.com.

See it done in software.

A 30-minute walkthrough on a live tenant, with your analysers and your allowable-error limits.