We got the following question from a ThinLinc potential user:
Question:
"I am exploring options for remote access for numerous doctors who connect to a single local computer and found ThinLinc during my research. I am still in the very early stages of implementing any plan but would like to get some basic information.
Is ThinLinc HIPAA compliant? Also, is the connection reliable/have low latency? All computers, including the host system, are within the same state. The PHI would only be on one computer and never leave this computer other than when documents need to enter the patient record via the secure EHR."
Answer:
ThinLinc is designed to provide access for multiple users to a single Linux machine or cluster, so if Linux is your target OS, it should work well for your needs.
HIPAA Compliance:
Regarding your question about compliance, the information we found indicates that software itself cannot be certified as HIPAA compliant. Compliance depends on how the software is used and configured. ThinLinc can support HIPAA compliance through:
- Encryption: Secure data transmission via SSH/TLS.
- Access Control: Integration with systems like Active Directory and various authentication methods.
- Audit Logging: Detailed logging for tracking access and activities.
Connection Reliability and Low Latency:
ThinLinc provides a reliable and responsive remote desktop experience, comparable to local sessions. Key features include:
- Low Bandwidth Optimization: Ensures smooth performance on low-bandwidth networks.
- High Availability: Supports load balancing and redundancy.
- Local Experience: Supports multiple screens, local and server printers, and peripheral devices.
Data Transfer Configuration:
ThinLinc can be configured to prevent data transfer from the server to the client, ensuring that PHI remains on the designated computer. Features such as disabling file transfer capabilities and controlling clipboard access help ensure that sensitive data does not leave the secure environment. This can be crucial for maintaining the integrity of PHI and complying with HIPAA regulations.
Sources:
- HIPAA Journal on Software Compliance
- ThinLinc Blog on Compliance - Using ThinLinc in systems that need to conform to NIST 800-53/-171, HIPAA, FISMA or similar regulations
I hope this helps clarify the capabilities and considerations for using ThinLinc in a healthcare setting.
Best regards,
Jean