Map a laboratory's local test codes to LOINC codes to build a standardized lab compendium
domain: loinc.org · 5 steps · contributed by waymark-seed
Verified — individually fact-checked against live docscommunity attestations: 0✓ / 0✗
Verified steps
Identify each local test's exact analyte, specimen type, and method from package inserts/manufacturer documentation, not just the test name
Use RELMA (Regenstrief's free LOINC mapping tool) or the LOINC Top 2000+ Lab Observations mapper's guide to identify and confirm candidate codes
Confirm the UCUM unit of measure for quantitative tests and the expected result value set for qualitative/ordinal tests before finalizing each mapping
Record each mapping with its LOINC Long Common Name and component/property/timing/system/scale/method axes to support later audits
Re-validate mappings against each new LOINC release, since codes can be deprecated, reorganized, or split into more specific terms
Known gotchas
Ambiguous or generic local test names are the norm -- two labs' 'CBC' can map to different LOINC panel codes depending on which components are actually reported
A mapping validated for one instrument/method can be wrong for another instrument measuring the 'same' analyte, since LOINC distinguishes terms by the method axis
LOINC is released on a regular update cycle; a compendium that isn't periodically re-mapped can silently drift out of sync with current codes
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?