Automated Visage 7 Migration Error Flags
Every hour, WebRun checks the migration queue in Visage 7, compares the studies and series that arrived against what the source archive sent, flags any failed transfer or incomplete series, and posts the details to Microsoft Teams so PACS admins can resolve it before a radiologist opens an incomplete study.
How do I catch study migration errors before a radiologist finds a gap?
WebRun checks the Visage 7 migration queue every hour, compares the series and image counts that arrived against the source archive's manifest, and flags any failed transfer or incomplete study. It posts the accession number and what's missing to Microsoft Teams, so PACS admins fix a migration error within the hour, before a radiologist ever opens an incomplete study.
- Failed transfers get caught within the hour, not when a radiologist hits a gap
- Every migration error is grouped by source archive for faster vendor follow-up
- Resolved studies are tracked so nothing gets flagged twice
Built for PACS administrators · imaging informatics teams · radiology IT · archive migration project leads
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.visageimaging.comin a real browser with your saved login - no setup, no API keys. -
1
Visage Imaging - compare migrated studies against the source archive
visageimaging.com
WebRun opens Visage Imaging to compare migrated studies against the source archive. - Open the migration queue in Visage 7 and pull this hour's completed transfers
- Compare series and image counts against the source archive's manifest
- Flag any study with a failed transfer, missing series, or incomplete image count
Done when Every study migrated this hour is checked against the source archive's manifest.
-
2
Microsoft Teams - alert PACS admins to any migration error
microsoft.com
WebRun opens Microsoft Teams to alert PACS admins to any migration error. - Post an alert listing every flagged study with the accession number and what's missing
- Group by source archive so the admin knows which migration batch to check
- Mark studies as resolved once a re-transfer confirms a full match
Done when PACS admins have an alert for every migration error found this hour.
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 retry the failed transfer automatically?
No. WebRun only detects and alerts. Re-triggering a transfer or contacting the source archive vendor stays a manual PACS admin decision.
How does it know a series is missing?
It compares the series and image count Visage 7 received against the source archive's manifest for that study, so a partial transfer is caught even if the study appears to have arrived.
Will a radiologist ever open an incomplete study?
That's exactly what this catches early. Flagging the gap within the hour, before the study reaches the reading worklist, is the point of the workflow.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.