Next OpenEMR release will be happening after get full MU2 certification (goal is to get the release out by 9/30/16; guessing the chances of getting it out by then is 50/50).
We have an opportunity here to bump up the version rather than using 4.3.1. Could bump it up to 5.0.0 since we will then be stuck in 5.0.x for a while to fulfill the full MU2 certification.
Hi,
Will assume that no reply is the go ahead to bump up the next release to 5.0.0 . Will likely change this over the next several days unless there is disagreement with this plan.
thanks,
-brady OpenEMR
The OpenEMR development version has been officially set to 5.0.0
Will open a new thread in the near future for tracking/managing the upcoming 5.0.0 release (guessing it will be released in 1-2 months). The 2 remaining big goals of this release will be gettting the Full MU2 certification and also getting in Ray’s eye form.
If there are any other goals we should include, post them here.
Will it be possible to add a function to copy old prescriptions and modify to fit what we need (from the same patient)? Also, can we have a way to save the most common Rx that any practice uses (similar to the fee sheet)? They will speed up the Rx process. Just some of my wishes. Thanks.
I did the copy and replace to the respective folders. At the Rx screen, I check the previous medication and click on “Re-issue (Rx)”. The screen flickers but nothing else happens. What else do I need to do?
Thanks. I download and add all the files and still not works. The screen just quickly flashed and nothing happens. Would you check again? I’m sorry to inconvenience you so much.
Not sure how big impact bootstrap will have on lbf since lbf functions generate full html code that uses classes like label, data, text etc. When we added bootstrap to patient portal, it instantly modernized the look and feel but we had display issues where lbf functions were used. Surely the rest of codebase is bound to have similar instances but since lbf code generation is centralized, it may be good to prefix these as lbf_label, lbf_data, lbf_text etc. in the next release.
This is no inconvenience. It is an exercise in getting things right. The flashing quickly means it is trying to work. I did this mod so long ago, I have forgotten all the pieces that went into it so thanks for your patience.