Medical Equipment Maintenance: Registers, Calibration & Downtime
A broken autoclave cancels a surgery list; an uncalibrated BP machine misdiagnoses quietly — the register, the service schedule and the calibration discipline a Kenyan facility needs, and which of the three we actually hold.
Medical equipment fails in two ways. Loudly — the generator dies during a procedure, the lab analyzer stops mid-batch, and everyone knows immediately. Or quietly — the BP machine drifts 15mmHg out of calibration and misinforms every diagnosis for a year. Kenyan facilities plan for neither: equipment is bought, installed, used until it breaks, then repaired in a panic at whatever the technician quotes. The alternative is not complicated. It is a register, a calendar, and the discipline to obey both.
The equipment register, clinical edition
Everything from the general asset register applies — named custodians, locations, movement history — plus the clinical fields:
- Service interval and last service date — per manufacturer specification, not per breakdown history.
- Calibration due date — for anything that measures: scales, BP machines, thermometers, lab analyzers, oxygen concentrators.
- User-level checks — the daily/weekly checks nurses do (battery, cuff condition, error codes), logged simply.
- Downtime record — every day out of service, with cause. This number justifies the maintenance budget better than any argument.
- Funding source — county, donor, program, or own funds; donated equipment often carries reporting obligations.
Three tiers of maintenance
| Tier | Who | Cadence | Examples |
|---|---|---|---|
| User care | The nurse or tech using it | Daily/weekly | Cleaning, battery checks, error code reporting, cuff and probe condition |
| Planned preventive service | Biomedical technician (in-house or contracted) | Per schedule | Autoclave gaskets and validation, suction machines, oxygen concentrator filters |
| Specialist service & calibration | Manufacturer agent / accredited lab | Per schedule | Analyzer calibration, imaging equipment, anesthesia machines |
The calibration blind spot
Broken equipment announces itself; miscalibrated equipment diagnoses patients wrongly while looking fine. Anything that outputs a number a clinician acts on needs a calibration date on the register and a sticker on the device. Inspectors look for exactly this — and so should you.
Making the schedule survive reality
- Get service dates out of the matron's diary and onto something that reminds you. Note what that something can be: a recurring task with a due date, which does genuinely raise its next occurrence for you. It cannot be a field on the asset, because the register carries no service interval and no next-service date — see the note below before designing around this.
- Contract a biomedical technician for a scheduled quarterly day rather than per-breakdown callouts — planned visits cost a fraction of emergency ones and prevent most of them.
- Keep critical spares for critical equipment: autoclave gaskets, suction tubing, concentrator filters. The KES 3,000 spare beats the two-week downtime waiting for it.
- When equipment moves between rooms or branches, the register moves with it — movement records are what keep service history attached to the right machine.
- Log every breakdown against the asset: three failures in a year is a replace-versus-repair decision the data should make, not sentiment.
The replacement horizon
Every machine has a service life, and a register that holds purchase date, cost and condition gives you the raw material for a rolling replacement plan rather than an annual budget surprise. Two cautions, because this is where facilities over-trust their software. Nothing turns those fields into a plan for you — the horizon is a spreadsheet you build from an export. And if you see a written-down value trend on an asset dashboard anywhere, check what rate it applies before quoting it to a board: a single flat rate across every asset class is common, it is not book value, and it will not agree with your audited accounts. Boards fund plans; they resent emergencies, and they notice a number that does not reconcile. The one-page annual report — register value, downtime days, maintenance compliance, and next year's replacements — is the same discipline schools use, with higher stakes.
What AWRA OpsHub does today
- An asset register with named custodians — person, department, location and warehouse, with full movement history, so you always know who holds a machine and where it went.
- Condition and status per asset, including an explicit maintenance status, plus risk level and an approval requirement for high-risk items.
- Purchase date, purchase cost, serial number, model, manufacturer and warranty expiry date on every record, with retirement captured with a reason and a date.
- Custody verification — last verified date and by whom — and asset movements as auditable events.
- Repair spend can be tracked as expenses or purchase orders against a vendor, so the repair-versus-replace argument has cost evidence behind it.
More we can add to your workspace
- A service interval and a last-service date. These are not fields on an asset.
- A calibration due date. The blind spot this post is built around is a blind spot in our data model too.
- A downtime record, and the reason is worth knowing. A maintenance status exists on an asset and can be set — but only by editing the record, which writes no movement and no date. Two movement actions named "sent to maintenance" and "returned from maintenance" exist in the code and are written by nothing at all, so the paired timestamps that would give you days out of service are never created. Flipping the status back erases any trace it happened. (Until 2026-08-04 those two dead actions were also offered in the movement filter on the reports screen, where they could only ever return an empty table; they have been removed from the menu.)
- Scheduling and alerting against the asset itself: a due date on the machine, and a lead-time reminder before a service falls due. The nearest working mechanism today is a recurring task, which reliably raises its next occurrence but lives beside the register rather than on it, so the reminder and the asset's history stay separate.
- A user-level check log for the daily and weekly checks nurses do.
- A funding source field, so donor and county-funded equipment carries no reporting flag.
- A replacement horizon. Age and cost are on the record; nothing turns them into a rolling plan.
This is the weakest match in the healthcare set and we would rather say so plainly. You get a solid custody register — what you own, who has it, where it is, what it cost, when the warranty ends — and that is genuinely useful. What you do not get is the maintenance calendar this whole post is about. A biomedical spreadsheet alongside our register is the honest answer today, and these fields are a small, well-defined build if a facility wants to push for them.
Anything above that you need, we can build for you
Everything listed above as something we can add describes what ships in the standard product today — it is a starting point, not a limit on what AWRA OpsHub can do for your organisation. Kenya's eTIMS integration and its maintained payroll engine are both in the product because clients needed them and commissioned them; neither appeared by itself, and the same door is open for whatever you just read about. One qualification so this is worth what it claims: a small number of things on this blog we deliberately leave to a specialist rather than build — a statutory ledger we will not sign our name to, a rule that would decide a tax question for you, a clinical or member-funds record that belongs in a regulated system — and where that is true the post says so in those words. Everything else is a scope, a timeline and a price.
The operational work, which is what most commissions actually are
An extra approval stage in a chain that does not match the standard one, a custom field set on employees or assets that only your sector needs, an expiry that has to block an order rather than send an email, a report your board asks for in a shape nothing produces, or a scanner or weighbridge feeding the goods-in door. These are the commissions we are asked for most often and the smallest ones we quote — and unlike a revenue-authority pipeline, none of them waits on a regulator.
The module-shaped additions, which are the ones readers ask for most often
A price list with real discount authority, a customer-facing quotation that expires, a bill of materials or recipe costing, a staff advance that is issued, acquitted and chased, a member or unit ledger, a matching rule that holds a payment. Each of these is a build rather than a setting, and each has been quoted before — a bigger piece of work than a custom field, with a written spec and a date instead of a roadmap slide.
The report, document or pack nothing currently produces
The board pack in the shape your board actually asks for, a donor or funder layout, an invoice or receipt template carrying what your regulator or your customer expects, a dataset the report builder cannot reach yet. Usually the fastest thing on this list to deliver, because the data is already in the system.
Systems, rails and hardware you already run
The accounting package, CRM, online store, core banking or custom database you intend to keep — connected through our API so a fact is entered once and appears everywhere it is needed. Plus the physical edge: a scanner, a scale, a weighbridge or a till peripheral feeding the door it belongs to.
How it works: you describe the requirement, we return a written scope, timeline and cost, and once agreed it is built into your environment and maintained as part of the product. Nothing here waits on a regulator or a published specification, which is why operational builds are the ones we quote fastest. Tell us the requirement that would otherwise rule us out — that is a better first conversation than a demo.
Tell us what your operation needsPut every machine on a calendar
A custody register with named holders, movement history, condition, warranty expiry and retirement. Service intervals, calibration dates, downtime and scheduling are not built — the note above lists every missing field.
See equipment management in AWRAFrequently asked questions
We cannot afford a biomedical technician on staff. Options?
Contract one: a quarterly scheduled day covers most small facilities, county biomedical units support public-linked facilities, and several Nairobi firms sell preventive-maintenance contracts by equipment count. The scheduled-day model costs less annually than two emergency callouts.
What does calibration actually cost, and who does it?
Basic measuring devices (scales, BP machines, thermometers) calibrate cheaply through accredited local labs; analyzers and imaging need manufacturer agents and cost more. Budget it per device on the register — it is a small, predictable line that prevents an unmeasurable clinical risk.
Is any of this legally required?
Facility licensing standards require equipment to be functional and appropriately maintained, and inspections check registers, service records, and calibration evidence. Beyond compliance, documented maintenance is your defense narrative if equipment is ever implicated in an adverse event.
How do we handle donated equipment that arrives without manuals or spares?
Register it like everything else, then make an explicit keep-or-decline decision: if no local agent, spares, or service knowledge exists, a donated machine can cost more in false confidence than it gives in capability. Donors generally respect a facility that asks for the service package upfront — ask.
