All templates

Automated Visage 7 DICOM Node Failure Alerts

Every few minutes, WebRun checks Visage 7's DICOM routing and node status, catches any modality, archive, or routing node that has gone down or stalled, texts the on-call PACS admin through Twilio, and posts the outage details to Microsoft Teams so IT can start troubleshooting immediately.

Deploy this workflow Browse all templates
Runs on WebRun · Strict Lockdown policy
Every 5 minutes, all day WebRunorchestrates each step
1 Visage Imaging detect a failed or stalled DICOM node
2 Twilio text the on-call PACS admin
3 Microsoft Teams post the outage details for IT
In short

How do I get alerted the moment a DICOM node fails?

WebRun checks Visage 7's DICOM routing and node status every few minutes, catches any modality, archive, or routing node that has gone down or stalled, and texts the on-call PACS admin through Twilio with the node, site, and studies queued behind it. It posts the outage details to Microsoft Teams, so IT starts troubleshooting minutes after a failure, not hours.

  • A failed DICOM node gets a human response in minutes, not after studies back up
  • Every outage has a timestamped record for vendor escalation
  • On-call rotation always gets paged, even if the first admin misses it

Built for PACS administrators · radiology IT teams · imaging informatics staff · hospital IT operations

Step by step

What does WebRun do on every run?

The exact actions WebRun takes, in order - in plain language, so you can adjust anything.

  1. WebRun signs in and gets to work

    Opens www.visageimaging.com in a real browser with your saved login - no setup, no API keys.

  2. 1
    Visage Imaging - detect a failed or stalled DICOM node
    visageimaging.com
    WebRun in Visage Imaging: detect a failed or stalled DICOM node
    WebRun opens Visage Imaging to detect a failed or stalled DICOM node.
    • Check the DICOM routing and node status dashboard in Visage 7
    • Identify any modality, archive, or routing node that is down, stalled, or failing to send
    • Capture the node name, site, last successful transfer time, and study count queued behind it

    Done when Every failed or stalled DICOM node is identified with its queued study count.

  3. 2
    Twilio - text the on-call PACS admin
    twilio.com
    WebRun in Twilio: text the on-call PACS admin
    WebRun opens Twilio to text the on-call PACS admin.
    • Draft a short text naming the failed node, site, and studies queued behind it
    • Send it to the on-call PACS admin's number on file
    • Escalate to the backup on-call if there is no acknowledgment within 10 minutes

    Done when The on-call PACS admin has been texted for every node failure.

  4. 3
    Microsoft Teams - post the outage details for IT
    microsoft.com
    WebRun in Microsoft Teams: post the outage details for IT
    WebRun opens Microsoft Teams to post the outage details for IT.
    • Post the outage details to the PACS operations channel with a timestamp
    • Keep a running log of downtime duration per node for vendor escalation

    Done when The PACS operations channel has a timestamped record of the outage.

Run settings

How is each run configured?

Starting pageWhere Chrome opens at the start of each run
www.visageimaging.com
ScheduleRuns automatically on this cadence
Every 5 minutes, all day
DeliveryHow each run's result reaches you
DICOM outage alert · Microsoft Teams
OutputWhat each run produces - A timestamped DICOM node failure alert (node, site, studies queued) texted to the on-call PACS admin and logged in Teams.
Alert
Setup & safety

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.

Your credentials stay in your own private environment - WebRun never stores your passwords.
Strict Lockdown

Every action is checked against this policy before it runs.

Domains ALLOWLIST
Typed input ALLOW
Shell command BLOCK
File uploads BLOCK
Runs in a contained environment More on policies
Good to know

Questions, answered

Does it try to restart or fix the failed node?

No. WebRun only detects and alerts. Restarting a node or rerouting studies stays a manual IT or vendor action, so nothing changes on your network without a person deciding to.

How fast does it catch a failure?

Within one check cycle, typically every few minutes, so a stalled DICOM node gets caught long before studies pile up unnoticed.

What if the on-call admin doesn't respond?

It escalates automatically. If there's no acknowledgment within 10 minutes, WebRun texts the backup on-call so an outage never sits unaddressed.

Keep going

Related templates

Automated Critical Result Notification Logging
WebRun checks the Visage 7 worklist for critical results, confirms the communication was documented, logs every case to Google Sheets, and flags any missing closure to Microsoft Teams.
Visage Imaging›Google Sheets›Microsoft Teams
Automated Peer Review Addendum Follow-Ups
WebRun tracks discrepancies flagged in peer review, drafts the addendum language for the reporting radiologist to review, and keeps following up in Microsoft Teams until it's signed and filed.
Visage Imaging›Google Sheets›Microsoft Teams
Automated Visage 7 Exam Volume Digest
Every night, WebRun totals completed exams in Visage 7 by modality, site, and radiologist, and logs the day's volume digest to Google Sheets.
Visage Imaging›Google Sheets

Put this on autopilot.

Turn it on in minutes - or have our team set it up for you.

Deploy this workflow Talk to us