Refuse an export nobody scoped, and stop naming UCUM without a code

Two findings from the deferred-audit list, both live since July.

A FHIR lab quantity stamped the UCUM system unconditionally while the
code was only added when the analyte map resolved a symbol for exactly
that unit. A receiver was told the unit came from UCUM and then handed
no UCUM code, which is a coding claim the bundle cannot back. System
and code now travel together, on the value and on both reference-range
bounds.

The doctor-report export accepted a selection that admits nothing. The
panel disables its own submit in that state, so only a hand-built
request reached it, and it rendered an empty artefact while spending a
rate-limit slot. This route has no documents-only mode that would make
an empty leaf list a legitimate scope, so it refuses with 422. The
share-link route, which does have that mode, is untouched.
This commit is contained in:
Marc-André Bombeck committed 2026-08-15 00:23:44 +02:00
1 parent d2491d5589
commit 09446846b1
4 files changed
+60 -16

No files matched your search

@@ -181,7 +181,12 @@ describe("lab-result FHIR Observations", () => {
});
describe("lab-result LOINC + canonical UCUM coding (v1.18.8)", () => {
function labOf(type: string, unit: string, value = 5.4) {
function labOf(
type: string,
unit: string,
value = 5.4,
bounds?: { low: number; high: number },
) {
const bundle = buildFhirDocumentBundle(
makeData({
labResults: [
@@ -191,8 +196,8 @@ describe("lab-result LOINC + canonical UCUM coding (v1.18.8)", () => {
value,
valueText: null,
unit,
referenceLow: null,
referenceHigh: null,
referenceLow: bounds?.low ?? null,
referenceHigh: bounds?.high ?? null,
catalogReferenceLow: null,
catalogReferenceHigh: null,
sourceReferenceText: null,
@@ -250,13 +255,15 @@ describe("lab-result LOINC + canonical UCUM coding (v1.18.8)", () => {
expect(tsh?.valueQuantity?.code).toBe("m[IU]/L");
});
it("omits the UCUM code when the unit does not match the mapped canonical", () => {
it("omits the UCUM code AND its system when the unit does not match the mapped canonical", () => {
// HbA1c mapped (LOINC present) but recorded in an mmol/mol unit we don't
// canonicalise → keep the LOINC coding, drop the UCUM code, keep display.
// The system goes with the code: a valueQuantity naming UCUM without a
// code claims a coding the bundle does not carry.
const o = labOf("HbA1c", "mmol/mol", 36);
expect(o?.code.coding?.[0].code).toBe("4548-4");
expect(o?.valueQuantity?.system).toBe("http://unitsofmeasure.org");
expect(o?.valueQuantity?.code).toBeUndefined();
expect(o?.valueQuantity?.system).toBeUndefined();
expect(o?.valueQuantity?.unit).toBe("mmol/mol");
});
@@ -264,10 +271,25 @@ describe("lab-result LOINC + canonical UCUM coding (v1.18.8)", () => {
const o = labOf("Selenium", "ug/L", 95);
expect(o?.code.text).toBe("Selenium");
expect(o?.code.coding).toBeUndefined();
// Display unit stays; no coerced UCUM code is invented.
// Display unit stays; no coerced UCUM code is invented, and no code
// system is named for a code that is not there.
expect(o?.valueQuantity?.unit).toBe("ug/L");
expect(o?.valueQuantity?.code).toBeUndefined();
expect(o?.valueQuantity?.system).toBe("http://unitsofmeasure.org");
expect(o?.valueQuantity?.system).toBeUndefined();
});
it("keeps system and code together on the reference range bounds too", () => {
// The bounds are stated in the SAME unit as the value, so an uncoded
// unit must leave them uncoded as well, on both halves.
const uncoded = labOf("HbA1c", "mmol/mol", 36, { low: 20, high: 42 });
expect(uncoded?.referenceRange?.[0].low?.system).toBeUndefined();
expect(uncoded?.referenceRange?.[0].low?.code).toBeUndefined();
expect(uncoded?.referenceRange?.[0].high?.system).toBeUndefined();
const coded = labOf("HDL", "mg/dL", 55, { low: 40, high: 60 });
expect(coded?.referenceRange?.[0].low?.system).toBe(
"http://unitsofmeasure.org",
);
expect(coded?.referenceRange?.[0].low?.code).toBe("mg/dL");
});
});
+5 -2
View File
@@ -80,11 +80,14 @@ export function labObservations(
// A lab quantity: the recorded `unit` is always the display string, and
// the canonical UCUM `code` is stamped only when the analyte map resolved
// one for exactly that unit (no coerced symbol).
// The `system` rides along WITH the code and never alone: naming UCUM as
// the code system while withholding the code claims a coding the bundle
// does not carry, and leaves a receiver unable to machine-compare the
// value it is attached to.
const quantity = (value: number) => ({
value,
unit: lab.unit,
system: UCUM_SYSTEM,
...(coding?.ucum ? { code: coding.ucum } : {}),
...(coding?.ucum ? { system: UCUM_SYSTEM, code: coding.ucum } : {}),
});
// The bounds are stated in the SAME unit as the value, so they carry the
// SAME coding — a bare unit beside a coded value leaves a receiver unable