Skip to content
LiteStreamNews
Menu

← All news

GDPR and Video Consultations: Consent, Recording and AI Transcripts 

Why consent is usually not your lawful basis for treating patients, what you still have to tell them about recording and AI transcripts, and what to ask a vendor.

Featured image alt text A clinician reviewing data protection requirements for video consultations

GDPR and Video Consultations: Consent, Recording and AI Transcripts 

The question practices usually ask first is whether they need the patient’s consent to record a consultation. It is a reasonable question, and it is the wrong place to start, because it mixes up two different things that the law keeps apart. 

One is your lawful basis for processing health data at all. The other is what you have to tell the patient, and what you have to agree with them, before you press record. Getting the first one wrong creates a problem you will not notice for years. Getting the second one wrong creates a problem on the day. 

Why consent is usually not your lawful basis 

Health data is a special category of personal data. The starting position under Article 9 of the GDPR is that processing it is prohibited, except in the limited circumstances the Article sets out. 

One of those circumstances, at Article 9(2)(h), covers health and social care purposes. In Ireland this is given effect by section 52 of the Data Protection Act 2018, which makes processing of special category data lawful where it is necessary for a set of health purposes including preventative or occupational medicine, medical diagnosis, the provision of medical care or treatment, and the management of health or social care systems and services. 

Two conditions sit on top of that, and both matter. 

Suitable and specific measures. The processing must be subject to suitable and specific measures to safeguard the fundamental rights and freedoms of data subjects. This is a precondition, not a nice-to-have. 

Who does the processing. It is lawful only where it is undertaken by or under the responsibility of a health practitioner, or a person who owes a duty of confidentiality to the data subject equivalent to that which a health practitioner would owe. 

The practical consequence is the part that surprises people. If you are relying on section 52 to treat patients, you are not relying on consent, and you should not describe it as consent in your privacy notice. Treating consent as the basis for clinical processing creates an awkward implication, which is that a patient could withdraw it and oblige you to stop processing their clinical record. That is not how care works, and it is not what the law requires. 

So where does consent come in? 

It comes in for the things that are not the care itself. 

Recording a consultation is the clearest example. The Medical Council’s telemedicine guidance for doctors says patients should be told whether the consultation will be recorded, that notes go into their medical record, and whether their information will be shared with other healthcare professionals. Where a recording is made, guidance is that it is kept in the patient record. That is a professional obligation about transparency and trust, and it sits alongside your data protection duties rather than replacing them. 

The same logic applies to transcription and automated note drafting. A patient who expects a doctor to be typing is not expecting the conversation to be captured and processed by a third party’s software. Telling them is not optional, and it takes about fifteen seconds. 

One distinction worth holding onto, from a DPC case study: consent to collect information is not consent to disclose it elsewhere. In that case the regulator accepted a claimant had consented to an insurer seeking medical information, but found the subsequent disclosure to a third party was a separate contravention. Each disclosure needs its own justification. 

The vendor question, and why section 52 makes it sharper 

Here is where remote consultation platforms, transcription services and AI note tools come in. 

Section 52 requires the processing to be undertaken by or under the responsibility of a health practitioner, or by someone owing an equivalent duty of confidentiality. A software vendor processing your consultation audio is not a health practitioner. It has to be operating under your responsibility, as your processor, on a proper contract, or be in a position to owe that equivalent duty. 

That translates into things you can actually check: 

  • A written data processing agreement that meets the requirements of Article 28, naming the subject matter, duration, nature and purpose of processing, the types of data and categories of data subject. 
  • A list of sub-processors, and a commitment to tell you before it changes. The AI model provider behind a transcription feature is a sub-processor. 
  • Where the data is stored and processed, and what happens if any of it leaves the European Economic Area. 
  • Whether your data is used to train the vendor’s models, and if so, on what basis. For health data the honest default should be no. 
  • Retention: how long audio, video and transcripts are kept by the vendor, and how deletion is evidenced. 
  • Security measures, breach notification timelines, and what help you get with access requests and DPIAs. 

A vendor that cannot answer these quickly has not thought about health data, whatever its marketing says. 

When you need a Data Protection Impact Assessment 

Often, for this kind of service. The Data Protection Commission publishes a list of processing operations that require a DPIA in Ireland. Processing special category data on a large scale is a direct trigger. The list also includes large-scale processing where the Data Protection Act 2018 requires suitable and specific safeguards, which is exactly the situation section 52 creates. 

The DPC also identifies the use of new or novel technologies, and the processing of sensitive data as defined in Article 9, as factors indicating high risk. A video consultation platform with AI transcription and visual analysis ticks several boxes at once. 

The Medical Council’s telemedicine guidance points in the same direction, suggesting a Data Protection Impact Assessment as a way to identify and reduce security and privacy risks. If your practice has not done one for its remote consultation service, it is the single most useful document to put in place, and it answers most of what a patient, an insurer or a regulator will later ask. 

Recordings, transcripts and the record 

Three practical points that practices get wrong. 

A recording or transcript is part of the record, not a working file. Professional guidance is that a recording of a consultation should be kept in the patient’s medical record and that the patient is told beforehand. It does not quietly disappear once the note is signed. 

Keep only what you need, for as long as you need it. Data minimisation and storage limitation are core principles. If a transcript exists only to produce a note, decide deliberately whether the audio needs to survive the note, write that decision down, and apply it consistently. 

Patients can ask for it. A recording of a person is their personal data, and the right of access applies. In one DPC case about a recorded online meeting, an organisation tried to withhold video and offer transcripts instead; after the DPC pressed the point, the full video was released. That was not a clinical setting, and the analysis of other people in frame would be different in a consultation, but the underlying point stands: if you hold it, expect to be asked for it. 

What to say to the patient 

This takes a few seconds at the start of a call. Adapt it to your service and have it reviewed before you adopt it. 


Sample wording, to be reviewed before use 

“Before we start, two quick things. This consultation is being transcribed so that I can write up your notes accurately, and the transcript and my notes go into your medical record, the same as they would if you were here in person. Nobody outside your care team sees them unless you ask me to share them or I have to tell you I am sharing them. 

If you would rather I did not use the transcription, that is completely fine and the consultation goes ahead exactly the same way. 

Is there anyone else in the room with you?” 


The last question is doing two jobs: it is a confidentiality check, and it tells you who else is contributing to the consultation. Both belong in the note. 

A checklist for a remote consultation service 

  • Your privacy notice describes the correct lawful basis for clinical processing, and does not call it consent. 
  • Your processing meets the suitable and specific safeguards condition, and you can say what those safeguards are. 
  • Every vendor touching consultation data has a signed Article 28 data processing agreement, with sub-processors listed. 
  • You know where consultation data is stored and processed, and whether any of it leaves the EEA. 
  • You have a written answer on whether vendors use your data for model training. 
  • You have a DPIA for the service, reviewed when the service changes. 
  • Patients are told about recording and transcription before the consultation starts, in plain language. 
  • Recordings and transcripts are retained in the patient record under a stated retention period. 
  • Someone owns access requests, and knows that recordings are in scope. 
  • Your breach process covers the vendor, with agreed notification timelines. 

Where LiteStream fits 

Two design decisions are relevant here, and they are ones you can see from the outside. Patients join a consultation by a secure link or a six-character access code, without creating an account, so the platform is not building a patient-side profile to hold a consultation. And every clinical note drafted from a transcript is reviewed and approved by the clinician before it is saved, so the clinician remains the person responsible for what enters the record. 

For anything beyond that, ask us for the specifics rather than taking them from an article. The questions in the vendor section above are the right ones, and any practice considering LiteStream should put them to us in writing and get a data processing agreement before a single consultation takes place. Our privacy policy is the reference for how we handle data, and it is linked from every page of the site. 

LiteStream is in working beta, and we are adding trial partners now. 

Frequently asked questions 

Do I need a patient’s consent under GDPR to provide care remotely? 

Usually not as your lawful basis. Health data processing for the provision of care is addressed by Article 9(2)(h) of the GDPR, given effect in Ireland by section 52 of the Data Protection Act 2018, subject to suitable and specific safeguards and to the processing being carried out by or under the responsibility of a health practitioner or someone owing an equivalent duty of confidentiality. 

Do I need to tell patients if a consultation is being recorded or transcribed? 

Yes. Medical Council telemedicine guidance is that patients should be told whether the consultation will be recorded, that notes go into their record, and whether information will be shared with other professionals. 

Where should a recording be kept? 

Professional guidance is that a recording of a consultation is kept in the patient’s medical record, with the patient informed in advance. 

Can a patient ask for a copy of the recording? 

A recording of a person is their personal data and the right of access applies. Handling other people who appear in a recording needs care, and is a question to take advice on. 

Do I need a DPIA for a video consultation platform with AI transcription? 

Very likely. Processing special category data on a large scale is a direct trigger on the DPC’s published list, and the use of new technologies and sensitive data are both flagged as high-risk factors. 

This article summarises published legislation and regulatory guidance and is not legal advice. Data protection law is fact-specific. Take advice on your own service before relying on anything here. 

Want the data protection answers in writing before you trial anything? Request early access and join the clinician waitlist. 

Sources 

  1. Regulation (EU) 2016/679 (GDPR), Article 9. https://eur-lex.europa.eu/eli/reg/2016/679/oj 
  1. Data Protection Act 2018, section 52 (processing of special categories of personal data for Article 9(2)(h) purposes). https://revisedacts.lawreform.ie/eli/2018/act/7/section/52/revised/en/html 
  1. Data Protection Commission. Special Category Data. https://www.dataprotection.ie/en/organisations/know-your-obligations/lawful-processing/special-category-data 
  1. Data Protection Commission. List of types of data processing operations which require a Data Protection Impact Assessment. https://www.dataprotection.ie/sites/default/files/uploads/2018-11/Data-Protection-Impact-Assessment.pdf 
  1. Data Protection Commission. Case study: processing of health data. https://www.dataprotection.ie/en/dpc-guidance/case-studies/transparency/processing-health-data 
  1. Data Protection Commission. Case study: request for footage from an online meeting. https://dataprotection.ie/en/dpc-guidance/case-studies/access-request-complaints/request-footage-online-meeting 
  1. Medical Council of Ireland. Telemedicine: A Guide for Doctors. https://www.medicalcouncil.ie/existing-registrants-/telemedicine-a-guide-for-doctors/ 

Related stories