Plan to postpone 5.0.0 until get the Complete MU2 certification(guessing about 3 weeks). In a way this is a good thing, because allows us time to get the tab layout to production quality and also get the registration feature more mature.
Just letting everybody know that the wheels are beginning to turn on the release process. Hopefully will be turning in the MU2 application to ONC this week. At that point, will branch the release and begin to prepare it to go out right after we get the certification (assuming we get it ).
Any person or company whom has contributed any time or resources is free to place themselves on the acknowledgemnts page, which then ends up in the Acknowledgments page in OpenEMR. Either enter it into the following wiki page(or give me your information and I’ll do it for you): http://www.open-emr.org/wiki/index.php/OpenEMR_Acknowledgments
MU2 certification is getting very close (ZH is finishing up a paper report(WCAG report for item e1) with infogard and then the MU2 application will go to ONC (I am told the turn around time is about 1-2 weeks with ONC)).
Plan to release right when get MU2 certification. So, have begun to prepare for the release process and have branched off the planned 5.0.0 release (rel-500) on github.
Now is a good time to start your testing and reporting of bugs.
I tested Version_5.0.0 on LinuxMint 18.1 and I find that the install script place Openemr in /var/www instead of /var/www/html ( apache2) . I also get an error when I try to port openemr.sql data base from version 4.2.2 to this version.
Did you install the development ubuntu package (I am guessing you did since have git-openemr for the path). Note this is a development package that collects the most recent development codebase(5.0.1-dev). It installs to path /var/www and sets up a alias with apache, so it should work in /var/www path. This package should be plug and play (easy easy removal/install to keep testing out most recent codebase), so if there were any issues after install, then would be a bug.
If you are bringing in a 4.2.2 database, then will need to run the sql_upgrade.php script(and set selector to 4.2.2; note it will default to 5.0.0 since this is version 5.0.1; also note the upgrade can take a really long time because it is converting database to innodb).
Thanks for the information. I installed the Development package but did not use the sql_upgrade script .Git-Openemr was installed to /var/www from the script and apache2 cannot open it in Firefox. I had to copy the whole directory to /var/www/html as root to get it to be work. I did not change apache2 to point to /var/www as I have other programs needing apache2 at var/www/html. Strangely Version-4.2.2. is pointed to /var/www and works!
Hi Premnath,
It will be released about 1 week after OpenEMR gets complete MU2 certification (I roughly estimate OpenEMR will get MU2 complete certification sometime over the next 1 to 4 weeks).
-brady OpenEMR
This is the last call for being placed in the acknowledgements page: http://www.open-emr.org/wiki/index.php/OpenEMR_Acknowledgments
(this listing also gets included in OpenEMR)
(either add your entry to the wiki page or let me know, and I’ll add it)
New feature list in OpenEMR 5.0.0:
-2014 ONC Complete Certified EHR
-New Modern Tab Based User Interface
-New Modern Ophthalmology/Optometry Module.
-New Logo
-New Login Screen
-User Interface improvements
-New Recurrent Appointment Widget on Patient Summary Page
-New Daily Summary Report
-New User Interface Themes
-New Feature to Import and Set holidays
-New Product Registration Feature
-Patient Tracker Board Improvements
-Patient Billing Statement improvements
-ICD10 Code Set Updated
-Form Validation Improvements
-Patient Appointment Display Improvements
-Fee Sheet Improvements
-EDI Module Improvements
-Supported in 33 Languages
-Numerous Bug Fixes
-Numerous Security Fixes and Security Improvements
-Converted Database Engine to InnoDB
-Migrated Main Codebase Repository to GitHub
Plan a press release in 1-2 days with more details.