In our CDM, we don't seem to use normal ranges from individual results (yet) either; we us an age/sex adjusted table: https://github.com/kumc-bmi/i2p-transform/blob/db7cf8809d810385d2e6d4e4f1e66ac7cb02ed57/curated_data/labnormal.csv https://github.com/kumc-bmi/i2p-transform/blob/master/Oracle/lab_result_cm.sql
In i2b2, we do mark Hi / Lo results on an individual basis, but it looks like we filter out things other than plain numbers. https://github.com/kumc-bmi/heron/blob/master/heron_load/epic_labs_transform.sql (private repository; see MultiSiteDev<https://informatics.gpcnetwork.org/trac/Project/wiki/MultiSiteDev> regarding access) FWIW, there is some regular expression stuff in there to handle result values such as ">40". It also uses https://github.com/kumc-bmi/heron/blob/master/heron_load/curated_data/lab_regex.csv ________________________________ From: Gpc-dev <gpc-dev-boun...@listserv.kumc.edu> on behalf of Phillip Reeder <phillip.ree...@utsouthwestern.edu> Sent: Tuesday, September 24, 2019 9:36 AM To: gpc-dev@listserv.kumc.edu <gpc-dev@listserv.kumc.edu> Subject: Lab Normal Value Processing We haven’t used the normal values associated with individual lab results in the past and while looking at the normal values, many of them are text with modifiers like <,> <=. Etc., along with some that are ranges like 1.0-10.0. Does anyone have SQL/regular expressions that will filter all of those out into the columns required for the PCORICDM? Thanks, Phillip ________________________________ UT Southwestern Medical Center The future of medicine, today.
_______________________________________________ Gpc-dev mailing list Gpc-dev@listserv.kumc.edu http://listserv.kumc.edu/mailman/listinfo/gpc-dev
