Updated 21 October 2026.
An AI tool does not become a medical device simply because a doctor uses it. Nor can a supplier necessarily avoid device regulation by describing clinically consequential functionality as "just information". The relevant question is what the product is intended to do, how it is designed and presented, and which rules apply to that function.
For clinicians, this is useful knowledge rather than an invitation to become a regulatory lawyer. It helps identify the evidence to request, the limits of a supplier's claims and the point at which a new feature should receive a fresh governance review.
Start with intended purpose, not the technology label
The MHRA's software and AI guidance provides the starting point for understanding qualification. Software intended for a medical purpose may fall within device regulation. The assessment is not determined by whether the supplier uses machine learning, a language model or conventional code.
A basic document-search function and a patient-specific recommendation system can both appear conversational. Their interfaces may look similar while the intended outputs differ. Conversely, a familiar calculator can be medically consequential without containing anything marketed as AI.
Read the instructions, product description and promotional claims together. Ask whether the software is intended to influence diagnosis, monitoring or treatment in a specified way. Do not rely on a short disclaimer that conflicts with the practical promise being sold.
Documentation and decision support need separate consideration
The MHRA's July 2026 AVT guidance distinguishes functions when discussing qualification and classification in Great Britain. Administrative transcription and documentation functions should not simply be equated with software that generates new clinical recommendations.
However, the word "scribe" is not a permanent exemption for every feature in a product. A platform may add coding, decision support or other medical functions. Those additions need to be considered on their own terms, including how they interact with the original workflow.
Equally, clinician review is not an automatic answer to qualification. Many medical devices support professionals who retain responsibility for decisions. The fact that a doctor reads an output does not by itself establish that the software is outside regulation or belongs in the lowest class.
Reference and education have important boundaries
A digital textbook, general learning exercise or simple document viewer may have a different regulatory position from software intended to analyse a patient's information and recommend an action. The boundary depends on the actual product and claims, not on a universal rule that reference is always unregulated.
A clinician should also distinguish using a source for education from putting identifiable patient information into a service. Information-governance requirements remain relevant even where a function is not a medical device. "Not a device" does not mean "no responsibilities".
For learning, fictional or appropriately abstracted scenarios can often address the educational need without reproducing a clinical record. For patient-specific organisational use, follow the approved workflow and assess the product's intended purpose and data arrangements.
What CE and UKCA marking tell you
These marks relate to conformity with the applicable requirements for the device's route and intended purpose. They are not universal ratings of model intelligence or clinical accuracy. The assessment process varies with classification and the framework.
European software guidance should be used when interpreting EU qualification and classification. Great Britain's rules should be considered separately rather than assuming that an EU classification slogan automatically resolves a British question.
For many Class I devices, conformity is declared by the manufacturer, with specific exceptions. Higher-risk routes generally require an appropriate independent assessment body. The precise documentation matters more than a vendor's generic phrase "fully certified".
The October 2026 CE decision corrects the old expiry narrative
The government's published outcome confirms an intention to implement indefinite recognition of EU MDR and EU IVDR devices, alongside changes to relevant legacy-device transitions. It is no longer accurate to describe eventual compulsory UKCA for all recognised devices as the government's settled destination.
The announcement does not make every implementing change immediately operative. Manufacturers must track the applicable legal requirements while the policy is implemented. Nor does indefinite recognition mean that an old certificate remains valid regardless of its conditions or subsequent product changes.
The policy concerns Great Britain. Northern Ireland's arrangements should be checked separately. This territorial distinction is especially important when a supplier casually says that one registration or mark covers "the UK" without further explanation.
Registration is a different obligation
MHRA registration guidance explains the relevant Great Britain requirements. A registration entry is not a blanket agency endorsement of clinical performance, and CE recognition does not replace registration.
A useful supplier response identifies the legal manufacturer, product, intended purpose, conformity documentation and current registration position. A claim about the company as a whole is not enough where it offers multiple functions or versions.
For iatroX, the same discipline applies. Its published positioning has described a UKCA Class I, MHRA-registered clinical-information product. That statement should be understood within the stated scope, not as agency approval of every generated answer or automatic certification of every educational feature. iatroX's methodology separately explains its clinical-information and learning design.
Regulation does not replace deployment judgement
A recognised medical device can still be inappropriate for a particular workflow. It may lack local validation, produce an unsuitable output or require a review process the service cannot support reliably. Those issues need their own assessment.
NHS DTAC and the clinical safety standards provide relevant assurance structures. Buyers should investigate the actual configuration and evidence rather than treating a conformity mark as permission for any clinical use.
A sensible evaluation includes routine use and foreseeable difficulties: missing information, ambiguous language, interruptions and incorrect outputs. It should identify who notices a problem, who can correct it and what evidence is retained for investigation.
A practical three-question check
First, ask what the software is intended to do. The answer should be specific enough to distinguish documentation, reference, learning and patient-specific recommendations. Second, ask what regulatory position and evidence support that function in the relevant territory. Third, ask what remains necessary for your local use.
These questions help avoid two opposite mistakes: assuming every AI tool needs the same conformity route, and assuming that a convenient educational label removes all obligations. They also make comparisons between products more useful.
The aim is not to choose the tool with the most impressive badge. It is to choose a product whose purpose, evidence and deployment are aligned, then use it within those boundaries.
Frequently asked questions
Is every AI application used by doctors a medical device?
No. Qualification depends on intended purpose and functionality under the applicable framework. General administrative and educational tools can differ from software with a specified medical purpose.
Does a clinician checking the answer remove device obligations?
Not automatically. Human review can be an important safety control, but it does not by itself determine whether the software is a device or which class applies.
Will all CE-marked devices eventually need UKCA?
That is no longer the government's stated destination. The October 2026 decision is to implement indefinite recognition of EU MDR and EU IVDR devices, with applicable domestic obligations and separate legacy-transition arrangements.
Keep the tool within the task
Explore how iatroX works across source-linked reference, clinical reasoning practice and structured learning.