How to Automate Adherent360

Discharge is where a prescription is most likely to be lost

Adherent360 is a discharge medication platform for hospitals and health systems. Its whole subject is the few hours around a patient leaving the building, which is where a prescription is most likely to disappear.

A physician sends the discharge prescription electronically into the Adherent360 application, which is integrated with the hospital's EHR and with Surescripts. A telepharmacist works the order through an in-hospital dispensing kiosk. Staff carry the filled medication to the room, a remote pharmacist counsels the patient by video on a handheld tablet, and the copayment and signature are taken at the bedside before discharge.

For anything that cannot be handed over in the room, the same platform runs a home leg. The patient picks a delivery window and pays in the app, the pharmacy places the bag in an Adherent360 locker, and Uber Direct collects it from there.

Emergency departments, inpatient units, urgent care and clinics all sit on the same rails.

The bed is held while a prior authorization sits unanswered

None of that takes the phone off the pharmacy desk.

A discharge order comes back needing a prior authorization, and somebody opens the payer's portal to see whether it has moved since yesterday. A drug is not on this patient's formulary, so the substitution has to be agreed with a prescriber who is in theatre. A copay quoted at the bedside was never taken, and becomes a balance nobody is looking at.

A bag went into a locker at four in the afternoon, and the courier's own dashboard is the only place that says whether it reached a door. A technician walks past the kiosk and eyeballs what is running low. Somebody builds a list of yesterday's discharges by hand to work out how many left with medication, because that number gets asked for monthly and nothing produces it.

Each of those is a person with a browser, working around the edges of a system that did its own part correctly.

Adherent360

Authorizations followed to a decision Pending cases tracked on the payer's own portal, so a stalled discharge order is on a worklist in the morning rather than learned about from the patient.

Deliveries that get confirmed Locker handoffs and doorstep drops checked against the courier's own record, so a refused or uncollected bag raises a flag the same evening.

Copays that do not quietly age Balances quoted at the bedside and never taken, gathered from the payment processor into one list somebody can work.

The kiosk knows the fill, not the reason it stalled

Adherent360 automates the hard part of this properly, and a hospital should be using all of it before adding anything.

The prescription arrives electronically rather than on paper, because the application is integrated with the EHR and with Surescripts. A pharmacist verifies remotely, so a kiosk can dispense at hours no counter is open. Counseling happens on a tablet at the bedside instead of being skipped. Payment and signature are taken while the patient is still in the room, which is the one moment they are reliably in front of you. On the delivery side, the locker handoff and the pickup through Uber Direct are coordinated by the platform rather than by a phone call.

Every one of those acts on an order Adherent360 is already holding.

The reason an order stops moving is almost never in there. It is a status on a payer's prior authorization portal, a rule on a plan's formulary page, a delivery exception on the courier's dashboard, or a bed that changed on the census after the prescription was written.

Every stalled script has an answer sitting in another login

Adherent360 already knows which prescriptions were written at discharge today. The question worth answering is which of them stalled, and every answer sits behind a login somebody on the team already has.

Prior authorizations followed on the payer's own portal from submission to decision, so a pending case is on a worklist at eight in the morning rather than found out when a patient rings from home. Formulary rules read before the substitution conversation, so a pharmacist calls the prescriber once instead of twice.

Deliveries squared against the courier's own record, so a bag refused at the door becomes an alert that evening rather than a discovery a week later. Kiosk stock read off the device's own reporting and matched against tomorrow's expected discharges, so a restock happens before the shelf is empty.

The discharge list checked against what was actually dispensed, which is how a health system learns how many of its own prescriptions left with the patient.

A hospital settles this line long before any software arrives. Reading a portal, matching what it says against the record and putting the mismatch on a worklist are all safe to run unattended overnight. Anything that changes a medication record, or reaches a patient or a prescriber, waits for a licensed person.

Chasing a copay needs nobody's pharmacy license

Refreshing a payer portal and reading a courier dashboard take none of the training a pharmacist spent years getting, and between them they decide whether a patient goes home with the medication written for them.

WebRun is an agent that works a real Chrome browser, signed in the way your staff sign in. It opens the payer's prior authorization portal, the courier's tracking page or the kiosk's own reporting, reads what is there, and brings back a worklist with the patient, the drug and the status attached.

It runs on your schedule inside your own private environment, and a workflow can be locked to named sites.

The workflows below are built already. Each one names the sites it opens and the point at which it stops.