mirror of
https://github.com/MBombeck/HealthLog.git
synced 2026-11-07 04:12:04 +00:00
Marc-André Bombeck
fd2bd67ff3
A lab runs its own method on its own device, so the window a physician evaluates a value against is the one printed next to it on that report, not a catalog band averaged over every lab. Reading a report pulled the value and dropped that range: the extraction asked for it, the commit handed it to the biomarker resolver, and the resolver only uses it when it mints a NEW marker. For every analyte the user already had — the normal case after a first panel — the printed range was read and then thrown away. Add `sourceReferenceLow` / `sourceReferenceHigh` / `sourceReferenceText` to `LabResult` and carry the range from the report to the reading. The text is stored whether or not numbers can be read out of it, because "bis 5,0" and "negativ" state a window too; a range that could not be parsed is kept verbatim, never replaced with invented bounds. `resolveEffectiveReferenceRange` is the one place the precedence lives: the source window wins for that single reading, and the catalog stays the net for readings without one. A printed string with no derivable bound does not displace the catalog. Every surface that judges a reading routes through it — the API verdict, the doctor report, the insights blocks and per-marker assessment, the coach snapshot, the MCP read and the FHIR `referenceRange` — so a value cannot read in range on one surface and out on another. The API keeps `referenceLow` / `referenceHigh` as the window in force, so a client that reads only those two renders the right range and the right verdict with no change of its own; the catalog band, the source window, its origin and a divergence flag ride alongside for clients that want to show both. Read side: the chart draws the source window as a second, visually distinct band with the reading it came from named beneath it, the reading rows name the printed range and the catalog band where the two disagree, and the doctor-report PDF prints the report's own string with a footnote naming the saved range. Entry side: one optional field on the lab form, folded away until asked for, and the printed range is editable on the scan review screen. The range parser covers the notations German and English reports actually print — two-sided, one-sided, comma or dot decimals, thousands separators, trailing units — reads units without ever converting them, and refuses to guess on anything ambiguous.
15 lines
742 B
SQL
15 lines
742 B
SQL
-- Per-reading source reference range on a lab result.
|
|
--
|
|
-- A lab report prints the window its own method and device produce, right
|
|
-- beside the value, and that window is what a physician evaluates against.
|
|
-- Until now the document reading pulled the value and dropped the range.
|
|
-- These three columns carry it: the derived numeric bounds where the printed
|
|
-- string yields them, plus the report's verbatim string, which is stored
|
|
-- whether or not it parsed. Nothing is backfilled — an existing row genuinely
|
|
-- has no source range on file and stays NULL.
|
|
|
|
ALTER TABLE "lab_results"
|
|
ADD COLUMN "source_reference_low" DOUBLE PRECISION,
|
|
ADD COLUMN "source_reference_high" DOUBLE PRECISION,
|
|
ADD COLUMN "source_reference_text" TEXT;
|