What a Real 24/7 PACS Support Model Requires Behind the Scenes
See the staffing, SLA, monitoring, escalation, runbook, recovery, and onboarding mechanics behind genuine 24/7 PACS support.
By Trisha Seal — September 24, 2026. Trisha documents the operating disciplines behind RAD365's vendor-agnostic PACS support, including staffed coverage, incident tiers, interfaces, monitoring, and recovery. RAD365 does not read or interpret studies.
Availability Is an Operating Model, Not a Phone Number
24/7 PACS support begins long before an overnight call arrives. The visible response depends on an operating system of staffed shifts, technical tiers, severity clocks, monitoring, escalation relationships, runbooks, and tested recovery procedures. Remove any one of those components and “24/7” becomes an availability claim that the hospital cannot reliably measure.
RAD365's managed PACS services put those components under one accountable operating model. The breakdown below focuses on what happens behind the scenes, while this related buyer's checklist covers what hospitals should include in an evaluation.
What Marketing Language Leaves Out
| “24/7” marketing language | What genuine coverage requires operationally |
|---|---|
| An after-hours number | Staffed shifts, owned tickets, and a response clock that starts at intake |
| Technical experts available | A written L1/L2 split with named escalation responsibilities |
| Fast response | Four defined severities with contractual commitments |
| Proactive support | Monitoring, alert ownership, current runbooks, and trend review |
| Vendor coordination | Documented manufacturer contacts, entitlement details, and escalation history |
| Disaster recovery ready | Validated backups, restore procedures, and tested recovery responsibilities |
1. Staffed Shifts Across Time Zones
Coverage cannot depend on one administrator being willing to answer a phone. A real model assigns responsibility across staffed shifts and time zones, preserves handoff context, and keeps the same incident process active overnight, on weekends, and during holidays. RAD365 describes this as 24/7 global coverage: the responsibility moves between active teams rather than following one exhausted person.
2. A Deliberate L1/L2 Split
L1 handles application, access, and clinical-user support. L2 handles infrastructure, DICOM and HL7 engineering, interface workflows, backup, and disaster recovery. This two-tier support framework protects specialist capacity without forcing users to diagnose the technical layer before asking for help.
3. A Severity Clock Everyone Understands
| Severity | Operational definition | Response commitment |
|---|---|---|
| Severity 1 | System down with clinical impact | 15 minutes; continuous work until resolved |
| Severity 2 | Degraded service | 1 hour |
| Severity 3 | Single-user or non-urgent issue | 4 business hours |
| Severity 4 | Standard request or change | Next business day |
The clock is useful only when severity definitions, intake time, ownership, escalation, communication, resolution, and closure are documented. RAD365 uses an ITIL-compliant lifecycle: logging, root-cause analysis, categorization and priority, escalation, resolution, and closure.
4. Omnichannel Intake Feeding One Incident Record
Email, phone, secure remote desktop, and a ticketing portal give clinical and IT users practical ways to report an issue. The important behind-the-scenes requirement is that every channel feeds one managed incident process. Otherwise four ways to ask for help create four disconnected queues.
5. Monitoring With Named Alert Ownership
Proactive monitoring is not a wall of dashboards. It is a defined set of availability, interface, queue, storage, and infrastructure signals with thresholds, ownership, and response instructions. The radiology IT operating layer turns those signals into actions before a local team has to reconstruct what changed.
6. Vendor Escalation Relationships That Already Exist
A mixed imaging estate may 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. Vendor-neutral engineers maintain the contacts, entitlement details, evidence, and escalation history needed to move a manufacturer case forward.
7. Runbooks That Survive Shift Changes
Runbooks capture architecture, dependencies, access paths, restart constraints, interface routes, known failure modes, vendor contacts, and communication rules. They turn institutional memory into an operational asset and let the next shift continue an incident without repeating discovery.
8. Backup and Disaster-Recovery Validation
A backup job reporting success is not the same as a proven recovery path. L2 ownership includes backup and disaster recovery, with procedures and responsibilities validated before an outage. Storage optimization and archive planning support that work, but recovery readiness has to be tested rather than assumed.
9. Onboarding That Builds the Model Before It Promises It
Standard onboarding takes two to four weeks to complete discovery, access provisioning, documentation, escalation mapping, runbooks, and monitoring. When a hospital is already exposed because a contract lapsed or an administrator departed, the process can compress to under a week with prompt access. Interim coverage can address that immediate gap while the full operating baseline is completed.
How the Model Changes the Economics
RAD365 uses a flat monthly fee rather than hourly or per-incident billing and reports 40–60% cost savings compared with maintaining equivalent capability in-house. Critical Access Hospitals receive the same severity commitments and flat monthly model; their common constraint is a single-person imaging IT function, not a lower standard of need. Peer review and QA remain a separate optional add-on, not part of core PACS support.
RAD365 is an operations and workflow partner providing PACS Support and the Radiology Workflow Manager only. It does not read or interpret studies and provides no preliminary-read services.
See What Real Coverage Requires
Map staffing, tiers, severity clocks, monitoring, escalation, and recovery against your current PACS support model.
Explore managed PACS services →Frequently Asked Questions
Coverage Foundations
What operating structure sits behind genuine 24/7 PACS support?
It requires staffed shifts, a documented L1 and L2 split, one severity clock, monitored systems, several ways to open an incident, current runbooks, vendor escalation contacts, and tested backup and disaster-recovery procedures. Availability is the product of that operating system, not a label placed on an after-hours phone number.
Which PACS failures can monitoring surface before clinical users report them?
Monitoring can identify availability, interface, storage, queue, and infrastructure conditions that fall within the connected environment before they become widespread user complaints. Monitoring does not prevent every incident, but it gives the support team an earlier signal and a defined path for investigation.
How can a hospital distinguish real around-the-clock coverage from marketing language?
Ask who is staffed on each shift, what L1 and L2 own, when the response clock starts, how severity is assigned, which channels create a ticket, who contacts the PACS manufacturer, and how backups are validated. If those answers are not documented, the promise is difficult to operate or measure.
Can smaller hospitals use a flat monthly support model?
Yes. RAD365 applies the same flat monthly fee model and severity commitments to Critical Access Hospitals. Their common constraint is a single-person imaging IT function, not a lower need for dependable coverage. Scope still reflects the environment, but support is not converted into hourly or per-incident billing.
Does coverage change when a health system runs several PACS platforms?
The operating model stays consistent while the technical runbooks change by platform and interface. Vendor-agnostic engineers can support mixed estates, allowing one incident process and severity scale to span several manufacturers, modalities, sites, and legacy systems.
People, Tiers, and Intake
Why is one in-house PACS administrator not enough for continuous coverage?
One person cannot be simultaneously available on every shift, handle routine access requests, investigate infrastructure faults, coordinate vendors, maintain documentation, and test recovery. A genuine 24/7 model distributes those duties across staffed shifts and technical tiers while preserving clear ownership.
What happens during the first 15 minutes of a Severity 1 outage?
The incident is logged and categorized, clinical impact is confirmed, the correct L1 and L2 resources are engaged, available monitoring and recent-change evidence is reviewed, and escalation begins under the documented runbook. The commitment is a 15-minute response followed by continuous work until resolution.
Which SLA terms should a hospital require in writing?
Require definitions for all four severities, response commitments, the start point for the clock, continuous-work language for Severity 1, communication expectations, escalation ownership, closure criteria, and reporting. Written mechanics prevent an urgent incident from becoming a debate about what the contract meant.
How do users contact support during an overnight incident?
RAD365 supports omnichannel intake through email, phone, secure remote desktop, and a ticketing portal. Each route feeds the same incident lifecycle so the case can be categorized, prioritized, escalated, resolved, and closed without relying on one person's inbox.
How are L1 and L2 responsibilities divided?
L1 handles application, access, and clinical-user support. L2 handles infrastructure, DICOM and HL7 engineering, interface workflows, backup, and disaster recovery. The split protects engineering capacity while keeping routine user issues moving.
SLAs and Technical Operations
Must a live person answer every overnight call for coverage to be genuine?
The essential requirement is staffed response under a measurable commitment, not a vague promise that a phone is monitored. Intake must reliably create an owned incident, trigger the correct severity clock, and engage the right tier without waiting for the next business day.
How does Severity 1 handling differ from Severity 3 handling?
Severity 1 means the system is down with clinical impact: response within 15 minutes and continuous work until resolved. Severity 3 is a single-user or non-urgent issue with a 4-business-hour response. The difference governs urgency, staffing, escalation, and communication cadence.
What response times define the four RAD365 severity levels?
Severity 1 has a 15-minute response and continuous work until resolved. Severity 2, degraded service, has a 1-hour response. Severity 3, a single-user or non-urgent issue, has a 4-business-hour response. Severity 4, a standard request or change, is handled by the next business day.
Can Critical Access Hospitals receive the same severity commitments as larger systems?
Yes. RAD365 applies the same four severity commitments and flat monthly fee model. Smaller facilities often need the operating depth more because imaging IT responsibility may sit with one person who cannot provide continuous coverage alone.
How does vendor-neutral support work across a mixed PACS estate?
Engineers maintain platform-specific knowledge and runbooks while incidents follow one common operating process. RAD365 supports 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.
Scope, Onboarding, and Value
What operational value does continuous support provide beyond system availability?
It creates consistent incident ownership, clearer escalation, maintained documentation, proactive monitoring, storage oversight, vendor coordination, and a repeatable closure process. Those disciplines reduce the amount of imaging-specific support work that falls unpredictably on hospital IT.
Are peer review and quality assurance included in core PACS support?
No. Peer review and quality assurance are a separate optional add-on. Core PACS support covers applications, access, infrastructure, interfaces, backup, disaster recovery, monitoring, administration, migrations, storage optimization, and vendor coordination.
How quickly can a hospital establish 24/7 PACS support?
Standard onboarding takes two to four weeks for discovery, access, documentation, escalation mapping, runbooks, and monitoring. It can compress to under a week when a hospital is already exposed, such as after a contract lapse or administrator departure, provided the hospital supplies prompt access.
