Version 2.82, February 2026

LOINC table core

There were no structural changes to the core table in this release, and no future changes to announce at this time. See the Readme included in the LOINC Table Core download file for information about its current file structure.

See the LOINC table notes below for information on content updates included in this release.

LOINC table

New Concepts and totals by type

TypeNew conceptsTotal
Laboratory (type 1)36466861
Clinical (type 2)58128635
Attachments (type 3)01161
Survey (type 4)13212668
Total1077109325

Totals by Status

StatusNumber of concepts
Active97314
Deprecated4991
Discouraged1583
Trial5437

Concept Status changes

Old StatusNew StatusNumber of conceptsType
ActiveDeprecated19Type 1
ActiveDeprecated1Type 2
ActiveDeprecated11Type 4
DeprecatedActive1Type 1
DiscouragedActive3Type 1
DiscouragedActive1Type 4
DiscouragedDeprecated2Type 1
DiscouragedDeprecated1Type 2
TrialActive3Type 2
TrialActive19Type 4
TrialDeprecated1Type 2

Edits by change type

Change type (field name CHNG_TYP)CHNG_TYP definitionNumber of concepts
NAMComponent update690
MAJUpdate to one of 5 other primary axes other than Component43
MINUpdate to a secondary field – see Updates file Readme for the full list651
DELStatus changed to Deprecated35
UNDStatus changed from Deprecated to Active1
PANELChange in the child elements or conditionality of one or more child elements in the panel or a sub-panel contained in the panel36
Total1456

Content highlights

A summary of changes and additions to LOINC concepts is no longer included within these release notes. Instead, please refer to the LOINC version 2.82 release announcement for this information. Notable terminology and technical changes specific to individual release artifacts and accessory files follow below.

Changes to the LOINC Table structure in this release

No changes were made as part of version 2.82.

See Appendix A in the LOINC Users’ Guide for the current LOINC table structure.

Answer Lists

See the ReadMe included in the Answer File folder for information about its current file structure.

This release contains all of the answer lists associated with any LOINC term published in the current release. There have been no changes other than the addition of new content since the last release.

Change Snapshot

See the ReadMe included in the Change Snapshot folder for information about its current file structure.

The LoincChangeSnapshot file contains all terms that had a change in Status between the previous and current LOINC versions, such as from TRIAL to ACTIVE. It does not contain terms that were newly added in this version. In addition to Status changes, the LoincChangeSnapshot file now includes changes to all fields in the Loinc.csv.

The PartChangeSnapshot file contains all of the Parts that had a change in Status between the previous and current LOINC versions, such as from ACTIVE to DEPRECATED or ACTIVE to INACTIVE (see ReadMe for Status definitions). In the future, this file may contain other types of Part changes in addition to Status changes.

There is a known issue where the VersionEffective field in the LoincChangeSnapshot file may show a prior version of LOINC. This field is derived from the VersionLastChanged field in the Loinc.csv file; however, certain types of changes do not trigger updates to it. The current discrepancies are related to changes in letter casing in the Component field and updates to the AnswerListId assigned to a LOINC. These issues will be addressed in a future LOINC release.

Consumer Names (Alpha)

See the ReadMe included in the Consumer Name folder for information about its current file structure.

This release of the Consumer names file remains at Alpha pre-production status. It contains Consumer names for all Type 1 (Laboratory) and a subset of Type 2 (Clinical) terms in LOINC. The Consumer Names are created algorithmically based on the set of primary rules documented in the associated ReadMe notes.

Consumer Names are intended for downstream display only and are not intended to be used at any point in the clinical workflow, or for the purpose of mapping local terms to LOINC. Their use case includes consumer-facing health and wellness applications that use LOINC to encode the underlying data.

We welcome user feedback about these names.

Document Ontology

See the ReadMe included in the Document Ontology folder for information about its current file structure.

Document Ontology OWL (Alpha)

See the ReadMe included in the Document Ontology OWL folder for information about its current file structure.

The Document Ontology OWL file, first released with LOINC version 2.74, includes all the changes and additions to LOINC documents and document ontology values in a format that allows navigation of document axis hierarchies and exchange as a formal ontology. It continues at Alpha status, meaning that it is part of a testing process, and the LOINC team continues to welcome comments regarding its usability and content.

Groups (Beta)

See the ReadMe included in the Group File folder for information about its current file structure.

This release of the Group File remains at Beta pre-production status. We received no significant public comments about its contents, structure, or utility that we would have used as the basis for incrementing its maturity level or conceptualization.

The LOINC Groups project is a work in progress. The contents of this file may change from release to release as we receive feedback from users and refine our processes.

The contents of the file and the groupings MUST be validated by the user prior to implementation in any aspect of clinical care. We have created Groups that may be useful in specific contexts, but these Groups have not been vetted for use in either patient care or research and should be used with caution.

Imaging Document Codes

See the ReadMe included in the Imaging Document folder for information about its current file structure and query used to generate the set of LOINC codes.‌

There have been no changes other than the addition of new content since the last release.

Linguistic Variants

See the ReadMe included in the Linguistic Variants folder for information about its current file structure.

Updated linguistic variants are generally based on the previous release version (i.e., LOINC version 2.81 is translated for inclusion in the 2.82 release). The de_DE German (GERMANY) linguistic variant for 2.82 does contain translations for new terms introduced in version 2.82.

Updated content for the LOINC 2.82 release has been provided by the translation for the following linguistic variants:

LanguageName
ar_JOArabic (JORDAN)
cs_CZCzech (CZECHIA)
de_DEGerman (GERMANY)
es_ESSpanish (SPAIN)
fr_CAFrench (CANADA)
it_ITItalian (ITALY)
nl_NLDutch (NETHERLANDS)
zh_CNChinese (CHINA)

The table below shows the LOINC version when each linguistic variant included in this release was last updated.

Linguistic variantVersion last updated
Chinese (CHINA)2.82
Dutch (NETHERLANDS)2.82
Estonian (ESTONIA)2.23
French (BELGIUM)2.47
French (CANADA)2.82
French (FRANCE)2.79
German (AUSTRIA)2.81
German (GERMANY)2.82
Greek (GREECE)2.81
Italian (ITALY)2.82
Korean (KOREA, REPUBLIC OF)2.27
Polish (POLAND)2.81
Portuguese (BRAZIL)2.51
Russian (RUSSIAN FEDERATION)2.65
Spanish (ARGENTINA)2.15
Spanish (SPAIN)2.82
Spanish (MEXICO)2.72
Turkish (TURKEY)2.56
Ukrainian (UKRAINE)2.79
Arabic (JORDAN)2.82
Czech (CZECHIA)2.82

Please note that some term translations are based on the translation of Parts. For such translations, even if no additional Part translations were provided by the producer, the number of translated terms may vary from release to release because new LOINC terms using previously translated Parts will also be included, and old LOINC terms that have been updated to use untranslated Parts will be excluded.

LOINC IEEE Medical Device Code Mapping Table

See the ReadMe included in the LOINC IEEE Medical Device Code Mapping Table folder for information about its current file structure.

There have been no changes to the structure or contents of this file since the LOINC 2.67 release in December 2019.

LOINC RSNA Radiology Playbook

See the ReadMe included in the LOINC RSNA Radiology Playbook folder for information about its current file structure.

There have been no changes other than the addition of new content since the last release.

The mappings to and content from the RSNA Playbook are based on version 2.5 of that terminology and Radiology Part mappings are based on RadLex version 4.3.

We are still seeking feedback on the usefulness of the PartSequenceOrder field from anybody who is utilizing this file to help inform our future efforts, e.g., whether we should remove this field.

There is a known parsing issue for terms with multiple Aggregation or View type values in which one or more values is not being assigned the correct PartSequenceOrder value. We plan to address the parsing procedure in a future release if necessary, depending on whether users find this field useful (see request for feedback above).

Terms with XXX (meaning Unspecified) as the Region Imaged without an Imaging focus do not have an Anatomy attribute (Region imaged or Imaging focus) represented in the file. The LOINC Radiology Committee is reviewing the representation of XXX without a specified imaging focus in the LOINC/RSNA model to determine how the Anatomy should be represented.

LOINC Universal Lab Orders Value Set

See the ReadMe included in the LOINC Universal Lab Orders Value Set folder for information about its current file structure.

There have been no changes to this file since the last release.

Component Hierarchy By System

The Component Hierarchy By System (formerly known as Multiaxial Hierarchy) file provides a way to organize LOINC codes based on multiple axes of each concept. See the ReadMe included in the Component Hierarchy By System folder for information about its current file structure.

For version 2.82, siblings within branches that shared the same CODE value were cleaned up to resolve duplicate and inconsistent entries. This resulted in some structural changes to the hierarchy. Please review implementations for any potential impacts.

Panels and Forms

See the ReadMe included in the Panels and Forms folder for information about its current file structure.

Parts

See the ReadMe included in the Part File folder for information about its current file structure.

This file contains all of the parts associated with any LOINC term published in the current release. Note that it does not contain Parts that are used to organize terms in the Component Hierarchy By System.

There have been no changes to this file other than the addition of new content since the last release.

The LoincPartLink_Supplementary.csv file exceeds the row capacity of Excel and LibreOffice.

Updates

See the ReadMe included in the Updates folder for information about its current file structure. As a reminder, the CHANGE_REASON_PUBLIC and STATUS_TEXT fields are no longer to be considered when determining if a LOINC term has been updated because they contain information for users about term edits but are not directly related to the attributes of a term.

With this release, the Updates.mdb file has been removed. We have replaced the LOINC_UPDATES table, that was part of the Updates.mdb file, with the UpdatesAdditionalFields.csv file. The LOINC_UPDATES_BASIC_FIELDS_ONLY table of Updates.mdb is the same as Updates.csv, as it was in prior LOINC releases.

RELMA Changes

The RELMA program for Windows remains in a maintenance mode. No significant changes have been made; however, the linguistic variant for Greek (GREECE) has been restored as an option for search.

All RELMA users are encouraged to install version 7.15 in order to gain access to all the new and updated terms available in LOINC version 2.82.