How to Automate Renvio
Renvio automates the dialysis clinic's own record. Dialysis Manager holds treatment documentation, labs and medications on one screen for haemodialysis and peritoneal dialysis, and Billing Manager scrubs claims, verifies insurance and posts remittances. Hospital systems, transport brokers and laboratory portals stay outside it, and an agent such as WebRun reads those.
The chair is booked for years, not for an hour
Renvio is the cloud EMR and billing platform for dialysis clinics, formed when Renesan and Visonex, two long-standing names in dialysis software, joined forces under one brand. The people in it are nurses, patient care technicians, dietitians, social workers, billers and a medical director.
A dialysis clinic is unlike almost any other outpatient setting, because its patients never really leave. Someone on in-centre haemodialysis arrives three times a week, sits in the same chair for four hours, and does that for years. Twelve hours a week in the building is more contact than a primary care patient gets in a decade.
The clinic is also a capacity business. A fixed number of stations each run two or three shifts a day, so every patient occupies a named chair on a named shift. Fill the chairs and the month works. Leave one empty and nothing refills it, because the patient who might have taken it is already sitting in their own.
An empty chair is decided somewhere else
The record is complete for the four hours a patient is on the machine. It says little about the twenty hours after they leave, and almost nothing about why they might not arrive at all.
Dialysis patients are hospitalised often, and an admission is the commonest reason a chair sits empty. The hospital knows at two in the morning. The clinic finds out when the van has nobody to collect. An emergency visit is the same story a shift later.
Transport is its own problem. Many patients reach treatment on non-emergency medical transport booked through a broker, and the booking lives on the broker's website, not in the clinic's schedule. A ride nobody confirmed becomes a missed treatment nothing in the chart could have predicted.
Then the reporting. Facility quality measures go to a federal submission system on a fixed calendar. Monthly panels are run by a reference laboratory with its own results portal. Payers keep eligibility on their own sites, and the nephrologist's practice runs on software the unit does not use.
Renvio holds the run, the lab and the claim in one record
Inside its own walls Renvio fits the work closely, and a clinic should push it as far as it will go.
Kidney Care Cloud is the platform and Dialysis Manager the EMR inside it: dialysis-specific documentation built around haemodialysis and peritoneal dialysis rather than general medicine, and a unified patient view putting labs, medications, prescriptions and treatment history on one screen. Clinical documentation flows into the billing workflow instead of being re-entered, and remote patient monitoring brings data from outside the clinic into the same record. Billing Manager submits, resubmits and scrubs claims, runs automatic insurance verification at every month and admit, and handles statements, remittances and AR reporting, working with Waystar and Availity. The analytical data warehouse holds the predictive work, surfacing patient risk and trends earlier along with what drives each signal.
The condition on all of it is the same. It reasons over what reached the record. A hospital's admission list has not. Neither has the transport broker's booking page, the reference laboratory's portal, or the federal quality submission site.
The reason a chair sits empty is knowable by six
Almost everything the floor gets surprised by was written down somewhere overnight.
Admissions and emergency visits read each morning against today's chair list, so a patient who is not coming is known to be in hospital before the van is dispatched and before a nurse spends twenty minutes on the phone. Tomorrow's transport bookings checked on the broker's own site against tomorrow's schedule, so the ride nobody made surfaces the night before instead of on the morning it is needed.
Monthly panels collected from the reference laboratory as they result and set against the previous two, so a falling haemoglobin or a drifting phosphate reads as a direction rather than a number on a page. The federal quality submission portal read against what the clinic still has outstanding, weeks before the window closes. Eligibility confirmed for visiting patients before a chair is promised to somebody who cannot be billed for.
A dialysis unit fixes this boundary and nothing overrides it. Unattended covers the reading of those sites, the comparison against last month, and the flag it raises. Anything that changes a treatment record, alters a prescription, files a claim or reaches a patient is prepared and waits for a qualified person to check it.
Somebody opens all of those sites already
They do it between rounds with a phone in one hand, and after the van has already left. The work is not difficult. It is badly timed.
WebRun is an AI agent that drives a real Chrome browser, signed in the way your staff sign in. It opens the hospital's system, the transport broker's page, the laboratory's portal or a payer's site, reads what is there, and returns one list against today's shifts with the exceptions at the top.
It runs on your schedule inside your own private environment, sessions are not shared between tools, and a workflow can be restricted to a named list of domains. You can watch a run and stop it at any point.
Below, every workflow shows its sites and its schedule before you switch it on.
Questions people ask
Will it alter a treatment record or a prescription?
No. It reads outside systems and reports back. Any change to documentation in Renvio, any dose adjustment, any claim and any message to a patient is prepared for a nurse, a nephrologist or a biller to approve, because those are clinical and financial decisions rather than lookups.
Neither the hospital nor the broker gives us data. What does it work from?
Through the browser, using the logins your staff already have. It works those sites the way a ward clerk does, reading what is on screen, so a system with no API and no export button is as reachable as one with both. Nothing needs building on either side first.
How does patient information stay protected during a run?
Runs happen in your own private environment using your staff's existing logins, and a workflow can be locked to a named list of domains so it visits only the sites you approved. Sessions are not shared between tools, and every run can be watched and stopped.
11 ready-made Renvio workflows
Each one names the apps it touches and the exact steps it takes. Open one to read what it will do, then turn it on.
Want one of these running on your own Renvio?
Show WebRun the process once and it will run it on schedule, in your own private browser environment.




