This describes the need for implementing SSL for transmission security…
Need: To safeguard the electronic protected health information from unauthorized access, the data can be transmitted in encrypted format by configuring SSL with OpenEMR. Server Certificates can be obtained from any one of the following.
By configuring the SSL, communication between the OpenMER server and client browser is encrypted,. We had configured the OpenEMR in HTTPS (ssl - using self signed certificate) environment (for linux) and it is working fine.
Since this should be taken care during the OpenEMR deployment, we believe that we need to provide a separate document for “OpenEMR SSL Configuration” for both Linux and Windows environments as part of the deliverables of this particular task.
However, this doesn’t address the transmission security between OpenEMR systems and HIEs.
Secure connection between OpenEMR and outside systems is subject, entirely, to the system you are connecting to and not a limitation of OpenEMR itself. An HIE for instance might require SSL, VPN or a PGP encrypted public/private key to communicate data back and forth.
Hi
I thought that Mirth was the HL7 tool of choice? http://www.mirthcorp.com/community/overview.
Isn’t it a requirement to get EHRs, Labs, and eRx talking to one another using HL7?
What of the HL7 parser under practice settings?
Having a box that will take an HL7 message and make it plain text is not really useful in the context of exchanging data with outside entities. Fortunately HIE is not the really required for CCHIT in the first go 'round