CCR Release of Information

MxRelease.com compresses all of your release documents and then creates a message digest. It then encrypts the data using Blowfish symmetric key encryption using a randomly generate key. The data is then sent to the MxRelease.com portal and the key is sent to the receiving party. This way the key is never even stored on the MxRelease.com servers and only the receiving party can decrypt it. MxRelease.com then used Rijndael (AES Encryption) to double encrypt using a private key on the server before it is stored. This way, even if someone would somehow get access to our servers that are located at a secured facility, they would not be able to decrypt it.

When the receiving party then logs in using the MxRetrieve for Windows client, they enter the key they received from the sending party. The MxRelease.com servers then decrypt the Rijndael (AES) decryption routines and send the data to the retrieval program. The retrieval program then applies the secret key locally using the Blowfish decryption routines and the documents are decompressed and compared against the original message digest for authentication. At this point the receiving party can import them into whatever programs they use to deal with their documents.

This provides one of the strongest, most secure methods of sending documents over the Internet available today. It far exceed HIPAA requirements, giving you the peace of mind that you need -- knowing that  medical information you send will only be viewed by its intended recipients.

What is Symmetric Key Encryption?

In symmetric key encryption, you and your receiving party share a "secret" key. Using this key, you can encrypt a message into "cyphertext". Cyphertext looks like a random sequence of characters and is completely meaningless to anyone unless they also have the secret key, in which case they can decrypt the cyphertext back into the original message and read it.

Using symmetric key encryption, eavesdropping and unwanted backups of your messages are no longer a problem (unless the eavesdropper knows what your secret key is). It also becomes harder for someone to modify your messages in transit in any kind of a meaningful way.

What Are Message Digests / Authentication Codes?

A "Message Digest" or "Message Authentication Code" is really a very simple concept. You take your message and pass it through an algorithm that spits out a relatively short sequence of characters (maybe 64 or 128 or so of them). This sequence of character is a "fingerprint" for the message. Any minute change in the message would produce a significantly different "fingerprint". There is no way to obtain the original message from its fingerprint and it is almost impossible to find two messages that yield the same fingerprint (just like trying to find 2 people who are not twins that have the same actual fingerprints).

Message Digests are quick ways to check to see if a message has been altered. If you have a digest of the original message and compare it with a digest of the message you just received and they match, then you know that the message has been unaltered.