Automated RamSoft Critical Finding Notification Drafts
Every hour, WebRun opens RamSoft, finds studies flagged with a critical finding, drafts a concise notification for the referring provider, and posts the draft to a Slack review channel so a radiologist or lead tech can approve and send it through the proper clinical channel. Nothing is sent externally without human sign-off.
How can I automate critical-finding notification drafts while keeping a radiologist in the loop?
WebRun scans RamSoft every hour for studies marked with a critical finding, prepares a draft notification for the referring provider, and posts it to a Slack review channel for a radiologist to approve before anything is sent externally. No PHI leaves the system and no notification reaches a provider without human sign-off.
- Every critical finding gets a draft notification ready within the hour, not lost in a manual queue
- Radiologists approve from a Slack queue rather than hunting through the RIS
- Full audit trail: every draft is logged before any external communication happens
Built for radiologists · imaging center medical directors · radiology ops managers
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.ramsoft.comin a real browser with your saved login - no setup, no API keys. -
1
RamSoft - detect studies flagged as critical findings
ramsoft.com
WebRun opens RamSoft to detect studies flagged as critical findings. - Open RamSoft and check the worklist for studies marked with a critical-finding flag
- Capture study type, accession number, flagged finding category, and referring provider name
- Draft a concise, template-based notification message for the referring provider without including PHI in the draft posted to Slack
Done when All newly flagged critical-finding studies have a draft notification prepared.
-
2
Slack - post draft notification for radiologist review
slack.com
WebRun opens Slack to post draft notification for radiologist review. - Post each draft notification to the critical-findings Slack review channel
- Include the accession number and modality so the reviewer can pull the study immediately
- Label each message as DRAFT, pending radiologist or lead-tech approval before external delivery
Done when Each critical finding has a draft notification queued in Slack for human review and sign-off.
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
Will it send the critical-finding notification to the referring provider automatically?
No. WebRun drafts the notification and queues it in Slack for a radiologist or lead tech to review and approve. No external message containing protected health information is sent without human sign-off, in compliance with HIPAA critical-result communication requirements.
Does the Slack draft contain any patient protected health information?
No. The Slack post includes only the accession number, modality, and finding category so the reviewer can pull the study. Full clinical details remain in RamSoft and are not posted externally.
What if a critical finding was already acknowledged?
Each hourly run checks the current flag status in RamSoft. Studies whose critical finding has already been acknowledged or cleared are excluded from the draft queue automatically.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.