Resources
Buyer's guide
Every product in this category demonstrates well. The demo is built from clean data by someone who knows exactly where not to click, and it tells you almost nothing about the Tuesday in month eight when a ward is short a pump. These are the questions that do tell you, including the ones we answer badly.
- Biomedical engineering
- Hospital operations
- Quality and compliance
- Executive and finance
What is an equipment management evaluation actually testing?
Definition
Evaluating equipment management software
A useful evaluation tests what a system refuses to do and what it does when data is missing, rather than what it can display when everything is present, because the first two determine whether the record survives scrutiny and the third is what every demo shows.
Almost every product in this category can show you a register, a work order and a chart. Those are table stakes and they discriminate between nothing. The questions worth your time are the ones where products actually differ, and they are all variations of one theme: what happens when things are not tidy.
The structure below is deliberately awkward. Each section is a question to ask a vendor out loud, in a live session, with your own hands on the keyboard if possible. Vendors who are strong on a point will enjoy answering it. That reaction is itself information.
How to test the safety gate, which is where the real difference is
Ask them to break it. A gate that can be talked around in a demo will be talked around on a ward.
Try to return a device to service without its tests
Do not ask whether it is possible. Ask them to do it, in front of you, and watch what the system says. Watch also for whether the refusal comes from the interface or from the server: ask what happens if the same request arrives from an integration.
Ask who can override, and how
Every product has an escape hatch or has decided not to have one. Both are defensible answers; being unable to answer clearly is not. If there is an override, ask who holds it, whether it is audited, and what it was built for. The honest ones will tell you about the customer who demanded it.
Ask what happens offline
Whether a technician can quarantine or clear a device with no signal. The right answer is that they cannot, because an offline device cannot establish that equipment is safe. A product that queues a safety decision for later sync has not thought about the hours in between.
Ask about the test instrument
Whether the system knows the calibration status of the instrument that produced a reading. Most do not. It is the quiet failure that leaves you with a complete-looking record that means nothing.
Why the missing-data questions matter more than the feature list
Because every estate has gaps, and how a system reports a gap decides whether your compliance figure is evidence or decoration.
Ask what a device with no data shows in a compliance report
The only safe answer is that it shows as having no data. If it shows as zero, as compliant, or is quietly excluded, the report will flatter you, and it will do so in exactly the direction nobody checks. The absence of a failed test is not a passed test.
Ask where the downtime clock starts and stops
It should start when the device became unavailable, not when someone logged it, and stop at an authorised return to service rather than when an engineer says it is fixed. Ask specifically whether it runs while waiting for a part. If it does not, a slow supplier is invisible in the report meant to expose one.
Ask what an hour of downtime costs, before you configure anything
If a number appears without you having supplied one, ask where it came from. Any figure the software knows before you tell it is a fact about somebody else's hospital. The honest answer is that the hour is unpriced until you price it.
Ask whether estimated and confirmed costs are added together
They should not be. An estimate from a revenue figure and an invoice are different claims, and a combined total is too soft to be an accounting number and too precise to be an estimate. It will be the first figure your finance director questions.
When to test the record, not the report
On the first day, because a record you cannot defend is a report you will not use twice.
Ask whether the audit trail can be edited
Then ask how that is enforced: by policy, by the application, or by the database. Ask whether an administrator can do it. A trail with an UPDATE path records what somebody currently wants it to say.
Ask to drill from a number to the rows behind it
Live, on their demo data. This is the single feature most likely to be missing and most likely to matter, because it is what survives somebody senior disagreeing with you in a meeting.
Ask what happens when a procedure changes
Whether work completed last year still shows the version it was done against, or silently appears to follow today's procedure. The second looks tidier and is a quiet falsification of your own history.
Ask how an attachment is stored
Real bytes or a link to a shared drive. A link is a promise about somebody else's folder structure, and it breaks silently, usually at the moment you need the document.
How Rydya answers these, including badly
Our own answers to our own questions. The last four are ones we currently lose on, and you should ask our competitors the same things.
| Question | Our answer |
|---|---|
| Can the safety gate be overridden? | No. There is no bypass and no demo mode that relaxes it. |
| Where does the downtime clock start and stop? | Unavailability to authorised return to service, including waiting for parts. |
| What does a device with no data show? | No data. Never zero, never compliant. |
| Do you know our downtime cost? | No, and we will not guess. Unpriced until you configure it. |
| Can the audit trail be edited? | No update or delete path exists at the database, for any role. |
| Can we drill from a figure to the rows? | Yes, and we would test this first in any product. |
| Do you have SOC 2 or ISO 27001? | No. Neither, and no penetration test yet. |
| Do you support SAML single sign-on? | No. Email and password with TOTP multi-factor. |
| Do you scan uploaded files for malware? | No, not today. |
| Do you integrate with our EHR or ERP? | No named connectors exist. Signed webhooks and imports only. |
Rydya against this guide's own questions
Who should be in the room, and when
Your security and privacy people in week one rather than at contract, and a technician rather than only a manager.
The most expensive sequencing error in this category is running the security review last. By then the clinical stakeholders are invested, the timeline is public, and the awkward questions have become costly to ask honestly. Ask them first, when the answer can still change the decision cheaply. Any vendor who finds that unwelcome has told you something.
The second is evaluating with managers only. The person who decides is rarely the person who has to use it in a plant room with no signal and cold hands. If a technician cannot report a fault or complete a job in front of you, without training, the adoption problem is already visible and it will not improve after purchase.
The third, and the one we would push hardest: ask every vendor what they have not built. The answer, and their comfort with the question, predicts the relationship better than any feature comparison. A vendor with no gaps is a vendor who has not told you about them yet.
Why we published questions we lose on
Four rows in that table are answers a competitor could use against us today: no certifications, no SSO, no malware scanning, no named connectors. They are in the guide because you would find them during diligence anyway, and finding them yourself after we omitted them is worse for us than publishing them. It is also the only way this page is worth reading: a buyer's guide that only asks questions its author answers well is a feature list in a costume, and you would spot it by the third heading.
Questions
What is the single most useful question to ask an equipment software vendor?
Ask them to return a device to service without its safety tests, in front of you, on their own demo. Then ask whether the refusal came from the interface or the server, and what happens if the same request arrives from an integration. It takes two minutes and it separates a real gate from a status field faster than any feature list.
Why does it matter what a system shows for a device with no data?
Because every estate has gaps, and the reporting of a gap decides whether your compliance figure is evidence or decoration. If missing data renders as zero, as compliant, or is quietly excluded, the report flatters you in exactly the direction nobody checks. The absence of a failed test is not a passed test.
Should we trust a vendor who quotes our downtime cost?
Ask where the number came from. Any figure a system knows before you supply one is a fact about a different hospital, presented as a fact about yours. It will be the first thing your finance director questions, and when it cannot be sourced, every other figure in the pack becomes suspect along with it.
When should security review happen?
Week one, not at contract stage. Running it last is the most expensive sequencing error in this category: by then clinical stakeholders are invested and the awkward questions have become costly to ask honestly. A vendor who finds early scrutiny unwelcome has told you something useful for free.
Keep reading
Security
Our own answers to the security questions above, gaps included.
Glossary
The terms vendors use loosely, defined so you can pin them down.
Implementation guide
What happens after the decision, and where rollouts actually fail.
Hospital CMMS vs generic CMMS
The category question underneath the evaluation.
See it on your equipment
Live in an afternoon, useful the same week. A person replies, usually within one working day.
Contact us