Skip to content
Service & spare partsMedical Technology

Safety inspections per device and hospital

Every safety inspection planned to the manufacturer's rules, the protocol written from the readings, the logbook entry ready.

Today

A manufacturer services thousands of devices at its customers, each with its own deadline: infusion pumps, syringe pumps and pump stations spread over wards, buildings and hospitals. Deadlines sit in spreadsheets, readings in the safety tester, protocols as PDFs with the technician. A missed safety inspection is a liability risk for operator and manufacturer, and a technician who cannot find half of the due devices on site drives out twice.

An example

Valbrecht services 1,140 VZ 248 infusion pumps and 460 syringe pumps in a hospital group with three sites. The agent finds 186 inspections due by the end of January, bundles them into six route days and plans 30 loan devices so the intensive care unit does not have to give up a pump. On site the technician tests electrical safety, flow rate, occlusion pressure and battery; the agent writes the 186 protocols from the tester's files. Two pumps fail because their occlusion alarm triggers only above the limit. They go to the workshop, and the hospital's clinical engineering team has protocols and entries the same evening.
Fictional company, typical workflow.

Your data, wherever it lives

What an inspection needs sits in many places today: devices and deadlines in spreadsheets and the maintenance system, contracts in the CRM, spare parts and loan devices in the ERP, readings in the safety tester, protocols as PDFs with the technicians. demi reads, understands and links all of it per device and hospital, with your rights. AI plans the routes and writes protocols and entries in minutes instead of hours; every protocol is released by the technician who tested.

Where the data lives today

  • Machines & sensors
  • Tickets
  • ERP
  • CRM
  • PDFs
  • Office files
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

    Data sources in this case: maintenance system, ERP, CRM, the safety testers and test protocols as PDFs. demi replaces nothing and brings together per device: serial number and UDI, location in the hospital, contract, the manufacturer's rules for scope and interval of the inspection, the tester's readings and all earlier inspections and repairs.

  2. 2 · PermitPermission Layer

    Each hospital sees only its own devices and protocols, each technician only his routes. A protocol counts only once the technician who tested releases it. demi reports a failed device straight to the operator and to the manufacturer's quality assurance, and every change is recorded with name and time.

  3. 3 · ActIntelligence Layer

    The agent computes due dates from the manufacturer's rules and the operator's obligations, bundles them into routes per hospital and plans loan devices so that no ward is left without a pump. After the test it checks every reading against its limit from IEC 62353 and the manufacturer, and writes the protocol and the device logbook entry. Limits are checked by fixed rules; the language model only words the text.

How it runs

  1. 1

    demi reads serial number, location, contract and the manufacturer's inspection rules for every device at the customer.

  2. 2

    The agent computes due dates, bundles them into routes per hospital and plans loan devices.

  3. 3

    On site the technician tests as usual; the readings come straight from the safety tester.

  4. 4

    demi checks every value against its limit and writes the protocol and the device logbook entry.

  5. 5

    The technician checks and releases; the hospital gets protocols and entries, and failed devices go to repair.

What changes

  • Every due inspection planned in time, even across thousands of devices

  • Protocols and logbook entries on the day of the test

  • Fewer wasted trips, because every route bundles all due devices

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

+384 hfreed per year

Assumptions and calculation

demi plans due dates and writes protocols from the readings; the technician checks and releases them.

12 min → 7.2 min per case

How does it run today?

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

How we calculate

400 device inspections × 12 min × 40% × 1.0 (manual) × 12 months = 23,040 min = 384 h

Value per year, before demi costs

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

+€24,960

gained per year

384 h ÷ 1,760 h per role = 0.2 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 the scope and interval of each inspection?

From the manufacturer's rules per device type, that is instructions for use and service manual, and from the operator's obligations, in Germany under the Medical Devices Operator Ordinance (MPBetreibV). Every deadline in the plan names its source. If the manufacturer changes its rules, the agent recalculates the affected devices.

Does demi read the readings straight from the safety tester?

Yes, if the tester exports its results as a file or through an interface, as most safety testers do. Otherwise a photo of the display or a printed protocol is enough. How the data gets to demi, we clarify in conversation.

Who keeps the device logbook?

The operator, that is the hospital. demi supplies the finished entry for every inspection with date, result, readings and tester, as a protocol or directly for the hospital's own medical equipment system. Nobody at the hospital retypes anything, and responsibility stays where it belongs.

What happens when a device fails its safety inspection?

The protocol shows reading, limit and the limit's source. The technician tags the device as blocked on site, the hospital is told at once, and the agent opens the repair order with serial number and findings. Quality assurance assesses whether an incident must be reported under the MDR.

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