Logical Observation Identifiers Names and Codes (LOINC) is a universal code system that assigns unique, unambiguous identifiers to medical laboratory observations, clinical measurements, and documents. Developed by the Regenstrief Institute, it standardizes the naming of tests like 'serum sodium' or 'blood pressure' so that a result from one electronic health record (EHR) system is semantically identical to the same result from another, enabling cross-system data exchange.
Glossary
LOINC

What is LOINC?
LOINC is the universal standard for identifying health measurements, observations, and documents to enable semantic interoperability.
LOINC codes consist of six major axes—component, property, time, system, scale, and method—that fully define a clinical observation. By mapping local test codes to LOINC, healthcare organizations achieve semantic interoperability, allowing disparate systems to aggregate lab results for public health reporting, clinical research, and clinical decision support without manual translation or loss of meaning.
Key Features of LOINC
LOINC provides a universal standard for identifying medical laboratory observations, clinical measurements, and documents. Its structured six-axis model ensures unambiguous semantic interoperability across disparate healthcare systems.
Six-Axis Semantic Model
Every LOINC code is defined by six distinct axes that uniquely characterize a clinical observation, eliminating ambiguity in data exchange.
- Component: The substance or entity being measured (e.g., Glucose, Leukocytes).
- Property: The characteristic being quantified (e.g., Mass Concentration, Presence).
- Time: The temporal aspect of the measurement (e.g., Point in time, 24-hour collection).
- System: The biological context or sample type (e.g., Serum, Urine, Patient).
- Scale: The data type of the result (e.g., Quantitative, Ordinal, Nominal).
- Method: The procedure used to obtain the observation, if relevant (e.g., Test Strip, Agglutination).
Interoperability Backbone
LOINC serves as the foundational terminology for exchanging clinical observations between Electronic Health Records (EHRs), laboratories, and public health agencies. It maps local proprietary test codes to a universal standard, enabling semantically accurate data aggregation for clinical research, quality reporting, and health information exchanges. Without LOINC, a 'serum glucose' test from Lab A is computationally unrecognizable as the same test from Lab B.
Clinical Document Codes
Beyond lab tests, LOINC includes a robust hierarchy for standardizing document types. This enables consistent indexing and retrieval of clinical notes across systems.
- Document Ontology: Codes for specific clinical documents like Discharge Summaries, Radiology Reports, and History & Physical Notes.
- Document Sections: Standardized codes for sections within a document, such as 'Chief Complaint' or 'Review of Systems', facilitating structured data extraction from narrative text.
Regulatory Mandates & Adoption
LOINC is a required standard in numerous national and international health IT frameworks, driving its near-universal adoption.
- US Core Data for Interoperability (USCDI): LOINC is a mandatory vocabulary for laboratory tests and clinical notes.
- Meaningful Use / Promoting Interoperability: Certified EHR technology must be capable of recording and exchanging clinical observations using LOINC.
- Global Reach: Adopted as a national standard in over 190 countries, translated into multiple languages, and maintained by the Regenstrief Institute.
LOINC Parts & Hierarchy
The LOINC system is built from a granular set of LOINC Parts, which are the atomic building blocks for each term. These parts are organized into a multi-axial hierarchy, allowing for powerful semantic grouping and querying. For example, all tests with the Component part 'Glucose' can be aggregated regardless of the specimen or method. This structure is critical for building clinical decision support rules and analytics dashboards that operate on standardized, roll-up categories.
Relational Mapping to Other Standards
LOINC does not operate in isolation. It is designed to work in concert with other core medical ontologies to create a complete semantic picture.
- SNOMED CT: LOINC identifies the question (the observation), while SNOMED CT often identifies the answer (the finding or organism).
- UCUM: LOINC codes reference Unified Code for Units of Measure to standardize quantitative result units (e.g., mg/dL).
- HL7 FHIR: LOINC is the primary code system used in the
Observation.codeelement of FHIR resources, cementing its role in modern API-based interoperability.
LOINC vs. Other Clinical Terminologies
A structural comparison of LOINC with other major clinical code systems, highlighting their primary domains, granularity, and use cases.
| Feature | LOINC | SNOMED CT | ICD-10-CM | RxNorm |
|---|---|---|---|---|
Primary Domain | Laboratory & Clinical Observations | Clinical Findings & Procedures | Diagnoses & Inpatient Procedures | Medications |
Primary Purpose | Test Ordering & Results Interchange | Clinical Documentation in EHRs | Billing, Epidemiology, & Statistics | Drug Interoperability & e-Prescribing |
Code Structure | 6-part fully specified name | Concept ID + Description + Relationships | 3-7 character alphanumeric codes | Normalized drug name + semantic identifiers |
Granularity | High (e.g., specific method, specimen) | High (e.g., laterality, severity) | Variable (e.g., combination codes) | High (e.g., dose form, strength) |
Semantic Relationships | ||||
Ontology Type | Pre-coordinated nomenclature | Post-coordinated ontology | Monohierarchical classification | Normalized nomenclature |
Maintenance Organization | Regenstrief Institute | SNOMED International | WHO / CMS / NCHS | U.S. National Library of Medicine |
Interoperability Standard | HL7 v2, CDA, FHIR | FHIR, CDA | X12 837, FHIR | FHIR, NCPDP SCRIPT |
Enabling Efficiency, Speed & Accuracy
Intelligent Analysis, Decision & Execution
We build AI systems for teams that need search across company data, workflow automation across tools, or AI features inside products and internal software.
Talk to Us
Search across company data
Give teams answers from docs, tickets, runbooks, and product data with sources and permissions.
Useful when people spend too long searching or get different answers from different systems.

Automate internal workflows
Use AI to route work, draft outputs, trigger actions, and keep approvals and logs in place.
Useful when repetitive work moves across multiple tools and teams.

Add AI to products and internal tools
Build assistants, guided actions, or decision support into the software your team or customers already use.
Useful when AI needs to be part of the product, not a separate tool.
Frequently Asked Questions
Clear, technical answers to the most common questions about the Logical Observation Identifiers Names and Codes (LOINC) standard and its role in clinical data interoperability.
LOINC (Logical Observation Identifiers Names and Codes) is a universal code system for identifying medical laboratory observations, clinical measurements, and documents. It works by assigning a unique, permanent identifier to each distinct clinical observation—such as a specific lab test, vital sign measurement, or survey instrument—based on a formal, six-axis model. This model defines the component (what is measured), property (the characteristic, like mass concentration), time (point or interval), system (the specimen or context), scale (quantitative, ordinal, nominal), and method (the procedure). By standardizing these atomic attributes, LOINC enables semantically interoperable exchange of results between disparate healthcare systems, ensuring that a 'serum sodium' test from one lab is computationally identical to the same test from another.
Related Terms
LOINC is a cornerstone of clinical data liquidity. These related standards and technologies form the essential ecosystem for encoding, mapping, and exchanging laboratory and clinical observations across disparate health IT systems.

About the author
Prasad Kumkar
CEO & MD, Inference Systems
Prasad Kumkar is the CEO & MD of Inference Systems and writes about AI systems architecture, LLM infrastructure, model serving, evaluation, and production deployment. Over 5+ years, he has worked across computer vision models, L5 autonomous vehicle systems, and LLM research, with a focus on taking complex AI ideas into real-world engineering systems.
His work and writing cover AI systems, large language models, AI agents, multimodal systems, autonomous systems, inference optimization, RAG, evaluation, and production AI engineering.
Partnered with leading AI, data, and software stack.
How We Work
Custom AI workflows for your Business
One-fit-all AI don't work for modern businesses. At Inferensys, we aim to understand your business & custom requirements; which we use to define most efficient agentic workflows, the data, and the tools for your business.
01
Review the use case
We understand the task, the users, and where AI can actually help.
Read more02
Pick the right approach
We define what needs search, automation, or product integration.
Read more03
Build the first useful version
We implement the part that proves the value first.
Read more04
Improve from there
We add the checks and visibility needed to keep it useful.
Read moreThe first call is a practical review of your use case and the right next step.
Talk to Us