There are several modifications pending a commit as I am merging the e-prescribing code with new changes I have been working on for Meaningful Use including RxNorm functionality, the new medication table and screen updates. So this is a preliminary update. Something in a recent 4.0 update is causing a few minor issues with displays such as a popup that doesn’t close and I should have an update for those commited tomorrow. I’m traveling part of today but I will be checking my email and the forum off and on today. If you have any questions, please feel free.
Also, the E-prescribing 3.2 patch (minus the med table and rxnorm) will be pushed to github in the morning.
Question:
When done loading NDC via “Download Latest NDC” it displays an uploading error in the results area. If I then select the items one by one from “Load Data from file” section it does load but displays results only for small uploads.
1. It’s based on somewhat outdated code from October. Recommend rebasing it to an updated master branch. Note you will get conflicts in interface/patient_file/summary/add_edit_issue.php that will need to be dealt with. Make sure you integrate your code with the changes in that file and also the changes in interface/patient_file/summary/stats_full.php .
Check out this commit to get an idea of what was done: https://github.com/openemr/openemr/commit/fc729f4b5b8e174ae369d66a1814f88a06241957
If any question on how to update your master, rebase or other stuff with git, give me a holler.
One improtant rec. is to change over to another branch before doing this stuff so you always have your original there.
2. Right before you do your rebase above, set up git to automatically remove windows eol characters. You have two files in your commit with these things. By changing the setting right before, then git will always automatically deal with them on your commits. It’s a one line git command setting (depends on your os) that is described here: http://help.github.com/dealing-with-lineendings/
I’ll plan to look over the rest of the code over the next several days (also, I invite anybody else to help out with these code reviews; they’re starting to pick up and the more the merrier)
The NDC load error may be due to permissions of the contrib directiory. The eprescribing-upgrade.sql must be run and also the permissions on the contrib directory should be modified for the NDC section to work properly.
However, the NDC code section will more than likely be going away as the RxNorm functionality that is in the works will identify a medication with the RxNorm RXCUI and pull in the NDC codes as necessary. In addition, there will be more traditional upload scripts for the code-sets. I’ll wait to see how the RxNorm and med table reviews go over and then a decision will be made on whether we should retain or X the NDC section.
Let me know if you have any other questions,
Thanks,
Connie
The MU team has been working with Connie on this and Micheal F is doing some cross testing to make sure the data structure covers the needs for the CCR/CCD project he is working on. Everyone gets to learn multiple branch merging
-Tony
I’m new to using github, but I did a checkout and created the upstream so I thought I was good on the current version. I think I understand now what has happened though, I was pulling upstream from my remote clone of the master. instead of pulling upstream from the actual master OpenEMR repo.
I’ll perform the rebase and make sure the upstream is linked appropriately. So, I’ll have to merge in the most recent updates and resubmit. Sorry for this, I’ll try to get it turned around as soon as possible.
The learning curve to git is rough; feel free to ask any questions so we can speed things up for you. To quickly see your remote locations, peek at your .git/config file.
You just got unlucky because Visolve and myself already committed code to make the meds/allergies NIST compliant and cleaned up the main issues screen a bit. So, gonna likely not be straightforward for you to merge those two scripts.
This stuff is not intrusive at all(ie. no databases changes and very minimal changes in the OpenEMR main code), so could potentially put this (after he fixes some minor issues) into the main codebase to avoid having to merge/update all these separate projects.
Brady,
I’ve been working with Mike on the CCR/CCD branch, I think he’ll be ready for first commit later in the week, he was waiting to announce it when he got some testing on a merged branch from Connie done.
-Tony
I have the merged branch with Connie’s code completed and did some testing.
Currently, I am working on cleaning up the code per Brady’s suggestions so that it can be committed.
-Michael
Michael,
Just keep pushing the new commits into your branch (as you’re doing). Let me know when it’s ready and I can quickly rebase your stuff into one commit (before I commit it to sourceforge codebase); after this you’ll then want to work off the sourceforge rebased commit. As an aside, give me the Full Name and Email Address you want me to list as the author of the commit; also, I suggest you put this information into your local git repo: http://help.github.com/git-email-settings/
-brady
Regarding Michael’s code for ccd/ccr (github link above), I’m recommending that we commit it (once he fixes some minor issues), despite it not being fully functional. The only OpenEMR code that it even touches is in interface/patient_file/report/patient_report.php, where it provides a button for a CCR and a CCD report. It’s interesting, because the outline of the reports and very basic functionality is there, but there are still likely many blanks to fill in. I suggest putting it into the main openemr codebase, but I plan to put the report buttons at the bottom of the page along with a tag (such as Experimental or Under Construction) so it is not viewed as reliable accurate reports. If we issue a official release before these reports are done, then can remove the links temporarily. The benefit of getting these reports in there now (albeit not completely finished) is that it allows others to contribute to it (will involve expanding parts of OpenEMR gui and database to support the CCR/CCD stuff) while working on other modules not yet committed (such as the CDR and escripts modules); all these module rely on each other, so will be nice to get at least one of them into the sourceforge codebase at an early stage.
On second thought, I’ll just use a global to control the showing of Michael’s buttons; duh. (I’ll default them to off for now; easy for testers to turn it on in Globals).
Brady that sounds reasonable. But do post to github and let me know when the commit is ready so I can look it over and make my comments before it goes in (though probably will be fine to commit to SF and deal with any issues after that).
Status and actions items for integration of Phyaura E-prescribe model and CCR/CCD module will be the topic of this week’s weekly call on OpenEMR CCR/CCD integration.
When: Thurday Jan 13, 2011, 12pm EST, 9am PST
Where: Dial-in: 1-213-289-0500 Access Code: 1522905
Volunteer developers are needed for improvements in the CCR/CCD module. Attendence of this weekly call is good place to get started with contributing CCR/CCD imporvements.
Volunteer NIST QA testers are needed for CCR/CCD functionality. Attendence of this weekly call is a good place to get started with NIST QA testing of CCR/CCD requirements.
