regarding:Code review tracker ID: 3316006 Patches for inclusion of RxNorm and SNOMED Codes.
I just tried to test your patches (added 6/21) and the still don’t work. Please post your patch on a publicly accessible github fork of openemr so that it can be reviewed by the team. And please test them on a clean branch of openemr 4.1-dev before submitting them.
Was able to pull out the RXNORM code from Phyauras original github branch (was a pain). I’ve fixed up most the code, but I need the rxnorm download for further testing/implementation. I’ve requested access to rxnorm downloads today, but takes at least 3 business days to get it. Do you (or anybody else) happen to have a rxnorm download ( http://www.nlm.nih.gov/research/umls/rxnorm/docs/rxnormfiles.html ).
hey,
Here’s interim work on RXNORM codes: http://github.com/bradymiller/openemr/commits/rxnorm_2
(note if follow instructions within the commit comments can get the rxnorm tables/data loaded into Openemr)
Still some path issues to clean up, a windows issue, and then need to figure out how to integrate into OpenEMR.
-brady
Just committed the code to robustly import rxnorm/snomed data. Now awaiting code that begins to incorporate the rxnorm/snomed data into OpenEMR.
Note that integrating rxnorm is high priority since this is required for certification; Phyaura, can your group give an approximate timeframe on rxnorm code integration?
Has anybody else tested this one recently?
The SNOMED import ran perfectly as advertised.
The RxNorm import reported success, but doesn’t seem to have actually worked, since none of the tables (RXNCONSO, RXNREL, RXNSAB, RXNSAT) seem to have showed up in the database.
I guess it’s not a big deal for now since there’s no code in place yet to reference those tables?
Just curious…
Brady,
FYI, I renamed the RxNorm downloaded zip file to fool the importer into thinking it was a newer version, & ran the import routine again. It took awhile, but eventually it finished & actually pulled in the data this time. Same success message when the process was done as last time, but now there’s tables in the database to prove it. Maybe not necessarily a bug? The only concern would be that it reportedly worked both times, but no data the first time around. I will try to do another test this week & see if there are any irregularities. Could be variance in MySQL versions that causes problems too, might not have anything to do with OpenEMR code. Have to wait & see if this kind of glitch happens to anyone else when importing.