How to Choose the Right Video Conferencing Tool for Digital Healthcare
Telemedicine is a true game changer in the Healthcare Technology field, making it very easy for patients to see their doctors without having to leave home. Thanks to Telehealth and video chats patients can now talk to their doctors, get diagnosed, and even have their health monitored remotely without having to wait long hours in the waiting rooms.
Given the right tools like digital stethoscopes or thermometers and real-time instructions on how to perform the measurements, doctors can recreate the same diagnosis as in a real-life visit.
But with all this happening online there’s a big question mark over keeping all the patient data private and secure, but also accurate. Choosing a video provider is therefore a strategic and critical decision.
What will you find in this article?
1. The differences between GDPR and HIPAA
2. Provide possible choice categories of video conferencing providers
3. Give you a developer perspective on what’s important when choosing a provider
4. What to look for when choosing a solution dedicated for healthcare
5. What providers are available and most popular in 2024
This year started with some of our clients asking us to help explore the possibilities of shifting from one of the major video providers that will decommission its video API by the end of 2024. This has put a lot of stress on some organisations, forcing them to act fast and look for a substitute.?
The mentioned provider highlights ZOOM as a potential replacement, but given the backlash of the 2020 data breach, and constant phishing attacks performed in ZOOM’s direction it’s hard to be 100% confident about its stability and safety. In all fairness, ZOOM has done a lot of work to improve their safety and no major breach has happened since 2020, but being one of the leaders always puts you in the “hacker spotlight”.?
In this article, we will provide key information you need to make an educated decision when choosing a video conferencing tool.
Compliance with GDPR vs HIPAA
What is the purpose of those regulations?
What are the differences between HIPAA and GDPR??
The Health Insurance Portability and Accountability Act (HIPAA) was enacted in 1996 in the U.S. to ensure the privacy and security of individuals’ health-related data, called Protected Health Information (PHI).
What is considered as PHI:?
Individual’s full name. Residential details include city, street, country, and postal code (anything more detailed than the state). Key life events and related dates, such as birth, hospital admission, discharge, passing away, and precise age for those 90 or older, except year details. Contact numbers, both landline and mobile. Numbers associated with fax machines. Email contact details. Social security numbers. Medical record numbers. Number related to an individual’s health plan benefits. Banking or financial account identifier. Numbers associated with licenses or certificates. Identification of automobiles and their associated serial numbers, including registration plate data. Identifiers associated with devices and their related serials. Website addresses. IP addresses used for internet connections. Biometric identifiers like voice or fingerprint patterns. Photographic images and other unique identifying features.Any distinguishing feature or detail that could single out the individual.
The General Data Protection Regulation (GDPR), enacted in May 2018, represents the European Union’s efforts to safeguard its citizens’ data, protecting Personally Identifiable Information (PII).
What is considered PII:?
Names Email addresses, Location information, Ethnicity, Gender, Biometric data, Religious beliefs, Web cookies, Political affiliations/opinions, Pseudonymous data (if it’s easy to identify someone from it)
Source: Medstack.co https://medstack.co/blog/hipaa-vs-gdpr/#:~:text=HIPAA%20applies%20to%20covered%20entities,regardless%20of%20the%20organization's%20location.
In layman's terms, Peer to Peer is what you need to understand. If a patient-doctor video call is to be HIPAA or GDPR-compliant the data needs to flow directly from one user to another without any third parties (servers) storing this data in between.
What choices do you have when deciding on a Telehealth video provider?
An honest answer to a question about the best video provider solution for your venture is as you might already know is: it depends. There are both business and technical factors that need to be taken into consideration and the decision must be a calculated one.?
We can only provide you with the spectrum of options that are at your disposal. So here they are.
Integrating native video conferencing into your Telehealth application can seem highly effective. This method offers a lot of flexibility and room for customisation, it ensures full control over the user experience.?
But “with great power comes great responsibility”.
Building a video conferencing tool is a startup in itself. This approach is best for companies with big budgets, definitely not an option for startups on VC funding. Yes, it offers a lot of flexibility and opens the door for new monetisation methods but it also leaves YOU to adjust and comply with all regulations and place all the risk that comes with it in your hands.
So not only is it a huge expense but also extra time-consuming when applying to get all the certificates.
Open-source solutions are usually a “smart choice”. It leaves you some room for customisation but takes the load of building the solution's core feature.?
Usually, I recommend it to startups as a first choice when they are already after the MVP stage. It requires some budget to build but in time the benefits start to show with time. However, they are not GDPR or HIPAA compliant by default.?
Take “Jitsy”, one of the more popular open-source video providers which we have integrated in the past. Even if it does not store conversation contents by default, it does process personal data to operate and store browsing data and conversation metadata in logs. Although it implements client-server encryption it does not implement end-to-end encryption between clients, so it has to be properly configured, to be GDPR compliant.
In other words, you can implement the solution in a compliant way, but it does not mitigate the “legal’ risk to a third party.
This is probably the most popular road that founders take when incorporating a video conferencing solution into their telehealth venture. It’s the most risk-averse option. But just like with the discontinuation of the API that we mentioned at the beggining, choosing an external provider might prove irritating in the future.
They offer all the basic features like calendar integrations, screen sharing, chat, or document sharing. Also, they have a seemingly low entry barrier because the only challenge is to integrate via a ready-made API. For all those founders lacking the engineering resources this is a good way to start.
Of course with those solutions, there is not much room for flexibility and you become dependent on external factors. At the same time alongside the ease of integration comes a lack of risk in regards to GDPR or HIPAA compliance but also the bills will get higher when more users join your platform.
In time, when your venture scales and reaches more users the monthly cost of supporting this solution will start to grow. It’s up to you to decide when or if there is a need to change. Balance out the development cost with monthly support and if those two meet within a few years, it's probably a good idea to look for alternatives. But when starting, this is the way to go.
Side FAQ:
Is “Google Meets” HIPAA and GDPR compliant?
“Google Meet safeguards HIPAA-compliant chat through a multi-layered approach, alongside robust encryption, access controls, 2FA, and data minimisation. It adheres to HIPAA regulations via a dedicated Business Associate Agreement and GDPR compliance on top, while offering features like chat log export and reporting tools for enhanced security and record-keeping.”
Source: cometchat.com
Engineers' perspective on video Telehealth videoconferencing solutions
If an engineer could choose a video conferencing tool to integrate what would they look for?
I’ve been talking with our team trying to get their point of view. Here are a few elements that we decided to highlight.
Telemedicine video conferencing tool checklist
To summarise, allow me to present a checklist of elements to look out for when choosing a provider.
Before you decide, ask your engineers for their opinion on each solution and if the available specifications are understandable and up to date.
Good to know: WebRTC
Web Real-time communication?
With WebRTC, you can add real-time communication capabilities to your application that works on top of an open standard. It supports video, voice, and generic data to be sent between peers, allowing developers to build powerful voice- and video-communication solutions. The technology is available on all modern browsers as well as on native clients for all major platforms
Good to know: SDK vs API
APIs are used to communicate between different applications, whilst an SDK is a tool kit to build applications and features. In most cases, an SDK application will contain an API — or even multiple APIs depending on the purpose of the software.
Video conferencing tools available to healthcare providers in 2024
Please note that we are not affiliated with any of the mentioned providers. This comparison is made to help you out by mentioning the providers' “Google” and “G2” search results place as the most popular. The information provided in the below table is gathered from the official websites of these solutions.
GDPR: Yes
HIPAA: Yes
Pricing starts from 35 USD (free plan available)
Worth mentioning
ZOOM for healthcare
GDPR: Yes (only paid plans)
HIPAA: Yes (only paid plans)
Pricing starts from 149.90 USD /year/user
Worth mentioning
GetStream
GDPR: Yes
HIPAA: Yes (only in enterprise plan)
Pricing : Pay as you Go available
Worth mentioning
Go To?
GDPR: Yes
HIPAA: Yes?
Pricing : starting from 12 USD /user/month
Worth mentioning
GOOGLE Meets
GDPR: Yes (under BAA)
HIPAA: Yes (under BAA)
But…?
“Customers are responsible for … ensuring that they use Google services in compliance with HIPAA.”
Pricing : Google workspace pricing plans
Worth mentioning
MS Teams
GDPR: Yes?
HIPAA: Yes?
Pricing : MS 365 pricing plans
Worth mentioning
Whereby
GDPR: Yes
HIPAA: Yes?
Pricing : Pay as you Go available
Worth mentioning
WEBEX by cisco
GDPR: Yes?
HIPAA: Yes?
Pricing : 14.50 USD/ month/user
Worth mentioning
Strong AI focus and a dynamic ecosystem with incoming new features.
I hope you found something valuable in this article and the information shared can help you choose the video conferencing tool that is the right one for you and your organization. Also please keep in mind that we are neither favoring any mentioned tools nor trying to dissuade you from any other providers available on the market but not mentioned here.
If you need more assistance or guidance on choosing the right provider, or you are unsure if the solution you would like to implement is fitting for your current architecture, do not hesitate to reach out to us directly. Our tech experts will happily guide you through the details.
Thanks for reading
Wow! ?? The level of detail in this article about telemedicine is impressive. Especially the part about HIPAA and GDPR differences. It's so important for data protection and benefits both provider and patient!