01 Hospital
Hospitals & medical centres
Many devices, many hands, three shifts: the report point makes every ward able to report — biomedical engineering gets complete cases instead of corridor rumour.
Solution · Medical technology & labs
The device fault, documented from the first second.
In hospitals, practices and labs a device fault isn't just an annoyance — depending on the device it's a case that has to be documented. It still tends to get reported by calling down the corridor. ServiceID turns that call into a structured report: clearly assigned to the device, with a timestamp and a photo — straight to biomedical engineering or your service partner. No app, no login, no IT project.
- 1 scan
- and device, location and time are captured
- 0
- apps or logins — including for agency staff and night shifts
- 24/7
- reportable — faults don't follow the duty roster
- from €0.50
- per device and month
The regulatory picture
Why a device fault belongs in the record.
The German Medical Devices Operator Ordinance (MPBetreibV) makes operators responsible for the safe operation of their devices. For certain active medical devices that includes a medical device log book — recording, among other things, the date, nature and consequences of faults as well as repeated operating errors of the same kind. The records have to be accessible when they're needed — during an inspection, for instance.
In everyday terms that means every fault needs a clean start: when, which device, what exactly. That start is what gets lost when the report is a call down the corridor — and it has to be laboriously reconstructed later.
- Depending on the device, faults have to be documented — with date, nature and consequences
- Gaps show up at the latest during an inspection or in a claim
- Reconstructing from memory is the most expensive and least reliable route
The problem
A call down the corridor is not documentation.
"The ECG in room three is playing up again" — that's how many fault reports begin. Whoever hears it is on their way somewhere else; by the time the report reaches biomedical engineering, the time, the device ID and half the description are missing. What's left is a case with no beginning.
Yet the person reporting is the best source there is: they're standing at the device, at the moment of the fault. What's missing is a route as fast as calling out — but one that records everything. The report point on the device is exactly that route: scan, pick a topic, done. Device, location and timestamp are written by the system itself.
- Reported at the moment of the fault — not from memory after the shift
- Unambiguous device assignment through the report point — no mixed-up devices
- Complete even on agency and night shifts, with no training
How it works on site
Scan. Report. Documented.
The reporting route is deliberately short enough to survive a normal day on the ward.
-
Step 01
Report point on the device.
Every report point is clearly assigned to one device — with its location and the details you store. You define the reporting topics: from "error message on the display" to "mechanical damage".
-
Step 02
Reporting without a hurdle.
Whoever notices the fault scans with the ordinary camera, picks the topic and optionally attaches a photo of the error message. No app, no login — including for staff who are only covering a shift.
-
Step 03
Structured, with the right team.
The report reaches biomedical engineering, building services or an external service partner — configurable per device, documented with a timestamp and a clean starting point for your device records.
Every report: device · location · topic · photo · timestamp
The honest limit
What ServiceID deliberately is not.
So there's no misunderstanding: ServiceID is not medical device software and replaces neither the medical device log book nor the device inventory nor your processes under the MPBetreibV. Whether and how you carry the reports into your device records stays your decision — and your quality management team's.
What ServiceID delivers is the part that most often goes missing today: the structured, timestamped start of every fault case — instead of a reconstruction days later. And one more clarification: what gets reported is devices, not patients. Reporting topics are configured so that no patient or health data is captured.
- Doesn't replace: the medical device log book, the device inventory, your QM processes
- Delivers: structured, timestamped fault reports as source data
- Captures no patient data — topics are configured accordingly
Places of use
For operators — and for those who do the servicing.
-
-
02 Practice
Medical & dental practices
Without an engineering department of your own, the short line to the service partner is what counts — the report goes straight to them, with everything they need to prepare.
-
03 Lab
Labs & analytics
Analysers in continuous operation: report anomalies immediately, before a deviation becomes an outage — documented for quality assurance.
-
04 Service
Medical device service providers
Fit your customers' devices with report points: you receive structured reports with a device ID instead of phone calls — and give your customers visible added value.
See the base solution
Frequently asked questions
The medical technology reporting route — in brief.
Does ServiceID meet the requirements of the MPBetreibV?
Answering that with a plain yes would be dishonest — the MPBetreibV addresses you as the operator, and it's your processes that meet the documentation duties, not a single tool. What ServiceID delivers is the structured source data: when, which device, what, with a photo. Whether and how that feeds into the medical device log book and your QM system is for you to define.
Is patient data captured?
No. What gets reported is devices, not people: the reporting topics are configured so that no patient or health data is requested. The system is GDPR-compliant and runs on servers in Germany and the EU.
How does the report reach our service partner?
Recipients are configured per device or device group: in-house biomedical engineering, building services or an external provider — every report lands by email in the right mailbox, and therefore in any ticket system with a mail inbox.
Does it work with changing staff?
That's exactly what it's built for: no app, no login, no training. Anyone who can operate a smartphone can report — including the night-shift cover seeing the device for the first time.
What does the reporting route cost?
From €0.50 per device and month, plus a one-time setup fee based on scope — no contract lock-in. It makes sense to start with one ward, one site or one device group; you expand once the reports prove the value.
Medical technology
Turn the fault into a clean case.
Describe your device estate — as an operator or as a service partner. You'll receive a concept with topics, recipients and terms. Two fields are enough, reply on business days within 24 hours.
Your contact
AS
You speak directly with us — the people who built the system, not with a reseller.
- Reply within 24 h on business days
- Free & no obligation
- Software made in Germany · Servers in DE & EU · GDPR-compliant
Prefer to write? Briefly outline your project — reply within 24 hours on business days.
Your request is in.
A confirmation is on its way to — check your spam folder just in case. We usually get back to you within one business day.
Submission failed.
That didn't go through just now. Send us your request directly by email instead — your details are already filled in:
Send by email