New feature list in OpenEMR 4.1.1:
* Continues to have Official ONC Complete Ambulatory EHR Certification: http://oncchpl.force.com/ehrcert/EHRProductDetail?id=a0A3000000LW494EAD&retURL=%2Fehrcert%2FEHRProductSearch&setting=Ambulatory
* Supported in 19 languages
* Supports ICD10 diagnosis and billing coding
* Supports SNOMED diagnosis coding
* Supports 5010 X12
* Ability to add support for region specific diagnosis/billing coding sets.
* Importing mechanism to support importing and upgrading of ICD9, ICD10, SNOMED and RxNORM standardized data.
* Modernized login screen
* Calendar layout improvements
* Reminders and Dated Reminders
* Compatible with MySQL 5.5 and PHP 5.4
* Ability to customize prescription layout, DEA, NPI and state license number
* Explicit support for a separate primary provider and referring provider in patient demographics
* Billing and Payment module improvements
* Supports multiple billing code modifiers
* Support for procedure specific claim notes
* Supports CouchDB storage of documents
* Additional patient searching mechanism added (Patient List)
* Customizable Facility specific user information tracking
* CQM and AMC reports with options for assigning patient-provider relationships
* Sort fax/scan pages to match the original order in a displayed document
* Ability to enter/modify Vital Signs timestamps
* The disclosures display screen supports pagination
* Additional contributed forms
* Multiple bug and security fixes
* Multiple database performance enhancements
* Patching mechanism
* Patient Notes module and the Message module are fully integrated/compatible
* Translation module supports comments in constants and translations
* ADODB framework upgraded
* Jquery framework upgraded
* Ubuntu package supports upgrading of Multisite Module OpenEMR instances
Just finished releasing the OpenEMR 4.1.0 Appliance and setting up the Official 4.1.1 Demo. All packages (tar, zip, ubuntu, xampp, appliance), the demos and the instructions sets are now finisshed. So, this release is officially finished
Kudos to the entire community for producing this solid release.
Brady, tnx for this release. I am still bussy/strugling with the new Appliance version. I did all commands as stipulated in the update part of the manual for Appliance.
Strangely enough I still get the old Login screen and in phpMyAdmin I still see the Version number as 4.1.0 Is there a setting I have to apply, or haw can I be sure I have the latest release?
Or should I redo the whole update steps……with backup copy I made from the VMWare files used in Openemr?
Tested my backup on a Virtualbox with the upgrade from 4.1.0(13) to 4.1.1 then from Ubuntu 11.10 to 12.04.1. So far, everything works fine except for the external dataloads. It’s in the Help topic, but the gist of it says that the mysql version is not supported (Ubuntu auto-update changes mysql to the latest).
Copy-paste from the other topic since it’s the exact same problem:
tried to install ICD9 Staged Release : csmv30_master_descriptions.zip
ERROR: query failed: LOAD DATA LOCAL INFILE ‘/tmp/ICD9/CMS30_DESC_SHORT_DX.txt’ INTO TABLE icd9_dx_code FIELDS TERMINATED BY ‘’ (@var) SET revision = 0, dx_code = trim(Substring(@var, 1, 5)),short_desc = trim(Substring(@var, 7, 60))
Error: The used command is not allowed with this MySQL version
install ICD10 Staged Release : 2012_PCS_long_and_abbreviated_title.zip, DiagnosisGEMS_2012.zip, ICD10OrderFiles_2012.zip, ProcedureGEMS_2012.zip, ReimbursementMapping._2012.zip
ERROR: query failed: LOAD DATA LOCAL INFILE ‘/tmp/ICD10/icd10pcs_order_2012.txt’ INTO TABLE icd10_pcs_order_code FIELDS TERMINATED BY ‘’ (@var) SET revision = 0, pcs_code = trim(Substring(@var, 7, 7)),valid_for_coding = trim(Substring(@var, 15, 1)),short_desc = trim(Substring(@var, 17, 60)),long_desc = trim(Substring(@var, 78, 300))
Error: The used command is not allowed with this MySQL version
I haven’t tested the SNOMED or RXNORM database loads since I was using Virtualbox for testing, but it’ll probably do the same thing. I also used the debian package for upgrading as per instructions in the wiki from 4.1.0 (13). I’m using the latest MySQL that is bundled with the Ubuntu 12.04.1 update as of yesterday, which is probably definitely the true culprit here.
apparently, this MySQL version is 5.0 instead of 5.5. The ICD9 database successfully updated here. Won’t try the ICD10 so you guys can check on it if you guys wanted.
Confirmed bug on Ubuntu 12.04 which is using sql version:
Ver 14.14 Distrib 5.5.24, for debian-linux-gnu (i686 using readline 6.2
Doesn’t seem like a sql version thing since the Windows Xampp package is working fine, which is using sql version:
Ver 14.14 Distrib 5.5.25a, for Win32 (x86)
Quick google search looks like may be related to privileges in mysql.
The my.cnf file you should edit is the /etc/mysql/my.cnf file. Just: $ sudo nano /etc/mysql/my.cnf
Then add:
[mysqld]
local-infile
[mysql]
local-infile
The headers [mysqld] and [mysql] are already given, just locate them in the file and add local-infile underneath each of them.
You need to restart the mysql server after making the changes. Confirmed that it works on Ubuntu 12.04.
(once I get confirmation it works for others, will then place this issues in the install/upgrade docs)(may be also good to bring this up on the actual External Download Page if the errors happens and could place this in the next patch).
Copy/paste the content from the following two files (please create a new forum thread for this to avoid bogging down this release thread):
/etc/openemr/openemr.conf (if there are passwords in this file, ensure you mask them out)
/var/log/openemr/install
I am using the previous xampp for windows, I believe it is 1.7.3, upgraded gradually to openemr 4.1.0 patch 13. I would like to know the best way to upgrade to both openemr 4.1.1 as well as the new xampp version. The windows upgrade to 4.1.1 leaves the old xampp, and the xampp install puts on a fresh install. So far I have figured out that you have to completely uninstall the old xampp using windows control panel before running the new xampp installer, or it won’t run at all. I also found that you cannot, after running the new xampp installer, just replace the mysql/data/openemr folder with your old data. Replacing the whole mysql/ data folder will run but gives mismatched versions in phpmyadmin and a warning of unpredictable behavior.The windows upgrade also doesn’t neccessarily place form files you placed in interface/ form, back in that file. Specifically I was using the chief complaint form. Also I found you have to go back and renew any security you put into the previous xampp as that doesn’t stay in place. The xampp site says that trying to upgrade xampp in place basically doesn’t work, so doing the windows upgrade followed by an xampp upgrade doesn’t seem like an option. I was thinking that maybe I need to make a phpmyadmin database dump backup and copy of openemr/sites/default files and then completely unistall xampp and openemr. Then run the new xampp 4.1.1 installer, replace back the sites/default files, import the database backup and then run the windows upgrade scripts. If you think that might work, would there be an order to do that in? Also for some reason I can’t just edit the sqlconfig.php file and make it work, instead I just have to replace it with my old one?
I was also surprised to find that doing the windows upgrade managed to keep my changes and additions to layout based forms. Those must be stored in the database instead of the openemr directory unlike the other non LBF forms. Anyway, thanks for all your work, this looks like a great upgrade. I hope I can make a small contribution and help with ideas on the best way for windows xampp users to upgrade to 4.1.1. It would be nice also to have an xampp installer with at least basic security enhancements in place, with maybe instructions for where to enter some passwords. As it stands, the xampp security issue gets confusing quickly. I think the lack of an easy windows install and upgrade may be the one thing holding this project back from mass adoption in the real world. As you can see from my last post, to do this currently takes someone who likes to tinker with this stuff, which is not your usual healthcare provider.
The my.cnf file you should edit is the /etc/mysql/my.cnf file. Just: $ sudo nano /etc/mysql/my.cnf
Then add:
local-infile
local-infile
The headers and are already given, just locate them in the file and add local-infile underneath each of them.
Just tried this. Sadly I still get the same error. There shouldn’t be a specific order to add values under each header right…. I tried the other method in the link, but I’m way too noobish to work with mysql with Terminal.
I tried doing the windows upgrade followed by the xampp upgrade installer from the xampp site, and that indeed doesn’t work. I tried exporting a database dump file, doing the xampp 4.1.1 install and the importing back the cvs file in phpmyadmin, and that didn’t work either. It gives a time out error, but none of the suggested solutions seemed to work either. So I can make it work so far only if I stop running and remove the service on apache and mysql using the xampp control panel, and move the current xampp directory to backup, then make a fresh install of the 4.1.1 windows xampp file, and copy back the sites/default directories and the mysql/data directories from the old files.You then run the xampp control panel and install services and start apache and mysql. Then run the sql_upgrade.php and acl_upgrade.php scripts. You also need to add back any customized files and forms except LBF. This does give you a version mismatch under phpmyadmin, but it seems that was present in the old xampp version as well without apparent problems. You also need to run localhost/security and add back your passwords. Anybody see problems with doing an upgrade this way?
There should not be a specific order (I placed them in new lines directly below and headings). Since it worked for me on Ubuntu 12.04 desktop, guessing it should work for you. The step I bet you are missing is to shutdown/restart your computer (or can manually restart the mysql server via 'sudo service mysql restart). Let me know if it then works for you.
It’s really odd for ubuntu/debian to stray from the “standards” since it appears the mysql default for 5.5 is to have this feature on (meaning the package makers seemed to have gone out of their way to turn this feature off be default). Will change the docs on the wiki when I get confirmation that this works for others).
The best way to approach (which you have basically done) is to treat it as a migration from one operating system to another. Basic steps in this case would be:
1. Perform the openemr upgrade steps (includes maintaining your custom forms/code).
2. Backup openemr (the mysql database via mysqldump command on commandline (which is in c:\xampp\mysql\bin\ directory) and a copy of the openemr web directory)
3. Uninstall the current xampp package and remove it completely
4. Install the xampp-4.1.1 package
5. Empty the openemr database and the openemr web directory
6. Restore your backup into the database (via commandline mysql command in c:\xampp\mysql\bin\ directory) and the web directory
7. Modify your sqlconf.php file to have the same credentials as the xampp-4.1.1 pacakge sqlconf.php file
8. Secure it
things to avoid:
Avoid directly copying the mysql database files (instead, use the mysqldump command) because can not guarantee compatibility of these between different mysql versions.
Agree would be nice to have a click/install version of this which is secure, but nobody has taken this on. I’d argue the current package is a nice, easy way for a user to get it up and running quickly (considering all the pieces involved, to simply have to unzip it, turn on the apache/mysql via the gui and then go to it into a browser is very easy), however I fully agree that then turning this into production level material (ie. actually using it in reality) is much tougher. At this point, generally need somebody with technical proficiency around (the user or hired/volunteer help) to properly run/maintain/secure/backup OpenEMR in any OS and some of the pros may even argue that Windows/xampp is not a very ideal platform to begin with…
There should not be a specific order (I placed them in new lines directly below and headings). Since it worked for me on Ubuntu 12.04 desktop, guessing it should work for you. The step I bet you are missing is to shutdown/restart your computer (or can manually restart the mysql server via 'sudo service mysql restart). Let me know if it then works for you.
It’s really odd for ubuntu/debian to stray from the “standards” since it appears the mysql default for 5.5 is to have this feature on (meaning the package makers seemed to have gone out of their way to turn this feature off be default). Will change the docs on the wiki when I get confirmation that this works for others).
-brady
OpenEMR
I tried both restarting the service by the service command and the init.d thing yesterday to no avail. I think the difference between my ubuntu and yours is that I updated from 11.10 to 12.04 and let the config files be replaced after I installed the openemr update through commandline. Commandline OS update didn’t work for me (sudo apt-get update) for some reason, so I did the autoupdater. I let it replace like 10 config files, which I think is the culprit here (I shouldn’t have let it lol). I tried re-applying the openemr update but it brought a version error (apparently updating 4.1.1 over 4.1.1 isn’t allowed). But then again, I don’t know what the openemr dpkg installs/replaces.
To be safe, suggest a shutdown/restart (to ensure the mysql server has been restarted). Suggest you copy/paste your entire /etc/mysql/my.cnf file here on the forum.
The OpenEMR package on a new install ensures some php settings and adds security to some openemr directories in apache (see the the /var/log/openemr/install file for the log of install, which shows what was modified). It doesn’t touch mysql, so reinstalling openemr will likely not help you to fix this. This appears to be an issue with the mysql setting local-infile not being turned on by default( at least it is on a new ubuntu 12.04 install; would be very odd if the upgrade from 11.04 to 12.04 was any different since the same mysql version/settings should be there).
Ok, something very bizarre is happening here. To make this work, do not even need to make the above configuration changes in /etc/mysql/my.cnf . All you need to do is to restart the current mysql service in terminal:
sudo service mysql restart
Then if I want to “recreate” the bug, I simply restart the apache service:
sudo service apache2 restart
Which can then be fixed again by entering the following command:
sudo service mysql restart
So, it appears that the apache2 is doing something to not allow this feature when it starts up (which is then reversed if restart the mysql service).
Will report more later after more testing,
-brady OpenEMR
Back to version 4.1.1 upgrade. Thank you Brady I finally got it to work. It took a bit of reading about mysqldump. You need to open a windows dos command prompt and enter:
CD C:\xampp\mysql\bin
Then from the command prompt
C:\xampp\mysql\bin>mysqldump -u root - p -databases openemr> C:\dumpfile.sql
Enter your root passord here:
It will run awhile and produce your backup file dumpfile.sql in the c:directory
When you go to restore it in the new xampp, you open up the database in phpmyadmin and at the bottom of the list, check all, and use the drop down list to empty the data files.
To restore your files run a dos command prompt again to the xampp/mysql/bin command prompt and type
C:\xampp\mysql\bin>mysql -u root -p openemr < C:dumpfile.sql
Enter password here:
This one runs a very long time with just a blinking cursor making you think it froze up. Just be patient, it took mine about 20 minutes to finish. The web directory refers to the openemr/sites/default files where your pdf attachment files reside.
I hope that helps someone else. I learned a lot about the whole think figuring this out
