Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
Telehealth security protects remote consultations, messaging, and home monitoring, where clinical care crosses networks, devices, and homes that the provider does not control.

What Is Telehealth Security?
Telehealth moved from a pilot to normal practice in a matter of weeks in spring 2020, and the security model has been catching up ever since. It covers video and telephone consultations, asynchronous messaging between patients and clinicians, remote monitoring of long-term conditions, virtual wards, and the e-prescribing and referral flows that follow a remote appointment. Telehealth security is the work of protecting all of that when the consultation room is a kitchen table and the network is somebody’s home broadband.
The hard part is not the video platform. It is everything around it: how the patient is identified, where the recording goes, which device the clinician used, and what happens to the data afterwards.
Health data is special category personal data, so a telehealth service needs an Article 9 condition alongside its lawful basis, and a data protection impact assessment is expected for a new remote service. The common law duty of confidentiality and the Caldicott Principles apply as they do in a clinic.
Clinical safety is the part that technology teams most often miss. Deploying health IT in the NHS engages the standards DCB0129 for manufacturers and DCB0160 for deploying organisations, which require a named clinical safety officer, a hazard log, and a clinical safety case. A video consultation platform is health IT for these purposes, and so is an automated transcription tool that writes into the record.
Where a telehealth tool performs a medical function rather than simply carrying a conversation, for example triage that recommends a course of action, it may be a medical device regulated by the MHRA under the Medical Devices Regulations 2002, and the MHRA’s software and artificial intelligence change programme is the relevant guidance. Larger NHS providers also work to the Data Security and Protection Toolkit, which NHS England has been realigning with the NCSC Cyber Assessment Framework.
Where a remote care platform needs testing before it carries real consultations, our web application security services cover the booking, identity, consultation, and record-writing paths together.
Only where the enterprise or healthcare edition is contracted with the right data protection terms, configured to prevent recording and external joining, and covered by a clinical safety case. Consumer accounts routinely lack a processing agreement, retain data in uncontrolled locations, and enable features that breach confidentiality by default. The platform choice is a governance decision, not an IT convenience.
Consent is not usually the lawful basis for processing health data in direct care, but recording still requires a specific decision, a clear explanation to the patient, and a documented basis and retention period agreed with the Caldicott Guardian. Default to not recording. Where a recording is made, it is part of the clinical record and must be accessible, secured, and deleted on schedule.
It can be. Software that performs a medical purpose such as diagnosis, prediction, or recommending treatment falls within the UK medical devices framework regulated by the MHRA, whereas software that only carries a conversation or books an appointment generally does not. The classification should be settled before procurement, because retrofitting conformity assessment to a deployed product is expensive.
Ask at the start whether the patient can speak freely and offer alternatives: switching to a telephone call, using yes and no questions, rescheduling, or arranging an in-person appointment. Train clinicians on the pattern, particularly for mental health, sexual health, and safeguarding contexts. This is a clinical safety control, and it belongs in the consultation protocol rather than in the security policy.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.