LOINC is a universal standard for identifying medical laboratory observations, clinical measurements, and documents. Developed by the Regenstrief Institute, it provides a universal code system that assigns unique, unambiguous identifiers to test results and clinical observations, enabling semantically interoperable data exchange between disparate health information systems.
Glossary
LOINC

What is LOINC?
Logical Observation Identifiers Names and Codes (LOINC) is a universal code system for identifying health measurements, observations, and documents to facilitate the exchange and pooling of clinical data.
A fully specified LOINC term consists of six major axes: Component, Property, Time, System, Scale, and Method. This structured nomenclature allows a serum glucose test performed in a lab to be distinguished from a urine glucose test performed at the point of care, ensuring that clinical data retains its precise meaning regardless of the originating system.
Key Features of LOINC
LOINC provides a universal code system for identifying health measurements, observations, and documents, enabling semantic interoperability across disparate health IT systems.
Six-Part Fully-Specified Name
Every LOINC term is defined by a unique formal name with six distinct axes, ensuring unambiguous identification:
- Component: The analyte or entity being measured (e.g., Glucose)
- Property: The characteristic measured (e.g., Mass Concentration)
- Time: The temporal aspect of the measurement (e.g., Point in time)
- System: The specimen or context (e.g., Serum/Plasma)
- Scale: The type of result (e.g., Quantitative)
- Method: The procedure used, if relevant (e.g., Test strip)
This structure allows for precise differentiation between tests like Glucose^Mass Concentration^Pt^Ser/Plas^Qn and Glucose^MCnc^Pt^Urine^Qn.
Laboratory and Clinical Domains
LOINC covers a broad spectrum of health measurements beyond just lab tests:
- Laboratory: Chemistry, hematology, microbiology, serology, toxicology, and molecular pathology
- Clinical: Vital signs, hemodynamics, intake/output, EKG measurements, obstetric ultrasound
- Survey Instruments: Standardized patient-reported outcomes like PHQ-9 depression screen and pain scales
- Documents: Titles for clinical notes, discharge summaries, and radiology reports
This breadth makes LOINC the universal standard for encoding any observable health data point.
Common Test Hierarchy
LOINC organizes laboratory tests into a hierarchical structure based on the Component axis, enabling roll-up reporting and panel grouping:
- Class 1: Chemistry (e.g., electrolytes, enzymes, hormones)
- Class 2: Hematology (e.g., CBC, coagulation)
- Class 3: Serology (e.g., antibody titers)
- Class 4: Microbiology (e.g., culture results, organism identification)
Each class contains parent-child relationships that allow systems to query for all sodium-related tests or aggregate results under a single category for population health analytics.
LOINC Panels and Forms
LOINC defines panels as ordered collections of individual terms that represent a complete test battery or clinical form:
- A Basic Metabolic Panel (LOINC 24323-8) groups eight specific chemistry tests
- A Complete Blood Count (LOINC 58410-2) bundles hematology parameters
- Survey forms like the PHQ-9 (LOINC 44249-1) link the form header to its individual question-and-answer terms
Panel structures preserve the clinical intent of ordering a grouped test and enable accurate billing and result interpretation.
LOINC Parts Database
The LOINC Parts file is a foundational reference table that decomposes every term into its atomic building blocks:
- Each part has a unique identifier (e.g., LP14635-4 for 'Glucose')
- Parts are linked to their parent terms and can be reused across thousands of LOINC codes
- The Parts hierarchy enables concept normalization by mapping local test names to standard components
This granular decomposition allows terminology servers to perform semantic matching and identify equivalent tests even when local naming conventions differ significantly.
LOINC vs. Other Medical Terminologies
A comparative analysis of LOINC against other major clinical code systems, highlighting their primary domains, structural characteristics, and use cases in healthcare interoperability.
| Feature | LOINC | SNOMED CT | ICD-10-CM | RxNorm |
|---|---|---|---|---|
Primary Domain | Laboratory tests, clinical observations, documents | Clinical findings, procedures, body structures | Diagnoses and reasons for encounters | Clinical drugs and medication ingredients |
Code Structure | 6-part fully specified name with hierarchical axes | Concept ID with defining relationships and descriptions | 3-7 character alphanumeric category codes | Normalized form with ingredient, strength, and dose form |
Granularity Level | Highly specific to individual test methods and panels | Comprehensive from broad body structures to specific findings | Moderate specificity for disease classification | Precise to branded and generic drug products |
Primary Use Case | Lab order and result identification, clinical document types | Electronic health record clinical documentation | Billing, epidemiology, and mortality statistics | Medication reconciliation and e-prescribing |
Maintained By | Regenstrief Institute | SNOMED International | CDC and CMS | U.S. National Library of Medicine |
Hierarchical Organization | Multi-axial hierarchy (component, property, timing, system, scale, method) | Polyhierarchical subtype (is-a) relationships | Monohierarchical chapter-based structure | Graph-based with ingredient, brand, and dose form relationships |
Post-Coordination Support | ||||
Total Concepts | ~95,000+ | ~350,000+ | ~72,000+ | ~250,000+ |
Interoperability Standard | HL7 v2, FHIR Observation, FHIR DocumentReference | FHIR Condition, Procedure, and BodyStructure | HL7 v2, FHIR Condition, FHIR Claim | FHIR Medication and MedicationRequest |
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, its structure, and its role in clinical data interoperability.
LOINC (Logical Observation Identifiers Names and Codes) is a universal code system for identifying health measurements, observations, and documents. It provides a unique, unambiguous identifier for each distinct clinical observation, enabling the semantic exchange of laboratory results, vital signs, and clinical documents between disparate health information systems. LOINC works by assigning a permanent, unique code to a fully specified clinical concept, defined by a formal six-axis model. This model differentiates observations based on the Component (what is measured), Property (the characteristic, like mass concentration), Time (point or interval), System (the specimen or organ), Scale (quantitative, ordinal, nominal), and Method (the procedure used). For example, the LOINC code 2951-2 specifically identifies a 'Sodium: SCnc: Pt: Ser/Plas: Qn' measurement, ensuring that a sodium level reported from one laboratory system is semantically identical to one from another.
Related Terms
Essential concepts for understanding how LOINC integrates with other medical terminologies and clinical data workflows.

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