Glossary Updates16 new terms added to the glossaries · 12 November 2026, 21:23 CET
AI TechDocKnowledge
  • English (US)
  • English (UK)
  • Deutsch
All context cards

Pathway card

From structured content to controlled evidence: five stages of AI-ready documentation

Is structured content enough to make medical-device documentation ready for AI?

A pathway card shows where a practice starts, where it can get to, what does not change on the way, and the steps from one to the other. The path from before to after

By knowledge.aitechdoc.world

Reviewed

Review log and changes

The short answer

No. Structure is the second of five stages: documents digitally available, content structured, information semantically linked, sources, versions and validity controlled, and AI output traced back to evidence. In a medical device file a warning in the IFU must not only be found; it must be linked to its risk, its risk control, its verification, the product version, the language and the released document state.

For: Technical writers, documentation managers and documentation systems developers in regulated industries

Key points

  • XML or DITA makes content addressable; it does not say what a warning is evidence of.
  • Stage 3 links content to the risk file and the verification records.
  • Stage 4 makes every element carry product version, language, released state and validity.
  • Stage 5 is the one AI needs: an answer that names the released elements it rests on.
  • Most organisations sit between stages 2 and 3; stage 5 is still research.

Before and after

Before

Structured, but not controlled

  • Content is split into typed elements.
  • Links to risk and verification live in people’s heads or in separate spreadsheets.
  • An assistant cannot tell released from draft or one product version from another.

After

Controlled evidence

  • Each element is linked to what it is evidence of.
  • Each element carries product version, language, released state and validity.
  • AI answers name the released elements they use, and the chain behind them can be shown.

Side by side

Each row names how far the control is as of the review date.

AspectBeforeAfterMaturity
1 · Documents digitally availableScanned or exported PDFs in folders.Every released document is findable with its document number and state.Building block available

DMS standard practice

2 · Content structuredWarnings are paragraphs in a word processor file.Warnings, steps and specifications are typed elements (e.g. DITA topics, hazard statements).Building block available

Structured authoring, CCMS

3 · Information semantically linkedThe warning names the hazard in prose.The warning element is linked to the hazard, the risk control and the verification that proved it.Product-specific

Requirements and content tools, varying integration

4 · Sources, versions and validity controlledNobody can say which product version a retrieved warning belongs to.Each element carries product version, language, released state and validity.Product-specific

Configuration management across systems

5 · AI output traced back to evidenceAn assistant answers from whatever text it finds.Each answer names the released elements it used, and the chain behind them can be shown.Research

Retrieval with provenance; no settled method

The path from before to after

Each step names who does it and what it leaves as evidence.

  1. Make documents findable

    Keep every released document in a controlled system with number, version and state.
    Who
    Documentation management
    Evidence
    Document register
  2. Structure the content

    Type warnings, steps and specifications as elements with stable identifiers.
    Who
    Technical writers
    Evidence
    Element model, style rules
  3. Link to the evidence

    Link each safety-related element to its hazard, risk control and verification record.
    Who
    Technical writers with risk management
    Evidence
    Trace links between content and risk file
  4. Control version and validity

    Attach product version, language, released state and validity to every element and keep them in sync with configuration management.
    Who
    Documentation systems developers
    Evidence
    Metadata rules, configuration baseline
  5. Trace AI answers

    Let answer functions retrieve only released elements of the right version and show the elements they used; review generated content before it is released.
    Who
    Documentation systems developers with quality
    Evidence
    Retrieval rules, answer log

Limits and residual risk

The stages describe documentation practice, not legal requirements. Stage 5 has no settled method yet; treat any tool that claims it with care.

The context

Why structure is only the beginning

Structured content — for example DITA topics — turns a manual into addressable elements. That is a real step: a warning becomes an element with a type, not a paragraph with a bold word. But an answer function does not only need to find the warning. It needs to know which product version it belongs to, whether it is released, in which language, and what it is evidence of.

The IFU warning as the test case

Take one warning in the instructions for use of an infusion pump: "Do not use the pump in an MRI environment." In a medical device file this sentence is the visible end of a chain. It informs the user about a residual risk; it is a risk control measure by information for safety under ISO 14971; its effectiveness has to be verified; it belongs to one product version and one language version, and only the released state counts.

At stage 2 the warning is an element. At stage 3 it is linked to the hazard and the risk control. At stage 4 it carries its version, language and release. At stage 5 an assistant that quotes it can show this chain — and refuses to quote a draft or a warning of another variant.

The five stages

The comparison below shows each stage with its maturity as of November 10, 2026. The stages build on each other: links without controlled versions give an assistant wrong answers with good references.

Where this leads

The links of stage 3 and 4 are what the medical-device evidence chain map draws station by station.

Questions readers ask next

Is DITA AI-ready content?
DITA is a strong basis for stage 2: typed, reusable elements. AI readiness also needs the links to the evidence, controlled versions and answers that show their sources.
Which stage do regulators require?
No regulation requires a maturity stage. The MDR requires consistent, traceable technical documentation and IFU; how it is produced is the manufacturer’s choice.
Can an assistant answer from stage 2 content?
It can, but it cannot tell released from draft or one variant from another unless the content carries that information — which is stage 4.

Sources

  1. Regulation (EU) 2017/745 on medical devices (MDR) — EUR-Lex, 5 May 2017Law in force: Binding legislation that applies as of the review date.
  2. EN ISO 14971:2019/A11:2021 Medical devices — Application of risk management to medical devices — ISO / CEN, December 2019Harmonized standard (cited): A harmonized standard whose reference is published in the Official Journal of the EU; applying it can give a presumption of conformity for the requirements it covers.
  3. 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.