Resources
Glossary
This field has a vocabulary problem. The same word means different things to a biomedical engineer, a finance director and a software vendor, and a good deal of confusion in procurement is really two people using one term for two ideas. These are the definitions we use, written so you can disagree with them precisely.
- Biomedical engineering
- Hospital operations
- Quality and compliance
- Executive and finance
What is this glossary for?
Definition
Equipment management vocabulary
This glossary defines the terms used across healthcare equipment management as concepts rather than as values: what each one means, what a system can do with it, and where the boundary sits between what software decides and what your qualified staff decide.
Every definition here is capability-first. You will not find an interval, a limit, a tolerance or a threshold anywhere in it, because those are decisions about your equipment and your standards, and a glossary that supplied them would be making clinical claims in the guise of being helpful.
Where a term is genuinely contested, or where the industry uses it loosely, this says so rather than picking a side quietly. Those are the entries worth reading.
Equipment and records
The vocabulary of what you own and what is recorded about it.
Asset
A single physical device you own or hold, with an identity, a location and a history. The data term. Frontline screens say equipment instead, because that is what people standing next to it call it. One asset means one physical thing: four identical pumps are four assets, and treating them as one is how a history becomes meaningless.
Asset register
The authoritative list of those devices. Not a spreadsheet with more fields: it is the object every other module points at. An imperfect register that everything shares beats a perfect one that half the system ignores.
CMMS
Computerised maintenance management system. Historically a work-order and asset database, often built for facilities rather than healthcare. The term is used loosely enough that it tells you almost nothing about whether a product handles calibration, safety gates or downtime cost, so it is worth asking rather than assuming.
Asset lifecycle
The whole life of one device: procurement, commissioning, use, maintenance, incidents, replacement, disposal. The value is not in the phrase but in whether one continuous record spans it, or whether the history restarts each time the device changes hands.
Audit trail
A record of what happened, who did it and when. The only question worth asking about one is whether it can be edited. A trail with an update path records what somebody currently wants it to say. See append-only.
Append-only
A record to which you can add but from which nothing can be changed or removed. Corrections become new entries that sit alongside the original rather than replacing it, so the history shows what was believed then as well as now.
Maintenance and calibration
The work vocabulary. Note that every interval mentioned here is yours to set, in every case.
Planned preventive maintenance (PPM)
Work done on a schedule to stop a failure rather than in response to one. Also called preventive or planned maintenance. How often it happens depends on the device, the manufacturer, its duty cycle and your risk appetite: it is a decision your qualified staff make, and no software should supply it.
Corrective maintenance
Work done because something has failed. The opposite of preventive, and the thing preventive work is trying to reduce. Most estates measure the ratio between the two and treat a shift toward preventive as progress.
Calibration
Establishing that a device measures what it claims to, by comparing its reading against a reference of known accuracy. What counts as an acceptable result, and how often it is checked, are yours. A calibration record is only as good as the calibration status of the instrument that produced it.
Traceability
The property that a measurement can be related back through an unbroken chain of comparisons to a reference. In practice it means the instrument used to check your device has its own documented calibration, and that this is recorded rather than assumed.
Procedure version
Which iteration of a written procedure a job was performed against. It matters because procedures improve. Storing the version with the result is what keeps work done two years ago interpretable today, instead of appearing to follow a procedure that did not exist yet.
Work order
A unit of work with an owner, a state and a history. The useful test is whether someone has explicitly acknowledged it, because a job assigned to a queue is a job assigned to nobody.
Safety and compliance
The vocabulary where precision matters most, and where loose usage is most expensive.
Return to service
The decision that a device is fit to be used clinically again. Properly, it is a gate: required tests present, results passing against your limits, and an authorised person recording a clearance. If it can be set directly as a status, it is not a gate, it is a field.
Quarantine
Removing a device from clinical use immediately, as an authoritative decision rather than a suggestion. The test of an implementation is whether it can happen offline: it should not, because a decision about clinical safety must be true the moment it is made.
Electrical safety testing
Checks that a device is electrically safe to use. The values, limits and frequency come from the applicable standards and your qualified staff. Software holds and enforces them; it does not know them.
CAPA
Corrective and preventive action: a specific change with an owner and a date, arising from something that went wrong. The word that gets dropped is preventive, and the step that gets dropped is checking afterwards whether it worked. Completion and effectiveness are different claims.
Incident
An event where equipment may have caused or contributed to harm or risk. Containment comes before investigation: the first question is what else is exposed, not why it happened.
Field safety notice and recall
A manufacturer communication about a problem with a device already in use, sometimes requiring action or return. Whether one applies to you is answerable only if you know what you own, by model, batch and lot.
Downtime, reliability and money
The most abused vocabulary in the category, because these terms sound like measurements and are frequently estimates.
Downtime
The interval during which a device was not available for clinical use. The contested part is the boundaries: it should start when the device became unavailable rather than when someone logged it, and end at an authorised return to service rather than when an engineer says it is fixed. Waiting for a part is downtime.
Uptime and availability
The inverse, usually as a percentage. Ask what the denominator is: availability against a 24-hour day and against scheduled operating hours are different numbers, and quoting one as the other is a common way to flatter an estate.
MTBF and MTTR
Mean time between failures and mean time to repair. Averages, which means they hide the distribution. An estate with one catastrophic device and forty reliable ones has a comfortable MTBF and a real problem, so treat these as prompts to look rather than as answers.
Estimated against confirmed impact
An estimate derived from a configured revenue figure, versus a cost that was actually incurred. Both are useful. Adding them together produces a number too soft to be an accounting figure and too precise to be an estimate, and it is defensible as neither.
Total cost of ownership (TCO)
Everything a device costs over its life, not just its purchase price. The reason a donated device is not free, and the reason two identical machines can be very different commercial propositions.
Downtime cost
What an hour of unavailability is worth. There is no industry figure for this that means anything about your organisation: it depends on what the device does and what that is worth to you. Any system quoting one without asking you first is quoting a fact about somebody else.
Why the loose terms are expensive, and how to pin a vendor down
Because a word everybody thinks they agree on is a disagreement nobody has noticed, and it usually surfaces after the contract is signed.
The pattern repeats through procurement in this category. A buyer asks whether the product does calibration management. Everyone says yes. What the buyer means is readings recorded against their limits with traceable instruments and certificates that expire. What the vendor means is a date field with a reminder. Both parties are being honest, and the demonstration will not surface the gap because the demonstration is built around the vendor's meaning.
The defence is not scepticism, it is specificity. Rather than asking whether a system does return to service, ask what happens when someone tries to return a device whose tests have not been done. Rather than asking whether it tracks downtime, ask when the clock starts and whether it is running while a part is on order. The answers to those questions are not marketing claims and cannot be given loosely.
The same applies to us. Every definition on this page is one you can hold us to, which is why they are written as concepts you could disagree with rather than as reassurances you could nod along to.
What you will not find here, on purpose
No intervals, no limits, no tolerances, no thresholds and no regulatory interpretations. This glossary defines what a calibration interval is; it does not tell you what yours should be. That belongs to your qualified staff and the standards that apply to you, and a glossary that quietly supplied a number would be making a clinical claim about equipment it has never seen. The rule is enforced by an automated test over every word on this page rather than by our good intentions.
Questions
Why does this glossary not give any actual intervals or limits?
Because they are not ours to give. How often a device needs servicing or what a passing test looks like depends on the device, the manufacturer, its duty cycle, your risk appetite and the standards that apply where you are. A glossary supplying a number would be making a clinical claim about equipment it has never seen, and would be wrong for most readers.
What is the difference between an asset and a piece of equipment?
Nothing, and that is deliberate. Asset is the data term and equipment is what people standing next to it say, so our data model says asset and our frontline screens say equipment. A register that speaks the vocabulary of the person filling it in gets filled in.
Is a CMMS the same thing as Rydya?
Not quite, and the term is loose enough to be unhelpful. A CMMS is historically a work-order and asset database, frequently built for facilities rather than healthcare, and the label tells you nothing about whether calibration, safety gates or downtime cost are handled. Rather than asking whether something is a CMMS, ask what happens when a device fails its safety test.
Why do you keep saying estimated and confirmed impact are different?
Because merging them is the most common way a maintenance business case fails. An estimate built from a configured revenue figure and a confirmed cost from a real invoice carry different weight. A combined total is too soft to be an accounting number and too precise to be an estimate, so it reads as authoritative while being defensible as neither.
Keep reading
Downtime analytics
Where the clock starts and stops, defined precisely rather than loosely.
Safety testing
What "return to service" means when it is a gate rather than a field.
Hospital maintenance
The whole picture these terms describe.
CMMS vs EAM
The two labels this field leans on, and why they tell you little.
See it on your equipment
Live in an afternoon, useful the same week. A person replies, usually within one working day.
Contact us