Replies: 3 comments
-
Thanks, @rimusia.
And then you list two records in the table. We need to finalize how to do ranges. Two records is not a good idea, because they are not linked, and a simple query "Give me all tumors larger than 2 cm" will return this record, because nobody checks that at the same day there is not only a record >1, but also not one <2. Forcing people would make querying a lot more complicated and much slower. I still like the addition of "range_value" or "plusminus", and then have value_as_number=1.5, and plusminus=0.5. Thoughts? |
Beta Was this translation helpful? Give feedback.
-
just pasting text for others to read quickly from the intro section Proposal for representing “numeric” concepts Background In OMOP CDM, these concepts are normally used in Measurement and Observation tables to store value_as_concept_id. Analysis of these data is currently possible only if the user knows exactly the concepts used to represent range or value, including their respective units. It is not possible to perform analysis on numeric values of these data, nor is it possible to differentiate numeric values by units. For example, it is not impossible to find tumors which size is less than 2 cm by issuing the following simple query: One has to know exactly the concepts that cover this range. Proposal |
Beta Was this translation helpful? Give feedback.
-
The question is how to represent the range. This has been discussed several times before. |
Beta Was this translation helpful? Give feedback.
-
Numeric concept proposal.docx
Beta Was this translation helpful? Give feedback.
All reactions