Automated symplr Primary Source Verification Flags
Every morning, WebRun opens symplr, checks every in-process application for a primary source verification item outstanding more than 10 business days, logs each stalled item to a Google Sheets tracker, and emails your CVO verification team an internal summary so bottlenecks get chased the same day.
How do I automatically flag stalled primary source verifications in credentialing?
WebRun checks symplr every morning for application files with a primary source verification item still outstanding after 10 business days. It logs each stalled file to a Google Sheets tracker and emails your CVO verification team an internal summary, so bottlenecks get chased the same day instead of surfacing at committee.
- Stalled verifications are caught after 10 business days instead of sitting unnoticed
- The CVO team opens an inbox digest every morning naming exactly which file needs a follow up call
- Credentialing turnaround time drops because bottlenecks surface daily instead of at committee
Built for CVO verification specialists · medical staff office coordinators · credentialing committees · hospital compliance teams
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
www.symplr.comin a real browser with your saved login - no setup, no API keys. -
1
symplr - find stalled primary source verifications
symplr.com
WebRun opens symplr to find stalled primary source verifications. - Open symplr Provider or CVO and go to the verification queue for in-process applications
- Check each primary source verification item: license board, NPDB, education, board certification, OIG or SAM exclusion
- Flag any item still outstanding more than 10 business days after it was requested
- Note the file, the specific verification item, and how many days it has been outstanding
Done when Every stalled primary source verification item is identified with the file and days outstanding.
-
2
Google Sheets - log outstanding verification items
google.com
WebRun opens Google Sheets to log outstanding verification items. - Open the PSV Outstanding Items tracker
- Add a row for each stalled verification with the file, item, and days outstanding
- Remove any row for an item that has since come back verified
Done when The tracker lists every currently stalled primary source verification item.
-
3
Outlook - alert the CVO team internally
microsoft.com
WebRun opens Outlook to alert the CVO team internally. - Compose an internal summary email listing every stalled verification item and how long each has been outstanding
- Group the list by verification type so the team can batch its follow up calls
- Send the summary to the CVO verification team's shared inbox
Done when The CVO verification team has today's summary of every file with a stalled verification item.
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 contact the state license board or NPDB directly?
No. It only reads the verification status already recorded in symplr. Reaching out to a primary source, a licensing board, NPDB, or a training program stays a task for your CVO verification specialist.
How long does a verification have to be outstanding before it is flagged?
By default, 10 business days with no update. That threshold can be adjusted to match your medical staff office's own turnaround policy.
Will it notify the provider that their file is delayed?
No. The summary goes only to your internal CVO verification team. WebRun never contacts a provider or applicant directly about the status of their file.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.