Context card
What an answer function may read: retrieval permissions for a medical-device technical file
Which parts of a medical-device technical file may an AI answer function retrieve?
The short answer
Only the parts released for the reader it answers, in the version and language that apply to the reader’s device. Confidential parts of the file, personal data from vigilance and complaints, unreleased drafts and translations and superseded versions stay out of its reach unless the reader is entitled to them. Retrieval permissions are decided per source and per reader before the function is built, and generated text is reviewed before it is released.
For: Documentation systems developers, technical writers and quality managers in MedTech
Key points
- A technical file mixes public information (IFU, SSCP) with confidential design and supplier data.
- Vigilance and complaint records hold health data protected under the GDPR.
- An unreleased translation or a superseded IFU is not a source for a user answer.
- Source authority: when two sources disagree, a rule decides which counts — never the retrieval score.
- Generated content that becomes part of labelling or the file is reviewed and released like any other content.
The context
Why this is a documentation question
A retrieval-augmented answer function reads whatever its index holds. A medical device technical file holds very different things: the IFU and the Summary of Safety and Clinical Performance, written for users and the public; design and manufacturing data, supplier agreements and test protocols, which are confidential; and records from vigilance, complaints and post-market surveillance, which contain health data about people.
Five questions per source
- Who may read it? Public, the deploying organisation, service staff, internal only. Role-based access control is set per reader of the answer, not per developer of the function.
- Is it released? Drafts, open reviews and unreleased translations are not sources for answers (document control).
- Is it valid for this device? Version, variant, market and language must match the reader's device; superseded versions are kept for the record, not for answers.
- Does it contain personal data? Vigilance and complaint records stay out unless the reader is entitled and the purpose is lawful; the GDPR applies to health data.
- Which source wins? When the IFU and a service note disagree, a source-of-truth rule decides — not the retrieval score.
Generated content
An answer is not labelling. When generated text is taken into the IFU, a service manual or the file, it is reviewed and released like any other content, with the sources it came from (content provenance).
What this card does not say
It does not assess any product or service. Whether an answer function is itself a medical device depends on its intended purpose; check that before building one for clinical users.
Questions readers ask next
- May a service chatbot answer from the full technical file?
- Only from the parts released for service staff, in the version of the device in front of them. Confidential design data and personal data from vigilance stay out unless there is a reason and a right to use them.
- Is an answer function for clinicians a medical device?
- It can be, if its intended purpose is medical — for example supporting decisions about a patient. That has to be checked before it is built.
Sources
- Regulation (EU) 2017/745 on medical devices (MDR) — EUR-Lex, 5 May 2017Law in force: Binding legislation that applies as of the review date.
- Regulation (EU) 2016/679 (General Data Protection Regulation) — EUR-Lex, 4 May 2016Law in force: Binding legislation that applies as of the review date.
- Regulation (EU) 2024/1689 (Artificial Intelligence Act) — EUR-Lex, 12 July 2024Law in force: Binding legislation that applies as of the review date.
Review log and changes
Every context card is checked against its sources before it is published, and again whenever it changes; the date under the byline is the last review. Corrections (something was wrong) and additions (something was missing) are logged below with date and time (Berlin time). Typos, formatting and link fixes are not listed.
Reviewed
No corrections or additions since publication.