[Feature] Open-ended reference/optimal ranges

[Jonseed]

Description

Some biomarkers have open-ended reference ranges. For example, my lab report shows "eGFR" has a reference range of ">59" and "HDL Cholesterol" has a reference range of ">39". It would be good if getbased supported these open-ended ranges for both reference and optimal ranges. Currently if you import labs with such ranges, they either import with the wrong range, or without any range at all. And there is no way to edit a range to be open-ended. If you delete a lower or upper range value, it reverts to the original built-in range value. Not sure how best to input an open-ended range? Delete lower or upper range value? Input > or < symbols as on the lab report?

System Info

• Browser: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/144.0.0.0 Safari/537.36 Edg/144....
• Screen: 1920x1080
• Theme: dark
• AI Provider: ollama

[elkimek]

Looked into this — it would need changes to the import pipeline, the range editor, and how ranges are displayed across the app. Markers like eGFR and HDL already have full two-sided ranges built in, so they work fine as-is. Keeping this open for a future release though, it's a good idea.

[Jonseed]

The problem is that if you try to import a biomarker that has an open-ended range on the lab report, then the range does not get imported correctly, and has to be manually fixed. For example, eGFR shows 59-? on the Import Preview, but imports with a range of 59-2.3, which obviously is wrong. HDL shows 39-? on the Import Preview, but imports with a range of 39-2.1, which is wrong. How can these open-ended ranges be imported correctly? Perhaps if the AI detects an open-ended range (59-?), the import pipeline can set the open-ended value to something really high or low, like 59-300 on eGFR? If the open-ended range is on the low end, it can just set the first value as 0?