What Hospital CFOs Should Know About PACS Support Costs Before Budget Season

A CFO's guide to outsourced PACS support pricing: flat monthly fees, SLA tiers, in-house cost drivers, and what to scope before budget season closes.

By Trisha Seal — September 28, 2026. Trisha writes about PACS support models, SLA structures, and operating costs drawn from RAD365's vendor-agnostic PACS Support work for hospitals and Critical Access Hospitals. RAD365 does not read or interpret studies.

Budget season forces a hard question about imaging IT: what does it actually cost to keep the PACS running, day and night? For many hospitals, the answer is scattered across salaries, overtime, OEM contracts, and emergency fixes. Understanding outsourced PACS support pricing before the budget locks gives finance leaders a way to compare that scattered spend against one predictable line item.

This guide walks a CFO through the questions to ask, the cost drivers to scope, and the contract terms that protect the organization. It is written for finance leaders, not engineers.

Part 1: Understand What You Are Actually Paying For Today

Before comparing options, build an honest picture of current spend. In-house PACS support rarely appears as one number. It usually hides in several places:

Salary and benefits for a PACS administrator or a share of IT staff time.
Overtime and on-call pay for nights, weekends, and holidays.
Backfill when the administrator is on vacation, on sick leave, or has resigned.
Training and tools needed to keep skills current across PACS, DICOM, and HL7.
Turnover, including the months spent recruiting a replacement.

Recruiting alone can take two to three months before a new administrator is productive. During that time, coverage gaps become clinical risk.

Part 2: Learn How Outsourced PACS Support Pricing Works

Most RAD365 engagements use a flat monthly operations fee based on environment size. The fee is scoped by five inputs: PACS instances, modalities, sites, study volume, and the SLA tier selected. It does not spike with after-hours tickets or incident volume, which is what makes it budgetable. The managed PACS services model replaces time-and-materials billing with a predictable monthly cost and a dedicated team.

RAD365 does not publish price lists, because each environment is scoped individually. The useful comparison for a CFO is not a sticker price. It is the full annual cost of internal coverage against a single fee that includes 24/7 engineers.

Part 3: Compare the Two Models Side by Side

Budget question	Outsourced PACS support	Hiring in-house
24/7 coverage	Engineers on shift across nights, weekends, and holidays	One person or a small team; nights and weekends require overtime, rotation, or gaps
Response speed	Severity-based SLAs written into the contract	Depends on workload, availability, and time off
Cost predictability	Flat monthly operations fee based on the environment	Salary, benefits, training, overtime, backfill, tools, and turnover
Time to value	Onboarding in two to four weeks; emergency onboarding under one week	Two to three months of recruiting before productivity
Turnover risk	No single-person dependency	One resignation can leave the organization exposed
Scalability	Scale coverage as sites, modalities, or PACS instances change	Adding headcount is slow and expensive
Accountability	One contract, one SLA, one team	Performance issues handled through HR cycles

The same comparison appears on the RAD365 homepage, and it is a useful starting document for a budget committee.

Part 4: Put the SLA Terms in Writing

A lower cost means little if response times are vague. Finance leaders should insist on severity-based commitments written into the contract. RAD365's standard SLAs are:

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 full structure of support tiers and escalation is described in the PACS support framework. Ask for monthly operations reporting so SLA performance can be reviewed alongside the budget.

Part 5: Scope the Environment Honestly

Multi-site hospitals often run more than one PACS. RAD365 is vendor-agnostic and supports GE, Philips, Sectra, Fujifilm, Agfa, Intelerad, Visage, Carestream, Merge Unity, and legacy stacks under one team, so a mixed environment does not require several support contracts. If a consolidation is planned, include it in the scope now; RAD365's PACS migration services run old and new systems in parallel during the transition.

Critical Access Hospitals deserve special attention. Rural markets rarely have local PACS specialists to hire, and RAD365 covers them under the same commitments as larger facilities.

Part 6: Separate Core Operations From Optional Layers

Keep the core PACS operations budget distinct from optional services. Blinded peer review and QA is an optional layer RAD365 offers for human radiology groups. Budget it as its own decision so the core support comparison stays clean.

A Budget-Season Checklist for CFOs

Total the full annual cost of internal PACS coverage, including overtime, backfill, and turnover.
List every PACS instance, modality, and site in scope.
Record after-hours coverage gaps and recurring incidents from the past year.
Define the SLA tier the organization actually needs.
Flag any legacy system or planned migration.
Request a scoped proposal and compare it against the internal total.

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.

Scope Your PACS Support Before the Budget Locks

Get a clear view of your environment, coverage gaps, and a predictable monthly operations model.

Explore Managed PACS Services →

Frequently Asked Questions

Budgeting Basics for PACS Support

How is outsourced PACS support pricing usually structured?

Most RAD365 engagements use a flat monthly operations fee based on the size of the environment: the number of PACS instances, modalities, sites, study volume, and the SLA tier selected. The fee does not rise with after-hours tickets or incident counts, which makes the line item predictable from month to month.

Which cost drivers should a CFO ask about before approving a PACS support budget?

Ask how many PACS instances and sites are in scope, which modalities feed them, current study volume, what response commitments are required by severity, and whether any system is legacy or deprecated. Those inputs determine the scope of a flat monthly fee far more than headcount does.

Why do in-house PACS support costs often exceed the approved budget?

The visible cost is salary, but the full cost of an in-house role also includes benefits, training, overtime for nights and weekends, backfill during vacation or sick leave, tools, and turnover. Those items often sit in different budget lines, so the true cost of internal coverage is rarely seen in one place.

Does outsourced PACS support replace the hospital IT department?

No. Outsourced PACS support works alongside the existing IT team. RAD365 takes ownership of PACS operations, imaging interfaces, and incident response under contractual SLAs, while hospital IT continues to own the broader network, identity, and enterprise systems.

Comparing Outsourced and In-House Models

What does a CFO get from outsourcing that one PACS administrator cannot provide?

Around-the-clock coverage by engineers on shift, contractual severity-based response times, team-wide experience across many PACS products, and no single-person dependency. A single administrator typically covers business hours and is limited to the systems he or she has worked on before.

How long does it take to get PACS coverage in place compared with hiring?

RAD365 onboarding typically takes two to four weeks, and emergency onboarding can be completed in under one week. Recruiting an in-house PACS administrator alone can take two to three months before that person is productive.

What happens to support continuity when an in-house PACS administrator resigns?

Institutional knowledge can leave with that person, and the organization may be exposed until a replacement is recruited and trained. With an outsourced team, knowledge stays with the team, so vacations, sick leave, and turnover do not create a coverage gap.

Is outsourced PACS support only cost-effective for large health systems?

No. Critical Access Hospitals and rural facilities often benefit most, because they cannot recruit local PACS specialists. RAD365 provides them with a full PACS operations team for a flat monthly fee under the same SLA commitments that larger hospitals receive.

SLAs, Risk, and Accountability

What response times should a PACS support contract commit to?

RAD365's standard SLAs are Severity 1 (system down or clinical impact) with a 15-minute response and continuous work until resolved; Severity 2 (degraded service) with a 1-hour response; Severity 3 (single-user or non-urgent) with a 4-business-hour response; and Severity 4 (requests and changes) handled the next business day. SLAs are tuned to each environment and contract.

How can finance leaders verify that a PACS support partner is meeting its SLAs?

Require severity-based response commitments written into the contract, plus monthly operations reporting that shows incidents by severity, response times, and recurring issues. That gives finance and IT leaders one document to review instead of anecdotes from clinical staff.

Can one partner support several different PACS products across our sites?

Yes. RAD365 is vendor-agnostic, with experience across GE Centricity and Universal Viewer, Philips IntelliSpace, Sectra, Fujifilm Synapse, Agfa Enterprise Imaging, Change Healthcare or Stentor, Intelerad, Visage, Carestream Vue, eRAD, Novarad, RamSoft PowerServer, Merge Unity, and legacy or open-source stacks.

Does an outsourced PACS support partner have an incentive to sell a new PACS?

RAD365 has no incentive to sell a replacement PACS. It operates the systems a hospital already has, including end-of-life and deprecated systems, so recommendations about replacement can be made on operational grounds rather than sales targets.

Planning for the Next Budget Cycle

Should PACS migration or consolidation support be budgeted separately?

Plan for it explicitly. RAD365 supports consolidation and migration work, including running old and new systems in parallel during a transition. Knowing whether a migration is planned in the coming year helps scope the environment accurately before the budget is locked.

Is peer review and QA included in a PACS support budget?

Not by default. Blinded peer review and QA is an optional layer RAD365 offers for human radiology groups on top of the PACS it supports. It should be budgeted as a separate decision from core PACS operations.

Can PACS support coverage scale up or down during the fiscal year?

Yes. Coverage can be scaled up or down as sites, modalities, or PACS instances change, which avoids the slow and expensive process of adding or reducing internal headcount mid-year.

What is the best first step before budget season closes?

Document the current PACS environment, recurring incidents, after-hours coverage gaps, and the full cost of internal support. A PACS assessment with RAD365 turns that inventory into a clear scope that finance and IT can evaluate together.