Three steps. Nothing enters your record without you.
This describes the target workflow. The worklist and review step (3) run live in the working application today; the EHR read and patient messaging (1 and 2) are currently simulated. See what’s built vs. simulated →
Your patient gets their medication list to review.
Before the appointment or pickup, the patient gets a secure, single-use link — no portal login, no app — showing their medications in plain language. Clinics pull this from the EHR automatically; pharmacies export a file instead (see “Getting started” below). Either way, the patient sees the same screen.
They confirm at home, with the bottles in hand.
One question per medication: taking it, taking it differently, stopped, or not sure — plus anything missing, including OTCs and supplements. No jargon, no account. Most finish in a few minutes with the bottles in hand.
You see what changed, not the whole list.
Your team gets a worklist sorted by what the patient flagged — confirmed items need no attention. A clinician decides what enters the chart; at a pharmacy, a Technician triages routine items and a Pharmacist reviews anything escalated. Nothing writes back automatically.
Watch the product walkthrough
The same steps described above, recorded from the running prototype. No account needed.
Pharmacy workflow
Clinic workflow
Why the clinical anchor matters
ConfirmMyMeds always starts from a list your clinic or pharmacy provides; not the patient’s memory. That’s deliberate: “confirm what’s here” is faster and more reliable than “tell us everything from scratch,” and it keeps two lists with known provenance (what was prescribed, what the patient reports) with the difference visible. Without that anchor, this would just be a personal medication tracker; and there are plenty of those already.
Start a pilot in a week
You don’t need a full system integration to test ConfirmMyMeds with real patients.
Immediate start (manual upload)
Export your scheduled patients’ records as a file — most EHR and pharmacy systems can — and upload it. Same confirmation flow, same worklist, no IT involvement or vendor approval. We recommend starting every pilot this way, and it’s the only path for pharmacies today (retail pharmacy systems don’t have the standardized interface the automated path below needs).
Automated path (clinics, when you’re ready)
Connect through your EHR’s standardized, federally required interfaces and medication lists flow automatically for your scheduled panel — the scale path for clinics, not a prerequisite.
The patient experience is identical either way — just your clinic or pharmacy’s name, their medications in plain language, and a simple set of questions.
Plain language, one question at a time
The patient flow is deliberately plain: your company’s name and branding first, one question per medication, no clinical jargon, no account to create, and a clear statement — with your phone number — that this isn’t a way to reach your team urgently. Book a Free Demo to see it running →
How flagged changes are handled
Attestation requests expires after a set time — A clinic or pharmacy need to send a request-link to start the process. Changes involving anticoagulants, insulin, antiepileptics, opioids, immunosuppressants, and antiarrhythmics are surfaced differently from a change to a multivitamin. Before any pilot goes live, we agree with you on who reviews flags and within what window. That’s an operational commitment, not a software setting.
If a patient isn’t on your medication list yet
Not every patient arrives with a medication snapshot. For them, we fall back to a short sign-in (name and date of birth, no account, no password) instead of the one-time link, and they build a list from nothing — same one-question-per-medication flow. Nothing auto-merges into a structured list; your team reviews it exactly like flagged changes. This is a fallback, not a second primary flow — most patients arrive with a list already on file.