Hi Everybody,
Starting to begin planning for the next OpenEMR release. This new release already has a myriad of new stuff (such as the new patient portal and institutional billing support from @sjpadgett, user interface improvements from @zbig01 and @robert.down, major layout engine improvements from @sunsetsystems, and huge amount of other new stuff, which plan to detail as get ready for the new release).
The goal is to release OpenEMR 5.0.1 within 2 months. And this post is a CALL TO ARMS for the community to begin focusing on this. There are several things that community needs to focus on getting done before releasing 5.0.1:
-
MedEx. This is work by @rmagauran which brings in third party support option for patient reminders along with marked improvements in the messaging and patient tracker modules. First step is for me to rebase the current code on top of master in a new pull request. Then @robert.down plans to help out with styling. Then it should be ready to get into the codebase.
-
Bootstrap and support for responsive. This is work by @zbig01. We have already checked in the core part of the work and a bunch of new themes into the codebase. I am currently working with @zbig01 to bring in the 70+ scripts that he has already updated to bootstrap/responsive.
-
PHP 7.1 support. This is something that we need testers and developers to focus on. And is a great thing to work on for testers/developers looking to work on small projects of high importance. There is already a development demo that is running in php 7.1 for testers here: http://www.open-emr.org/wiki/index.php/Development_Demo#Alternate_Demo_.28Ubuntu_17.10_-_uses_php_7.1.29 . And note there is a php error log link there. Recommend doing a bunch of testing and then reporting the errors you note in the php error log. For example, check out Administration->Globals->Save. And of course, feel free to fix these issues in a pull request.
-
cTakes support. This is @Matthew_Vita’s baby and it will be awesome. Basically will take unstructured data such as a clinic note and point out coding elements (SNOMED/ICD10 etc). This is cutting edge research stuff. Goal for OpenEMR 5.0.1 is to just support it in some way (ie. does not need to be fancy). This will give OpenEMR 5.0.1 a real research scope to it.
-
FHIR support. @visolveemr is working on this. Goal is for OpenEMR 5.0.1 to just support it in some way (ie. does not need to be fancy).
-
Education support. I am working on this. Goal is to support several education/instruction sites with a online demo and instruction set(ie. the site will provide their instruction material and we would host it and the companion demo(s)).
-
Massive amount of demo data patient records. @JBW is working on this, and is vital for support of above Education and Research (ie. cTakes stuff) items; waiting on above FHIR support which will then allow use of tools to import huge amount of patient data. @JBW is also working on some other awesome big data analysis projects (such as incorporating R into analysis of patient records in OpenEMR), which also requires large demo data sets.
-
General testing and bug fixes. This goes without saying. As with the above PHP 7.1 Support, we need to identify all bugs and fix em.
-brady
