mapping-loinc
Maps laboratory and clinical observation names extracted by OpenMed to LOINC codes using the public Regenstrief LOINC and FHIR terminology APIs. Use when the user wants to code lab tests, vital signs, or observations to LOINC, resolve a test name plus specimen and method to the correct LOINC part-model code, attach UCUM units, or build a US Core Laboratory Result Observation. Trigger keywords: LOINC, lab coding, observation code, UCUM units, specimen, method, US Core lab, FHIR Observation, lab result mapping, panel vs analyte. Pairs after OpenMed NER: consume Disease/Chemical/lab-name entities
npx skills add maziyarpanahi/openmed --skill mapping-loinc --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Mapping lab/observation names to LOINC Ground free-text lab and observation names that OpenMed surfaces to **LOINC** (Logical Observation Identifiers Names and Codes), the universal standard for identifying *what was measured*. A LOINC code is a fully specified observation — not just an analyte but the full six-axis model: **Component, Property, Time, System (specimen), Scale, Method**. LOINC is **free** to use. It is published by the Regenstrief Institute under the LOINC license: you accept terms-of-use (and register to download the table), but there is no fee and no per-use restriction. The standard, public path for license-clean mapping is a **FHIR terminology server** exposing LOINC via `$lookup` / `$validate-code`, or Regenstrief's hosted **fhir.loinc.org**. ## When to use - A note or report contains lab/observation names ("serum potassium", "hemoglobin A1c", "blood pressure") and you need a stable LOINC code each. - You must disambiguate by **specimen/system** ("glucose in serum" vs "glucose in urine") or **method** ("HbA1c by HPLC"). - You need **UCUM** units to pair with the result value, or a US Core `Observation` (Laboratory Result) coded with LOINC. - You are mapping a
- When to use
- Quick start (real LOINC / FHIR terminology calls)
- Workflow
- Hand-off from OpenMed
- Edge cases & gotchas
- Standards & references
What does the mapping-loinc skill do?
Maps laboratory and clinical observation names extracted by OpenMed to LOINC codes using the public Regenstrief LOINC and FHIR terminology APIs. Use when the user wants to code lab tests, vital signs, or observations to LOINC, resolve a test name plus specimen and method to the correct LOINC part-model code, attach UCUM units, or build a US Core Laboratory Result Observation. Trigger keywords: LOINC, lab coding, observation code, UCUM units, specimen, method, US Core lab, FHIR Observation, lab result mapping, panel vs analyte. Pairs after OpenMed NER: consume Disease/Chemical/lab-name entities
How do I install it?
Run `npx skills add maziyarpanahi/openmed --skill mapping-loinc --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From maziyarpanahi/openmed, a repository with 4,851 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.