How to Automate OmniMD

A vein practice is documentation with a procedure attached

An endovenous ablation is a short procedure with a long paper trail in front of it, and OmniMD is where that trail lives. It is an EHR, practice management and billing platform sold in specialty configurations, and the vascular build covers what a vein practice actually does: venous insufficiency, peripheral arterial disease, carotid disease, aneurysm and dialysis access.

The imaging arrives on its own. Duplex studies come in from the ultrasound units over HL7 and DICOM interfaces and sit in the chart next to the ABI documentation, so the study, the interpretation and the note are one record rather than three.

The people around it are a vascular surgeon, a sonographer, a front desk booking consults and procedures, an authorisation coordinator who spends the day on payer portals, and a biller who finds out weeks later which of it was paid for.

Payers decide when a vein can be treated

Very little about the timing of a vein procedure is decided in the clinic.

Most payers will not authorise an ablation until the patient has completed a documented trial of conservative therapy: compression stockings worn for a set number of weeks, with the wear and the response written down. So somebody is counting weeks, patient by patient, and checking the notes a payer will look for actually exist.

Then the request goes in, and the checking starts. Was it received. Is it still pending. Around that sit the rest of the errands: a medical necessity packet of clinical photographs, the duplex report and the therapy notes to assemble and label. Denials arriving with appeal windows attached. Procedures completed and never charged. A cancellation two days out leaving a slot and a waitlist. Patients due a post-ablation duplex recheck, on a list nobody has built.

OmniMD

The compression trial, counted for you Every patient on conservative therapy counted by week, so the authorisation goes in the day the trial is long enough.

Authorisations chased on day twenty-one Pending ablation requests read each morning, with anything that has not moved in three weeks surfaced before the surgery date.

Denials ordered by the closing window Appeal deadlines grouped by payer and reason, sorted by which window shuts first rather than by which balance is biggest.

The chart was built to survive a payer review

Inside the record OmniMD does the hard part well, which is why a vein practice pays for a specialty build instead of a general EHR.

Structured interpretation templates walk the physician through peak systolic velocities at each segment, waveform classification and reflux timing on the venous studies, so a finding is selected rather than typed. ABI documentation, TASC II classification and reporting shaped for the vascular registry sit alongside procedure note templates for open and endovascular cases. On the money side, charge capture for endovenous ablation is built into the vascular procedure module with medical necessity triggers attached, claim scrubbing and payer rules run before a claim leaves, and a pre-authorisation workflow can start from the scheduled procedure order and pull the codes and documents out of the chart.

All of that is real, and a practice that uses it properly is already ahead.

What all of that has in common is an event. A visit happens, an order is placed, a claim goes out, and the system responds. The clinic's other problem is the passage of time. Worklists exist, and somebody still has to open one every morning and work it against a portal belonging to somebody else.

Every vein authorisation can be watched to its answer

Once the record and the payer's portal get read on a rota, the clinic stops depending on who remembered.

Patients on conservative therapy counted by week, so the request goes in the day the trial is long enough instead of a month after it. The compression notes checked for the wear and tolerance detail a payer will ask for, while the patient is still in the trial.

Pending ablation authorisations read every morning with any change written down, so a request that has not moved in three weeks is chased before the morning of surgery. Denials collected daily and grouped by reason and payer, ordered by which appeal window shuts first. Completed procedures set against what was actually billed, so an unbilled ablation surfaces the same week. Necessity packets gathered ahead of the request: photographs, duplex report and therapy notes in one labelled folder. Patients due a post-ablation recheck listed with a recall drafted and a candidate slot held.

In a clinic that line is not open to argument. Reading, counting, comparing and listing run unattended, and nothing clinical is decided in any of them. Anything that changes a chart, goes to a payer or reaches a patient waits for the qualified person whose decision it is.

The typing in a vein clinic is not the medicine

Counting weeks and refreshing a portal takes no clinical training at all. It only takes somebody who will do it every day, for every patient, indefinitely.

WebRun is an agent that drives a real Chrome browser inside a private environment of your own, signed in the way your staff already sign in. It opens the chart, the payer's portal or the imaging folder, reads what is on the screen, and hands back a worklist ordered by which date falls first.

It runs on your schedule, a workflow can be restricted to an explicit list of sites, and you can watch a run and stop it part way. Nothing is written into a record, filed with a payer or sent to a patient without a qualified person approving it first.

Each workflow below names what it opens and when it runs.