You usually are not comparing numbers, and which is bigger. Typically, you are asking for patients where a measurement is above or below a certain threshold. Like in “Give me all patients where the leuko count in the urine is above 10 per HPF”. In that case, @QI_omop’s record would fit. If the question were “Give me all the patients above 30” or “Give me all the patients above 70” it would not match.
This is exactly what I was thinking. In assessing response in liquid tumors, one of the most common criteria is whether or not the blast count in a bone marrow biopsy is above or below a given threshold. We get blast counts out of the bone marrow biopsy using NLP - but they’re sometimes expressed as a range, and, as @Christian_Reich mentioned, what’s important is just whether or not the patient is below or above the maximum (or minimum) of the range. So if you’re looking to see if the patient has ≥20% myeloblasts, a range of 10-25 wouldn’t qualify.
I wonder if you could do this using the OPERATOR_CONCEPT_ID - but then you’d need two rows, one for the “less than” and one for the “greater than.” My sense is that having two rows with the same measurement_id is a violation of the DDL - @Christian_Reich, is that a fair statement?