OpenEMR 5.0.2 has just been released!

OpenEMR 5.0.2 has just been released!!!

It can be downloaded here:
https://open-emr.org/wiki/index.php/OpenEMR_Downloads

Installation instructions can be found here:
https://open-emr.org/wiki/index.php/OpenEMR_Installation_Guides

Upgrading instructions can be found here:
https://open-emr.org/wiki/index.php/OpenEMR_Upgrade_Guides

Online Demos can be found here:
https://www.open-emr.org/demo/

New feature list in OpenEMR 5.0.2:

  • 2014 ONC Complete Certified EHR
  • Numerous User Interface Improvements that Include Bootstrap and Responsive Web Design
  • Numerous Security Improvements
  • Multi-Factor Authentication Support (Support for TOTP and U2F)
  • Robust Encryption Support
  • Brute Force Login Prevention
  • Access Control Improvements
  • Lightweight Directory Access Protocol (LDAP) Improvements
  • Optimization of Security for Sessions and Cookies
  • Docker Deployment that Supports Best Security Practices
  • New REST API
  • New Support for Online Payment Universal Gateway (Authorize.Net and Stripe Supported)
  • New Support for Insurance Eligibility Checking
  • New Support for SNOMED Release Format 2 (RF2)
  • New Support for Unique UUID to Identify Application
  • New Howto Documentation and Tooltips
  • External Module Support Improvements
  • Patient Portal Improvements
  • Patient Flow Board and Recall Board Improvements
  • Patient Lookup and Searching Improvements
  • Calendar Module Improvements
  • CCDA Module Improvements
  • Eye Form Module Improvements
  • CAMOS Form Improvements
  • Online Drug Lookup Improvements
  • Online Drug Interactions Lookup Improvements
  • Billing Module Improvements
  • Collections Report Improvements
  • Patient Documents Module Improvements
  • CouchDB Support Improvements
  • Lab Module Improvements
  • Messaging Module Improvement
  • MedEx Module Improvements
  • List Editor Module Improvements
  • Log Module Improvements
  • Prescription Module Improvements
  • WENO eRx Improvements
  • NewCrop eRx Improvements
  • Backup Module Improvements
  • Birthday Alert Improvements
  • ICD10 Code Set Updated
  • SNOMED RF2 Support
  • Supported in 34 Languages
  • Internationalization Improvements
  • Numerous Bug Fixes
  • Numerous Fixes to Ensure Compatible with Most Recent Version of PHP
  • Fixes to Ensure Compatible with Most Recent Version of MySQL and MariaDB
  • Speed and Performance Optimizations
  • Modernization of Codebase
  • Complete InnoDB Database Support
12 Likes
2 Likes

Best EMR ever!!!

thanks

2 Likes

As of today, 17 Aug 2019, I am having issues installing 5.0.2 on Ubuntu 16.04 and have been told that 5.0.2 was still under construction for UbuntU.

Is this correct.

Not to my knowledge, @nursejeff. openemr-devops/packages/lightsail at master · openemr/openemr-devops · GitHub is a good example of a functional (I tested it not thirty minutes ago) way to install OpenEMR 5.0.2 on an Ubuntu 16.04 instance. Can you go into more detail on the issues you’re observing?

Please see this tread.

Hi @nursejeff ,
Ubuntu can use the standard linux install/upgrade or docker if need now. The Ubuntu specific package (deb package) is still under construction. This package won’t fix your php version issue.
-brady

Hi @nursejeff, try removing all html files from sites/default/documents/smarty/main except README. As for 5.0.2, it uses smarty framework so html file gets created dynamically inside above mentioned directory and these html contains windows paths. That’s why it gives error. And even after deleting these files error won’t go, install mbstring php extension as it doesn’t configure these extension while installing PHP on ubuntu. You’ll need to configure. By doing above steps, your zipped openemr will work absolutely fine.

Hi - Im on Version Number: v5.0.1 (6). Haven’t customised, but have configured quite a lot - including the data records where I have added fields using the menu options.

  1. Is it important to upgrade for security?
  2. Is there any risk of loosing any of what I have configured?
    Thanks

HI…
2. Not really. Before any upgrade always backup.

  1. Alway YES.