Skip to content
Quality, standards & complianceMedical Technology

Handle medical device complaints

For each complaint you see whether your criteria make it reportable, and by when.

Today

Every complaint has to be checked quickly for reportability. The facts are spread across e-mails, the CRM, service reports and the QMS. Trend analysis and periodic reports tie up the regulatory team for weeks.

An example

At Valbrecht an intensive care unit reports that a VZ-248 infusion pump raised its occlusion alarm late. The agent links the serial number, the software version and infusion-set lot 2603-L, finds two similar complaints from the last quarter and flags a potentially reportable event with its deadline. The head of regulatory affairs receives a draft assessment covering all three cases.
Fictional company, typical workflow.

Your data, wherever it lives

Complaints arrive by e-mail, by phone or from a service visit today, service cases sit in the CRM, lots and UDI in the ERP, the risk file and earlier reports in the QM system and DMS. demi reads, understands and links them per device and lot, with your rights. A draft assessment with deadline and similar cases is ready in minutes instead of after a long search, and the responsible person decides on reporting.

Where the data lives today

  • E-mails
  • Phone & voice
  • CRM
  • ERP
  • QM system
  • DMS & archive
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 QMS, CRM, ERP and DMS. demi replaces nothing and ties every complaint to exactly one device and one lot, with UDI, service data, the risk file and earlier reports. The approved assessment goes back only after your approval.

  2. 2 · PermitPermission Layer

    The responsible person decides on reportability, never the agent. Patient data is kept to the minimum and shown only to authorised roles, and every assessment is recorded with its reasoning.

  3. 3 · ActIntelligence Layer

    The agent structures the complaint, works through your reportability criteria as a fixed checklist and computes the deadline exactly from the recorded awareness date. It trends complaints by device and lot and drafts assessments and periodic reports with sources.

How it runs

  1. 1

    A complaint arrives by e-mail, phone note or service visit

  2. 2

    The agent links device, UDI and lot and looks for similar cases

  3. 3

    It checks the reportability criteria and computes the deadline from the awareness date

  4. 4

    The responsible person decides and approves the assessment

  5. 5

    Trends and draft reports are built from the same cases

What changes

  • A computed deadline on every case

  • Trends per device and lot spotted early

  • Periodic reports with less effort

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

+108 hfreed per year

Assumptions and calculation

demi logs complaints, checks the reporting criteria and works out deadlines; you decide on reporting.

45 min → 31.5 min per case

How does it run today?

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

How we calculate

40 complaints × 45 min × 30% × 1.0 (manual) × 12 months = 6,480 min = 108 h

Value per year, before demi costs

Freed per year+108 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

+€7,020

gained per year

108 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 are reportability criteria applied?

Your criteria are stored as a checklist, the way your procedure defines them. The agent answers each question with evidence from the complaint and the linked data and flags missing information. A person always decides whether to report, and the legal assessment stays with your experts.

Is patient data protected?

demi takes over only the details the assessment needs and shows them only to roles allowed to see them. Everyone else sees the complaint without personal data. Every access is logged, and the data stays in the EU.

How are deadlines computed?

demi computes the deadline from the recorded awareness date and the rule set out in your procedure. Every open case shows the time left and moves up the list as it gets close. The responsible person confirms the awareness date.

Can it draft periodic reports?

Yes. From the same complaints, trends and actions the agent drafts the sections of your post-market reports, each figure linked to its cases. Your regulatory team reviews and approves them.

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