At UMN we received the NDC drug code from Epic and mapped it to the RxNorm CUI at the most granular level possible using the NLM API. We also created a set of rules when the NCD was missing of how to map to RxNorm.
We then used NDF-RT to categorize medications. So levofloxacin displays in i2b2 as follows AM000] ANTIMICROBIALS - 729065 [AM400] QUINOLONES - 171011 Levofloxacin Injectable Product - 16194 Levofloxacin Oral Liquid Product - 1173 Levofloxacin Oral Product - 63357 Under each of the Levofloxacin categories are more detailed drugs I've missed [image: Inline image 1] <https://i2b2.ahc.umn.edu/webclient/#> <https://i2b2.ahc.umn.edu/webclient/#> Bonnie L. Westra, PhD, RN, FAAN, FACMI Associate Professor, University of Minnesota, School of Nursing & Institute for Health Informatics Director, Center for Nursing Informatics Location - WDH 6-155 P - 612-625-4470, Fax - 612-625-7091 email - [email protected] Mail - WDH 5-140, 308 Harvard St SE, Minneapolis, MN 55455 On Mon, Apr 6, 2015 at 2:47 PM, Dan Connolly <[email protected]> wrote: > Phillip, > > Maybe it's obvious to people who deal with this stuff regularly, but I > don't see how adding in the ingredient level makes for a more useful > hierarchy. Would you please elaborate? What sort of thing would a > researcher do that's easier if the terms are organized by ingredient? > > A researcher here at KUMC just asked: > > ... in HERON, for example, the drug levofloxacin can be found in different > paths as Levofloxacin 500 mg PO TAB or Levofloxacin IN DJW. For this > project, dosage or forms of administration is not important, for instance > oral tablet or injection of the same drug should be considered together. So > I need to an algorithm to automatically treat levofloxacin 500 mg PO TAB or > Levofloxacin IN DJW as just Levofloxacin. > > Would organizing by ingredient let this researcher search for "just > Levofloxacin" > more easily? > > Is the UTSW med hierarchy on babel already organized this way? When I > search the one with lots of counts, I get dozens of hits for Levofloxacin > and they don't seem to have a common ancestor. > > Under NCATS they sort of have a common ancestor, but it seems to have two > homes in the hierarchy: > > > <dimcode>\NCATS\Medications\N0000010574\N0000029216\N0000029216\N0000029218\N0000029327\82122\</dimcode> > <tooltip>\NCATS\Medications\Ophthalmic agents\Ophthalmic > agents\Anti-infective,topical ophthalmic\Antibacterials,topical > ophthalmic\Levofloxacin</tooltip> > > > > <dimcode>\NCATS\Medications\N0000010574\N0000029074\N0000183553\82122\</dimcode> > > <tooltip>\NCATS\Medications\Antimicrobials\Antimicrobials\Quinolones\Levofloxacin</tooltip> > > > same code, 82122, in both cases. I guess it's both an Opthalmic and an > Antimicrobial? > > Here's hoping I find time to ask this researcher if that NCATS hierarchy > would be more natural to work with. > > -- > Dan > > ------------------------------ > *From:* Phillip Reeder [[email protected]] > *Sent:* Thursday, April 02, 2015 2:47 PM > *To:* Dan Connolly; Apathy,Nate; Russ Waitman > *Cc:* [email protected]; Meyer,Aaron > *Subject:* Re: Medication Mapping Issue (standardization measurement > framework, milestone:data-quality3) > > If we really want to reconsider the design, I’d propose adding in the > ingredient level to the hierarchy, making it for example: > ANTINEOPLASTICS\ ANTINEOPLASTIC HORMONES\Tamoxifen\Tamoxifen Oral Solution > ANTINEOPLASTICS\ ANTINEOPLASTIC HORMONES\Tamoxifen\Tamoxifen Oral Tablet > > Basically it groups the SCDFs by ingredient so that the user can easily > grab all “Tamoxifen” medications. And for UTSW, with medications that are > simply “Tamoxifen Oral” without the tablet/solution/dosage, I can map them > to the ingredient level, instead of at the SCDF level. And it would be > inline with how the NCATS/ACT project has their terminology created. > > This would probably be a more disruptive of a change in the terminology > than simply adding the SCD level, but it does make for a more useful > hierarchy. > > Phillip > > > _______________________________________________ > Gpc-dev mailing list > [email protected] > http://listserv.kumc.edu/mailman/listinfo/gpc-dev > >
_______________________________________________ Gpc-dev mailing list [email protected] http://listserv.kumc.edu/mailman/listinfo/gpc-dev
