mirror of
https://github.com/MBombeck/HealthLog.git
synced 2026-11-17 07:42:23 +00:00
feat(labs): keep the reference range a report prints beside a value
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.
This commit is contained in:
1 parent
3778e70ff5
commit
fd2bd67ff3
57 files changed
+2281
-175
No files matched your search
@@ -0,0 +1,14 @@
|
||||
-- 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;
|
||||
+33
-1
@@ -5005,9 +5005,41 @@ model LabResult {
|
||||
/// reference bounds + range verdict are meaningless for a qualitative row.
|
||||
valueText String? @map("value_text")
|
||||
unit String
|
||||
/// Optional reference-range bounds as reported by the lab.
|
||||
/// Reference-range bounds stamped onto the row at write time. Despite the
|
||||
/// name these are NOT the lab's printed range: since v1.18.1 every write
|
||||
/// path copies the linked `Biomarker`'s `lowerBound` / `upperBound` here as
|
||||
/// historical truth, so a later catalog edit does not silently rewrite a
|
||||
/// past reading. The range the LAB printed lives in `sourceReference*`.
|
||||
referenceLow Float? @map("reference_low")
|
||||
referenceHigh Float? @map("reference_high")
|
||||
|
||||
/// The reference range as PRINTED ON THE SOURCE REPORT for this one reading.
|
||||
///
|
||||
/// Labs run different methods on different devices, so the window a
|
||||
/// physician evaluates against is the one printed beside the value on that
|
||||
/// report — not a catalog band that averages every lab. These three columns
|
||||
/// carry it: the parsed numeric bounds where a bound could be derived, and
|
||||
/// `sourceReferenceText` as the report's own verbatim string ("< 5",
|
||||
/// "bis 5,0", "negativ", "siehe Befund"). The text is kept whenever the
|
||||
/// source printed one, parseable or not — absence reads as absence, and a
|
||||
/// window that could not be derived is never invented.
|
||||
///
|
||||
/// Precedence: for a single reading the source bounds win over the catalog
|
||||
/// band; the catalog stays the net for readings that carry no source range.
|
||||
/// `resolveEffectiveReferenceRange` in `src/lib/labs/reference-range.ts` is
|
||||
/// the one place that rule is expressed, and every surface that judges a
|
||||
/// reading routes through it.
|
||||
///
|
||||
/// Plaintext, not `*Encrypted`: that suffix marks user prose (`noteEncrypted`
|
||||
/// here, `Biomarker.contextEncrypted` next door). This is a structured
|
||||
/// lab-report field of exactly the class of the plaintext `analyte` / `unit`
|
||||
/// / `value` / `valueText` columns beside it — `valueText` already carries
|
||||
/// the actual clinical RESULT ("positiv") in the clear, so encrypting the
|
||||
/// window that result is judged against would protect strictly less while
|
||||
/// making the column unreadable to the SQL the read paths run.
|
||||
sourceReferenceLow Float? @map("source_reference_low")
|
||||
sourceReferenceHigh Float? @map("source_reference_high")
|
||||
sourceReferenceText String? @map("source_reference_text")
|
||||
/// When the sample was taken (UTC instant; wall-clock anchoring is the
|
||||
/// reader's concern per the schema's UTC-only convention).
|
||||
takenAt DateTime @map("taken_at")
|
||||
|
||||
Reference in new issue
Block a user