Who Is Required To Comply With HIPAA?
Not all operations that handle health-related information must follow HIPAA law (such as many schools, state agencies, law enforcement agencies, or municipal offices). Under HIPAA the 2 groups that must follow HIPAA rules are
OrthoLive would be considered the business associate of a covered entity that uses OrthoLive in communicating private health information with a client.
Is A Software Vendor Considered a Business Associate Under HIPAA?
It depends. If a vendor or subcontractor transmits, maintains, or has routine access to protected health information (PHI) when providing its services to a covered entity then it is considered a business associate. For example, a vendor that hosts the software containing patient information on its own server or accesses patient information when troubleshooting the software, then it is considered a business associate and must have a business associate agreement with the covered entity as specified under the HIPAA Privacy Rule 45 C.F.R. § 164.504(e).
While OrthoLive never has access to any information, health or otherwise, that you may observe, transmit, or receive by using OrthoLive, it is still considered a business associate because it is used to transmit private health information over the Internet. To be HIPAA-compliant, a covered entity using OrthoLive for this purpose must have a Business Associate agreement with OrthoLive.
How is HIPAA involved in your use of video conferencing?
Videoconferencing may involve the electronic exchange of health information which is protected under HIPAA law. Security considerations with videoconferencing may involve making sure unauthorized third parties cannot to record or “listen in” on a videoconferencing session, making sure recorded videoconferencing sessions are stored and identified in a secure and proper manner, or having a procedure for initiating and receiving video calls. Other video collaboration features affecting security may include text chat, screen-sharing, and file-transfer.
Videoconferencing would only be one small piece to consider when establishing and maintaining HIPAA-compliant IT security standards as described by the Privacy Rule and the Security Rule.
How does OrthoLive allow you to comply with the HIPAA Privacy and Security Rules?
OrthoLive has several characteristics that make it easy to protect the confidentiality of protected health information:
OrthoLive uses a managed peer-to-peer architecture, where video (and other media) are streamed directly from endpoint to endpoint. Information is never stored on any OrthoLive servers or intercepted by OrthoLive in any way. The OrthoLive management server is only used for address look up, connection brokering, and system/user administration. This prevents information leakage between point A and point B.
Encryption adds another layer of security of OrthoLive. All OrthoLive traffic is encrypted with FIPS 140-2 certified 256 bit Advanced Encryption Standard. No servers, including OrthoLive’s, have access to the decryption keys. This keeps keeps your videoconference absolutely confidential.
OrthoLive allows users to record videoconferences and keeps chat history that could be regarded as electronic protected health information (e-PHI). These files are stored on a user’s computer and are not accessible to OrthoLive. Covered entities may securely save recorded conferences or chat histories to their own HIPAA compliant electronic health record (EHR) system.
Does data have to be encrypted to be HIPAA compliant?
“While covered entities and business associates are not required to follow the guidance, the specified technologies and methodologies, if used, create the functional equivalent of a safe harbor, and thus, result in covered entities and business associates not being required to provide the notification otherwise required by section 13402 in the event of a breach.” (p. 19008)
Encryption processes that have been tested and meet the guidance standard:
(i) “Valid encryption processes for data at rest are consistent with NIST Special Publication 800–111, Guide to Storage Encryption Technologies for End User Devices.” (p. 19009-10)
(ii) “Valid encryption processes for data in motion are those that comply with the requirements of Federal Information Processing Standards (FIPS) 140–2. These include, as appropriate, standards described in NIST Special Publications 800–52, Guidelines for the Selection and Use of Transport Layer Security (TLS) Implementations; 800–77, Guide to IPsec VPNs; or 800–113, Guide to SSL VPNs, and may include others which are FIPS 140–2 validated.” (p. 19009-10)
OrthoLive does not store any of your data. All OrthoLive traffic is encrypted with FIPS 140-2 compliant 256-bit Advanced Encryption Standard.
Official Documentation For HIPAA