Clinical Engineering and Healthcare Technology Management Exercises

These exercises practise clinical engineering and healthcare technology management as operational engineering. They cover installed asset readiness, preventive maintenance capacity, availability, downtime planning, electrical safety screening, recall closure, network load, incident evidence, replacement decisions, and controlled release after change.

The purpose is not to replace local procedures, manufacturer instructions, clinical governance, or regulatory obligations. The purpose is to develop the engineering reasoning needed to keep healthcare technology safe, available, traceable, maintainable, and fit for real clinical workflows.

Assume simplified project-specific criteria unless an exercise states otherwise. Real clinical engineering decisions should also check device criticality, patient-care dependency, manufacturer recommendations, local policy, clinical risk, cybersecurity, infrastructure, training, service contracts, spares, utilization, and incident history.

How to Use These Exercises

For each calculation, define:

1. the clinical workflow or asset fleet being managed;
2. the failure consequence and downtime tolerance;
3. the evidence needed before clinical release;
4. the maintenance, training, network, safety, or spare-part control being tested;
5. the action if the metric fails.

The common mistake is treating clinical engineering as repair administration. Useful metrics connect asset data, risk, maintenance capacity, infrastructure, training, and patient-care continuity.

For each result, identify whether the metric is a dashboard signal, a release gate, or a corrective-action trigger. Aggregate completion percentages should never hide an incomplete safety, alarm, network, training, or configuration check.

Exercise 1: Acceptance Readiness Before Clinical Use

A hospital receives 48 networked patient monitors. Before clinical use, each monitor needs five readiness records:

1. asset tag;
2. visual inspection;
3. electrical safety screen;
4. network connectivity check;
5. user training confirmation.

The commissioning review finds:

Readiness status	Monitors
All five records complete	39
Missing training confirmation only	5
Missing network check only	3
Missing safety screen	1

Calculate the clinical release readiness rate. Which monitors must be blocked from release?

Solution

Readiness rate:

Monitors not fully ready:

The monitor missing safety screening must be blocked immediately. The three missing network checks should also be blocked if network connectivity supports alarms, waveforms, data export, or central monitoring. The five missing training confirmations require local release decision based on risk and user availability.

Engineering Comment

An 81.25 percent readiness rate is not sufficient for a connected clinical fleet. The issue is not only quantity. A single monitor with incomplete safety screening or unverified network behavior can create patient-care risk.

Acceptance evidence should match local use. If monitors are deployed for central alarm surveillance, network validation is part of clinical release, not an optional IT task.

Exercise 2: Preventive Maintenance Workload Capacity

A clinical engineering team manages a fleet of infusion pumps:

Each pump requires one preventive maintenance event every six months. Each event takes:

The team has:

available for this pump fleet after urgent repairs and other duties. Calculate the monthly PM workload and capacity margin.

Solution

Monthly PM events:

Monthly PM time:

Convert to hours:

Capacity margin:

Engineering Comment

The pump PM workload fits within the available monthly hours. The margin should not be interpreted as idle time. It must also cover locating devices, cleaning delays, missing accessories, documentation, failed PM actions, corrective repairs discovered during PM, and clinical scheduling constraints.

If device availability is poor because pumps cannot be found or removed from service, the real bottleneck may be logistics rather than technician labor.

Exercise 3: Fleet Availability from MTBF and MTTR

A ventilator fleet has observed:

and average repair time:

Estimate inherent availability:

Solution

Availability:

As a percentage:

Engineering Comment

The inherent availability appears high, but clinical availability may be lower if failed devices wait for parts, vendor response, cleaning, battery replacement, software access, or clinical handoff. MTTR should be clearly defined: hands-on repair time is not the same as total downtime.

For life-support assets, the engineering decision should include spare coverage and escalation time, not only the MTBF/MTTR equation.

Exercise 4: Loaner Equipment for Downtime Coverage

A ward uses 72 syringe pumps. Historical data show that 6 percent of the fleet is unavailable during peak weeks because of preventive maintenance, repair, cleaning, or battery replacement.

The ward wants at least 3 additional pumps as surge margin. Estimate the minimum number of loaner pumps needed.

Solution

Expected unavailable pumps:

Round up to whole pumps:

Add surge margin:

Engineering Comment

The minimum loaner pool is 8 pumps. This is a planning value, not a guarantee. If failures cluster after software update, battery aging, cleaning backlog, or accessory shortage, the loaner pool may still be insufficient.

Downtime planning should also confirm chargers, cables, compatible syringes, storage location, cleaning status, user familiarity, and asset tracking.

Exercise 5: Electrical Safety Screening

A portable device has measured insulation resistance:

during a local safety screen at:

Estimate leakage current using:

Compare the result with a local screening limit of 3 microA.

Solution

Convert resistance:

Leakage current:

In microamps:

Comparison:

Engineering Comment

The screening result passes the local criterion. The clinical engineering record should still preserve device identity, accessory configuration, test equipment calibration, environmental condition, applied part setup, and whether the test was performed after repair, relocation, cleaning, or incident review.

Electrical safety decisions should not be reduced to a single number without configuration context.

Exercise 6: Recall Closure Rate

A safety notice affects 126 devices across four departments. After two weeks, the recall team records:

Status	Devices
Corrected and verified	96
Located but awaiting correction	18
Temporarily removed from service	7
Not yet located	5

Calculate the correction closure rate and the unresolved affected-device count.

Solution

Correction closure rate:

Unresolved affected devices:

Unresolved fraction:

Engineering Comment

A 76.2 percent closure rate may be unacceptable if the safety notice affects essential performance or patient safety. The five devices not yet located are especially important because they may remain in use without correction.

Recall management depends on accurate asset data, department ownership, quarantine rules, loaner availability, clinical communication, and verification that the correction actually reached the installed configuration.

Exercise 7: Network Load from Physiological Monitors

A central monitoring network receives waveform data from 64 bedside monitors. Each monitor sends:

of sustained data during normal operation. The network segment has planned available capacity for this traffic of:

Estimate utilization from waveform traffic alone.

Solution

Total waveform traffic:

Convert to Mbit/s:

Utilization:

Engineering Comment

Waveform traffic alone uses 57.6 percent of planned capacity. That leaves margin, but the review should include alarms, retries, software updates, image transfer, time synchronization, cybersecurity tools, logging, wireless overhead, burst traffic, and failure modes.

Clinical network validation should test behavior during degraded network conditions, not only nominal bandwidth.

Exercise 8: Alarm Routing Latency

A nurse call integration requires alarm delivery within:

The measured average latency components are:

Component	Time
Device alarm processing	0.8 s
Gateway transmission	1.1 s
Server routing	1.4 s
Mobile notification delivery	0.9 s

Calculate total average latency and margin. Should the team accept this as complete validation?

Solution

Total average latency:

Average margin:

Engineering Comment

The average latency meets the criterion, but average latency is not complete validation for alarm routing. The team should test peak latency, packet loss, wireless roaming, mobile device sleep state, server failover, alarm floods, user acknowledgement, and escalation.

An alarm system can pass average timing while still failing under precisely the conditions where clinical response matters most.

Exercise 9: Incident Evidence Completeness

A device incident review requires six evidence fields:

1. device serial number;
2. software version;
3. configuration profile;
4. accessory set;
5. device log export;
6. maintenance history.

Across 22 incident records, the review finds 102 completed fields out of the possible total. Calculate evidence completeness.

Solution

Total possible fields:

Completeness:

Missing evidence:

Engineering Comment

Evidence completeness of 77.3 percent is weak for incident investigation. Missing software version, configuration, accessory, or log data can prevent root-cause analysis and lead to corrective actions based on assumptions.

Clinical engineering should improve incident intake forms, device quarantine rules, log export workflow, asset database accuracy, and staff instructions for preserving evidence after device-related events.

Exercise 10: Replacement Decision from Repair Cost Ratio

A laboratory analyzer has:

The last 12 months of corrective repair cost total:

The local review threshold flags replacement when annual repair cost exceeds 25 percent of replacement cost. Calculate the repair cost ratio.

Solution

Repair cost ratio:

Comparison:

The analyzer exceeds the local replacement review threshold.

Engineering Comment

The threshold flags the device for replacement review, not automatic replacement. The decision should also include downtime, parts availability, service response, clinical volume, quality control failures, cybersecurity support, operator complaints, reagent compatibility, and procurement lead time.

Replacement planning is a lifecycle engineering decision, not only a finance decision.

Exercise 11: Controlled Release After Software Update

A vendor software update is applied to 38 connected devices. The local release checklist requires four checks per device:

1. version confirmation;
2. functional smoke test;
3. network data export;
4. alarm routing test.

After the update, the team has completed:

Check type	Completed checks
Version confirmation	38
Functional smoke test	36
Network data export	34
Alarm routing test	32

Calculate release-check completion across all required checks. Which missing category is most critical for connected monitoring use?

Solution

Total required checks:

Total completed checks:

Completion:

Missing checks:

Check type	Missing
Version confirmation	0
Functional smoke test	2
Network data export	4
Alarm routing test	6

Engineering Comment

The overall completion is 92.1 percent, but connected monitoring release should focus on the missing alarm routing tests. Six devices have not proven that alarms reach the intended clinical path after the update.

A release decision should not hide critical missing checks inside an aggregate score. If alarm routing is patient-care critical, those devices should remain blocked or restricted until validated.

Review Checklist

When reviewing clinical engineering metrics, ask:

• Does the metric reflect clinical consequence, not only work-order completion?
• Is the installed configuration known: location, software, accessories, network, and owner?
• Are safety, alarm, data, training, and downtime checks complete before release?
• Does preventive maintenance capacity include locating, cleaning, documentation, failed checks, and clinical scheduling?
• Are downtime and loaner plans tested under realistic conditions?
• Are recalls closed on the actual installed devices, not only in a spreadsheet?
• Do incident records preserve logs, configuration, accessories, and maintenance history?
• Do software and network changes include rollback, validation, and user communication?
• Are critical release gates separated from lower-risk administrative completion items?
• Can each operational decision be traced to device identity, location, configuration, and clinical owner?

Clinical engineering is strongest when asset data, risk, maintenance, infrastructure, user workflow, and evidence all point to the same operational reality.