Hi @prikala,
Nice finding.
Ideally, this concept should be represented as whole MEASUREMENT table row:
Measurement_concept_id = Blood ethanol measurement
value_as_number = 20,
unit_concept_id = milligram per milliliter
operator_concept_id = <.
We want to add the “Wide mapping table” to store relationships between a source concept and different attributes (to Event_concept_id, unit, operator and number in this case).
Not sure, when it will be agreed by the community and takes an actual place.
So, you can create some look-up table and use it during your conversion to get the result above.
Note, the concepts like
Y90.2 Blood alcohol level of 40-59 mg/100 ml
will end up in two rows, one with >=40, another with <=59
And if you don’t want to be bothered with the additional logic, just break the rule of Meas Value restriction for now.
And once we release the “Wide mapping table”, you can fix that.