The first OpenEMR 4.1.1 patch has been released, which fixes several critical bugs. Download, installation instructions and details regarding new fixes can be found here: http://open-emr.org/wiki/index.php/OpenEMR_Patches
The 4th patch for OpenEMR 4.1.1 has been released. The patch includes a Critical scheduling module bug fix and Clinical Decision Rules (CDR) engine/reporting bug fixes and performance optimizations : http://www.open-emr.org/wiki/index.php/OpenEMR_Patches
The 5th patch for OpenEMR 4.1.1 has been released. The patch includes a Critical billing bug fix (fixes a X12 and HCFA/CMS creation bug that was unmasked by a bug fix in the previous patch) and includes processing animation added to the CQM/ACM/Rules reports(so users are not confused when the reports finish processing) : http://www.open-emr.org/wiki/index.php/OpenEMR_Patches
Hi.
The 6th patch for OpenEMR 4.1.1 has been released. The patch includes major enhancements in CDR based reports (standard rules, CQM, AMC and creation of clinical reminders) that improves performance, allow tracking and allows saving of these reports. It also includes some bug fixes (in addition to Tony’s rec above): http://www.open-emr.org/wiki/index.php/OpenEMR_Patches
tnx for the newest patch corrections. In your notes I saw that my changes on a Pharmacy file general_edit.html are not included. Good , since yesterday I had to make another small correction in translation xl (…) field.
After a synchronization on GitHub are there more steps to take, if I wanted to get my changes included? How can I delete the file afterwards, if I am not convinced it is an additional benefit for OpenEMR? Is there an option to change the file while seeing the file committed in GitHub?
Excuse me for the possible stupid remarks, but as a novice I am very much afraid to do something that confuses me and that is of no benefit of future releases.
One of the great things about Git, is that everyone can have their own branches and it is relatively easy (especially if they are small changes) to pull in corrections from anywhere.
I think people are intimidated by Git when there isn’t really a need to be. It’s not possible to mess things up for others, and worst case if your repository gets “messed up” you can always create a new clone in a new directory. It’s hard to lose data with git. (That’s the whole point of source control!).
I’m not sure what your present repository looks like or where your changes reside right now. However, the simplest thing to do to get your changes incorporated might be to update your master branch from the OpenEMR repository, then just create a new branch for you changes. Since it’s only one file, you can just copy the file with your changes into the new branch and then push.
The only way to learn git is to play with it.
One other thing. Only Brady messes with the patch release branches, although any of the Integration developers could do it in theory. Code pretty much always goes through the main/master development branch before it goes into a patch, so the fact that the patch was released actually doesn’t affect how/what you need to do to get your changes incorporated into a future release.
Yester thx for the INFO. To be sure: I just have to confirm my changes on my local PC GitHub and do a synchronize?
And if accepted by the GURU it will appear in the official release branche?
I have a copy of OpenEMR V4.1.1. and committed to my personal computer the changes, and to my surprise saw thing synchronizing and I had committed the file (possibly the first time unintentionally. Than I wanted to delete, but that did not work on GitHub. Than I wanted to make changes on GitHub, but of course also could not find the option.
So please confirm this statement:
If I make a change on my local GitHub branch-file, the personal PC, and do a synchronize… and get the message synchronization completed, is all I need to do?
A link to your repository on https://github.com/ so I can take a look would help.
Did you create a branch in your local repository or did you work in “master.”
If I make a change on my local GitHub branch-file, the personal PC, and do a synchronize… and get the message synchronization completed, is all I need to do?
I’m not sure exactly what you did, but I’m guessing what you’ve done is not sufficient, as it doesn’t sound like you did a “git push” to github. Your changes are tracked on your local PC, but I’m guessing you haven’t shared them with the world yet.
What tool are you using for git? It’s possible that your “synchronization” is equivalent to the “push” I’m talking about, but again I’m not sure exactly what you are doing.
And if accepted by the GURU it will appear in the official release branche?
After someone shares code on github, there is an additional manual step taken by one of the integration developers which puts it into the official branches (master/rel-411/rel-410). Changes generally go into the official master first, then when it’s time for a patch, Brady is the one who moves code from master to rel-411/410.
The patch includes the following new fixes/improvements:
-Patient portal (offsite) bug fixes and improvements - contributed by ZH Healthcare
-Bug fixes and improvements of social security form items in demographics/insurance - contributed by yehster
-Bug fix to include Newcrop eRx module medications in AMC report - contributed by ZH Healthcare
-Bug fix for incorrect syntax in disc_fragment.php script - contributed by yehster
The patch includes the following new fixes/improvements:
*Bug fix for security vulnerability - contributed by bradymiller
*Bug fix for copays in appointment encounter report - contributed by ZH Healthcare
*Bug fix and improvements to lab display in then onsite patient portal - contributed by bradymiller
*Added feature to show lab results in the offsite patient portal - contributed by ZH Healthcare
*Added feature to save new patient data to audit tables in the offsite patient portal - contributed by ZH Healthcare
*Bug fix for emailing reminders - contributed by arnabnaha
*Bug fix in AMC reporting - contributed by pfwilliams
*Improvement to fee sheet code set search selector - contributed by bradymiller
*Bug fix in codes import module - contributed by pfwilliams
*Added feature to focus on field when searching for billing/diagnosis codes - contributed by yehster
*Bug fix in user add/modify gui - contributed by Sunset Systems
My suggestion for users that are using versions less than 4.1.1 (ie. can’t use above patch) is to remove the following file/directory:
file-> /openemr/library/openflashchart/php-ofc-library/ofc_upload_image.php
directory(if it exists)-> /openemr/library/openflashchart/tmp-upload-images/
The patch includes the following new fixes/improvements:
*Security fixes - contributed by bradymiller
*Minor improvement in fee sheet - contributed by bradymiller
*Bug Fix for deleting payments via the Front Office Receipts report - contributed by Sunset Systems
Main reason for this patch is to fix a xss vulnerability in the ‘site’ parameter (does not require authentication), which will likely be a published vulnerability in the next several days.
The patch includes the following new fixes/improvements:
*Bug fixes and improvements to Date of Birth calculations, formatting and options - contributed by yehster
*Security fixes - contributed by bradymiller
*Bug fix in billing report - contributed by Sunset Systems
*Bug fix in scanned documents module - contributed by Sunset Systems
Interesting.
There is an unrelated (to OpenEMR) forum online where .zip downloads are saved in this same state.
This is the first time that one of the OpenEMR patch downloads has done this.
What I have to do to fix the file…
1. Download 4-1-1-Patch-12.zip
2. Rename the file to 4-1-1-Patch-12.zip.gz
3. Unpacking the .gz file results in a valid 4-1-1-Patch-12.zip