AgileRx
AgileRx runs the clinical side of an Ontario pharmacy — MedsCheck, the 28 funded minor ailments, vaccinations, injections, incident reporting, the appointment calendar, and a claim scrubber that watches all of it. On an iPad you carry, alongside the dispensing system you already run.
Why one system
Buy seven tools from seven vendors and you get seven records and no cross-checks. Every rule below is invisible to a product that only runs one service.
A MedsCheck Follow-up (PINs 93899981–84) and a prescription-issuing minor ailment assessment, billed for the same patient on the same day, is a prohibited billing combination. A minor ailment point solution cannot see the MedsCheck. Your dispensing system sees neither claim. Billing Guard catches it before you submit — because AgileRx runs both services on the same record.
Close a minor ailment assessment and the follow-up it generates appears on the Appointment Calendar as a chip on the day it is due, in the right duration, with the patient context already attached. A booking tool that does not know what the booking is for cannot do this. Nobody re-enters the follow-up, so nobody forgets it.
An adverse event captured in Vaccinations cross-links an Incident record carrying the anonymous field set. The description, the contributing factors, the actions taken and the recorder’s identity stay in the pharmacy. Only the anonymous set goes to the NIDR — and AgileRx shows the pharmacist exactly which fields are which.
The suite
Teal earns. Blue protects. Every module carries its own fees, its own rules and its own published sources — and every one of them writes to the same patient record.
Revenue
Four modules that turn clinical work into a claim the ministry will actually pay — with the eligibility rule, the right PIN, and the record that survives a verification.
Finds every eligible patient, runs the review on the ministry forms, and bills it without clawback risk.
All 28 funded conditions — eligibility, red flags, the legal formulary, and the right PIN of four.
Flu, COVID and the new Adult Vaccine Bundle through one DIN-based claims pipe, with the pharmacist gate enforced.
The stickiest recurring visit a pharmacy runs — with the two authority lanes and the dosing window modelled properly.
Compliance
Three modules that stand between you and a rejected claim, a ministry recovery, or a College finding. Two of them you will need whether you want them or not.
Catches what HNS would reject before you submit — and the documentation gaps that lose a verification after you are paid.
Built to the OCP Platform Criteria, with anonymous daily NIDR upload. This is the module the law requires.
One surface for the clinical day — bookings and the follow-ups the system generated for you.
Incident Reporting is built to the published OCP Platform Criteria. The College does not endorse platforms, and we do not claim it does — read the criteria and check our work.
Alongside, not instead of
AgileRx does not replace your dispensing system. Fillware keeps filling prescriptions. AgileRx runs the clinical services Fillware was never built to run, on the same patients, on a different device.
AgileRx is designed to integrate with Fillware — and it does not wait for that adapter to be useful. In assisted worklist mode the pharmacy works from a worklist AgileRx builds, with the patient context entered once and carried across all seven modules. No interface, no vendor negotiation, no queue.
That is the honest version, and it is also the stronger one: integration is upside, not a prerequisite. AgileRx runs in your store on day one either way.
Zero integration required. The pharmacy runs the full clinical day from the first week, with no dependency on another vendor’s roadmap.
When the adapter lands, the profile flows in and the worklist builds itself. Nothing about the workflow changes — it just gets faster.
Fees, maximums and PINs live in a rules table. When the ministry changes one, that is a row — not a software release you sit and wait for.
iPad-first
The dispensing terminal is anchored behind the counter, and that is where it should stay. The MedsCheck, the minor ailment assessment, the injection consent, the incident that just happened — those take place with the patient, in the aisle, in the consultation room. AgileRx is built for an iPad you carry: deliberately a separate device from the dispensing terminal, so the clinical service is documented in the encounter rather than reconstructed from memory forty minutes later.
On the roadmap
Two things a pharmacy reasonably asks for that AgileRx does not ship today. We would rather name them now than let you find out in month two.
MedsCheck and minor ailment assessments require notifying the patient’s prescriber. The workflow and the notification documents are built; automated sending — fax or secure message — is next, not finished. Until it lands, AgileRx generates the notification for the pharmacy to send.
Booking, reminders and intake from the patient’s own phone are a Phase 2 surface — planned, not yet built. AgileRx today is the pharmacy-facing clinical system. The patient app follows once the clinical modules are proven in a live store, not before.
Thirty minutes. Your store, your services, your dispensing system. We will show you what is built, what is still a simulator, and what is waiting on a ministry notice — and we will show you the numbers behind every claim on this page.