Industries
Diagnostic and imaging centres
Imaging is the segment where the cost of downtime needs no explaining. A scanner that is down is a room full of appointments that have to be moved, and everyone in the building already knows it. What is usually missing is not the awareness, it is the number, and the number is what changes a vendor conversation.
- Executive and finance
- Biomedical engineering
- Hospital operations
What is different about an imaging centre?
Concentration. A small number of devices carry most of the revenue, so equipment management stops being an operational function and becomes the business.
A hospital ward with forty devices can absorb the loss of one. An imaging centre with three scanners cannot. The estate is small, expensive, and directly attached to the appointment book, which means the arithmetic of downtime is unusually clean: an hour lost is a known number of slots, and the slots have a price.
This concentration cuts both ways. It makes downtime brutally expensive, and it makes the business case for managing it unusually easy to prove, because you are not trying to aggregate a thousand small inconveniences into a plausible total. You are pricing one room.
It also means the vendor relationship matters more than in almost any other segment. The service contract on a scanner is a large annual number, and the question of whether it is worth what you pay for it is answerable only if somebody recorded when the engineer was called and when the room came back.
How Rydya helps an imaging centre
Prices the room, measures the vendor, and keeps the evidence that makes both defensible.
Downtime priced against what the room earns
You set the revenue figure and the period on the asset, and the platform converts a measured interval into an estimated impact. You set it because only you know what your room earns. Rydya will not guess it, and where nothing is set the hour reads as unpriced rather than as zero.
The interval is measured honestly
From when the device became unavailable, not when somebody logged it, through the waiting for parts and engineers, to an authorised return to service. Waiting is downtime. A scanner waiting three days for a vendor engineer was down for three days.
Vendor performance from real jobs
When the engineer was engaged, when the room came back, order after order. Recorded as it happens rather than reconstructed at renewal, when everybody is arguing from memory about the same two incidents.
Estimated and confirmed stay apart
The estimated revenue impact of an outage and the confirmed invoice for fixing it are different records and are never merged. That separation is what lets you take either one into a negotiation without the other undermining it.
The evidence trail is append-only
Every state change hash-chained in the same transaction as the change. When the dispute is about what happened and when, the answer is retrievable rather than reconstructed.
Why the contract renegotiation usually goes badly
Because you arrive with an anecdote and they arrive with a report, and the anecdote loses even when it is true.
The pattern is familiar to anyone who has sat in one. The centre believes response times have been poor. The vendor produces figures showing the contract was met. The centre has recollections; the vendor has a system. The meeting is decided by that asymmetry rather than by the facts, and the contract renews on the vendor's terms.
The asymmetry is fixable and it costs nothing extra, because the information is generated by work that is already happening. Every fault report, every engineer visit, every return to service is a data point that somebody in the building already knows. The only question is whether it was recorded in a form that survives to the meeting, and that is a tooling question rather than a discipline question.
The figure that lands hardest is rarely the repair cost. It is the priced downtime, because it is the number the vendor is not measuring and cannot dispute without disputing your revenue.
When a small estate makes this easier, not harder
Because a handful of high-value devices is the ideal place to start, and the whole thing can be running in a week rather than a programme.
Centres sometimes assume a platform like this is for organisations with thousands of assets, and that a few scanners do not justify it. It is backwards. A small, concentrated, high-value estate is the easiest possible starting point: the register is short enough to import in an afternoon, the devices that matter are obvious rather than a prioritisation exercise, and the revenue figure per room is a number the finance lead already has.
The practical sequence is short. Import the register. Set the revenue figure on each room. Put codes on the equipment so a radiographer can report a fault by scanning rather than by finding out who to call. That is most of the value, and none of it is a project.
Rydya holds no images and no patient records
This is worth stating plainly for this segment in particular. Rydya stores no patient clinical records at all, and it is not a PACS, a RIS or an EHR. It manages the equipment: its history, its maintenance, its downtime and its cost. It does not touch the study, the report or the patient, and that boundary limits what a breach of Rydya could ever expose.
Who feels the benefit first
The radiographer who can report a fault in ten seconds, and the finance lead who finally has a number for the conversation they have been losing.
The frontline change is small and immediate. A radiographer scans a code, describes the problem, photographs it, and gets a reference to follow. No finding out who to call, no describing a device that has four identical siblings, no wondering whether anything happened.
The commercial change takes a quarter and is larger. By the time the contract comes up, the centre has priced downtime per room, vendor response measured from real jobs, and an audit trail that was written as the events happened rather than assembled for the meeting. That is a different negotiation, and it is the same information the building always had.
Questions
Does Rydya know what an hour of scanner downtime costs us?
Only once you tell it. You set the revenue figure and the period against the asset, and the platform converts a measured downtime interval into an estimated impact. It will not guess, and it will not reach for an industry benchmark, because that would be a fact about somebody else's centre. Where nothing is configured the hour reads as unpriced rather than as zero.
Is Rydya a PACS or a RIS?
No. Rydya holds no images, no studies, no reports and no patient records of any kind. It manages the equipment: history, maintenance, calibration, downtime and cost. It sits alongside your clinical systems rather than replacing any of them, and that boundary is deliberate because it limits what a breach could ever expose.
Does waiting for a vendor engineer count as downtime?
Yes. The interval runs from when the device became unavailable to an authorised return to service, including the days spent waiting for a part or an engineer. A system that only counts hands-on repair time is measuring effort while claiming to measure availability, and it makes a slow vendor invisible in exactly the report that should expose one.
We only have a few scanners. Is this too much system for us?
A small, concentrated, high-value estate is the easiest place to start rather than the hardest. The register imports in an afternoon, the devices that matter are obvious rather than a prioritisation exercise, and the revenue per room is a figure your finance lead already has. The concentration that makes downtime expensive also makes the case easy to prove.
See it on your equipment
Live in an afternoon, useful the same week. A person replies, usually within one working day.
Contact us