Planning for OpenEMR 5.0.1 release

(Brady Miller) #21

We are still going strong on the above roadmap. Gonna start to really focus on 5.0.1 release, which will hopefully be in 8 weeks. Here’s the list of active issues (always feel free to chip in :slight_smile: ):


(Brady Miller) #22


Still working towards 5.0.1 release. Down to only 16 active issues : 5.0.1 Milestone · GitHub
(Please feel free to chip in :slight_smile: )

Hopefully will get release out in 6-8 weeks.


(Brady Miller) #23


Set up the release planning page with goal of the OpenEMR 5.0.1 release being at the end of March (yes, just 4 weeks :slight_smile: ).


(Brady Miller) #24

Also, if you have contributed to OpenEMR in any form (forums, development, testing, translations, money, time, etc.), then feel free to place yourself on the Acknowledgments page here:
(if you email me at with your info, then I am also happy to do this for you)

Note these acknowledgments are also included in OpenEMR (on the acknowledgments link at the login screen).


(visolve) #25

Thanks Khaleela.

Can I show case whatever we have with FHIR?

Do w3 have any one page arch diagram for this?

Sena Palanisami


(Brady Miller) #26

For an update on ongoing FHIR progress, see here:

@sjpadgett is actively working on this with several codebase commits on this recently.


(Brady Miller) #27


Still planning to release OpenEMR 5.0.1 at the end of March. Branched the code on the repository to rel-501 to prepare.

Folks can test the most recent 5.0.1 development demos (build daily) here (just a mere 6 demos on the 3 main OS’s with and without demo data :smile:):
(please test and report bugs/issues)

And folks can test the 5.0.1 development builds (build daily) here (the instructions sets to install/upgrade can also be found here):
(please test and report bugs/issues)

Can follow the ongoing 5.0.1 release process here:


(Brady Miller) #28

I also forgot to mention above:
There is also a 5.0.1 development docker (plan to build this every couple days) here (it is using tags of either ‘5.0.1’ or ‘next’) for the docker folks:

Can get it up and running on by clicking following link(give it 5 minutes or so):

Can find more info on OpenEMR dockers here:
OpenEMR Official Docker has been released!


(Brady Miller) #29


We are still sprinting to get OpenEMR 5.0.1 released by end of March. At this time, there is only 1 critical show stopper bug in the care coordination module, which ZH Healthcare is now working on fixing.

There are still minor bugs/features that would be great to get done, though, here. So, feel free to work on any of these:
5.0.1 Milestone · GitHub

And, of course, please keep testing via above links and reporting any bugs.


(Joseph Aghatise) #30

Great plan! I am new here though and trying to catch up on so many issues. I look forward to the 5.0.1 release.

(Brady Miller) #31


We are still working on the 5.0.1 release, and I expect it to be released in 2 weeks (note we HAVE to release it very soon to ensure it is out before Ubuntu 18.04 is released, since the prior version 5.0.0 of OpenEMR is not compatible with Ubuntu 18.04). The main holdup now are several fixes and some more testing to ensure OpenEMR 5.0.1 will fully work on Ubuntu 18.04.


(Brady Miller) #32


Expected release of OpenEMR 5.0.1 is in 1 week (note Ubuntu 18.04 is released on 4/26/18 and OpenEMR 5.0.1 has to release prior to this because OpenEMR 5.0.0 is not compatible with Ubuntu 18.04, which uses PHP 7.2). Still bringing in lots of fixes and last minute features :smile:
Please keep testing and report any bugs.


(Brady Miller) #33

Hi everybody,

Release is getting close, so please keep testing and reporting any bugs.

Testing demos, which are updated daily, can be tested here:


(Sherwin Gaddis) #34

is there any documentation on how to use the Dicom feature?

(Matthew Vita) #35

@juggernautsei Nope. Our hope was that it is 100% intuitive, assuming folks have dcm files.

What has your experience been?

(Sherwin Gaddis) #36

My first programming job was working on dicom for hospital radiologist. The viewer was written on the JBOSS platform. I wrote the code to remotely install all server components on an OSCent box or windows.

So, people are to upload the dicom images to the patient chart and the viewer just works?

(Jerry P) #37

My last few commits for DICOM gave some pretty good info on mime and zip content usage. It should just work as long as they are supported types.

(Matthew Vita) #38

@juggernautsei That must have been an awesome kickoff to your programming career! I think there’s a lot to be said for some of the older enterprise Java technologies. While it is true that many of them are hard to use and a bit too configuration-heavy, there have been so many patterns that emerged from that time. My favorite web framework is Spring because it “just works” and has a reasonable amount of configuration and reliable “enterprise patterns” with Spring Boot (along with modern tools, dependencies, and “hot reloading”)

Anyways, yes, what Jerry said. You literally just need to drop a DICOM file into documents and then click on it. You’ll be able to interact with the image or images in a very easy and streamlined way.


(Jerry P) #39

Also, if you receive files from radiology without extensions, Upload doesn’t require one and one will be added for you. This is true for single or zipped multiple views. Another little known feature is that I added a patient select drill down in Miscellaneous->New Documents where if you have many documents to add to different patients you may select and change patients to upload documents. Saves time of having to bring up each patients chart to do document maintenance by doing all patients/documents from same screen. I’m actually kind of proud of that little gem…

(Sherwin Gaddis) #40

That is good to know @sjpadgett.

Is there a specific virtual folder the EU is suppose to use or can they create their own DICOM folder?