Verify MC Automated Card Issuance Logging
Every night, WebRun opens Verify MC, finds recommendations and patient ID cards generated that day, appends each to a running issuance register in Google Sheets with its reference and expiry date, and sends you a Telegram summary of how many cards were issued and their expiry spread, so your certification records stay audit-ready without manual logging.
How do I keep an audit-ready log of every medical cannabis recommendation card issued?
WebRun opens Verify MC each night, finds the recommendations and patient ID cards issued that day, and appends each to a running Google Sheet register with its reference and expiry date. It then sends you a Telegram summary of the day's totals and upcoming expiries, so your certification records stay audit-ready without any manual logging.
- Every issued card lands in an audit-ready register the same night
- Upcoming 30-day expiries are visible for renewal planning
- The log holds only references and dates, never patient identities
Built for medical cannabis clinics · MMJ certification physicians · clinic compliance staff · cannabis practice administrators
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
verifymc.comin a real browser with your saved login - no setup, no API keys. -
1
Verify MC - find cards issued today
verifymc.com
WebRun opens Verify MC to find cards issued today. - Open Verify MC and list recommendations and patient ID cards generated today
- For each, capture the patient reference, certifying physician, issue date, and expiry date
- Note any card marked as a renewal versus a first-time issuance
Done when Every card issued today is captured with its issue and expiry dates.
-
2
Google Sheets - append to the issuance register
google.com
WebRun appends each card to the issuance register in Google Sheets. - Append one row per card to the issuance register with reference, physician, issue date, expiry date, and type
- Keep the register sorted by issue date so the full history reads top to bottom
- Record only the patient reference, never names or contact details, to keep the log free of identifying data
Done when The issuance register contains a row for every card generated today.
-
3
Telegram - send the nightly issuance summary
telegram.org
WebRun sends the nightly issuance summary to Telegram. - Send a Telegram summary of the day's issuance: total cards, first-time versus renewal split, and physician breakdown
- Flag the count of cards expiring in the next 30 days so upcoming renewals are visible
- Keep the message to counts and references only, with no patient names
Done when You have tonight's issuance summary in Telegram.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Does it issue or reissue any cards?
No. WebRun only reads cards already generated in Verify MC and logs them. It never creates, edits, or reissues a recommendation or ID card, so the register is a passive audit trail and issuance stays a physician action.
Is patient identity stored in the register?
No. The Google Sheet and Telegram summary use a patient reference number, physician, and dates only, never names or contact details, so your issuance log holds no directly identifying protected health information.
Can it also surface upcoming renewals?
Yes. The nightly Telegram summary flags how many issued cards expire within the next 30 days, and the register's expiry column lets you filter for any renewal window you want to plan around.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.