Switching PACS Support Providers Without Disrupting Radiology
A structured look at how hospitals change PACS support partners without a coverage gap: SLAs, documentation handoff, and a 72-hour interim bridge if needed.
By Trisha Seal — September 29, 2026. Trisha writes about PACS support transitions, SLA structures, and escalation design drawn from RAD365's vendor-agnostic PACS Support work for hospitals and Critical Access Hospitals. RAD365 does not read or interpret studies.
Changing PACS support providers sounds like a procurement task. In practice, it is an operational handoff with clinical stakes: the moment one team steps back and another steps in, someone has to own every modality, interface, and after-hours alarm. Good PACS support transitions are quiet. Bad ones show up as a stalled worklist at 2 a.m.
What follows is a generic, composite scenario, not a named client. It walks through how a mid-size, multi-site hospital network decided to switch, how it planned the handoff, what cutover week looked like, and where things stood 90 days later.
The Decision: When Renegotiating Stopped Making Sense
The network ran three hospitals and two outpatient imaging sites on two PACS platforms. Its support contract was up for renewal, and the imaging director had a folder of evidence: Severity 1 incidents with slow first responses, tickets escalated and then left open, and no monthly report showing actual response times.
The team tried escalation first. The incumbent promised improvement, but the next two outages followed the same pattern. The deeper problem was structural: most of the environment's knowledge lived with one senior engineer on the provider's side. When that person was unavailable, nobody else could answer basic questions about interface routing.
That combination, repeated missed commitments, no documented SLA reporting, and single-person knowledge, is usually the signal that renegotiation will not fix the underlying model. The network decided to switch.
Planning the Handoff
Separating support from software
The first clarification was that nothing about the PACS platforms themselves had to change. Support and software are separable. A vendor-agnostic team can operate GE Centricity and Universal Viewer, Philips IntelliSpace, Sectra, Fujifilm Synapse, Agfa Enterprise Imaging, Change Healthcare/Stentor, Intelerad, Visage, Carestream Vue, eRAD, Novarad, RamSoft PowerServer, Merge Unity, and legacy or open-source stacks. Keeping the platforms in place removed an entire category of risk from the project. A full platform move could come later, through a separate PACS migration plan, if it ever made sense.
Documentation before anything else
The incoming team started with a documentation handoff list: vendor contacts and entitlements, recent incident history, DICOM and HL7 interface maps, escalation paths, backup and disaster-recovery procedures, and every open ticket with its history. Onboarding followed RAD365's standard two-to-four-week path: discovery, access, documentation, escalation mapping, runbooks, and monitoring.
A short overlap window
The network negotiated a few days of overlap before the old contract ended. That window let the new team validate remote access at every site, confirm monitoring was catching real alerts, and walk each modality's connection with the outgoing engineers still reachable.
Where Transitions Break, and How a Structured Switch Holds
| Transition risk point | What goes wrong | How a structured switch addresses it |
|---|---|---|
| Fragmented handoff | Interface maps, vendor contacts, and runbooks are scattered or missing | A written documentation checklist completed before cutover |
| Single-person knowledge | One engineer holds the environment in his or her head | Knowledge captured into shared runbooks owned by a team |
| No documented SLA | Response times cannot be measured or enforced | Contractual severity tiers with monthly reporting |
| Coverage gap at exit | Old provider leaves before new provider is ready | Overlap window, or interim coverage within 72 hours |
| Open tickets lost | In-progress issues are closed and restarted from scratch | Tickets transferred with full history |
| Unmapped sites | A satellite site or modality is missed in monitoring | Every site and modality confirmed during onboarding |
Cutover Week Under a New Severity Clock
On cutover day, the new provider took ownership of monitoring, ticketing, and on-call. The severity clock changed immediately, using the tiers described in the PACS support framework:
- Severity 1 (system down or clinical impact): 15-minute response, continuous work until resolved.
- Severity 2 (degraded service): 1-hour response.
- Severity 3 (single-user or non-urgent): 4-business-hour response.
- Severity 4 (requests and changes): next business day.
The hospital's own IT and administration team handled communication to referring physicians and satellite sites, while the new provider supplied updated contact channels. The first test arrived midweek, when an outpatient site's modality stopped sending overnight. It was logged as Severity 2, answered inside the hour, and traced to an interface configuration issue documented in the handoff notes.
When There Is No Time for a Full Onboarding
Not every switch has the luxury of a planned overlap. Sometimes a provider exits the support business, a contract ends abruptly, or the one person who held everything together resigns. In those cases, a two-to-four-week onboarding is too long to wait. That is what interim PACS support is for: coverage operational within 72 hours, 24/7, across all major PACS platforms, with no long-term commitment required. It bridges the gap while a permanent partner is chosen, and it can roll into ongoing operations or hand off cleanly.
Ninety Days Later
By the end of the first quarter, the network had monthly reports showing incidents by severity and actual response times, runbooks that did not depend on any single engineer, and one escalation path across all five sites. The two PACS platforms were unchanged. Budgeting was simpler under a flat monthly operations fee rather than hourly or per-incident billing, and the smallest site, a Critical Access Hospital, received the same severity commitments as the largest.
The network kept its internal IT team focused on enterprise systems and network infrastructure while managed PACS services covered daily PACS operations, nights, weekends, and holidays. Peer review and QA remained a separate, optional decision outside core PACS support scope.
What to Take From This Scenario
A switch goes well when the new team is staffed and operational before the old one steps back, when documentation is transferred rather than rebuilt, and when the SLA is written down and measured from day one. When there is no time for any of that, a short interim bridge closes the gap.
RAD365 is an operations and workflow partner providing PACS Support and the Radiology Workflow Manager only. It does not read or interpret studies, and it does not provide preliminary reads, dictation, or reporting.
Changing Providers? Close the Gap First.
Interim PACS support can be operational within 72 hours, with 24/7 coverage and no long-term commitment.
Get Interim PACS Support →Frequently Asked Questions
Why Hospitals Switch PACS Support Partners
What are the most common reasons a hospital switches PACS support providers?
Contract non-performance such as repeated missed SLAs, an incumbent provider consolidating or exiting the support business, a single point of failure like one administrator leaving, rising cost without added coverage, or growth into multi-site or multi-PACS operations the current provider can no longer handle.
How do you know it's time to switch PACS support providers rather than renegotiate?
When missed severity commitments repeat despite escalation, when the provider cannot document response times, when institutional knowledge lives with one person rather than a team, or when growth into new sites or modalities has outpaced what the current contract covers.
Does switching PACS support providers mean switching the PACS software itself?
No. Support and software are separable. RAD365 is vendor-agnostic, so a hospital can change who operates and supports its PACS environment without touching the underlying PACS platform.
What risk does a hospital carry by staying with an underperforming PACS support provider?
Repeated Severity 1 incidents without contractual accountability are a direct threat to clinical continuity. Every week without documented, enforced SLAs is a week of unmeasured operational exposure.
Planning a Switch Without a Coverage Gap
What is the biggest risk in switching PACS support providers?
A gap in coverage between the outgoing provider's exit and the incoming provider's readiness. Zero clinical downtime requires the new partner staffed and operational before the old one steps back.
How long does it take to onboard a new PACS support provider?
RAD365's standard onboarding takes two to four weeks for discovery, access, documentation, escalation mapping, runbooks, and monitoring. It can compress to under a week, or start as interim coverage operational within 72 hours, when a hospital is already exposed.
Should the old and new PACS support providers overlap during a transition?
Yes, when possible. A short overlap window, even a few days, lets the incoming team validate access, documentation, and monitoring before the outgoing provider disengages.
What should be documented before a PACS support handoff begins?
Vendor contacts and entitlements, recent incident history, interface maps for DICOM and HL7, escalation paths, backup and disaster-recovery procedures, and any open tickets, so nothing is lost between providers.
Can a hospital switch PACS support providers mid-contract?
Contract terms vary, but most agreements include a notice period and transition clause. It is best to start onboarding a new partner before formally terminating the old contract, to avoid a coverage gap.
What Actually Happens During the Transition
Does clinical work stop while PACS support providers change?
No, not when the transition is handled correctly. The goal is zero clinical downtime: monitoring, escalation, and Severity 1 response should be active under the new provider before the old contract lapses.
Who notifies referring physicians and satellite sites about a PACS support change?
Typically the hospital's own IT or administration team leads external communication, while the new support provider supplies updated contact channels and confirms every site and modality is mapped.
What happens to open support tickets during a switch?
Open tickets should be documented and handed to the incoming provider with full history rather than closed and restarted, so no in-progress issue is lost mid-investigation.
Does interim coverage make sense during a longer PACS support transition?
Yes. When a switch is planned but not yet finalized, or a provider relationship ends abruptly, short-term interim PACS support can be operational within 72 hours with no long-term commitment required, closing the gap while a permanent partner is selected.
Choosing and Evaluating a New Partner
What should a hospital ask a new PACS support provider before signing?
For documented severity-based SLAs, the L1/L2 support structure, which PACS platforms and vendors the team actually supports, the onboarding timeline, and how coverage scales as sites are added.
Does a vendor-agnostic PACS support provider reduce switching risk in the future?
Yes. Support built tightly around one specific PACS platform limits future options. A vendor-agnostic partner supports the hospital's PACS today and any platform it adopts later.
Is a flat monthly fee typical for PACS support after a switch?
Many providers, including RAD365, use a flat monthly operations fee scoped to the environment rather than hourly or per-incident billing, which makes budgeting easier when moving off a different pricing model.
Can Critical Access Hospitals switch PACS support providers without losing coverage quality?
Yes. Critical Access Hospitals often benefit most from switching to a partner offering the same severity commitments as larger systems, since they rarely have a deep bench of local PACS specialists to fall back on.
