How to Automate CureMD

CureMD carries an infectious disease practice on one cloud platform

CureMD puts an infectious disease practice on a single cloud system, with the chart, the billing and the recalls sharing one login. It is sold across many specialties and configured per specialty rather than as one generic record, so the infectious disease build is its own thing.

That practice does not look like a family clinic. Its patients are on long courses rather than short visits: a hepatitis C treatment run to completion, an HIV panel every few months, six weeks of intravenous antibiotics finished at home, PrEP that only helps if the refill genuinely happens, a travel consultation that has to land before the flight.

So the chart is less a record of what happened than a set of open commitments with dates attached, and CureMD is where every one of them is written down.

Infectious disease work is mostly the waiting between visits

The clinic day is the small part. The work is the month in between.

A patient discharged on Friday with four weeks of outpatient antibiotics, whose discharge summary sits in a hospital portal the practice barely otherwise uses. A prior authorisation for an expensive antibiotic filed on Monday that the payer has not decided. A reportable result that has to reach the state on its own form and its own timetable.

Then the people who are not in the building. Someone whose viral load was due in March and who was last seen in October. An infusion missed on Thursday that nobody has rebooked. A specialty pharmacy holding a PrEP order it has not shipped. A referral from a hospital that arrived as a fax and is waiting to be triaged.

None of it is difficult. All of it is a queue, and a queue is only as current as the last free afternoon anybody had.

CureMD

Approvals chased on day four Every pending antibiotic or infusion authorisation checked on the payer's own site each morning, ranked by how long it has been sitting there.

Refills that actually shipped The specialty pharmacy's status page read daily, so an order that has not moved is visible while the patient still has tablets in the bottle.

The follow-up dates that slipped Viral loads, hepatitis C checks and missed infusions listed by how far past due they are, with a draft ready for a clinician to send.

Specialty templates and recalls only reach inside CureMD

CureMD has built a great deal of this into the specialty version, and a practice paying for it should be using all of that first.

The infectious disease build ships Complete Immunotherapy and Infectious Disease Medicine Templates with vaccine history, an Antibiotic Dosing Calculator, Automated Health Maintenance alerts and a patient recall system for immunotherapy management, alongside bi-directional lab interfaces and an integrated e-fax. Immunizations report automatically to state immunization registries. Above the platform sit the AI Medical Scribe, AI Coder and AI No-Show Prediction.

Every one of those acts on something CureMD holds, or travels a route built to carry it. The recall fires because the chart knows the date. The immunization reaches the registry because an interface exists for it.

The routes that do not exist are the ones the open list depends on. A payer's authorisation portal decides when it decides and announces nothing. The specialty pharmacy's status page is a website. The hospital's discharge portal belongs to the hospital. The state's communicable disease form is a form. Nothing is wrong with the software; the answer is simply on the far side of somebody else's login.

The chasing between visits stops being a memory test

The month between appointments could be worked by something that never runs out of afternoons.

Pending antibiotic and infusion authorisations checked on each payer's portal every morning and sorted by how long they have been sitting, so a stalled request is chased in week one rather than discovered on the day the chair was booked.

The specialty pharmacy's page read daily, so a PrEP order that has not shipped is visible while the patient still has tablets. Discharge summaries pulled from the hospital portal and matched against the referrals the practice was told to expect, so a four-week antibiotic course is scheduled before the first dose is due.

Patients whose viral load or hepatitis C follow-up has passed its date, named and ranked by how overdue they are. Missed infusions listed with the next open slot beside them. Reportable results collected with the state's own deadline attached, ready for a clinician to submit.

The line in a clinical setting is fixed. Reading a screen and assembling a list can run unattended overnight. Anything that changes a clinical or billing record, and anything that reaches a patient, is prepared for a qualified person to read and send.

The reading is not the part that needs a clinician

Opening six portals to see whether anything moved since yesterday calls for judgement about as often as reading a bus timetable does.

WebRun is an agent that drives a real Chrome browser, signed in the way your staff sign in. It opens CureMD and the payer, laboratory, pharmacy and hospital sites beside it, reads what is there, and brings back a worklist with the names and dates already filled in.

It runs on your schedule inside your own private environment, a workflow can be locked to a named list of domains, and sessions are not shared between them. Nothing touching a chart, a claim or a patient goes anywhere without a person approving it.

Each workflow below names the systems it signs into.