A relative of mine in southern Greece is being treated for an aggressive cancer. He lives more than three hours from a suitable treatment facility in Athens, and that distance is interfering with his care. We should be doing more to bring specialist treatment closer to people like him.
He’s only a couple of years older than me and has lived all his life in a small village. His treatment sessions have been delayed, and maintaining a regular schedule has been pretty much impossible. I don’t know what those delays mean for his individual prognosis, and I won’t pretend to. I do know that the journey to Athens has become part of the difficulty of being treated.
When people talk about access to healthcare, they sometimes seem to mean that a service exists somewhere and a patient is entitled to use it. For my relative, the service exists in Athens. Getting there regularly while undergoing treatment is the problem.
That’s why a report in IEEE Spectrum about a robot intended for remote stroke procedures caught my attention. The proposed use is to let a specialist operate on a patient in another hospital, without first moving the patient to the specialist. The treatment the developers ultimately want to make available remotely is thrombectomy, the removal of a blood clot from a blocked blood vessel.[1]
My relative isn’t waiting for stroke surgery. Nothing in this research suggests that this particular robot could provide his cancer treatment. The connection is the problem of distance, and the possibility of moving some specialist capability closer to the patient.
I find that a much more compelling reason to develop medical technology than the prospect of a more impressive operating theatre.
There is an evidence boundary here, and it needs stating before enthusiasm gets ahead of the work. Unity Health Toronto reports that a surgeon performed diagnostic angiograms on two patients at St. Michael’s Hospital while he was at another hospital six kilometres away. These were diagnostic procedures, not remote emergency clot removals. A specialised clinical team stayed with the patients, and the hospitals were connected by a fibre-optic network.[2]
Remedy Robotics, the developer, describes its N1 system as investigational. Its safety and effectiveness for clinical use have not been established, and it isn’t available for commercial sale.[3]
So this is an early step towards a possible service. It gives us a reason to investigate, without giving us grounds to tell regional patients that the problem has been solved.
One comment in the Spectrum report is worth keeping in front of anyone assessing it. David Bell, Remedy’s surgeon co-founder, tells the reporter: “Smoothness and precision are not clinical outcomes.”[1]
I agree. If the aim is better access, we have to ask whether patients actually receive appropriate treatment sooner and whether their lives are better afterwards. Watching a machine perform a controlled movement won’t answer either question.
The detail I keep coming back to in the Toronto account is the team beside the patient. The surgeon was elsewhere, but the patient was still in a hospital with specialised people in the room.[2] That ought to shape how we think about introducing this technology into regional care.
Imagine a regional hospital considering such a service. The specialist can connect from a major centre, and the equipment has passed its tests. Who gets the patient ready? Who operates the imaging equipment, monitors the patient and deals with a complication that needs hands in the room?
Those are staffing questions before they’re purchasing decisions. I’d want the people responsible for the local service answering them before anybody announced that their hospital was getting a robot.
The same applies to the connection. A hospital planning remote intervention needs a tested response to an interrupted link, with clear responsibility for what happens at the bedside. A stopped machine doesn’t settle what to do about a patient who still needs treatment. The service needs an agreed way to continue care or arrange transfer, including the circumstances in which the remote procedure shouldn’t begin.
I’ve spent much of my working life in software, so I’m inclined to look at what happens around the equipment. Here, the consequence of an incomplete design would be borne by somebody lying in a hospital bed. The handover between teams deserves at least as much attention as the controls on the surgeon’s screen.
None of this is an argument for waiting until every difficulty has disappeared. That would be a convenient way to leave things exactly as they are. My relative would still have his trip to Athens, and families elsewhere would still have to organise their lives around journeys to treatment.
I’d favour careful trials in regional hospitals that can support the work, with funding for the local staff and their training included from the beginning. I’d also want the evaluation to follow patients through the whole service. Time saved by avoiding a transfer should be counted alongside time spent preparing equipment or waiting for a remote specialist to become available. Complications and subsequent transfers belong in that account too.
There will be places where the necessary local capability can’t be provided safely. In those places, better transport or stronger referral arrangements may be the more useful investment. We shouldn’t force a robot into the answer simply because somebody has built one.
Nor should we accept that a long journey is the only reasonable answer without examining what could be done locally. The judgement needs to be about the particular treatment and the hospital expected to provide it. It won’t be the same for every town.
This is a question Australians ought to take seriously as well. I wouldn’t assume that a village in southern Greece and a regional Australian community face identical healthcare arrangements. The question I’d ask of both is how much of a patient’s care could safely be delivered nearer home, with specialist support from elsewhere when it is needed.
For ongoing treatment, that might mean something quite different from remote surgery. The doctors have to determine which parts require a major centre and which could be provided locally. My relative’s experience gives me no basis to prescribe his treatment, but it does give me a reason to ask why getting to it has become so difficult.
I want this sort of research to succeed. Bringing specialist expertise closer to regional patients is a worthwhile use of engineering. When a hospital proposes buying the equipment, though, ask it to show who will be beside the patient and how the service will run. Fund those people for as long as the equipment is expected to be used.
Sources:
[1] Max G. Levy, IEEE Spectrum, Can Robots Bring Stroke Surgery to Remote Hospitals?, https://spectrum.ieee.org/telesurgery-stroke
[2] Unity Health Toronto, Remote robotic-assisted diagnostic procedures, https://unityhealth.to/2025/11/first-robotic-assisted-neurovascular-procedure
[3] Remedy Robotics, N1 System investigational status, https://www.remedyrobotics.com


