Key result
Robotic surgery was successfully performed in two patients with permanent cardiac pacemakers, emphasizing the importance of pre-procedure planning and intraoperative management for patient safety.
Why the study?
Is robotic surgery safe and feasible in patients with permanent cardiac pacemakers?
Case Report (n=2)
Is robotic surgery safe and feasible in patients with permanent cardiac pacemakers?
This case series highlights the feasibility and safety considerations, including pre-procedure planning and the WHO checklist, for performing robotic surgery in patients with permanent pacemakers.
May support feasibility of robotic surgery in pacemaker patients with planning; leaves open need for larger prospective studies.
With increasing experience, more complex patients are undergoing robotic surgery but the patient safety during these procedures remains paramount. Being a relatively recent technique of minimal access surgery, the safety and feasibility of robotic surgery is still under scrutiny. We recently performed two robotic procedures in patients who have permanent cardiac pacemaker. We believe this is the first published report through which it is shared and discussed, the preoperative and intraoperative management for these patients along with the importance of WHO checklist for safely performing robotic procedures. The importance of pre-procedure planning and briefing cannot be emphasised enough as these along with intraoperative management remain the key step in dealing with an adverse cardiac event due to permanent pacemaker malfunction.
No takes yet. Share an insight, caveat, or question.
Ubee et al. (2018) conducted a case report in Permanent cardiac pacemaker (n=2). Robotic surgery was evaluated. Robotic surgery was successfully performed in two patients with permanent cardiac pacemakers, emphasizing the importance of pre-procedure planning and intraoperative management for patient safety.
Synapse has enriched 5 closely related papers on similar clinical questions. Consider them for comparative context: