LOINC codes are a universal system for identifying health measurements, observations, and documents so that different healthcare systems can understand each other’s data. Short for Logical Observation Identifiers Names and Codes, the LOINC database contains over 109,000 terms and serves as the shared language that lets hospitals, labs, public health agencies, and researchers exchange clinical information without confusion.
How LOINC Codes Work
Think of a lab test as a question and the result as an answer. A LOINC code represents the question: “What is this patient’s blood glucose level?” or “Were bacteria found in this blood culture?” The actual result (the answer) gets recorded using other coding systems like SNOMED CT. This separation keeps things clean. Every lab, clinic, and hospital asks the same “questions” using the same codes, even if they use completely different software behind the scenes.
Each LOINC code is built from up to six components that precisely define what’s being measured:
- Component: what substance or property is being tested (glucose, potassium, hemoglobin)
- Property: the type of measurement (concentration, mass, volume)
- Time: whether it’s a single snapshot or measured over a time interval
- System: the sample type (blood serum, urine, cerebrospinal fluid)
- Scale: whether the result is a number, a category, or a yes/no answer
- Method: included only when the testing technique changes the clinical meaning of the result
These six parts are separated by colons in the code’s formal name. So a single LOINC code doesn’t just say “glucose test.” It specifies glucose, measured as a mass concentration, at a single point in time, in blood serum, on a quantitative scale. That level of precision is what makes the system reliable across organizations.
Why Healthcare Systems Need a Common Language
Without standardized codes, the same lab test can have dozens of different names. One hospital might call a test “Blood Culture, Aerobic,” while another logs it as “BC-Aero” and a third uses a proprietary vendor code. When those three systems need to share data, nothing lines up. Aggregating patient records across facilities, tracking disease trends, or comparing outcomes between hospitals becomes nearly impossible.
LOINC solves this by assigning one universal identifier to each distinct observation. A blood culture test coded as LOINC 600-7 means “Bacteria identified in Blood by Culture” regardless of which lab performed it, which software generated the report, or which country the hospital is in. The original purpose of the system, developed by the Regenstrief Institute, was specifically to allow tests done at different laboratories to be aggregated independent of local naming practices.
Where LOINC Codes Are Required
In the United States, LOINC isn’t optional for many healthcare IT systems. The Office of the National Coordinator for Health IT (ONC) requires certified electronic health record systems to use LOINC codes when transmitting reportable laboratory results to public health agencies. Federal regulation specifically mandates LOINC Database Version 2.72 or newer for this purpose, with compliance required by December 31, 2025. Systems can also certify using more recent versions; the latest release is Version 2.82, published in February 2026.
This regulatory backing means that if you interact with the US healthcare system, your lab results are almost certainly being tagged with LOINC codes behind the scenes, even if you never see them on your printed report.
Public Health Surveillance
Public health agencies rely heavily on LOINC to track infectious diseases and other reportable conditions. When a lab identifies a case of tuberculosis, measles, or any nationally notifiable disease, that result needs to reach state and federal agencies quickly and accurately. The CDC publishes the Reportable Condition Mapping Table, which pairs specific LOINC and SNOMED CT codes with reportable conditions so labs know exactly how to tag their results.
The CDC also maintains files that map manufacturer-specific diagnostic test codes directly to the correct LOINC codes. This automation matters because manual mapping is error-prone. When a lab technician has to manually choose the right code from a list of thousands, mistakes happen. Automated mapping significantly reduces the risk of incorrectly tagged results and speeds up the reporting pipeline. During outbreaks, that speed can shape how quickly public health agencies detect and respond to emerging threats.
Enabling Data Exchange Through FHIR and HL7
LOINC codes plug directly into the major data exchange frameworks that healthcare systems use to communicate. In HL7 messaging (the most common standard for sharing clinical data between systems), LOINC codes identify the test being reported, while SNOMED CT codes capture the result. In FHIR, the newer web-based standard that’s rapidly replacing older formats, LOINC codes are embedded in observation resources so that any system reading the data knows exactly what was measured.
For example, a FHIR observation for a blood culture would include the LOINC code 600-7 alongside a human-readable description. Any receiving system, whether it’s a specialist’s office, a pharmacy, or an insurance platform, can parse that code and understand the test without needing to know anything about the originating lab’s internal naming conventions.
How LOINC Differs From Other Medical Codes
Healthcare uses several coding systems, and they serve different purposes. LOINC identifies tests and observations. ICD codes (like ICD-10) classify diagnoses. CPT codes handle billing. These systems work alongside each other rather than competing.
The most common point of confusion is between LOINC and SNOMED CT, since both appear in lab reports. The distinction is straightforward: LOINC codes the question, SNOMED codes the answer. A LOINC code says “We tested for bacteria in the blood.” A SNOMED code says “We found Staphylococcus aureus.” In practice, LOINC codes are also used for ordering tests, while CPT codes for the same tests are used for billing purposes. A single lab test might carry a LOINC code for clinical communication and a CPT code for the insurance claim, each serving its own function in the workflow.
Beyond the Lab
While LOINC started with laboratory tests, the database has expanded well beyond chemistry panels and blood cultures. It now includes codes for clinical observations like vital signs, patient assessments, survey instruments, and clinical documents. A nursing assessment, a patient-reported pain score, or a discharge summary can all be tagged with LOINC codes, making them findable and comparable across systems.
For clinical researchers, this standardization is especially valuable. When studying outcomes across multiple hospitals, researchers need to be confident that “fasting blood glucose” means the same thing in every dataset they’re merging. LOINC makes large-scale data aggregation feasible by ensuring that observations collected at different sites, by different instruments, in different software systems all carry the same identifier. Without it, a significant portion of multi-site research would require tedious manual reconciliation of local lab catalogs before any analysis could begin.