Situation
Hi i would like to ask if anyone in here is on AWS? And if anyone encounter any issue on the patient signature generated in EMR?
We just recently migrated to AWS and for the first week everything is working until now we just noticed that the signature for privacy policy of the patient is no longer working.
Search
Did you search the forum for similar questions?
Logs
Did you check the logs?
Was there anything pertinent in them?
Please paste them here (surround with three backticks (```) for readability.
You can also turn on User Debugging under Administration->Globals->Logging User Debugging Options=>All
@casper how did you migrate to AWS and from where/what did you migrate? Did you migrate from Linux to Linux or from Windows to Linux or windows to windows.
Its linux to linux, we migrated from a web hosting company to aws. First we install a fresh copy of open emr in the aws (application and db). To make sure all folder is in right permission. Once it was comfirm that its working (we can login in the new installed version). We replace the db in aws with the one we have from the hosting company. 3rd. Delete the 2 key located in the document folder and let the system generate the new key. It was working before (privacy policy signature) then all of a sudden it just stop working.
Forgot to mention that in aws we have 2 instance 1 production and 1 staging, we also try to install a fresh installtion in the staging and its still the same issue we have in production. And also to mention our account in aws is an ec2, and we dont used the image of open emr from aws market place, we are the who setup the web server and installed the open emr.
