Every LOINC code carries several names. The long common name is a human-friendly description. The short name is a compact identifier. The formal name is a structured composition of parts. And the display name might be either of the above depending on how the terminology tool renders it. Choosing the right name to search against is what separates a clean LOINC lookup from a frustrating one.
Naming the names is the discipline. For related walkthroughs, more on terminology in FHIR collects the surrounding material.
The Long Common Name
The long common name is the description clinicians recognize. "Hemoglobin [Mass/volume] in Blood" reads like a sentence and covers what the code actually measures. It is the right target for a clinician-driven search.
The catch is that long common names can share phrases across many codes. Searching "hemoglobin" against long common names returns dozens of candidates. Additional clarifiers narrow the field. A pass through the site's LOINC picker uses the long common name as the primary display but pre-filters by common vitals and labs.
The Short Name
The short name is a compact identifier like "Hgb Bld-mCnc". It appears on lab reports, in EHR displays, and in bandwidth-constrained UIs. Recognizable to lab staff, cryptic to everyone else.
Searching against short names is the right choice when the requester came in with a term from a lab report. Otherwise the short name is a display convenience rather than a search target.
The Formal Name (LOINC Parts)
The formal name is the structured composition: Component:Property:Time:System:Scale:Method. For hemoglobin: Hemoglobin:MCnc:Pt:Bld:Qn. It carries the full semantics of the code in one string.
Searching against the formal name requires knowing the parts. It rewards experienced terminology teams and confuses everyone else. For the parts model, the LOINC parts model: property, system, and method at a glance covers the axes.
The Display Name Trap
Different tools display LOINC codes differently. Some show the long common name; some show the short name; some show a truncated composite. Searchers who copy a display name from one tool and paste it into another sometimes get no results because the display name did not match the target index.
Every LOINC integration should choose which name it uses for display and search consistently. Mixed choices produce inconsistent results.
The Right Name for the Right Job
Three quick rules:
- Clinician conversations: long common name.
- Lab report inputs: short name.
- Terminology-team internal work: formal name.
The wider search strategy that this feeds into is covered in starting a LOINC search when the requester speaks clinical, not codes.
Alternative Names Are a Safety Net
LOINC also carries related names and previous versions. When a search misses on the primary name, checking the alternative names sometimes surfaces the match. Not every terminology tool exposes the alternatives; those that do save real time.
Hierarchy as a Fallback
When no direct name search matches, the LOINC hierarchy can broaden the query. Parent codes represent broader concepts; walking up the hierarchy from a candidate can reveal the intended concept. For the hierarchy pattern, using LOINC hierarchies to broaden a match without losing precision covers the method.
Picking the right name to search against is a small decision that saves significant time over the life of a terminology program.
Sources
- LOINC canonical users-guide page defining long common name - LOINC canonical users-guide page defining long common name, short name, and display name
