7 Things Every PACS Support Contract Should Always Include in 2026
Most 'PACS support' contracts leave gaps. Here are the 7 things real 24/7 outsourced PACS support should include — and often doesn't.
Two hospitals can buy something both call PACS support and end up with completely different services. One gets continuous monitoring, named engineers and a resolution target at 3am on a holiday. The other gets an email address, a four-hour acknowledgement promise, and a bill for everything that turns out to be "out of scope". The label is identical. The outcome, on the night the archive stops accepting writes, is not.
This is a checklist of the seven inclusions that actually distinguish the two. RAD365 delivers managed PACS services as a systems, infrastructure and uptime discipline — not reading or interpretation — so everything below is written from the operational side of the imaging chain.
inclusions that separate real support from a ticket queue
typical transition to a fully scoped support model
response and resolution — most contracts only publish one
1. Monitoring tuned to your baseline, not a generic template
Most imaging failures announce themselves hours before anyone notices clinically: a DICOM association starts failing intermittently, a queue depth creeps upward, an archive node approaches its write ceiling, a nightly backup returns a non-zero exit code to nobody. Generic infrastructure monitoring catches none of this because it watches servers, not the imaging chain.
What to require: per-node DICOM association and echo checks, queue-depth thresholds set against your actual traffic pattern rather than a default, interface backlog alerts on every HL7 feed, archive headroom measured against your growth rate, and backup job success verified by restore rather than by log line. Ask to see a sample alert from an existing customer's environment with identifying details removed.
2. Named engineers with a published roster
"You'll have a dedicated team" is not the same as "here are the three engineers assigned to you and here is the shift pattern they work". The difference shows up during an incident. A named engineer who has read your runbook and knows your AE-title map starts diagnosing in the first minute. A pooled responder spends twenty minutes learning your environment while a scanner sits idle.
3. Resolution targets, not just response targets
Nearly every contract publishes a response target because it is easy to hit — an automated acknowledgement satisfies it. Far fewer publish a resolution or documented-workaround target, because that requires actual capability. Severity should be defined by clinical impact, not by system, and both clocks should be measured monthly and reported whether or not the target was met.
4. After-hours cover that is staffed, not scheduled
The single most misleading phrase in the market is 24/7. Ask two questions and it resolves immediately: is the overnight responder on shift or on call, and do they have standing authority to restart a service or reroute DICOM traffic without waiting for a daytime approval? A department admitting emergency cases at 2am needs both answers to be the right one. Our PACS support framework sets out how severity, escalation and out-of-hours authority should be structured.
5. A written scope table — inclusions and exclusions, element by element
Scope disputes are the most common source of unbudgeted spend in imaging IT, and they are almost entirely preventable. The contract should carry a table naming every element — archive, DICOM routing, worklists, each interface, each modality class, viewer administration, workstation support, network path, vendor liaison — with an explicit in or out against each. Ambiguity always resolves in favour of the party that wrote the document.
6. Vendor escalation handled on your behalf
Manufacturer cases stall on missing evidence. A support partner holding your vendor account references, opening cases with logs, timestamps and reproduction steps attached, and chasing them daily removes weeks from the average resolution and removes the case-management burden from your team entirely. Where the imaging chain crosses into network, storage or gateway territory, DICOM gateway ownership should be named in the same escalation path.
7. A clean exit
Data, configuration, documentation and runbooks are hospital property. The contract should say so, define a hand-over package delivered at no extra charge, and offer a transition period at standard rates. Providers who resist this are pricing in switching cost, which tells you what they expect the service quality to be in year three.
PACS Support vs. Radiology IT Support: What's the Difference?
These two terms get used interchangeably in procurement documents and they should not be. Radiology IT support is the broader estate discipline: workstations, department networking, printers, dictation hardware, accounts, endpoint issues and everything else that surrounds imaging without being imaging. PACS support is narrower and deeper — the archive, DICOM routing, AE titles, modality connectivity, worklists, hanging protocols, viewer performance and the HL7/FHIR interfaces that move orders and studies.
| Dimension | PACS support | Radiology IT support |
|---|---|---|
| Primary objects | Archive, DICOM nodes, worklists, interfaces | Workstations, network, peripherals, accounts |
| Failure mode it prevents | Studies not reaching or leaving the archive | A user unable to work at their desk |
| Skills required | DICOM/HL7, imaging storage, modality behavior | General enterprise IT and endpoint support |
| Typical out-of-hours need | High — imaging runs overnight | Moderate — mostly business-hours demand |
| Who usually owns it | Specialist partner or imaging informatics | Hospital IT service desk |
The practical consequence: a generalist radiology IT contract will not catch a broken DICOM route, and a PACS-only contract will not fix a reading-room workstation. Departments need both defined, and they need to know which contract owns which boundary before an incident forces the question.
How to run the check on your current contract
- Print the scope table. If there isn't one, that is finding number one.
- Find the resolution target. Not the response target — the resolution or workaround target, by severity.
- Ask who is on shift tonight. A name and a shift pattern, or an on-call rota. There is no third answer.
- Request last quarter's SLA report. Its absence is itself the result.
- Read the termination clause. Confirm the hand-over package and who pays for it.
- Test a restore. Not a backup log — a restore, documented, with a date on it.
Two or more gaps in that list means the department is running reactive support with a proactive label on the invoice.
Get a free PACS assessment
Talk to a RAD365 PACS engineer about coverage, migration, or interim support for your environment. No obligation, no sales pitch.
Get a free PACS assessment →Related Reading
- Outsourced PACS support from RAD365 — what the service covers end to end
- Managed PACS services — scope, SLAs and coverage tiers
- Radiology IT support — the broader estate discipline and where it stops
- The RAD365 PACS support framework — severity, escalation and reporting structure
- DICOM gateway services — routing, normalisation and store-and-forward
- Veterinary PACS support — the same discipline for practices and vet groups
Frequently Asked Questions About PACS Support
What PACS Support Actually Covers
What do PACS support services include for radiology departments?
Complete PACS support covers continuous monitoring of the whole imaging chain, SLA-bound incident response with severity tied to clinical impact, DICOM node and routing administration, modality worklist health, HL7 and FHIR interface management, archive tiering and storage headroom planning, verified backups with documented restore tests, user and hanging-protocol administration, patch and change control, vendor escalation handled on the department's behalf, and a monthly SLA attainment report. Anything not named in a written scope table should be assumed excluded.
How do PACS support services help reduce downtime in medical imaging workflows?
By shortening every phase of an incident rather than only the last one. Monitoring tuned to your baseline detects a stalled DICOM queue or a failing archive node before a technologist notices a missing study. A named engineer holding your runbook removes the diagnostic delay a first-time responder adds. Standing authority to restart services or reroute traffic at 3am removes the approval delay. Problem management — root-cause records rather than repeated fixes — removes the recurrence. Detection, diagnosis, authority and prevention are the four levers; a break-fix ticket queue improves none of them.
What should I look for when choosing a PACS support service for my hospital?
Vendor-agnostic coverage of the exact PACS, modality, storage and interface stack you actually run; named engineers with a published shift roster instead of a rotating pool; resolution targets alongside response targets, with severity defined by clinical impact; genuinely staffed after-hours cover rather than intake-only answering; a written scope table listing inclusions and exclusions element by element; and clean exit language confirming your data and documentation are yours. Reference calls with hospitals of similar size and vendor mix outweigh any capability slide.
Can PACS support services be customized to work with multiple imaging modalities?
Yes, and in a real department they must be. A typical estate runs CT, MR, CR/DR, ultrasound, mammography, nuclear medicine and fluoroscopy from several manufacturers, each with its own DICOM conformance quirks and tag behavior. Customisation means per-modality AE-title and routing rules, tag normalisation where a device writes non-conformant metadata, worklist mappings per device, and monitoring thresholds tuned to each modality's normal traffic pattern. Support that treats all modalities identically misses the failures that matter most.
What is a managed PACS support company and how does it differ from in-house IT support?
A managed PACS support company owns the operational outcome of the imaging chain under contract — availability, incident response, change control and reporting — rather than supplying hours on request. In-house IT typically covers one shift, splits attention across the whole hospital estate, and holds imaging knowledge in one or two individuals. A managed model brings a team, round-the-clock cover, monitoring tooling, documented runbooks and measurable SLAs. The two are complementary in practice: internal IT keeps ownership and context, the managed partner supplies depth and out-of-hours capacity.
Costs & Contract Structure
How much do PACS support services typically cost for a mid-sized clinic?
Pricing depends on the estate — number of modalities, sites, archive size, interface count and required coverage hours — so any number quoted without a scoping conversation is a guess. What matters more than the figure is the structure behind it: a fixed monthly fee for a written scope, projects such as migrations estimated separately, and no per-incident charging that penalises staff for raising tickets. Ask any provider to show what is inside the fee line by line, and what triggers a change order.
Should PACS support pricing be flat-fee or hourly?
Flat-fee for the defined scope, with change control for work outside it. Hourly billing creates the wrong incentive — the provider earns more when your environment behaves badly — and turns every judgment call into a budget conversation, which is exactly when staff stop reporting problems. A flat fee shifts incident-volume variance onto the provider, where it belongs, and gives them a financial reason to prevent incidents rather than bill for them. Migrations, new site builds and major upgrades sit outside as separately estimated projects.
What SLAs should a managed PACS support company guarantee for uptime and response time?
Severity 1 — imaging unavailable or studies not reaching the archive — should carry a response measured in minutes at any hour of any day, with a resolution or documented-workaround target attached. Severity 2, such as one degraded modality or a slow worklist, should carry same-business-day resolution targets. Severity 3 configuration requests typically resolve within a few business days. Uptime should be expressed against the clinical service, not just the server, measured monthly and reported whether or not targets were met.
What exit and data-ownership clauses belong in a PACS support contract?
The contract should state plainly that all imaging data, configuration, documentation and runbooks are hospital property; that on termination the provider delivers a hand-over package within a defined window at no additional charge; that a transition period of 30 to 90 days is available at standard rates; and that monitoring configuration and credentials transfer rather than retire. A provider comfortable writing a clean exit clause is signalling that it expects renewal on merit rather than on switching cost.
Choosing the Right Model
What's the real difference between "pacs support" and "radiology IT support"?
PACS support is the narrower, deeper discipline: the archive, DICOM routing, modality connectivity, worklists, hanging protocols, viewer performance and the interfaces that move studies and orders. Radiology IT support is broader — workstations, printers, department networking, dictation hardware, general endpoint and account issues that surround imaging without being imaging. Departments run into trouble when a generalist contract is assumed to include the imaging-specific layer. The practical test is whether the contract names DICOM, HL7, AE titles and archive health explicitly.
Is outsourced PACS support the same thing as managed PACS?
They overlap but are not identical. Outsourced PACS support means an external team supports the system you already own and license. Managed PACS usually goes further, with the partner also taking responsibility for the platform itself — sometimes including hosting, licensing or hardware refresh — as a single service. Many hospitals want the first and are quoted the second, or vice versa. Ask precisely which assets the provider owns, which you own, and who signs off change to each.
Can a hospital keep its existing PACS vendor and still use outsourced PACS support?
Yes, and that is the most common arrangement. A vendor-agnostic partner supports the system you already run, holds your vendor account references, and opens and drives manufacturer cases on your behalf with evidence attached. Nothing is ripped out and no license changes. The benefit is that operational cover, monitoring and documentation stop depending on a vendor support desk whose scope ends at its own software and does not extend to your network, modalities or interfaces.
Which managed PACS support companies offer genuine 24/7 monitoring and incident response (not just an answering service)?
The claim is common; verification is simple. Ask for the overnight shift roster and the names on it, evidence of incidents resolved between midnight and 6am in the last quarter, the mean time to engineer engagement for those incidents, and whether the overnight responder has standing authority to act without daytime approval. Ask what monitoring platform is used and request a sample alert. Providers running real cover answer these in minutes; providers running an answering service change the subject to escalation paths.
Getting Started
How quickly can a hospital transition to outsourced PACS support?
Four to eight weeks is typical for a single hospital and longer for a multi-site network. The sequence is discovery and inventory of modalities, nodes and interfaces; archive and backup review with a documented restore test; monitoring deployment tuned to your baseline; runbook authoring and an agreed escalation matrix; a shadow period alongside current support covering at least one full week including a weekend; then formal SLA commencement. Interim cover can start far sooner when a department is exposed by a resignation or a vendor gap.
Does 24/7 PACS support really mean nights, weekends, and holidays — or just business hours with an on-call number?
It depends entirely on the contract, which is why the phrase is nearly meaningless on its own. Genuine cover means an engineer awake and on shift at 3am on a public holiday, holding your runbook, with authority to act. The common alternative is an intake line that records a ticket for the morning, sometimes with a best-effort call-out. Both are marketed as 24/7. The distinguishing questions are whether the overnight responder is on shift or on call, and what the resolution target is at that hour.
What are the benefits of outsourcing PACS management versus hiring in-house?
Coverage, depth and continuity. A single in-house specialist covers one shift, takes leave, and eventually resigns, taking undocumented knowledge with them. An outsourced team covers nights, weekends and holidays, carries breadth across multiple PACS and modality vendors, and includes monitoring, documentation and reporting as standard rather than as spare-time work. The in-house role remains valuable for ownership, clinical relationships and context — the strongest departments keep both and give the external team the operational load.
Do PACS support providers work with legacy or end-of-life systems?
Good ones do, and it is often the reason they are engaged. When a PACS reaches end of life the manufacturer's support narrows, patches stop and expertise leaves the market, but the archive still holds clinical history and the department still runs. Support for legacy systems means compensating controls, tightened monitoring, careful change freeze, documented workarounds and a realistic migration plan on a timeline the hospital controls rather than one forced by an outage.
