The system secures information during exchange. It uses Direct messaging to securely exchange health information between approved healthcare providers and organizations ensuring compatibility and compliance with the latest healthcare technology standards and practices. Messages and attachments can then be electronically downloaded in an encrypted package for use by the receiving party.
Identity Verification
Direct standards require a Level of Assertion 3 (LOA3) for identity proofing to allow a user/provider to participate in exchange. This ensures the sender and receiver are considered eligible to be participating in the exchange of protected health information and are confirming to standards.
User/provider identity verification is not required with secure email.
Content:
A Direct message delivers the content to the recipient and enables the recipient to process the message and the content without accessing an external site or portal.
Secure email delivers a link to the content that requires the recipient to log in to the sender’s system, much like a secure portal, and then download the information.
Structure:
A Direct message has structure (patient data) and thus can be processed with automation.
Secure email sends a message without structure.
Format:
Direct messages delivered in the system are viewable within the system, including XML documents, HL7 messages, PDF, Word, Excel, etc.
Secure email allows documents of varying formats to be attached, but relies on third party viewers.
Download:
Content delivered in Direct messages via the system can be downloaded in the native format or can be converted to a PDF, but the system does not allow the content to be saved in the cache of the local device.
Content delivered via secure email is downloaded to the local device and must be converted to store in many systems, and “cleaned up” on the local device.