Skip to content
Quality, standards & complianceMedical Technology

Keep the MDR file consistent after changes

Documentation, risk file and UDI data stay aligned after every change, with open items visible early.

Today

A medical device file has to stay consistent across design changes, risk management, labelling and UDI data. Today every change ripples through many documents that are updated by hand. Whatever gets missed often surfaces only in the audit.

An example

Valbrecht changes the material of a housing part on the VZ-248 infusion pump (MDR IIb). The agent lists 17 affected documents, one risk control without updated verification and two labels with an outdated UDI-DI. The head of regulatory affairs assigns the items and releases the file only once all are closed.
Fictional company, typical workflow.

Your data, wherever it lives

Today design data and change requests sit in the PLM, the technical documentation in the DMS, risk analyses often in spreadsheets, test records in the QM system, UDI data in the ERP and labels as PDFs. demi reads, understands and links them per device down to each piece of evidence, with your rights. With every change, the AI shows in minutes instead of hours every affected document, every gap in the evidence chain and every outdated UDI on a label, and your head of regulatory affairs releases the file.

Where the data lives today

  • PLM
  • DMS & archive
  • QM system
  • ERP
  • Office files
  • PDFs
Data LayerOne view of everything, with your rights

How demi solves it

Three layers in this order: connect the data first, then the rights, then the AI.

  1. 1 · ConnectData Layer

    The case needs data from the PLM, DMS, QMS and ERP. demi replaces nothing and links technical documentation, risk analyses, change requests, labels, UDI records and test evidence; each device carries all its documents. demi writes back only after approval.

  2. 2 · PermitPermission Layer

    Regulatory affairs owns the file. Changes run through your controlled document process with signatures, and every release is recorded with person and time.

  3. 3 · ActIntelligence Layer

    Through recorded links the agent finds every document a change touches, checks the chain from hazard to risk control to evidence and matches UDI data exactly against the labels. It cites the source for every open item.

How it runs

  1. 1

    A change request is raised in the PLM

  2. 2

    demi shows every affected document, risk control and label

  3. 3

    The agent checks evidence chains and UDI data for gaps

  4. 4

    Owners get their open items as tasks

  5. 5

    Release with signatures in the controlled document process

What changes

  • A consistent file after every change

  • Gaps visible before the notified body looks

  • Less searching before each submission

What does it bring you?

Check it with your own numbers

Every starting value is an assumption you can change. The calculation sits right below, step by step.

Assumption, editable

Your numbers

Result

+144 hfreed per year

Assumptions and calculation

demi keeps technical documentation, risk file and UDI data consistent after each change; you approve.

4 h → 2.8 h per case

How does it run today?

What is already digital saves less: the factor lowers the share demi brings.

How we calculate

10 changes × 4 h × 30% × 1.0 (manual) × 12 months = 144 h

Value per year, before demi costs

Freed per year+144 h

Assumption: labour cost of €49.50 per hour in German manufacturing in 2025 (Destatis), plus workplace, IT and overheads.

= Value per year, before demi costs

+€9,360

gained per year

144 h ÷ 1,760 h per role = 0.1 full-time roles

An estimate, not a promise. The starting values are assumptions for an industrial company with 150 to 500 people.

Combine with more cases and get the package

Questions about this use case

How does demi know which documents a change affects?

Through the links your systems already record: bill of materials, risk analysis, test evidence, labels. demi brings them together per device and follows them from the changed component. Where a link is missing, the agent shows it as an open item instead of guessing.

Does demi check UDI data too?

Yes. The agent compares UDI records with labels, instructions for use and master data. Mismatches appear as a list, each with the document it sits in.

Is anything released automatically?

No. The agent prepares and lists; release runs through your existing controlled document process. Every signature is recorded with person and time.

Does demi replace the regulatory assessment?

No. demi collects, links and checks evidence and prepares documents. Whether a change is significant and how to assess it is decided by your regulatory affairs experts. The legal assessment stays with you.

See this case with your data

In the demo we show you the workflow on your own systems.

Your configurator

No use cases yet

Your configurator is still empty

Add a use case from any card or case page and see what it brings per year, with the calculation. Free, no sign-up, no commitment: try it out and change any number.

Browse use cases