Interface control of treadmills. Risks with non-compliance of safety features.
DOWNLOAD the full PDF
Dear customers, distributors, field service engineers and manufacturers,
A potential risk for patients and/or subjects on a remote controlled treadmill may arise, if the remote control from host equipment (PC, ECG, stress test, CPET, metabolic cart, MoCap, etc.) via interface
- takes place through interface protocol without high safety standard, or
- if safety features (failsafe, status communication, checksum and acknowledgement, etc.) of the interface protocol have not been implemented well.
- A treadmill is remote controlled via ECG or metabolic cart during a cardiopulmonary stress test / ergometry.
- The software of the ECG or metabolic cart has an incorporated load profile, for example Bruce, Naugthon or ramp protocol, where the treadmill belt speed and incline are automatically increased step by step based on pre-set time intervals.
- The patient or the operator press STOP button on the treadmill or the emergency push-button on the treadmill because for example an ECG electrode became lose or the mask for VO2max measurement does not fit well.
- The treadmill stops. Since the patient and operator feel safe, the patients turns 90° on the treadmill belt and then facing the operator / doctor in order to fix the electrodes or the mask.
- Suddenly the treadmill belt automatically starts again without warning, when the patient is still standing 90° on the treadmill belt and facing the operator / doctor.
- In such unexpected / unwanted start of the treadmill (when the subject and operator are not prepared) there is an increased risk of falling on a treadmill, which may result in serious injury.
This possible scenario can occur, if the manufacturer of the controlling host equipment and software (ECG, stress test, CPET, metabolic cart, MoCap, etc.) did not implement several safety features and functions which are available on safe treadmills.
Q: Why does the treadmill start suddenly?
A: Because in that scenario the software of the controlling ECG or metabolic cart did not communicate the STOP status of the treadmill.
So “in the background” the automated load protocol was still active, and when the next stage of the protocol was due, the software of the controlling ECG or metabolic cart started the treadmill automatically again to continue the stress test.
h/p/cosmos treadmills with interface protocols coscom v3 and/or coscom v4 have safety features and functions which can prevent from such risks and accidents. See www.coscom.org
Extract of h/p/cosmos quality assurance & regulatory affairs agreement | coscom v3 | coscom v4 regarding standards
EN 62304, ISO 14971 and medical device regulation MDR (EU) 2017/745.
For staying in compliance with safety related issues, the MDD and the MDR on the interface communications and linkage of medical devices both parties agree to:
- inform each other in writing before each party makes amendments on interface and/or software which can have safety related impact on the treadmill control. The same clause applies for other safety related parts & components.
- perform & exchange tests & test protocols on interface and/or software which can have safety related impact on the treadmill and/or ergometer control.
b1) With electronic data logger all commands between the systems (treadmill/ergometer and host equipment/software) via coscom v3 or coscom v4 protocol are saved and documentation will be exchanged and analyzed, verified, validated and archived by both parties.
b2) Checksum and Acknowledgement have to be implemented in the interface protocol accordingly.
b3) Error simulation on failsafe function (timeout simulation of broken interface cable or PC failure or software crash) and with “status communication” of stop button pressed on the treadmill have to be made.
b4) If “stop” or “pause” button was pressed on the treadmill and/or ergometer, also the load protocol on the host PC-Software or system has to stop or pause and must not continue to send speed or elevation commands automatically. See implementation notes v3 or v4 on http://www.coscom.org
Download of the checklist, sample agreement and template for test and release protocol:
It is important for programmers to bi-directional communicate and synchronize the status of the treadmill with the status of the load profile software (e.g. stress ECG) and also to read the load data and parameter (speed, elevation, distance, time, etc.) from the treadmill and synchronize. Especially for validity of ergometry tests it is important to have the real treadmill and ergometer data (speed, elevation, load) transmitted via interface and then assigned with the data of the subject such as ECG, oxygen uptake, breathing frequency, breath volume, etc. If only the assumed target data (speed, elevation, load) are considered in the assessment, the test could be invalid due to wrong load data in case the treadmill speed has been modified or the treadmill could not reach the target speed due to weak power supply for example.
Not only experts, software programmers or field service engineers can check if the treadmill control via host equipment is safe.
Some checks and simulations (not all!) can also be made by customers and operators of such treadmills controlled via stress test software.
Simple but effective test scenario which can be performed by any user:
- Do not put anybody on the treadmill for safety reasons!
- control the treadmill via host equipment with an incorporate load profile, for example Bruce, Naugthon or ramp protocol, where the treadmill belt speed and incline are automatically increased step by step based on pre-set time intervals.
- press STOP button on the treadmill or the emergency push-button on the treadmill.
- wait several minutes until the next stage of the protocol was due
- the software of the controlling ECG or metabolic cart MUST NOT start the treadmill automatically again
Repeat such tests with other functions of the treadmill, such as reducing speed and load with manual treadmill keyboard control, pause function, safety stop, emergency stop, power off and re-power on, etc.
Report the observed results to the respective manufacturers and suppliers.
For any questions and/or support and/or PMS observations on that please send an eMail to email@example.com
Check also www.coscom.org and h/p/cosmos website: