top of page
Frequently Asked Questions
Below you’ll find quick answers to the most common questions about Downtime PACS. If your question isn’t listed, our team is here to help
➣ Contact Us
Downtime PACS is an imaging continuity infrastructure platform designed to keep imaging operations functioning when normal healthcare infrastructure fails. DTP provides four layers of resiliency spanning connectivity, hospital infrastructure, radiology vendor infrastructure, and fully autonomous on-premises operation. Depending on the failure, DTP can preserve the normal workflow, provide a modified or alternate workflow, or maintain an essential local imaging workflow when external infrastructure is completely unavailable.
Modern imaging depends on a chain of systems: network connectivity, PACS/RIS, interfaces, cloud services, vendor platforms, remote radiologists, and other infrastructure. Failure of any link can interrupt image transmission, interpretation, clinician access, and patient care. DTP isolates those failures and provides alternate paths and infrastructure so imaging can continue.
No. DTP is designed to complement existing infrastructure. During normal operations, customers continue using their established clinical systems. DTP adds independent connectivity and imaging-continuity capabilities that become valuable when normal infrastructure is degraded or unavailable.
Layer 1 is Connectivity Resiliency, which protects the normal workflow when internet or WAN connectivity is lost or degraded. Layer 2 is Hospital Infrastructure Resiliency, which provides a modified workflow when hospital-side PACS, routing, interfaces, or related imaging infrastructure fail. Layer 3 is Radiology Vendor Infrastructure Resiliency, which provides an alternate reading workflow when the radiology provider's infrastructure is unavailable. Layer 4 is Autonomous / Isolated Clinical Continuity, which maintains an essential on-premises imaging workflow when external infrastructure is unavailable.
Traditional network redundancy can provide another path to the same systems, but it does not solve failure of those systems themselves. DTP extends resiliency beyond network failover to hospital imaging infrastructure, radiology vendor infrastructure, DICOM workflow continuity, and autonomous local imaging operation.
No. While Failsafe PACS is specifically designed for imaging continuity, DTP Connect can carry DICOM, HL7, and any other other IP-based traffic and may support additional clinical connectivity use cases when appropriately engineered (i.e. transit of hybrid or remote EMR or Lab data).
The current platform includes DTP Connect Home for last-mile clinician-home resiliency, DTP Connect Lite for non-acute and distributed care environments, DTP Connect Enterprise for acute-care and mission-critical environments, and DTP Failsafe PACS for independent imaging continuity. These products can be deployed individually or combined according to clinical risk and site requirements.
Images stored by DTP can be exported or forwarded using standard DICOM workflows for reintegration into the organization's primary imaging environment. The specific recovery and reconciliation process is established with the customer during implementation.
The interaction depends on the product and continuity layer. DTP Connect interfaces with approved network paths to protect normal clinical connectivity. Failsafe PACS provides an independent imaging environment that is segmented or isolated from primary hospital infrastructure. The architecture is tailored to the customer's network and security requirements.
Yes. With a current DTP service agreement, DTP provides 24/7/365 monitoring and support for our products. DTP continuously monitors system health, connectivity, and the status of DTP-managed components to help identify and address issues before they affect continuity. Customers can also access DTP Insight, our customer-facing monitoring platform, for visibility into their DTP systems, connectivity, and operational status.
DTP is designed for healthcare environments and uses security controls appropriate to protected health information, including encryption, authenticated access, and logging. Contractual, hosting, and implementation details are reviewed with the customer as part of the security process.
bottom of page