Today
A periodic safety update report needs complaints, incidents, corrective actions, sales figures and clinical follow-up results in one analysis. That data lives in separate systems and in external consultants' files. So every report starts with a long round of collecting.
An example
For the VZ-248 infusion pump family (MDR IIb) the agent computes the complaint rate per 1,000 units sold, spots a rise in occlusion alarms and flags that one sales region's data is missing. The head of regulatory affairs at Valbrecht closes the gap before the draft goes to review.
Your data, wherever it lives
Today complaints, incidents and CAPA sit in the QM system, customer contacts in the CRM, sales and installed-base figures in the ERP, clinical follow-up results in spreadsheets that external consultants send by e-mail, and earlier reports in the DMS. demi reads, understands and links them per device family and period, with your rights. The AI calculates rates and trends and drafts every section with its source in hours instead of days of compiling, and the responsible person reviews and signs.
Where the data lives today
- QM system
- CRM
- ERP
- Office files
- E-mails
- DMS & archive
How demi solves it
Three layers in this order: connect the data first, then the rights, then the AI.
- 1 · ConnectData Layer
The case needs data from the QMS, CRM, ERP and DMS. demi replaces nothing and links complaint and vigilance records, CAPA, sales and installed-base data and clinical follow-up results to each device family. demi writes back only after approval.
- 2 · PermitPermission Layer
Regulatory affairs sees every device family. The responsible person signs the report, and every step is recorded.
- 3 · ActIntelligence Layer
The agent codes complaints with your scheme and computes rates exactly per period and population, compared with earlier reports. It drafts each section, every figure linked to its record, and names missing data instead of papering over it.
How it runs
- 1
Clarify the data sources: QMS, ERP and CRM per device family
- 2
The agent codes complaints to your scheme
- 3
demi computes rates and trends per period
- 4
The agent drafts each section, every figure sourced
- 5
The responsible person reviews and signs
What changes
Reports on schedule
Consistent coding over the years
Gaps visible before the notified body sees them
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.
Your numbers
Result
+86 hfreed per year
Assumptions and calculation
demi brings complaints, incidents, sales and corrective actions together and drafts the report; you review.
24 h → 16.8 h per case
How we calculate
1 safety reports × 24 h × 30% × 1.0 (manual) × 12 months = 86 h
Value per year, before demi costs
Freed per year+86 h
Assumption: labor cost of $48.62 per hour in US manufacturing in June 2026 (BLS), plus workplace, IT and overhead.
= Value per year, before demi costs
+$5,590
gained per year
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 packageQuestions about this use case
Which device classes and report types does demi support?
demi works with the report templates you define, such as the periodic safety update report or the post-market surveillance report. Which report a device class needs is assessed by your regulatory affairs experts. The legal assessment stays with you.
Who signs the PSUR?
The person responsible for it in your company. The agent delivers a draft in which every figure links to its record. Signature and release are recorded with person and time.
Can demi use our existing complaint coding?
Yes. The agent codes to your scheme and puts cases that do not clearly fit up for review. That keeps the coding comparable over the years.
What happens when sales or complaint data is missing?
The draft names the gap explicitly, for example a region without sales data. The agent fills nothing in and computes no rate on an incomplete base.
