Automated IR QA Complication Digest
Every Monday, WebRun opens HI-IQ, reads the prior week's logged complications and QA events, groups them by complication type, severity grade, and physician, counts them against the number of cases, and posts a Slack digest so the QA committee has a ready summary before the review meeting.
How do I prepare a weekly IR complication log for QA review?
WebRun opens HI-IQ every Monday and reads the prior week's logged complications and QA events. It groups them by type, severity grade, and physician, counts them against case volume for a rate, and posts a Slack digest with high-severity events and incomplete entries flagged, so the QA committee walks into the review with a ready summary.
- The QA committee opens Monday to a ready complication summary
- High-severity events are surfaced instead of buried in the log
- Incomplete QA entries are flagged in time to finish before the meeting
Built for IR quality managers · interventional radiology QA committees · IR medical directors · angio lab charge nurses
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.hi-iq.comin a real browser with your saved login - no setup, no API keys. -
1
HI-IQ - read the week's complication and QA entries
hi-iq.com
WebRun opens HI-IQ to read the week's complication and QA entries. - Open HI-IQ and pull the prior week's logged complications and QA events
- Record each event with its complication type, severity grade, case type, and physician
- Count the events against the number of cases performed that week to get a rate
- Flag any severity grade above your review threshold and any event missing required QA fields
Done when Every logged complication from last week is grouped by type and severity, with a rate against case volume.
-
2
Slack - post the QA digest to the committee
slack.com
WebRun opens Slack to post the QA digest to the committee. - Post a weekly digest to the IR QA channel with the total events and the rate against case volume
- Break events down by complication type and severity grade
- Flag high-severity events and any entry missing required QA fields to complete before the meeting
- Keep patient identifiers out of the post and reference events by case number only
Done when The QA channel has the week's complication digest grouped by type and severity, with gaps flagged.
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 patient information appear in the Slack digest?
No. The digest references events by case number and groups them by type, severity, and physician. No patient names or identifiers leave HI-IQ, so the internal channel stays free of protected health information.
Does it grade or judge the complications itself?
No. WebRun reads the severity grade already assigned in HI-IQ and organizes the entries. Clinical judgment, grading, and any peer review stay with your QA committee.
What if a QA entry is missing required fields?
It flags incomplete entries in the digest so they can be completed before the review meeting, listing which required QA fields are blank on each flagged case.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.