This shows you the differences between two versions of the page.
Both sides previous revision Previous revision | |||
documentation:oncology:meeting_notes_2019_jul-30 [2019/08/07 12:59] mgurley |
documentation:oncology:meeting_notes_2019_jul-30 [2019/08/07 13:00] (current) mgurley |
||
---|---|---|---|
Line 8: | Line 8: | ||
* https://forums.ohdsi.org/t/how-to-represent-ranges-in-the-measurement-table/7504 | * https://forums.ohdsi.org/t/how-to-represent-ranges-in-the-measurement-table/7504 | ||
* https://forums.ohdsi.org/t/how-to-implement-a-lab-test-range-result-in-measurement-table/5221 | * https://forums.ohdsi.org/t/how-to-implement-a-lab-test-range-result-in-measurement-table/5221 | ||
- | * The group agreed to test out Rimma's recommendation for representing numeric ranges as two entries within the MEASUREMENT table. Michael raised the issue that this will require manual curation by the OMOP vocabulary team that might not be scalable in the future -- to make the necessary entries within the new CONCEPT_NUMERIC table. Michael also raised data quality concerns about creating duplicate non-connected entries within the MEASUREMENT table. The group agreed to reassess Rimma's recommendation after ETL testing. | + | * The group agreed to test out Rimma's recommendation for representing numeric ranges as two entries within the MEASUREMENT table. Michael Gurley raised the issue that this will require manual curation by the OMOP vocabulary team that might not be scalable in the future -- to make the necessary entries within the new CONCEPT_NUMERIC table. Michael Gurley also raised data quality concerns about creating duplicate non-connected entries within the MEASUREMENT table. The group agreed to reassess Rimma's recommendation after ETL testing. |