LOINC lookups start fast on a small value set and slow down as the set grows. The slowdown is not usually the LOINC vocabulary itself; it is how the deployment's terminology server indexes and caches the codes. Getting the caching right... Read More

LOINC and SNOMED CT overlap on some observations and diverge on others. Deciding which vocabulary owns a specific observation is the small choice that shapes downstream terminology consistency for the life of the deployment. The choice is... Read More

Not every clinical measurement has a LOINC code yet. New biomarkers, novel methods, rare tests, and highly-local protocols show up in real workflows and produce local codes without a LOINC equivalent. The disciplined response is to submit... Read More

LOINC organizes its codes into hierarchies where broader concepts sit above narrower ones. The hierarchy is what saves a search that started too specific from returning zero results. Walking up the hierarchy releases specificity along one... Read More

Every LOINC code is a composition of six axes, and knowing the axes at a glance is the shortcut from "I searched for hemoglobin and got twenty results" to "here is the right code and here is why." The axes are stable, small, and worth... Read More

LOINC uses three broad categories that beginners often blur together: lab tests, panels, and observations. The distinctions are small in the vocabulary and large in the terminology tool. Getting them right the first time saves the "why... Read More

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... Read More

A clinician says "get me the LOINC for hemoglobin." A developer sits at the terminology tool and stares. LOINC has three dozen entries that match that request depending on specimen, panel, and unit, and the clinician does not want to have... Read More