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, the patient receives a message from your practice with a secure, single-use link. No portal login. No app. They see the medications your clinic has on file, displayed in plain language — the clinical anchor they’re confirming against.
How the list gets there: your EHR provides it automatically through standardized, federally required data-exchange interfaces, or your staff uploads it from an existing export file. Either way, the patient sees the same confirmation flow built around your clinic’s record.
They confirm at home, with the bottles in hand.
One question per medication: still taking it, taking it differently, stopped it, or not sure. They can add anything missing — including OTCs, vitamins, and supplements. No clinical jargon, no account to create. Most finish in a few minutes with the bottles in front of them.
You see what changed, not the whole list.
Your team gets a worklist sorted by what the patient flagged. Confirmed medications need no attention. Flags show the patient’s own words, who answered, and when. High-risk medication classes surface distinctly. Your clinician decides what, if anything, goes in the chart. Nothing is written back to your EHR.
Why the clinical anchor matters
ConfirmMyMeds always starts from a list your clinic provides — not from the patient’s memory. That’s a deliberate design choice. “Confirm what’s here” is faster and more reliable than “tell us everything from scratch,” and it preserves what makes this a clinical tool: two lists with known provenance (your record of what was prescribed, the patient’s report of what they take), with the difference between them made visible. Without that anchor, you’d have a personal medication tracker. There are plenty of those already. That’s not what this is.
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’ medication lists as a file — most EHR systems can produce one from the chart — and upload them to ConfirmMyMeds. Your patients get the same confirmation flow, and you get the same worklist. No IT involvement, no vendor approval. This is how we recommend starting every pilot.
Automated path (when you’re ready)
Connect through your EHR’s standardized, federally required data-exchange interfaces. Medication lists flow automatically for your scheduled panel. This is the scale path — but it’s not a prerequisite.
The patient experience is identical either way. The source of the list is invisible to the patient; what they see is their clinic’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 clinic’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 are tied to a scheduled appointment and expire afterward — we don’t accept medication reports with no visit on the horizon. 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 — a new patient, or one your team added without an import. For them, we fall back to a short sign-in (name and date of birth, no EHR account, no password) instead of the one-time link above. From there the patient builds a list from nothing, same one-question-per-medication flow, same bottles-in-hand approach. Nothing is auto-merged into a structured list; your team reviews everything they reported the same way it reviews flagged changes, and decides what belongs in the chart. This is a fallback for patients with no starting list, not a second primary flow — most patients arrive with an EHR-sourced list already.