
Embedding AI Triage into the Radiology Workflow of a Hospital Imaging Network
Let's Connect
Overview
What we built
A 14-hospital imaging network had already paid to license AI models that spot urgent findings in scans, but nothing connected them to the systems radiologists actually use. We built the missing plumbing and put the models to work.
In plain terms: the network's scanners produce a constant stream of studies, and overnight those studies waited in a single first-in-first-out queue regardless of how urgent they might be. The AI models the network had licensed could spot the scans that needed a radiologist first, but they sat disconnected: no link into the picture archive, no way to reorder a worklist, no way to alert the on-call reader. Paying for intelligence and getting none of it was the daily reality.
We built the integration layer the model vendors did not supply, wiring the licensed models into the network's imaging systems, its radiologist worklists and its on-call phones, then rolled it out hospital by hospital. The change shows in the numbers the network cares about: the median wait for a flagged study to reach a radiologist's worklist fell from 47 minutes to under 4, 94% of eligible studies now route through the pipeline automatically, and all 14 hospitals went live within 7 months with zero unplanned downtime in the systems radiologists depend on.
The Problem
Licensed AI models sitting unused
The network had done the hard commercial work: it had licensed regulator-cleared AI triage models built to flag urgent findings in imaging studies. What it had not bought, because the vendors did not sell it, was any connection between those models and the way radiology actually runs across 14 hospitals. The picture archive, the radiologist worklists and the on-call escalation paths all sat on one side of a gap, and the models sat on the other.
Overnight was where the gap hurt most. Studies queued strictly first-in-first-out, so a scan with a potentially urgent finding waited behind routine work with nothing to move it up the list. If a model had flagged it, no one would have known: there was no route from a model flag to the right reader, and no record of whether anyone acted on a flag at all.
For radiologists the licensed models were invisible; for department leads they were an unaccountable line item. The network could not say which studies the models would have prioritised, could not audit what happened after a flag, and could not defend continuing to pay for capability that never touched a patient pathway.
Disconnected models
Regulator-cleared triage models were licensed and ready, but nothing linked them to the PACS, the worklists or the escalation paths where they could matter.
Blind overnight queue
Studies processed strictly first-in-first-out overnight, so potentially urgent scans waited behind routine work with no mechanism to surface them any sooner.
No routing to readers
Even when a model flagged a study, there was no way to get that flag in front of the right radiologist or into an on-call escalation path.
No audit trail
Nothing recorded whether a flag was ever seen or acted on, leaving the network unable to evidence the models' clinical use or value.
What it was costing them
The network was paying licence fees for models that never influenced a single read. Urgent findings sat in overnight queues exactly as they had before the purchase, on-call escalation depended on phone habits rather than a system, and every month without integration widened the gap between what leadership had promised the AI investment would deliver and what radiologists actually experienced.
The Solution
Triage wired into PACS workflow
We built the integration layer the vendors left out, treating the triage models as services to be wired into the network's existing workflow rather than tools to be worked around. A DICOM router identifies eligible studies as they arrive and streams them to the third-party triage services, so the models see the right scans without anyone lifting a finger.
An orchestration service takes the flags coming back and writes prioritisation directly into the PACS worklists radiologists already use, so a flagged study rises up the queue inside the familiar screen rather than in a separate portal. When a flag needs a human now, mobile on-call notifications reach the right reader, and full audit logging records every flag, every notification and every acknowledgement.
Rollout ran hospital by hospital behind feature flags, so each site could be switched on, observed and tuned without risking the rest of the network. Dashboards tracking pipeline latency, uptime and flag volumes gave the programme team live evidence at every stage, which is how all 14 hospitals went live without a single episode of unplanned PACS downtime.
Key decisions
Integrate into PACS, not around it
Prioritisation flags are written straight into the worklists radiologists already use, so the AI changes reading order without asking anyone to learn a new screen.
One router for all vendors
A single DICOM routing layer decides study eligibility and streams scans to each third-party triage service, keeping every vendor connection in one controlled, observable place.
Rollout behind feature flags
Each hospital was switched on independently and could be switched off instantly, letting the team tune the workflow site by site without endangering live clinical systems.
Audit logging from day one
Every flag, notification and acknowledgement is logged, so the network can evidence what the models did and whether the right person responded to each one.
Escalation goes mobile
On-call notifications reach radiologists on their phones rather than relying on someone watching a queue, closing the loop between a model flag and a human decision.
Measurable Impact
What changed after launch
The pipeline turned licensed but idle models into working clinical infrastructure. Median time from scan completion to a flagged study reaching a radiologist's worklist dropped from 47 minutes to under 4, and by the end of rollout 94% of eligible study volume was routing through the triage pipeline automatically, with no manual steps in between.
The rollout itself held to its discipline: all 14 hospitals went live on the integrated workflow within 7 months, with zero unplanned PACS downtime along the way. And the escalation loop now closes: after mobile notifications launched, on-call escalations acknowledged within 10 minutes rose from 58% to 87%, so a flag raised overnight reliably reaches a person who answers.
Urgent-study visibility
47 minutes median from scan to worklist flag
Under 4 minutes median from scan to worklist
Overnight queueing
Strictly first-in-first-out, with urgency invisible overnight
94% of eligible studies routed and prioritised automatically
On-call escalation
Acknowledgement within 10 minutes for 58% of escalations
87% of escalations acknowledged within 10 minutes
Rollout footprint
Models licensed but live in no hospital
All 14 hospitals live within 7 months, zero unplanned downtime
Headline results
Median time from scan completion to a flagged study reaching a radiologist's worklist dropped from 47 minutes to under 4
94% of eligible study volume routed automatically through the triage pipeline by the end of rollout
All 14 hospitals live on the integrated workflow within 7 months, with zero unplanned PACS downtime
On-call escalations acknowledged within 10 minutes rose from 58% to 87% after mobile notifications launched
Tech & Tools Used
What powered the build
Every tool below earned its place in this engagement. Here is the part each one played.
Python (FastAPI)
Powers the orchestration service at the heart of the pipeline, receiving triage results from the vendor models and turning them into worklist updates, notifications and audit entries.
Orthanc (DICOM)
Acts as the DICOM routing layer, identifying eligible imaging studies as they arrive and streaming them out to the third-party triage services.
Mirth Connect (HL7)
Handles the HL7 interfaces with hospital systems, keeping patient and order context in step with the studies flowing through the triage pipeline.
RabbitMQ
Queues study events and triage flags between the router, orchestration service and notification layer, so a slow downstream step never blocks incoming scans.
PostgreSQL
Stores the audit trail: every flag, worklist update, notification and acknowledgement is recorded here so the network can evidence what happened after each model result.
Docker
Packages each pipeline service into identical containers, so the stack behaves the same way in every hospital it is rolled out to.
Kubernetes
Runs the containerised services across the network's environments, restarting failed components and scaling the pipeline as more hospitals come online.
Prometheus + Grafana
Provides the dashboards tracking pipeline latency, uptime and flag volumes that the rollout team watched as each hospital was switched on.
Firebase Cloud Messaging
Delivers the mobile on-call notifications, pushing urgent flags to the right radiologist's phone the moment the orchestration service raises them.
Ready to Build your Hospital & Health System Business with AI Integration & Implementation
Ask Byte
Ask Byte
Typically replies instantly
just Now
Hi! I'm OrganByte's assistant. How can I help you today?
AI-generated content may be incorrect

