Same for me, from a previous experience on another EMR (commercial one), the onsite one was easy to manage specifically appointments (directly with EMR). Regarding an onsite one it was really complicated.
BTW you always have choice to run production instance on internal network and run another tightened instance as portal on external network with limited firewall exclusions for specific ports for only mysql traffic. Web and db servers do not need to be on same machine or network. If you do not plan on using couchdb based documents store, there will be few additional tweaks to grant access to specific patient documents thru portal.
2 Likes
Thanks for this argument, with this adaptation no secure gap between onsite & offsite portal. Jerry was right
1 Like
Yes, I agree, the issue is that I am struggling with my setup and with access to mysql not being in localhost.
But if there are two instances of openemr accessing the same database it would not cause a problem?
Hello Sandra,
I would be happy to. I am not sure how much time I will have.
But at the very least I want to solve the authentication problem
with 5.0.2. That has really effected my practice and has to be
fixed.
–Craig
1 Like
Well, I have more time.
I am setting up my php7.2 environment, since the 7.4 environment failed
No new issues due to multiple instances as long as scripts expect same db schema.
Existing issues of lack of locking and transaction based updates that show up with high usage will continue but a separate db server does give more dedicated processor cycles compared to single host.
1 Like
Hi,
Just found this topic today. Has anyone created a WordPress plugin that uses patient registration API to generate corresponding users in Open EMR, real-time?