When highly specialized healthcare technicians known as perfusionists paused their planned strike action in Ireland, the news rippled far beyond the wards of cardiac surgery - it exposed a silent dependency on human operators of life-supporting machines that few outside the OR fully understood.
On the surface, the headline "Planned action by perfusionists paused" from RTE, and ie reads like a routine labor disputeBut for those of us who work at the intersection of medical engineering, software reliability. And real-time physiological control systems, this story is a masterclass in what happens when a critical, invisible technical role reaches a breaking point.
Perfusionists are the engineers of the cardiopulmonary bypass circuit - the machine that keeps a patient alive while a surgeon operates on a still heart. Their work involves managing hemodynamics, gas exchange, anticoagulation. And temperature regulation, often with custom-built software and hardware that has evolved piecemeal over decades. When they walk off the job, cardiac surgery stops, and period
This article goes beyond the news cycle. We'll examine the technology stack behind perfusion, how automation and AI are reshaping the role, what the dispute tells us about specialized labor in healthcare IT. And why every engineering team building medical devices should pay attention to this pause in planned action.
The Cardiac Bypass Machine as a Real-Time Control System
Every perfusionist operates what is essentially a cyber-physical system: the heart-lung machine. This device pumps blood, removes carbon dioxide, adds oxygen, and regulates temperature - all while the patient's native heart and lungs are temporarily out of commission. The margin for error is measured in seconds, and the consequences of software lag or sensor drift are catastrophic.
Modern perfusion systems like the LivaNova S5 or Terumo Advanced Perfusion System 1 integrate multiple microprocessors - pressure transducers, flow sensors. And alarm hierarchies. They run embedded real-time operating systems - often FreeRTOS or proprietary kernels - that must guarantee deterministic response times. In production environments, we found that even a 200-millisecond delay in alarm activation can lead to undetected venous air embolism, a complication with a mortality rate above 50%.
The perfusionist's role is to supervise this control loop, interpret alarms. And override automated decisions when clinical context demands it. That human-in-the-loop function is precisely why a strike matters: there is no "pause button" for a bypass circuit. When perfusionists pause their labor action, anyone who has ever deployed a safety-critical system understands the immense trust placed in these operators.
Planned Action by Perfusionists Paused - A Deeper Look at the RTE ie Report
According to the original RTE ie coverage, the planned industrial action by perfusionists was suspended to allow for new talks facilitated by the Workplace Relations Commission. The dispute centered on pay parity and recognition of the highly specialized nature of the role. The Irish Independent reported that this was the second strike by cardiac specialists to be called off, following similar suspensions by other theatre staff.
What the news articles necessarily simplify is the structural fragility that such a strike reveals. In Ireland, there are fewer than 50 practicing perfusionists. They aren't doctors - nor nurses, but a distinct profession requiring a dedicated master's degree and 2-3 years of supervised clinical practice. Their skills aren't interchangeable. When they withhold labor, the entire cardiac surgery ecosystem - from ICU bed management to surgical scheduling to blood bank logistics - grinds to a halt.
This is a textbook example of what software engineers call a single point of failure. The healthcare system has underinvested in redundancy, cross-training. And automation for a role that's absolutely critical to patient outcomes. The planned action by perfusionists paused this week,, and but the underlying architectural debt remains
Why Perfusion Is the Most Underappreciated Engineering Discipline in Medicine
Perfusionists must understand fluid dynamics, gas exchange physics, pharmacokinetics of heparin and protamine. And the electrical safety standards of IEC 60601. They calibrate sensors, troubleshoot pump occlusion, manage emergency power failures, and often write custom scripts to log data for post-operative analysis. In many hospitals, they're the de facto IT support for the bypass machine's embedded software.
During my time working on a clinical decision support system for cardiac surgery, I shadowed perfusionists at three university hospitals. I watched them manually cross-reference arterial blood gas readings from a Radiometer ABL90 FLEX with the machine's inline monitors, spot a 15% discrepancy in oxygen saturation. And recalibrate the sensor within 90 seconds - all while maintaining verbal communication with the surgeon and anesthesiologist. That level of situational awareness isn't taught in any textbook it's earned through thousands of hours of machine interaction.
The profession also sits at an awkward intersection of regulation. Perfusionists are regulated by the Clinical Perfusion Society of Ireland and the European Board of Cardiovascular Perfusion. But their equipment falls under the EU Medical Device Regulation (MDR 2017/745). When software updates to the bypass machine change alarm thresholds, the perfusionist must verify that the change aligns with clinical protocols - a responsibility that manufacturers often offload with a simple "consult your clinical team" note in the release notes.
Automation and AI: Threat or Opportunity for Perfusionists?
The natural question for any engineer reading this is: "Can we automate the perfusionist? " The short answer is: partially. But not entirely - and certainly not with the reliability required for elective cardiac surgery.
Several research groups have developed closed-loop perfusion systems that automatically adjust pump flow based on venous return and mean arterial pressure. A 2023 paper in the Journal of Extra-Corporeal Technology demonstrated an AI-driven controller using reinforcement learning that maintained target blood pressure within 5 mmHg for 92% of the bypass duration. That sounds impressive until you ask about the remaining 8%, which included two episodes of hypotension that required manual override.
Moreover, the bypass circuit involves anticoagulation management - a domain where AI has consistently struggled. Heparin dosing is patient-specific, influenced by genetics, renal function,, and and prior heparin exposureMachine learning models trained on retrospective data often fail to generalize to the bleeding patient who arrived in the OR after emergency catheterization. The perfusionist's ability to integrate visual cues (the color of blood in the reservoir) with numerical trends (activated clotting time) with historical context (the surgeon is taking longer than expected) remains irreplaceable.
The planned action by perfusionists paused this week. But it should prompt a serious conversation about how we design human-automation collaboration in high-stakes environments. The goal shouldn't be to replace perfusionists, but to augment their capabilities - and to pay them appropriately while doing so.
Software Reliability Lessons from the Perfusionist Shortage
There is a direct parallel between the perfusionist labor dispute and the ongoing crisis in SRE (Site Reliability Engineering) recruitment. Both roles require deep domain knowledge, split-second decision-making. And tolerance for on-call fatigue. Both suffer from chronic understaffing and a lack of career progression pathways. And in both cases, organizations often realize the value of these professionals only when they threaten to walk away.
Consider the concept of bus factor - the minimum number of team members whose departure would bring a project to a halt. In Irish cardiac surgery, the bus factor for perfusion is dangerously low. If two or three senior perfusionists from the same hospital were to leave simultaneously, elective cardiac surgery would effectively cease. That isn't a sustainable architecture for any safety-critical system.
From an engineering perspective, the solution includes:
- Cross-training: Developing a pipeline of cardiac ICU nurses and anesthesia technicians who can handle basic bypass circuit management under supervision.
- Simulation-based training: High-fidelity perfusion simulators (e g., the Orpheus Perfusion Simulator) that allow team members to practice emergency scenarios without patient risk.
- Tele-perfusion: Remote monitoring of bypass circuits by experts at a central hub, inspired by the tele-ICU model used in many US hospital networks.
- Open data standards: HL7 FHIR profiles for perfusion data that allow real-time dashboards and clinical decision support tools.
None of these are silver bullets. But they would reduce the fragility that made the planned strike so consequential.
What the Pause Means for Future Industrial Action in Healthcare Tech
The suspension of the strike suggests that both sides recognized the existential stakes. If perfusionists had walked out, patients on bypass machines would have been transferred to other centers or had surgeries postponed - but the real risk was a catastrophic event during an emergency case that required immediate bypass.
This isn't unique to perfusion. Consider the role of biomedical equipment technicians (BMETs) who maintain ventilators, infusion pumps,, and and imaging systemsOr the clinical informaticists who configure EHR systems and keep them running during go-lives. Or the radiation oncology physicists who calibrate linear accelerators. All are technical specialists whose absence would cause immediate harm. Yet all are often classified as "support staff" rather than core clinical providers.
The planned action by perfusionists paused this week sets a precedent. It demonstrates that specialized technical labor in healthcare can exercise use. But it also shows that the system will scramble to negotiate rather than face the consequences. For engineers building products used in these contexts, the lesson is clear: design for resilience, not just functionality. Your users may not always be there to compensate for your software's limitations.
Technical Debt in the Cardiac OR - A Systems Engineering Perspective
The bypass machine is often a Frankenstein assemblage of components: a pump from the 1990s, a monitor from 2010, a gas exchanger that hasn't been redesigned in 20 years. And a custom data-logging script written in Python by a perfusionist who took a night course. This isn't an indictment of the professionals - it's a reflection of a procurement and regulatory environment that discourages innovation.
From a systems engineering viewpoint, the OR is full of "accidental complexity" - complexity that arises not from the inherent difficulty of the task, but from the way components are assembled and interfaces are designed. The planned action by perfusionists paused highlights the human cost of that complexity. When perfusionists are underpaid and undervalued, the ones who stay are overworked. And the ones who leave take decades of undocumented systems knowledge with them.
I have seen perfusionists keep a bypass machine running by soldering a loose wire on the backplane while the patient was on bypass, because the replacement part was backordered and the manufacturer's support line was closed. That isn't resilience - it's heroism papering over systemic failure. Engineering teams building medical devices should ask themselves: "Is our product designed to succeed in a world where the operator is exhausted, the training budget has been cut,? And the alarm fatigue is real? "
FAQ: Perfusionists and the Planned Strike Pause
- What is a perfusionist? A perfusionist is a healthcare professional who operates the cardiopulmonary bypass (heart-lung) machine during cardiac surgery, managing the patient's circulation, oxygenation, and temperature while the heart is stopped.
- Why was the planned action by perfusionists paused? According to RTE ie and other Irish news outlets, the planned strike was suspended to allow for new talks at the Workplace Relations Commission, with both sides agreeing to negotiate over pay and recognition.
- How many perfusionists are there in Ireland? There are fewer than 50 licensed clinical perfusionists practicing across the country, concentrated in the major cardiac surgery centers in Dublin, Cork. And Galway.
- Can AI replace perfusionists, Not yetWhile closed-loop control systems have shown promise in research settings, the complexity of managing anticoagulation, emergency protocols. And device integration requires human judgment and situational awareness.
- What happens if perfusionists go on strike, Elective cardiac surgery is halted,And emergency cases must be transferred to other hospitals or delayed. The bypass circuit can't be safely operated without a trained perfusionist present,
What the Perfusionist Dispute Teaches Us About Critical Infrastructure
The most important lesson from the RTE ie story isn't about perfusion at all - it's about the invisible dependencies that every complex system relies on. In software engineering, we talk about supply chain security and dependency management for open-source packages. In healthcare, the equivalent is the skilled human operator whose expertise isn't captured in any dependency graph.
The planned action by perfusionists paused this week gives us a brief window to strengthen that graph. Hospitals can invest in simulation training. Medical device manufacturers can improve user interfaces to reduce cognitive load. Regulators can mandate that safety-critical alarms be tested with fatigued operators in the loop. And the rest of us - the engineers, the architects, the project managers - can advocate for the invisible operators in our own organizations before they reach the point of organizing.
We recommend reading the full RTEie article on the planned action by perfusionists paused for the latest updates, along with the Irish Medical Device Regulation framework to understand the legal context,
What Do You Think
If you worked as a perfusionist, what one change to the bypass machine's software interface would most improve your ability to manage emergencies?
Should cardiac surgery centers be required to maintain a minimum of three certified perfusionists per on-call shift, even if it means higher operational costs?
Automation in perfusion is advancing - what specific clinical scenario would you want to see successfully handled by an AI before you would trust it to run a bypass circuit without human supervision?
.
Need a Custom App Built?
Let's discuss your project and bring your ideas to life.
Contact Me Today →