translate-health-data

Translate health data

Health data arrives under whatever name the source used. Last year's checkup wrote A1c, this year's HbA1c, the clinic Glycated Hemoglobin; a Chinese report prints 血红蛋白 for what an English one calls hemoglobin. One test, several names, nothing to compare until each lands on one code. And a model reading a report is fluent about the rows it got wrong: the failure is never "I don't know", it is a confident paragraph about the wrong analyte.

This skill is the offline translator for both problems: names to LOINC, units to UCUM, complaints and diagnoses to ICPC-3, a FHIR Observation for the result. The codes come from the vocabulary, never from you. When the vocabulary does not know a term the answer is a refusal, and a refusal is an output to report, not a gap to fill from memory.

Setup

pip install mirobody              # resolution, units, ICPC-3, Apple export: no key, no network
pip install 'mirobody[parse]'     # adds document parsing, which needs one model key

The first is two packages, numpy and this one; the vocabulary ships inside the wheel and the first call loads it in a few seconds. It needs Python 3.12 or newer: on an older interpreter pip quietly installs a release from before 1.2, which has no mirobody resolve. Install into a virtual environment (python3.12 -m venv .venv), never into the user's system Python. With uvx, no install: uvx --python 3.12 mirobody resolve 血红蛋白 (uv fetches that Python if it is missing). For parsing, put ONE key in the environment or a .env in the working directory (OPENROUTER_API_KEY, OPENAI_API_KEY, GOOGLE_API_KEY, ANTHROPIC_API_KEY, DEEPSEEK_API_KEY or DASHSCOPE_API_KEY). The model reads the document into rows; the codes still come from the offline resolver.

No key, no search. If neither the environment nor the working directory's .env has a key, do not look for one anywhere else: no find ~, no reading another project's .env or ~/.config. Read the document yourself, then resolve every row with resolve_reading(name, value, unit), which needs no key. Ask the user for a key only if they want mirobody parse itself.