New non-Docker AWS migration with latest LAMP stack

Management and Administration
#1

Hello everyone. I have tried my hand at Docker and find that I am unable to wrap my brain around this concept at this time. The simplest of changes to an OpenEMR environment under Linux are now out of my reach. Each file becomes a multi-headed hydra with the introduction of overlapping versions of files.

At this point I would like to install OpenEMR 6.x on AWS and migrate my OpenEMR 5.x data to this new platform all without the use of Docker. We already have OpenEMR 5.0.3 running in AWS on an Ubuntu 16.x EC2 instance (I believe it was a pre-package deal.) I would like to use the latest version of Ubuntu - should I use 20.04 LTS or 21.10? Would you recommend that I use the latest version of the Maria database vs MySQL? Or in the case of AWS should I migrate our MySQL data to the Amazon Aurora system and would it even work with OpenEMR? Should I use the latest version of PHP 8.1.1?

Should I assume that we need to upgrade to 6.x in order to take full advantage of the ePrescription functionality? California has a mandate that all prescriptions be filed electronically as of January 1, 2022 and there are few exceptions to this new rule.

Apologies for any redundancy as this was originally posted in Slack. Thanks in advance for any suggestions.

#2

Hi @Help_Desk, the problem with rolling your own if in US is satisfying HIPAA requirements which the AWS packages have taken care of for you. Check out the guidance on patching which shows how to move a zip file into the containers.

#3

This is a very indepth support request and you may need to hire this out if you lack the experience in IT / security of your infrastructure.

If you are going to try this out on your own on bare metal, you should essentially go and look at how the docker images are constructed in OpenEMR. That will tell you what software is installed, what steps are used to build the docker, etc.

Note once again that while you can do this, if you lack experience in this area, it is highly not recommended for production environments that must safeguard PHI and satisfy HIPAA security constraints.