This section last updated: 2024-08-06 (4 months ago)
Table of contents:
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.
Type | New terms | Total |
---|---|---|
Laboratory (type 1) | 968 | 62,866 |
Clinical (type 2) | 539 | 27,693 |
Attachments (type 3) | 0 | 1,161 |
Survey (type 4) | 82 | 12,334 |
Total | 1,589 | 104,054 |
Status | Number of terms |
---|---|
Active | 94,432 |
Deprecated | 4,858 |
Discouraged | 1,501 |
Trial | 3,263 |
Old Status | New Status | Number of terms | Type |
---|---|---|---|
Active | Deprecated | 3 | Type 2 |
Active | Deprecated | 2 | Type 4 |
Change type (field name CHNG_TYP) | CHNG_TYP definition | Number of terms |
---|---|---|
NAM | Component update | 863 |
MAJ | Update to one of 5 other primary axes other than Component | 26 |
MIN | Update to a secondary field - see Updates file Readme for the full list | 414 |
DEL | Status changed to Deprecated | 5 |
UND | Status changed from Deprecated to Active | 0 |
PANEL | Change in the child elements or conditionality of one or more child elements in the panel or a sub-panel contained in the panel | 108 |
Total | 1,416 |
No changes were made as part of version 2.78.
See Appendix A in the LOINC Users' Guide for the current LOINC table structure.
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.
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 LOINC version 2.77 and version 2.78, such as from TRIAL to ACTIVE. It does not contain terms that were newly added in 2.78. In the future, this file will likely contain other types of term changes in addition to Status changes.
The PartChangeSnapshot file contains all of the Parts that had a change in Status between LOINC version 2.77 and version 2.78, 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.
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.
See the ReadMe included in the Document Ontology folder for information about its current file structure.
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.
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. If you are using this file and have feedback (good or bad), please contact us.
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.
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.
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.77 is translated for inclusion in the 2.78 release). The de_DE German (GERMANY) linguistic variant for 2.78 does contain translations for new terms introduced in version 2.78.
Updated content for the LOINC 2.78 release has been provided by the translation for the following linguistic variants:
Language | Name |
---|---|
de_AT | German (AUSTRIA) |
fr_CA | French (CANADA) |
fr_FR | French (FRANCE) |
de_DE | German (GERMANY) |
it_IT | Italian (ITALY) |
nl_NL | Dutch (NETHERLANDS) |
es_ES | Spanish (SPAIN) |
The table below shows the LOINC version when each linguistic variant included in this release was last updated.
Linguistic variant | Version last updated |
---|---|
Chinese (CHINA) | 2.77 |
Dutch (NETHERLANDS) | 2.78 |
Estonian (ESTONIA) | 2.23 |
French (BELGIUM) | 2.47 |
French (CANADA) | 2.78 |
French (FRANCE) | 2.78 |
German (AUSTRIA) | 2.78 |
German (GERMANY) | 2.78 |
Greek (GREECE) | 2.34 |
Italian (ITALY) | 2.78 |
Korean (KOREA, REPUBLIC OF) | 2.27 |
Polish (POLAND) | 2.75 |
Portuguese (BRAZIL) | 2.51 |
Russian (RUSSIAN FEDERATION) | 2.65 |
Spanish (ARGENTINA) | 2.15 |
Spanish (SPAIN) | 2.78 |
Spanish (MEXICO) | 2.72 |
Turkish (TURKEY) | 2.56 |
Ukrainian (UKRAINE) | 2.75 |
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.
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.
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.4 of that terminology and Radiology Part mappings are based on RadLex version 4.1 and pre-release 4.2.
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.
Known issues:
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).
A few outstanding cases for LOINC Radiology Parts without mappings to RadLex RIDs exists. We plan to review these with RSNA and add mappings, as appropriate, in a future release.
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/RSNA 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.
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.
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.
There have been no changes other than the addition of new content since the last release.
See the ReadMe included in the Panels and Forms folder for information about its current file structure.
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.
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.
There have been no changes to this file other than the addition of new content since the last release.
The Updates.mdb file will be removed in a subsequent release. It covers more fields than the Updates.csv file. This additional granularity will be replaced in a corresponding CSV file.
For RELMA versions 7.9 and older, the online search, powered by Apache SOLR service, will be retired on Dec. 31, 2024. Users are strongly encouraged to:
More information and instructions on making that change are available in the LOINC Knowledge Base.