Michael, I think you're looking at obsolete code (well, obsolete with respect to the current KUMC ETL code anyway). The medication mapping code was recently rewritten<http://listserv.kumc.edu/pipermail/gpc-dev/2014q4/000655.html> and the part you asked about was removed.
The main design change implemented during the rewrite was the paths/full names are comprised of the RxNorm AUIs/local medication IDs (for example, \i2b2\Medications\RXAUI:3257490\RXAUI:3257495\MEDICATION_ID:129272\). As far as I know we plan to use the AUI-based paths as the GPC standard for medications (see also gpc-dev conference call notes for 2014.10.28<http://listserv.kumc.edu/pipermail/gpc-dev/attachments/20141028/554bffae/attachment-0001.pdf>). Before the rewrite the paths were a concatenation of the medication/NDF-RT names which got really long and messy. I think you'll also find that the new code is much easier to read and better documented (hopefully). For the newer code see epic_med_mapping.sql<https://informatics.kumc.edu/work/browser/heron_load/epic_med_mapping.sql> on the KUMC Informatics wiki. Or, update to a newer version of the KUMC ETL code from the GPC shared repository (see MultiSiteDev<https://informatics.gpcnetwork.org/trac/Project/wiki/MultiSiteDev>). The GPC tickets relevant to the medication mapping rewrite include #78<https://informatics.gpcnetwork.org/trac/Project/ticket/78>, #181<https://informatics.gpcnetwork.org/trac/Project/ticket/181>, and #152<https://informatics.gpcnetwork.org/trac/Project/ticket/152>. Regards, Nathan From: [email protected] [mailto:[email protected]] On Behalf Of Munns, Michael B Sent: Tuesday, December 02, 2014 3:59 PM To: [email protected] Subject: RxNorm metadata I am working on the RxNorm metadata using the KU epic_med_mapping.sql script. In there is the creation of a table rxnorm.clarity_name_to_rxcui_medex and then a second table is created off of that. I don't see where the rxnorm.clarity_name_to_rxcui_medex gets populated from. There is a link a medex tool in the script. What am I missing? Michael Munns Database Analyst 402-559-3821 The information in this e-mail may be privileged and confidential, intended only for the use of the addressee(s) above. Any unauthorized use or disclosure of this information is prohibited. If you have received this e-mail by mistake, please delete it and immediately contact the sender.
_______________________________________________ Gpc-dev mailing list [email protected] http://listserv.kumc.edu/mailman/listinfo/gpc-dev
