Neither deleting everything nor retaining everything is a defensible default for every healthcare AI workflow. Different records serve different purposes: a raw recording, an approved clinical note and evidence needed for an incident may require different treatment. Define the purpose, necessity, access and retention decision for each category, with an authorised process for exceptions.
This article is dated 10 October 2026 and focuses on NHS care in England within UK data-protection requirements. The ICO's storage-limitation guidance does not prescribe one universal retention period for all personal data. It requires a justified approach rather than indefinite storage without a defined need.
A consultation produces several different records
Consider a fictional service using an AI scribe. It captures audio, creates a transcript, generates a draft, stores the approved note in the clinical record and keeps technical information about processing. A support ticket is later opened about a disputed sentence.
Calling all of these "the consultation data" hides important differences. The approved note supports continuing care. The raw audio may have served the immediate drafting and checking process. Technical logs may support reliability or investigation, while the support ticket has its own access and retention arrangements.
The organisation should know which copies exist before deciding what to keep. Otherwise a deletion promise may refer only to the visible conversation while other copies remain, or an aggressive deletion process may remove evidence needed for an unresolved incident.
Retention should follow purpose, not file format alone
A transcript may be unnecessary after an adequate approved record is completed, but a relevant extract may need preservation during a particular investigation. An audio file may contain far more sensitive third-party detail than the final note, making routine long-term retention a separate question from retaining the clinical record.
NHS ambient-scribing guidance for information-governance professionals, checked on 10 October 2026, explains that recordings and transcripts may be deleted after the summary is approved as accurate and adequate, unless further retention is needed for safety or accuracy. That is a scoped statement, not an instruction to delete every record immediately or retain every recording indefinitely.
The decision should be documented in the actual processing arrangement. Staff and patients should not have to infer it from a button labelled delete or from an assumption that all healthcare information follows one schedule.
Build a retention matrix before the service goes live
The following proposed matrix is a starting point for clinical, records-management, legal and information-governance teams. It deliberately does not supply universal time periods.
| Data category | Main purpose to establish | Decision to document |
|---|---|---|
| Raw audio | Capture and any justified checking or investigation | When routine retention ends and who can authorise an exception |
| Transcript | Drafting, review or defined evaluation | Whether the whole transcript remains necessary after approval |
| Unapproved draft | Review and correction | What is retained after replacement by the approved record |
| Approved clinical record | Continuing care and applicable record obligations | The relevant records-management schedule |
| Technical logs | Reliability, security and reconstruction | Which fields are necessary and how access is restricted |
| Safety evidence | A specified incident or investigation | Scope, preservation authority and review of continuing need |
| Support material | Resolving the reported issue | Necessary content, recipients and deletion arrangements |
Each row should identify where copies exist, including backups and external providers. A supplier's standard retention period is relevant information, not automatically the appropriate answer for every purpose in the organisation's deployment.
Plan the exception process rather than relying on informal requests
A patient complaint, access request, investigation or legal issue may affect the treatment of relevant information. The organisation needs an authorised process for identifying that material and reconciling preservation with routine deletion.
This article does not determine which legal hold applies to a particular event. The practical recommendation is to identify who can obtain advice, issue a preservation instruction and record its scope. A clinician should not respond by keeping private copies of every consultation in anticipation of possible disputes.
The process should also have an endpoint. Evidence retained for a specific issue should be reviewed when that purpose changes or ends. Otherwise temporary exceptions can quietly become permanent archives without anyone reassessing necessity.
Deletion and correction are not the same operation
If a patient disputes a statement in the clinical record, deleting the raw recording does not determine whether the statement is correct. Retaining the recording also does not guarantee that it resolves every disagreement: meaning, interpretation and incomplete capture can remain contested.
The record should be reviewed through the appropriate clinical and information-governance process. A correction needs to preserve the distinction between the original entry and later amendment where required, rather than pretending that the disputed version never existed.
The ICO's health-information access guidance also illustrates why requests involving clinical and third-party information need contextual handling. A retention policy should support lawful access and review processes without promising that every recording will always be available or that every deletion request can always be fulfilled immediately.
Test what the system actually does
A proposed implementation test should follow one synthetic encounter through capture, approval, routine deletion and an authorised preservation exception. Check the main application, linked systems, support workflow and relevant supplier arrangements.
Ask whether a user can tell the difference between deleting a draft from view and deleting the underlying stored data. Establish how backup retention works and how the organisation would explain it accurately. These are verification questions, not claims about a particular supplier's technical behaviour.
Also test exit. If the organisation stops using the product, what approved records, unfinished work and necessary safety evidence remain accessible? A subscription ending should not unexpectedly determine the fate of information the organisation needs for continuing care or an active investigation.
Retain less where the same purpose can be achieved safely
The useful choice is not always whole-record retention versus no evidence. Depending on the purpose, a limited event record, version identifier, relevant extract or aggregate measure may be sufficient. That possibility requires assessment; an extract that removes the disputed context may be inadequate for investigation.
For reference and learning tools, avoid creating a patient-data retention problem unnecessarily. Ask a general clinical question rather than uploading a recognisable consultation. As published in iatroX's policy checked on 10 October 2026, finalised simulation transcripts, Tutor conversation text and assessment results are normally retained for up to 180 days. That statement concerns educational simulation data, not a retention schedule for NHS patient records or every iatroX data category.
A good retention policy is explainable: this information is kept for this purpose, accessible to these people, for this justified period, with these exceptions. That is more useful than either an impressive promise of total deletion or an indefinite archive described as necessary for safety.
Frequently asked questions
Is there one correct retention period for all healthcare AI data?
No. The purpose, type of record, applicable obligations and justified need must be considered, rather than applying a universal period to audio, notes and technical logs alike.
Should all recordings be kept in case a patient later disputes the note?
Not automatically. The potential evidential value needs to be weighed and governed alongside necessity, privacy and the applicable retention arrangements.
Does deleting a conversation from the interface prove every copy has gone?
Not necessarily. The organisation should establish what deletion means for underlying storage, backups, logs, support material and any authorised preservation exceptions.
Explore the clinical question without uploading the consultation record →