Patch 9 skipping sections

Management and Administration
1

hitechelp wrote on Wednesday, April 04, 2012:

Greetings,

We are concerned that patch 9 did not update our system as intended.
We’re running on Ubuntu Server 11.10. 
So far, we’ve been very happy.  Patch 7 was executed with no problems on 02/Mar. (run from command prompt)
After reading the forums we decided not to apply patch 8 and wait for 9.
Until now we have only had self pay patients and had no reason to use billing.

We downloaded and ran patch 9 as directed (by pointing browser at sql_patch.php)
and it appeared to execute without errors however,
a long list of items were skipped and this has us concerned. 

The first thing we noticed was that the version was not updated on the login page. 
It still reads OpenEMR v4.1.0 (7)

This lead us to check the list of files to be changed.
The first file in the list of files to be changed (as indicated with double asterik) was
**interface/billing/sl_eob_process.php  - Ours appears unchanged, the file date is still showing as Sep/11.
**library/Claim.class.php - File date is Dec/11.
**version.php - File date is 02/Mar.

The following screen capture from the patch update is provided:

Processing patch.sql…
Skipping section #IfNotIndex lists type
Skipping section #IfNotIndex lists pid
Skipping section #IfNotIndex form_vitals.pid
Skipping section #IfNotIndex forms pid
Skipping section #IfNotIndex form_encounter pid
Skipping section #IfNotIndex imunizations patient_id
Skipping section #IfNotIndex procedure_order patient_id
Skipping section #IfNotIndex pnotes pid
Skipping section #IfNotIndex transactions pid
Skipping section #IfNotIndex extended_log patient_id
Skipping section #IfNotIndex prescriptions patient_id
Skipping section #IfMissingColumn version v_realpatch
Skipping section #IfMissingColumn prescriptions drug_info_erx
Skipping section #IfMissingColumn insurance_data policy_type
Skipping section #IfNotColumnType billing modifier varchar(12)
Skipping section #IfMissingColumn billing notecodes
Updating global configuration defaults…
Updating version indicators…

Database patch finished.

How do we determine if this patch did what it was supposed to do or not?
and if not,
How do we fix it?

Thanks in advance for your assistance.

Regards,

David

2

yehster wrote on Wednesday, April 04, 2012:

My suspicion is that you didn’t unzip/update the files on to your system correctly.

3

yehster wrote on Wednesday, April 04, 2012:

The sql_patch.php’s purpose is only to update your database with schema changes.  However, if you didn’t actually update the files (which is what it looks like given that your system still says 4.1.0(7), it’s just skipping over previously applied schema changes.

If you copied over the files correctly, your system should say 4.1.0(9) even without running sql_patch.php.

4

yehster wrote on Wednesday, April 04, 2012:

Side note though.  I don’t think there are actually any database changes between patch 7 and patch 9.

5

hitechelp wrote on Wednesday, April 04, 2012:

Kevin,

Your suspicion was correct.
Apparently running unzip from the command line in Webmin doesn’t cut it!
There was no indication that it had bombed.
Thanks for the quick response.  All is well.

Regards,

David