Read about OpenEMR's Response to the COVID-19 Pandemic at https://www.open-emr.org/covid19/

OpenEMR 5.0.2 Patch

Hi,

The 1st patch for OpenEMR 5.0.2 has been released:
https://www.open-emr.org/wiki/index.php/OpenEMR_Patches

The patch includes security fixes, new support for custom modules, and a bunch of fixes :
*Security fixes - reports by Will Porter, Mera, Mirna Bassaly, and Brady Miller; fixes by Will Porter and Brady Miller
*Added custom modules support - by Jerry Padgett
*MariaDB critical fix for install/upgrade - reported by Robert Down, fixed by Brady Miller
*Cookie and session fixes - reported by Jerry Padgett, fixed by Brady Miller
*Clear billing log feature added - by Sherwin Gaddis
*Billing manager updates - by Jerry Padgett
*Patient portal fixes - reported and fixed by Jerry Padgett
*CCDA fix - reported and fixed by Jerry Padgett
*Eye form fixes - reported and fixed by Ray Magauran
*User editing fix - reported and fixed by Sherwin Gaddis
*Patient history save fix - reported by CodderEMR, fixed by Stephen Waite
*Patient history fix - reported by Stephen Waite, fixed by Jerry Padgett
*Batch payment fixes - reported by Stephen Waite, fixed by zbig01
*837 claim fix - reported by Ray Magauran, fixed by Stephen Waite
*X12 fix - reported and fixed by Derrik Milligan
*Another X12 fix - reported by Ray Magauran, fixed by Stephen Waite
*Fee sheet fixes - reported by Stephen Waite and Ray Magauran, fixed by Jerry Padgett
*EOB invoice last bill date - reported and fixed by Stephen Waite
*API (patient service) fix - reported and fixed by Stephen Waite
*Code styling fix - reported and fixed by Brady Miller
*MedEx fix - reported and fixed by Jerry Padgett
*New patient add fix - reported by Jeremiah Ocasio, fixed by Stephen Waite
*Calendar scrolling fix - reported and fixed by Aaron Chantrill
*eRX fix - reported by Harley Tuck, fixed by Ken Chapple
*Save and dispense rx fix - reported and fixed by Dimitry Remish

-brady

3 Likes

Forgot to mention,
We also have rebuilt the docker, zip package, and the tar.gz package to include this patched code.
-brady

1 Like

Hello,

Great work guys…

I don’t see Merge Patient mentioned…
Was it addressed within one of the fixes?

hi @APerez, see your report in this post, OEMR 5.0.2 Merge Error, started the issue, merge error · Issue #2720 · openemr/openemr · GitHub

My apologies… I need to remember never to do early morning pre-coffee posting.

1 Like

I have downloaded the patch. I was having the ‘eye-table’ installation issue. But I don’t seem to be able to get the patch to run.

When I execute the sql_patch.php file I get the following message:

“Check that mysqld is running.”

Also, the setup.php file has a stated 0 bytes size on both the zipped and unzipped versions of the patch (804 kb)

Am I doing something wrong?

Make sure that you are using the correct DB creds in your sites/default/sqlconfig.php file.

I am running XAMPP as localhost on my machine, and the control panel for mysql is supposed to be running.

I have looked for a sqlconfig.php file within the xampp folder to no avail.

it will be in openemr/sites/default/sqlconfig.php

Found it, but it is called sqlconf.php

In the mean time I did a new install and everything is working now. Thank you for your help.

My mistake, it is sqlconf.php. I verbally call it the sql config file. Sorry if I confused you.

For other people who are reading this thread, the sites/default/sqlconf.php file is where the database creds are stored. Make sure that the username, password, and database name match the values you chose when you first set up OpenEMR.

Here is a screenshot of the file:

Chances are the host and port variables will be the same on most systems. The password will most definitely be different because the password displayed (openemr) does not meet security standards.

If openemr is your password, you should change it.

Hi,

The 2nd patch for OpenEMR 5.0.2 has been released:
https://www.open-emr.org/wiki/index.php/OpenEMR_Patches

The patch includes security fixes and a bunch of improvements and fixes :
*Critical security fix - reported by Dennis Brinkrolf (RIPS Technologies), fixed by Jerry Padgett and Brady Miller
*Security fixes - reported by Dennis Brinkrolf (RIPS Technologies), Daniel Pflieger, and Visolve, fixed by Jerry Padgett and Brady Miller
*COVID19 ICD10 codes added - by Stephen Waite
*Patient portal security improvements, updates and fixes - by Jerry Padgett
*API security improvements and updates - by Brady Miller and Stephen Waite
*Payment improvements - by Jerry Padgett
*MySQL 8 fix, part 1 - reported by Sanjeev Kumar, fixed by Brady Miller
*MySQL 8 fix, part 2 - reported by Tman, fixed by Amit Meena
*Calendar styling improvements - by Jerry Padgett
*Patient Portal styling improvements - by Jerry Padgett and Tyler Wrenn
*Referral form improvements - by Stephen Waite and Visolve
*Added diagnosis history finder for procedure order form - by Jerry Padgett
*Newcrop Rx improvements - by Ken Chapple
*Rx improvements - by Sherwin Gaddis
*MedEx fixes - by ophthal
*PDF fix - reported by Tyler Wrenn, fixed by Jerry Padgett
*Merge patient fix - reported by APerez, fixed by Brady Miller
*Date of birth autocomplete fix - reported by Philip Herrick, fixed by Stephen Waite
*ICD10 import fix - reported and fixed by Stephen Waite
*Fees checkout fix - reported by Evgenios, fixed by Stephen Waite
*Calendar fix - reported by and fixed by Stephen Waite
*Billing fix - reported by and fixed by Stephen Waite
*Billing statement fixes - reported by Stephen Waite, fixed by Jerry Padgett
*Billing fix in billing/service facility - reported by and fixed by Daniel Pflieger
*Messaging fix - reported by syedyawar and fixed by Visolve and Stephen Waite
*Modules fix - reported by and fixed by Jerry Padgett
*Zip code fix - reported by and fixed by Stephen Waite
*Transaction date fix - reported by and fixed by Sherwin Gaddis
*Fix functional and cognitive status form - reported by Pete Boyd and fixed by Stephen Waite
*Fix pharmacy import - reported by and fixed by Robert Hausam

-brady

2 Likes

Yet again @brady.miller, thanks for producing this recent patch. I know it to be a tedious and time consuming task which i’m sure the community appreciates as I do!

For others, a note concerning payment improvements. I added the ability to take manual credit card payments from our billing Front Payments. This was extended from the Patient Portal online payment feature using the same gateway to Authorize.net or Stripe which is setup in Globals->Connector.
Also note that only payment amount and authorization codes are maintained onsite and not credit card numbers or pins.

1 Like

This kind of important announcement warrants its own thread so that it is more visible to people, e.g. “OpenEMR 5.0.2.2 released”. This post could easily be missed by people who might think “Oh I read that thread when it was first posted, I expect people are just commenting on an old thread”.

sure thing @PeteBoyd, if you registered your instance you will also receive an email regarding the nice work by @brady.miller on this.

1 Like

hi @PeteBoyd, Good point. Just created it’s own thread in News section. Here’s our announcement strategy for patches (see bottom of the wiki page):
https://www.open-emr.org/wiki/index.php/Steps_for_a_patch_release

3 Likes

Had to make changes to the patch.sql file due to the error, hopefully the changes we made look right, they seemed to work at least. This is with mariadb server.

Just posting in case this helps someone else with the same error message.

Error message:

UPDATE icd10_dx_order_code
SET revision = (SELECT MAX(revision) from icd10_dx_order_code) WHERE dx_code = ‘U071’;
You can’t specify target table ‘icd10_dx_order_code’ for update in FROM clause

Made changes to multiple lines but from line 304 now reads

#IfRow2D icd10_dx_order_code dx_code U071 active 1
set @newMax := (SELECT MAX(revision) from icd10_dx_order_code);
UPDATE icd10_dx_order_code
SET revision = @newMax WHERE dx_code = ‘U071’;

#EndIf

#IfNotRow2D icd10_dx_order_code dx_code U072 active 1
INSERT INTO icd10_dx_order_code
(dx_code, formatted_dx_code, valid_for_coding, short_desc, long_desc, active, revision)
VALUES (‘U072’, ‘U07.2’, ‘1’, ‘COVID-19, virus not identified’, ‘COVID-19, virus not identified’, ‘1’, ‘1’);
#EndIf

#IfRow2D icd10_dx_order_code dx_code U072 active 1
set @newMax2 := (SELECT MAX(revision) from icd10_dx_order_code);
UPDATE icd10_dx_order_code
SET revision = @newMax2 WHERE dx_code = ‘U072’;
#EndIf

hi @madmax ,

Thanks for reporting this and a solution. What version MariaDB are you using (I didn’t see this issue on MariaDB 10.4)? Luckily, all this error results in is not getting the new covid codes (ie. it won’t break any of the other changes in the patch). Once get this sorted out and test this solution on all versions of mysql/mariadb, will fix the rel-502 branch and then get out a fixed patch.

thanks,
-brady

Hi,
Version is: 5.5.67