Patient monitors are rarely bought on one line of a datasheet. They are bought as a decade-long bundle of hardware, firmware, sensors, service and batteries. The part of that bundle that wears out first is usually the power section: the monitor is unplugged for a transfer, wheeled to another ward, the battery ages quietly, and the runtime promised at purchase stops being true exactly when an alarm needs to reach a nurse.
The working answer for a buyer is to treat battery backup as a declared performance specification with stated test conditions, not a badge value. Four questions separate a real answer from a marketing number: what configuration the hours refer to, what evidence backs them, how the figure decays as the battery ages, and who pays for replacement. This guide turns those questions into RFQ fields, documents to request, acceptance checks and contract terms.
Why autonomy deserves its own evaluation section
Bedside monitors spend a meaningful share of their life on battery: intra-hospital transport, power interruption, procedure rooms, temporary beds in corridors. The monitor is also a device whose alarm function must survive the moment mains power disappears, so autonomy is not a convenience feature — it is part of how the device behaves in its worst-case scenario.
The standards frame the obligation rather than the number. IEC 60601-1:2005 with Amendments 1:2012 and 2:2020 sets the general safety framework for medical electrical equipment, and the collateral alarm standard IEC 60601-1-8 makes loss of the mains supply an alarm condition, so the monitor has to annunciate it while continuing to run from its internal supply. The particular standard for multifunction patient monitoring equipment, IEC 80601-2-49, and the parameter standards (for example IEC 60601-2-27 for ECG) define performance for their own functions. None of them hands you a universal minimum runtime for a multi-parameter monitor. The runtime is a manufacturer's declaration in the instructions for use and technical description — which means the burden of defining "enough" sits with the buyer.
Runtime is also a load problem, not a tank problem. Active parameters, NIBP cycling interval, display size and brightness, wireless or network connection, recorder use, ambient temperature and the battery's state of health all move the number. A supplier can be honest and still quote a figure your ward will never reach.
RFQ fields that turn a battery claim into a requirement
Write the power section of the RFQ as measurable fields with units and a stated basis. The table below is a workable starting set for a multi-parameter bedside monitor; adjust the configuration to your worst-case ward rather than to a quiet demo room.
| RFQ field | What to specify | Unit / basis |
|---|---|---|
| Declared runtime at worst case | Runtime with all parameters in normal clinical use, NIBP auto-cycle at your interval, maximum display brightness, wireless enabled, 25 °C ambient, battery at full state of health | Minutes; reference to the test report |
| Battery capacity and chemistry | Chemistry (typically lithium-ion), capacity in Wh, nominal voltage, pack part number; mAh alone is not comparable across voltages | Wh, V, part number |
| Ageing and end-of-life criterion | Usable capacity after 300 and 500 full cycles; definition of a cycle; criterion for end of life (for example capacity falling below 80 % of rated) | % of rated capacity, cycle count |
| Charge behaviour | Charge time with the device switched off and while monitoring; whether charging continues during use; charge-temperature limits | Hours, °C |
| Annunciation and shutdown | Low-battery alarm thresholds, time between first annunciation and automatic shutdown, and what stays functional on battery (alarms, trends, network link) | Alarm priority per IEC 60601-1-8; minutes |
| Field replacement | User-replaceable pack, tools required, swap time, hot-swap capability, whether calibration or service software is needed after a swap | Yes/no, minutes |
| Spare pack supply | Part number, price validity period, lead time, minimum order, and how long the pack will stay available after the model is discontinued | Price, weeks, years |
| Transport documentation | UN 38.3 test summary for the pack and IEC 62133-2 report for the cells and battery | Document reference and revision |
| Service access to state of health | Whether service software can read remaining capacity and state of health, and export it as a record | Report format |
Two fields are worth arguing over during negotiation. First, the ageing criterion: a battery warranty that only covers "defects" does not cover the ordinary loss of capacity that changes your clinical risk profile. Second, the spare-pack commitment, because a five-year capital plan that assumes battery replacement every three years has to know the price of that replacement before the first unit ships.
Evidence to request, and what each document actually proves
Ask for documents, not adjectives. For each claim on the offer, name the record that would support it and the mismatch that would disqualify it.
| Supplier claim | Document to request | What disqualifies it |
|---|---|---|
| "Up to X hours of backup" | Runtime test report with method, configuration, sample size and state of health of the tested packs | No configuration recorded, single new pack, or conditions looser than your RFQ |
| "Medical-grade lithium battery" | IEC 62133-2 test report for the pack plus a datasheet naming the cell and protection circuit | Report covers a catalogue cell, not the pack shipped in your units |
| "Certified device" | Notified body certificate (ISO 13485:2016 plus the MDR certificate) with device and accessory model scope; for the US, the 510(k) clearance number and the cleared device description | Certificate or clearance covers a different model, or names the OEM brand rather than the supplier you are contracting |
| "Safe to ship" | UN 38.3 test summary under the UN Manual of Tests and Criteria, Part III, sub-section 38.3 | Test summary exists for the finished monitor only, not for the spare packs you will reorder |
| "Smart battery management" | Software documentation under IEC 62304 and security documentation under IEC 81001-5-1, with version numbers | No version or change history, so you cannot tie the behaviour to the firmware you receive |
The US pathway is a useful sanity check on power claims because the power source is part of the cleared device description. Public 510(k) summaries for multi-parameter monitors routinely describe the device as "battery or line-powered" and list the parameter regulations it covers — for example 21 CFR 870.1025 (arrhythmia detector and alarm, product code MHX), 870.2300 (cardiac monitor) and 870.1130 (non-invasive blood pressure). If your tender specifies a different battery chemistry, capacity or number of packs from the cleared configuration, ask how that change is controlled and whether the supplier treats it as a new submission or a documented change. The same question applies in Europe, where a monitor used for continuous surveillance of vital physiological parameters is generally class IIa or class IIb under MDR Annex VIII Rule 10, depending on the intended purpose and on whether variation of the monitored parameters could cause immediate danger.
Capability and quality checks that predict runtime failures
Battery failures are rarely design failures in the abstract; they are lot, process and ageing failures. Check the supplier on these five points before you compare price.
Pack-level control. Who assembles the pack, and to whose specification? Cell provenance can be held under NDA, but the pack drawings, protection circuit and test criteria should not be. Ask for the pack's incoming inspection plan and the sampling rate for capacity testing on production lots.
Traceability from pack to serial number. You want to be able to answer "which units have the suspect battery lot" in an hour, not a week. That requires lot-to-device traceability and a UDI on the label — the FDA UDI system under 21 CFR Part 830, and the UDI requirement under the EU MDR, both give you a record you can reconcile against a field action notice.
Ageing data, not just fresh-pack data. Request cycle-life test data and the accelerated ageing method behind it, including the temperature and depth-of-discharge assumptions. A pack that performs at 25 °C may behave very differently on a cart parked near a radiator.
One quality system covering design and production. The FDA's Quality Management System Regulation took effect on 2 February 2026 and incorporates ISO 13485:2016 by reference into 21 CFR Part 820. For a supplier selling into the US, a single certificate covering design and manufacture, plus design-transfer records for the battery and power-management firmware, is the cleanest evidence that battery changes go through change control.
Service data on battery behaviour. Ask for aggregate field data for the last twelve months — the share of service calls attributable to batteries or charging, and the typical age at failure. Suppliers will not name customers, but a supplier who cannot produce an aggregate number is telling you something too.
Delivery, contract and after-sales terms
Write the following into the order or the service agreement, not into a side email:
Capacity warranty, not a defect warranty. State a measured threshold — for example at least 80 % of rated capacity at twelve months or 300 cycles, whichever comes first — and the test method used to check it. This converts an argument into a measurement.
Incoming runtime verification. Define an acceptance test you can run on receipt: full charge, run the unit in the agreed configuration with the agreed NIBP interval, and log the time from mains disconnection to the first low-battery annunciation. Record a baseline per model, then re-test a sample annually.
Spare-pack availability and price protection. Fix a part number, a price ceiling and an availability period that covers your depreciation cycle, plus a notification obligation before the pack is discontinued.
Firmware and battery pairing. Confirm the firmware version shipped, how battery-related alarms and shutdown thresholds are configured, and whether a firmware update can change runtime behaviour. Require release notes with each update.
Certificate continuity. Require written notice if the certificate covering the device lapses or its scope narrows. This matters in Europe right now: under Regulation (EU) 2017/745 Article 120 as amended by Regulation (EU) 2023/607, legacy certificates can support placing devices on the market only until 31 December 2027 for class III and class IIb implantable devices and until 31 December 2028 for other class IIb, class IIa, class Is and class Im devices, and only if conditions such as a lodged application and a notified body agreement are met. A tender that runs to 2031 should not rest on a certificate whose validity you never re-checked.
Loaner and exchange terms. If a pack has to go back for analysis, what runs the bed in the meantime? Battery swaps are exactly the case where a slow RMA becomes a clinical problem.
Red flags in the supplier's answers
Any one of these is worth a follow-up question; two or more together should change your shortlist.
- Runtime quoted as a single number, with no configuration, temperature or battery-age conditions.
- "Up to" figures supported only by a fresh pack in a supplier's demo room.
- Test reports that are undated, untraceable to a pack part number, or issued for a generic cell rather than the assembled pack.
- No documented end-of-life criterion, so "battery needs replacing" becomes a judgement call by a service technician.
- Battery not field-replaceable, or replacement requiring factory return on a device that stays in continuous use.
- No UN 38.3 test summary for spare packs, which quietly turns every reorder into a shipping delay.
- Certification documents naming a different legal manufacturer from the party you are contracting, with no explanation of the OEM or private-label relationship.
- Refusal to state which parameters and functions remain active on battery power.
What this guide does not do
It does not give you a target runtime in minutes, because that number belongs to your clinical workflow: the length of your longest routine transfer plus the time needed for someone to reach the patient, per ward type. It does not assess clinical measurement accuracy, cybersecurity depth or price benchmarks, which need their own evaluation sections. Standards and regulatory dates cited here were current at publication; check for amendments, and confirm certificate status against the issuing body rather than a supplier's PDF.
Frequently asked questions
How many minutes of battery backup should we require?
Derive it from the workflow, then test it. Take the longest routine intra-hospital transfer, add the response time you consider acceptable for reaching a mains outlet or a replacement device, and require the runtime at your worst-case configuration rather than the lightest one. A number set to cover the real transfer, measured under load, is more defensible than a larger number measured on an empty configuration.
Does a bigger battery mean longer backup?
Not reliably. Runtime depends on the energy drawn by the active parameters, display brightness, network use and recorder, plus the efficiency of the power management and the age of the pack. A larger pack also adds weight to a cart and changes charging behaviour. Compare watt-hours together with a measured runtime at the same configuration, not capacity figures on their own.
Is the battery part of the certified device or an accessory?
It depends on the manufacturer's technical documentation, and the answer has procurement consequences. Where the power source appears in the cleared device description — as it does in many public 510(k) summaries describing monitors as battery or line-powered — a change of chemistry, capacity or pack count may need regulatory assessment rather than a simple part-number swap. Ask the supplier how the ordered configuration maps to the certified one.
Can we accept the supplier's own test report instead of a third-party one?
Often yes, if the report is traceable to a controlled quality system: a defined method, recorded configuration, sample size, battery state of health and clear acceptance criteria. Keep third-party testing for the safety and transport questions, where independent evidence of the standard matters more than internal repeatability — IEC 62133-2 for the battery and UN 38.3 for transport.
What should a battery replacement clause contain?
A capacity threshold and the method used to measure it, a price ceiling and availability period for the spare pack, an exchange or loaner mechanism during analysis, and a notification duty before the pack is discontinued. Add the service tooling and training needed to read state of health on site, so the clause can be enforced by your own technicians.
Sources and templates
Primary references behind the checks above: IEC 60601-1:2005 with Amendments 1:2012 and 2:2020; IEC 60601-1-8 (alarm systems); IEC 80601-2-49 (multifunction patient monitoring equipment); IEC 60601-2-27 (ECG); IEC 62304 (medical device software); IEC 81001-5-1 (health software security); IEC 62133-2 (secondary lithium cells and batteries); UN Manual of Tests and Criteria, Part III, sub-section 38.3; ISO 13485:2016; Regulation (EU) 2017/745 with Annex VIII Rule 10 and Article 120 as amended by Regulation (EU) 2023/607; FDA 21 CFR Part 820 (QMSR, effective 2 February 2026), 21 CFR Part 830 (UDI) and public 510(k) summaries for patient monitors citing 21 CFR 870.1025, 870.2300 and 870.1130. The RFQ and evidence tables above are designed to be copied into a tender pack, and paired with the incoming runtime test described under acceptance so that the requirement survives contact with the ward.