The Managed PACS Question Most Hospitals Forget to Ask — Until It Costs Them
Hospitals compare managed PACS providers on price and uptime. The question that actually predicts a good contract is one almost nobody asks first.
Every managed PACS evaluation we see runs through the same three questions. What does it cost. What uptime do you guarantee. How fast do you respond. All reasonable. None of them predicts whether the contract will work.
The question that does is unglamorous enough that it rarely makes the scoring matrix: "Walk me through exactly what happens in your first thirty days on our environment." Ask it early, and the answer sorts the field faster than any pricing comparison — because managed PACS services fail far more often in transition than in steady state.
where most managed contracts are won or lost
realistic single-site PACS migration window
staffed response, not paid uplift
reconciliation is the migration proof point
Why the first thirty days decide everything
A managed PACS provider inherits an environment it did not build, documented by people who have left, running integrations nobody wrote down. Everything the contract promises afterwards — response times, root-cause analysis, capacity forecasting — depends on whether that environment gets properly discovered and documented in the opening weeks.
Providers that skip discovery look excellent for about a quarter. Incidents get resolved, tickets close, the reporting looks clean. Then a complex fault arrives, and the engineer is troubleshooting an environment nobody mapped. That is the moment the department discovers it bought a service desk instead of an operating partner.
What a good thirty-day answer sounds like
- Discovery and documentation. Archive product and version, storage topology, retention policy, integration map covering HL7 feeds and DICOM routes, modality inventory, user and role structure. Delivered as an artefact you keep.
- Monitoring deployment. Instrumentation on the archive, database, integration engine and storage — with thresholds tuned to your volume rather than defaults.
- Access under least privilege. Named accounts, audit logging, a documented provisioning and revocation process. No shared credentials.
- Runbooks and an escalation matrix. Written procedures for the incidents your environment actually produces, with named contacts and hours.
- Shadow running. The incoming team works incidents alongside the incumbent before owning them outright.
- Hypercare. A defined heightened-attention window after go-live, with the outgoing provider still reachable.
A provider that has done this repeatedly answers in that shape without prompting. One that hasn't will answer with capability statements: "we're ITIL aligned", "we have a 24/7 NOC". Note which you get.
PACS support vs. radiology IT support — where scope quietly leaks
The second question worth asking early concerns the boundary. Departments often buy archive support and assume the surrounding estate came with it. It usually didn't, and the gap surfaces during an incident: the archive is healthy, so the ticket is closed, but studies still are not reaching the reading workstation.
Radiology IT support covers the wider imaging estate — viewers, workstations, modality connectivity, network paths, interface engines — while PACS support covers the archive, its database and the study lifecycle. Both are needed; a single owner across both is what prevents incidents from being handed back and forth. If your organisation historically referred to this function as radiology IT infrastructure, that scope now sits under the same consolidated radiology IT support service.
| Question asked | What it actually tells you | Predictive value |
|---|---|---|
| "What's the monthly fee?" | Commercial fit only | Low |
| "What uptime do you guarantee?" | Nothing, without a measurement method | Low |
| "What's your response time?" | Useful, if severity is clinically defined | Medium |
| "Is out-of-hours staffed or on-call?" | Real coverage depth | High |
| "Walk me through your first 30 days." | Whether they've done this before | Highest |
The migration corollary
The same question applies to any archive move. Ask a provider to walk through a migration and listen for reconciliation. Competent PACS migration services are built around proving that every study arrived — identifier mapping, a pilot subset, study-level count validation against the source, phased bulk transfer with the legacy archive still readable, then a defined decommission window. Providers who describe migration in terabytes and bandwidth have costed the easy half.
Three follow-up questions worth more than the pricing sheet
- "Show me a real monthly report." Redacted is fine. It reveals whether reporting is analysis or a ticket export.
- "When did you last test a restore, and what was the measured recovery time?" A date and a number, or DR is theoretical.
- "What's your transition-out process?" Providers confident in their service describe leaving cleanly. Providers who aren't get vague.
If you need cover before a full evaluation completes — a departing administrator, a migration window, an environment that needs stabilising first — interim PACS support is a lower-risk way to test the answers against reality before committing to a multi-year term.
Put us through the thirty-day question
Send us your environment and we'll write out exactly what our first thirty days would look like on it — discovery, monitoring, runbooks, escalation. No obligation.
Talk to a PACS engineer →Managed PACS Support: Frequently Asked Questions
Evaluation Criteria
What is a managed PACS support company and how does it differ from in-house IT support?
A managed PACS support company takes operational ownership of the imaging archive and its surrounding systems as a contracted service: monitoring, incident response, administration, lifecycle management and vendor escalation, delivered against SLAs. In-house IT support is staffed capacity — capable, but bounded by headcount, working hours and whatever imaging-specific expertise happens to sit in the team. The practical difference is that a managed arrangement guarantees an outcome and a response time; an in-house team provides effort and best endeavours.
Which managed PACS support companies offer 24/7 monitoring and incident response?
Round-the-clock monitoring with a staffed response rota is the dividing line between genuine managed services and business-hours break-fix, and fewer providers offer it than claim it. When evaluating, ask three specific questions: is the out-of-hours tier staffed or on-call; is it the same team that knows your environment or a generic first line; and what is the contractual response time for a severity-1 raised at 3am. RAD365 operates 24/7/365 monitoring and incident response as standard rather than as a paid uplift.
How do I evaluate managed PACS support companies before signing a contract?
Score them on six axes: imaging-specific depth (can they discuss your interface engine, not just servers); coverage model and whether out-of-hours is staffed; SLA specificity including measurement method and remedy; transition-in methodology with a written thirty-to-sixty day plan; vendor neutrality across archives and modality mixes; and reference environments of comparable size and complexity. Ask for a sample monthly report — it reveals more about how a provider operates than any capability deck.
What are the benefits of outsourcing PACS management to a dedicated support company?
Continuous coverage without recruiting for it; specialist depth across archives, integration engines and modality behaviour that a single administrator cannot maintain; predictable cost in place of variable emergency spend; removal of single-person continuity risk; and the return of internal IT time to project work. The benefit departments report most often, though, is simply that imaging problems stop landing on the radiology manager's desk.
Should we outsource PACS management or hire another administrator?
Compare coverage rather than cost. A second administrator extends weekday capacity but still leaves nights, weekends, leave and resignation uncovered. Outsourcing converts that into a rota. The strongest arrangement in larger networks is usually hybrid — retain internal ownership of identity, network and clinical relationships, and contract the imaging-specific operational layer.
SLAs & Uptime
What SLAs should a managed PACS support company guarantee for uptime and response time?
Expect severity definitions written in clinical terms rather than IT terms, a response target per severity (minutes for severity-1, not hours), a resolution or workaround target, an archive availability commitment with a stated measurement method and exclusion list, named escalation contacts with hours, monthly attainment reporting, and a service-credit remedy when targets are missed. An availability figure with no measurement method attached cannot be enforced and should be treated as marketing.
How is PACS uptime actually measured under a support contract?
Properly, it is measured from the clinical user's perspective — can a study be stored, retrieved and displayed — using synthetic transactions against the archive rather than a server ping. Measurement should also state what is excluded: agreed maintenance windows, third-party network outages, and faults inside a system the provider does not control. Get that exclusion list in writing before signing; it is where most uptime disputes originate.
What counts as a severity-1 PACS incident?
Typically a total loss of the archive or viewer for clinical users, an inability to store studies from modalities, or a failure that halts reporting across the department. It should be defined by clinical impact, not by which component failed — a working definition lets the service desk classify correctly without escalating a judgement call at 3am.
What happens if a managed PACS provider misses its SLA?
A meaningful contract attaches a service credit, a root-cause review with a written corrective action, and — for repeated breaches — a termination trigger. Credits alone rarely change behaviour; the mandatory root-cause review is what prevents recurrence.
Migration & Transition
How do the best PACS support providers handle system migrations and upgrades?
As a planned programme with reconciliation at its centre, not as a data copy. The sequence is inventory and audit of the source archive, mapping of study, patient and accession identifiers, a pilot migration of a representative subset, validation of counts and image integrity against the source, phased bulk migration with the old archive still readable, then cutover and a defined decommission window. The step that separates competent providers from the rest is the reconciliation report — a study-level count proving nothing was lost.
How long does a PACS migration take?
For a single site with a few years of studies, typically eight to sixteen weeks end to end; multi-site networks and long retention periods run considerably longer. The bulk transfer is rarely the bottleneck — data cleansing, identifier reconciliation and validation are. Any provider quoting a migration purely on terabytes and bandwidth has not scoped the part that actually takes the time.
Can we switch managed PACS providers without downtime?
Yes, when the transition is phased. The incumbent stays live while the incoming provider deploys monitoring, documents the environment and shadow-runs incidents, then coverage transfers with the outgoing provider still reachable for a defined period. Downtime during a provider change is a planning failure, not an inevitability.
What should a transition-in plan include?
Environment discovery and documentation, monitoring and tooling deployment, credential and access provisioning under least privilege, runbook creation, an escalation matrix, a shadow-running period alongside the incumbent, an agreed go-live date, and a hypercare window afterwards. Ask to see a real one from a previous client with names redacted.
Cost & Commercials
Who are the best PACS support providers for large hospital networks in the US?
For a multi-site network, the shortlist should be judged on four capabilities rather than brand recognition: proven multi-site operation with centralised monitoring and per-site reporting; vendor-neutral experience across mixed archives, because networks rarely run one product everywhere; migration and consolidation capability, since network estates are usually mid-consolidation; and a 24/7 staffed response tier. RAD365 operates in exactly that space — physician-owned, vendor-neutral, and structured around contractual SLAs alongside existing systems and IT teams.
How is managed PACS support priced?
Most commonly as a fixed monthly service fee scoped against environment size — coverage hours, study volume, archive size, number of integrated systems and number of sites — with project work such as migrations quoted separately. Per-ticket pricing is a warning sign: it creates an incentive to resolve symptoms rather than eliminate root causes.
What is usually excluded from a managed PACS contract?
Typically third-party licence and maintenance fees, hardware and storage procurement, major migrations and implementations, bespoke development, and faults inside systems the provider does not administer. None of these are unreasonable exclusions — the problem is discovering them during an incident rather than during contract review.
Does managed PACS support cover radiology IT beyond the archive?
It can, and in most real deployments it should. The archive does not fail in isolation: viewers, workstations, modality connectivity, interface engines and network paths all sit in the same fault chain. RAD365 scopes radiology IT support alongside managed PACS so a single team owns the whole imaging path rather than passing incidents across a boundary.
Related Resources
- Managed PACS services — the full outsourced operating model and coverage tiers
- What's included in a managed PACS contract — scope, SLAs and reporting
- Radiology IT support — the imaging estate around the archive
- PACS migration services — reconciliation-led archive moves
- The RAD365 PACS support framework — ITIL-aligned incident lifecycle
- Interim PACS support — short-term cover during transition
Written by Trisha Seal, RAD365 — 11 August 2026. RAD365 delivers managed and outsourced PACS support to hospitals, imaging centres and veterinary networks: 24/7 monitoring, SLA-backed incident response, PACS administration, migrations and vendor management alongside existing systems and IT teams.