Check every certification records a valid qualifying condition
Every night, WebRun opens Verify MC, reviews certifications completed that day, checks that each documents a qualifying condition accepted in the patient's state and that supporting notes are present, records any missing or state-mismatched condition in a Google Sheet, and sends your medical director a Telegram exceptions list so charts stay compliant and audit-ready.
- No credit card
- Under $0.01 per run
- Cancel anytime
How do I verify every medical cannabis certification records a valid qualifying condition?
WebRun opens Verify MC each night, reviews the day's certifications, and checks that each documents a qualifying condition accepted in the patient's state with supporting notes. It logs any gap or mismatch to a Google Sheet and sends your medical director a Telegram exceptions list, so charts stay defensible and audit-ready before a reviewer ever asks.
- Condition documentation gaps are caught the same night, not at audit
- Every certification is checked against its state's accepted conditions
- Only references and issue types ever leave the source system
Built for cannabis clinic medical directors · MMJ certification practices · clinic compliance teams · telehealth cannabis physicians
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 - review documented qualifying conditions
WebRun opens Verify MC to review documented qualifying conditions. - Open Verify MC and list certifications completed today
- For each, read the documented qualifying condition and the patient's state
- Check the condition against the accepted list for that state and confirm supporting notes are recorded
Done when Every certification today has a pass or exception on its qualifying condition.
-
2
Google Sheets - log condition gaps and mismatches
WebRun logs condition gaps and mismatches in Google Sheets. - Append a row for any certification where the condition is missing, unsupported by notes, or not accepted in that state
- Record the patient reference, state, documented condition, and the specific issue
- Keep only the reference and the issue, never the patient's name or full clinical narrative
Done when Every condition exception from today is logged with its reason.
-
3
Telegram - send the exceptions list
WebRun sends the exceptions list to Telegram. - Send a Telegram exceptions list to the medical director of certifications needing a condition review, by reference
- Note the total certifications checked and how many passed cleanly, so the pass rate is visible
- Keep the message to references and issue types only, with no patient names or clinical detail
Done when The medical director has tonight's qualifying-condition exceptions 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 change or void any certification?
No. WebRun only reviews and flags certifications where the qualifying condition looks missing or state-mismatched. It never edits, voids, or approves a record, so correcting any exception stays the medical director's decision.
How does it know a condition is valid for the state?
It checks each documented condition against the accepted qualifying-condition list you configure per state. Anything outside that list, or lacking supporting notes, is flagged as an exception with the specific reason for review.
Does patient clinical data leave the clinic?
No. The Google Sheet and Telegram list carry a patient reference, state, and issue type only, never names or the full clinical narrative, so protected health information stays inside Verify MC.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.