TO be honest, I need to put some thought into that BUT I have also thought about a wrapper for the application in mind. We currently use an application that makes php apps into exes. We have ours pointed to our server and which we will no longer be using soon do to us just learning our server is not HIPAA complaint.
But what this positive effect for many practices and other facilities brings is NO SHOWN LINKS, no right-clicking and selecting view source and view other sources. It’s fully encrypted and keeps data safe from within the openEMR software for those running local servers as we probably will be.
Not to say “CLOSED SOURCE” but just like earlier, I needed some info off a website for a certain set of words but couldn’t copy it, I right-clicked, viewed the source and copied from within the code of the little section I needed. Can’t have that in openEMR and for sure can’t have that kind of access on dozens of computers in an office other than IT needing chrome access to test pragmatics. So it’s still open source available but with a bit better security to the application overall. Meaning do your testing but production should be from the wrapper app. Looks a lot better and professional for a workplace than browsing through looking at links at the top.
I also find that some sort of integration with at the least Office Ally is much needed. Some sort of SFTP connection for when you generate your claims, it can automatically submit via sftp without even having to click on anything else. Thus this is AFTER you review and assure the claim is ready