What Happens When Your PACS Vendor Sunsets the Product, and What to Do Next
A hospital receives a PACS sunset notice. Follow its 90-day decision window, support bridge, migration plan, and practical next-step checklist.
By Trisha Seal — September 22, 2026. Trisha writes about PACS support operations and transition planning for RAD365. RAD365 keeps imaging infrastructure working; it does not read or interpret studies.
The Notice
At 8:17 on a Monday morning, an unnamed regional hospital's imaging director opens a letter from its PACS vendor. The product is being sunset: end of life is now dated, future support is narrowing, and the platform will soon be discontinued. Nothing has failed yet. Studies still arrive, priors still open, and users can still sign in. But the operational contract beneath all of that has changed.
The director does not begin by shopping for software. She opens an incident and transition record, asks internal IT to preserve the notice and contract terms, and brings the existing environment under a documented PACS support framework. The first objective is continuity while the hospital makes a defensible decision.
The First 30 Days: Stabilize Before You Select
Inventory What the Notice Actually Affects
The team inventories the PACS version, archive, storage, modalities, workstations, user access, DICOM routes, HL7 interfaces, backups, and disaster recovery dependencies. It identifies which commitments end on the sunset date and which third-party components remain supported. This turns a broad manufacturer announcement into a specific operating risk register.
Put One Severity Clock Around the Estate
L1 takes application, access, and clinical-user support. L2 takes infrastructure, DICOM engineering, interface work, backup, and disaster recovery. Every issue follows an ITIL-compliant lifecycle: logging, root cause analysis, categorization and priority, manufacturer escalation where available, escalation management, resolution, and closure. Staff can reach the team through email, phone, secure remote desktop, or a ticketing portal.
The contractual response remains clear: Severity 1, system down with clinical impact, receives a 15-minute response and continuous work until resolved; Severity 2 degraded service receives a 1-hour response; Severity 3 single-user or non-urgent issues receive a 4-business-hour response; Severity 4 requests or changes receive a response the next business day.
The 90-Day Window
By day 30, the hospital has a stable baseline. Days 31 through 60 are used for requirements and vendor-neutral assessment. Days 61 through 90 produce a decision, migration sequence, interface plan, data-validation plan, and accountable owners. The calendar is a plausible case scenario, not a universal manufacturer deadline.
Critically, the hospital does not confuse choosing a target with abandoning the existing environment. It uses PACS migration and consolidation support to plan legacy-to-cloud or on-premise consolidation while preserving access to historical data.
Bridging the Gap
The chosen replacement cannot safely go live before the manufacturer deadline. RAD365 therefore keeps the legacy and deprecated PACS operating while the migration proceeds. The bridge includes monitoring, user support, interface ownership, backup validation, incident response, and documented workarounds. RAD365 manages parallel environments during the transition so the hospital can validate the new system without surrendering the old one prematurely.
The mixed estate is supported vendor-agnostically. It can include GE Centricity or 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. These names identify supported environments; no manufacturer directs the recommendation.
What Changes and What Does Not
| Do this | Don't do this |
|---|---|
| Confirm the precise support and patch dates | Assume the software stops working on the notice date |
| Inventory data, interfaces, access, backups, and dependencies | Begin with product demonstrations before mapping the estate |
| Run legacy and target environments in parallel when validation requires it | Switch off the old archive before reconciliation is complete |
| Keep one incident owner and one severity clock | Split sunset issues among the manufacturer, IT, and project team |
| Choose the target through vendor-neutral requirements | Let the shortest sales timeline decide the architecture |
| Set an exit date and completion criteria for the bridge | Turn temporary legacy support into indefinite postponement |
The Practical Sunset Checklist
- Record the final support, patch, and escalation dates from the manufacturer notice.
- Inventory every PACS instance, archive, modality, workstation, DICOM route, HL7 interface, and user group.
- Validate backup execution and a real restore path.
- Apply the Severity 1–4 response commitments to the transition estate.
- Document the L1/L2 ownership boundary with internal IT.
- Define replacement requirements independently of a specific manufacturer.
- Plan historical-data validation and continued access to priors.
- Test parallel operations and cutover rollback criteria.
- Set the bridge end date and legacy decommissioning evidence.
If the notice exposes an immediate support gap, interim PACS coverage can protect the current environment while the full transition is scoped. Standard onboarding for consolidated support takes two to four weeks and can compress to under a week when the hospital is already exposed.
What the Hospital Has at Day 90
It has not rushed into a replacement. It has an operated legacy environment, one support owner, a tested migration path, a target selected against requirements, and a controlled period of parallel operation. A flat monthly fee replaces unpredictable combinations of hiring, overtime, and fragmented escalations while the transition remains active. Ongoing managed PACS operations can continue after cutover if the hospital wants the same ownership model around the new platform.
RAD365 is a global operations partner for PACS support and workflow. It does not read or interpret studies. Clinical interpretation remains entirely with the hospital's radiologists.
Turn a Sunset Notice Into a Controlled Transition
Map the support gap, stabilize the current PACS, and build a vendor-neutral bridge to the next environment.
Review the PACS support framework →Frequently Asked Questions
Understanding the Sunset Notice
What does it mean when a PACS vendor sunsets a product?
A sunset means the manufacturer has set an end date for some combination of maintenance, security updates, compatibility work, and technical support. The software does not necessarily stop on that date, but the hospital can no longer treat the original manufacturer as a dependable operating backstop. The practical response is to document exactly which commitments end, stabilize the current environment, and plan the next platform without turning the notice into a rushed cutover.
How much warning do hospitals typically get before a PACS vendor discontinues support?
There is no universal warning period, so the contract and formal notice control the answer. A hospital should capture the last supported date, any final upgrade or patch deadline, interface dependencies, data-export rights, and the date support contacts change. The scenario in this article uses a 90-day decision window, not a claim that every manufacturer provides 90 days.
What happens to patient imaging data when a PACS product is sunset?
The data remains the hospital's responsibility and does not disappear because support ends. The immediate work is to verify archive integrity, backup and restore readiness, DICOM metadata, retention requirements, export methods, and continuing access to priors. During a migration, RAD365 maintains access to historical data while validating integrity before, during, and after transfer.
Can a hospital keep running a discontinued PACS system safely?
It can be operated for a controlled transition when risk is documented, access is restricted appropriately, backups and restores are validated, interfaces are monitored, and qualified support owns incidents. That bridge should have an exit plan. It is not permission to leave an unsupported environment unmanaged indefinitely.
What are the clinical risks of running an unsupported PACS platform?
Operational failures can delay access to current studies or priors, interrupt modality worklists, break DICOM or HL7 flows, and slow clinical users. The risk comes from deteriorating supportability around the system, not from the sunset label alone. A monitored bridge reduces exposure while the hospital selects and implements its next platform.
The Decision Window
What should a hospital do in the first 30 days after a sunset announcement?
Confirm the notice and contract terms; inventory the PACS version, archive, modalities, interfaces, users, backups, and open incidents; test restore procedures; assign one incident owner; and document the migration decision process. The first month should produce a stable operating baseline and a dated decision path, not an emergency product purchase.
How long does a full PACS migration typically take?
Duration depends on data volume, number of sites, interfaces, target architecture, and validation requirements. RAD365's migration process is scoped after assessment rather than promised from a generic calendar. The important distinction is that support for the legacy environment and the migration timeline can run in parallel, so clinical operations do not have to wait unprotected.
Should a hospital migrate immediately or bridge the gap first?
Bridge first when an immediate cutover would force weak vendor selection, incomplete data validation, or unsafe downtime. Move directly only when the target platform, interfaces, migration plan, validation criteria, and operational ownership are genuinely ready. A bridge creates decision quality; it should not become an open-ended reason to postpone the move.
What is a PACS support bridge and when is it needed?
A support bridge is temporary operational ownership of the current PACS while replacement selection and migration proceed. It is useful when manufacturer support ends before a safe replacement can go live, when multiple PACS must run together, or when a hospital needs to preserve access while data and interfaces are validated.
How does a hospital choose a replacement PACS platform under time pressure?
Separate platform selection from immediate stabilization. Define clinical and technical requirements, inventory integrations, confirm data portability, compare deployment options, and validate references without asking the existing outage team to run the selection alone. RAD365 provides vendor-neutral assessment and planning, so support for the current estate does not depend on selling a particular replacement.
Operating the Transition
Who supports a sunset PACS system while a replacement is selected?
The hospital needs a named operations owner capable of covering users and applications at L1 and infrastructure, DICOM, HL7, backup, and disaster recovery at L2. RAD365 can take that role across the legacy and transitional estate while internal IT retains its documented enterprise responsibilities.
What SLA coverage should apply to a legacy system during a transition?
The severity clock should remain explicit: Severity 1, system down with clinical impact, receives a 15-minute response and continuous work until resolved; Severity 2, degraded service, a 1-hour response; Severity 3, a single-user or non-urgent issue, a 4-business-hour response; and Severity 4, a request or change, next business day. Legacy status should not make urgent ownership ambiguous.
Can vendor-agnostic support cover a mixed environment of old and new PACS?
Yes. A vendor-agnostic team can cover active, legacy, and transitional systems under one incident process. RAD365 supports mixed estates that can include GE Centricity or 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.
What happens to DICOM and HL7 interfaces during a PACS transition?
They are inventoried, tested, monitored, and moved according to a controlled cutover plan. During parallel operations, routes and messages may need to reach both environments while reconciliation confirms completeness. L2 engineering owns AE titles, connectivity, interface behavior, and exception handling rather than treating interfaces as an afterthought.
How does 24/7 support differ for a legacy system versus an active one?
The response channel and severity commitments should not differ. The technical options may: a legacy product may lack a current manufacturer patch or escalation path, so the support team relies more heavily on monitoring, documented workarounds, infrastructure controls, backup readiness, and disciplined change management. The limitation is recorded rather than hidden.
RAD365's Role
Does RAD365 replace a sunset PACS or operate it during the transition?
RAD365 operates and supports the environment the hospital already owns while the hospital decides and executes its next step. It does not sell a replacement PACS. When a migration is approved, RAD365 can manage the bridge, parallel environments, validation, and consolidation work around the selected target.
What does RAD365's migration and consolidation bridge cover?
It covers legacy-to-cloud moves, on-premise consolidation, multi-site migration, continued access to legacy data, integrity checks, parallel-run validation, cutover coordination, and vendor-neutral planning. The objective is zero clinical downtime while old and new environments overlap.
How quickly can RAD365 take over support for a system a vendor just discontinued?
Standard consolidation of support takes two to four weeks for discovery, documentation, access, escalation mapping, and monitoring. When a sunset deadline leaves the hospital exposed, onboarding can be compressed to under a week, provided the hospital can supply the required access and system information promptly.
