Inside the observation
Why LabPrism shows missing lab fields explicitly
How LabPrism handles absent units, reference text and interpretation when displaying normalized lab entries from an authorized record connection.
Absence is part of the result display
A result inspector needs to distinguish a supplied value from an absent field. LabPrism uses explicit fallback text for missing reference information, interpretation and source details. A fallback label describes the display state; it is not a finding about the patient.
Do not make a more complete-looking record
The interface reads what was returned and leaves missing clinical context visible. It does not insert a familiar laboratory range or derive a diagnosis from the number. A polished presentation should still let a reader recognize where the available information ends.
Inspect the mapping when something looks unexpected
Developers can compare the selected normalized object with the displayed quantity and labels. That is a concrete debugging path: identify the field, check the formatting helper, and verify the fallback. It is more useful than treating every unexpected display as an upstream clinical error.
Separate software checks from interpretation
Implementation tests can check that an absent field remains absent and that source text survives formatting. They do not clinically validate a result. A future operator should keep that distinction when adding comparison features. The existing application has not activated live patient connections.
The FinchNode normalization boundary
LabPrism uses FinchNode as the upstream connection for its lab category. The product then chooses how to present returned fields and how to describe omissions. Readers can inspect that boundary through the visible JSON and the public implementation.
Questions about this guide
Does normalization fill in every missing field?
The interface cannot assume it does. It handles the response it receives and exposes missing context explicitly.