Why legacy WAN cannot support modern healthcare workloads
Legacy WAN architectures cannot support healthcare's demands for clinical application performance, multi-site connectivity and regulatory compliance. SD-WAN and SASE address these challenges through application-aware routing, centralised management and integrated security for NHS DSPT, UK GDPR and Caldicott Principle compliance.
Impact on patient care. Healthcare organisations depend on network connectivity for every patient interaction, clinical decision and administrative process. When networks fail or perform poorly, clinicians cannot access patient records, diagnostic images experience delays, telehealth consultations freeze mid-session, and critical alerts from connected medical devices fail to reach the appropriate staff. The result is delayed treatment decisions, compromised patient safety and potential regulatory breaches.
Operational strain. Traditional healthcare network architectures struggle with operational demands. MPLS circuits are expensive to deploy across geographically dispersed sites and inflexible when services relocate or new facilities open. Backhauling all traffic through central data centres can introduce latency that degrades real-time applications (PACS and telehealth platforms), leading to single points of failure, with guest WiFi, medical IoT devices and remote working staff all competing for bandwidth.
SD-WAN and SASE address these challenges through application-aware traffic management, supporting multiple connectivity types, providing centrally managed security that scales across distributed sites and minimising the need for on-site expertise.
Different healthcare operating environments
Not all healthcare organisations' needs are the same. GP surgeries, acute hospitals and community facilities operate from different site types, each with distinct connectivity requirements and tolerance for failure.
GP Surgeries and Primary Care. Continuous connectivity for electronic patient records, e-prescribing and referral systems. Extended network outages force practices to revert to paper-based processes, creating patient safety risks and administrative backlogs that take days to clear.
Acute Hospitals. PACS requiring rapid transfer of diagnostic images (often several hundred megabytes per study), real-time patient monitoring transmitting continuous vital signs, and laboratory information systems coordinating thousands of test results daily. Slow PACS performance means radiologists cannot review images promptly, potentially delaying time-critical diagnoses.
Community Healthcare. District nursing teams, community mental health services and rehabilitation centres often operate from smaller sites with minimal IT support. Network reliability is essential for mobile clinicians accessing records during home visits (often via 4G/5G), secure messaging between care teams, and video consultations with patients who cannot travel.
Technical performance standards
Three clinical workload thresholds drive the technical design: teleradiology and imaging (2 to 3 Gbps burst during morning rounds), telehealth and VoIP (sub-150ms latency and sub-30ms jitter), and EHR (sub-50ms round-trip for clinician screen transitions).
Teleradiology and imaging. Standard 3D mammography files are often multiple gigabytes per examination. Radiology departments with multiple consultants simultaneously accessing PACS during morning reporting rounds generate burst traffic reaching 2 to 3 Gbps, requiring bandwidth aggregation across multiple circuits to prevent image rendering queues. SD-WAN broadband links reduce transfer time, enabling radiologists to access imaging studies without clinical workflow interruption during on-call emergency trauma assessments.
Telehealth and VoIP. Real-time video consultations and VoIP communications require strict latency and jitter tolerances. Industry standards state latency should remain under 150ms and jitter under 30ms. Forward Error Correction (FEC) capabilities of SD-WAN enable reconstruction of lost packets in real-time without retransmission delays, maintaining audio and video quality even when packet loss reaches 1 to 2 per cent.
EHR performance. Legacy connections with 100 to 200ms latency create visible delays in screen transitions, forcing clinicians to pause between clicks. SD-WAN deployments achieve consistent sub-50ms round-trip latency through path selection optimisation, ensuring instantaneous screen updates that match on-premises performance.
Compliance and security 2026: The Data (Use and Access) Act
DUAA introduces mandatory data auditing and access control requirements for healthcare organisations processing patient information. SD-WAN platforms support these obligations through centralised logging, policy enforcement and sub-50ms latency for AI-assisted diagnostic human-in-the-loop intervention as mandated by DUAA Article 22A.
Data (Use and Access) Act 2025. Mandatory data auditing and access control requirements for healthcare organisations. SD-WAN supports the obligation through centralised logging and policy enforcement.
AI-assisted diagnostics and human-in-the-loop. UK healthcare providers integrating AI-assisted diagnostic tools face specific human oversight requirements under DUAA. Network-induced delays displaying AI-generated diagnostic overlays on high-resolution CT scans can create screen lag that impedes human intervention (required under DUAA Article 22A). SD-WAN architectures resolve this by supporting AI-assisted radiology workflows with sub-50ms latency.
Encryption and NHS DSPT. NHS DSPT and HIPAA regulations mandate that encryption keys for patient data transmissions remain under healthcare organisational control rather than third-party transport providers. Healthcare SD-WAN deployments implement customer-managed encryption (CME) where the organisation generates, stores and rotates cryptographic keys independently.
BT SD-WAN and SASE capability pillars for Healthcare
Eight capability pillars cover the procurement question set: Clinical Performance, Protocol Support, UK Safety Standards (DCB0129 and DCB0160), Compliance Mapping (NHS DSPT and HIPAA), IoMT Security, Identity and Access (ZTNA), Threat Protection, and Data Residency.
Clinical Performance. Detail how the solution prioritises EHR, PACS, imaging and telehealth traffic across MPLS and 5G. Safety-critical traffic requires low jitter and zero packet loss. NHS DCB0129 Standard and HHS HICP Guidance apply.
Protocol Support. Confirm support for DICOM, HL7 and FHIR protocols without MTU or asymmetric routing issues. Medical protocols behave differently than generic SaaS traffic.
UK Safety Standards. Map network and security policy changes to DCB0129 and DCB0160 clinical risk management standards. Statutory obligations to manage clinical safety risks from network services.
Compliance Mapping. Provide a mapping for NHS DSPT (CAF aligned) and HIPAA technical safeguards (45 CFR 164.312). Statutory compliance requires clear traceability between network controls and regional data laws.
IoMT Security. Describe the segmentation model for medical hardware that cannot support security agents or frequent patching. Unmanaged clinical devices are primary breach vectors.
Identity and Access. Explain ZTNA enforcement for clinicians and support for "break glass" emergency access. Clinical workflows require rapid entry during emergencies without creating permanent security gaps.
Threat Protection. Detail DNS security and SWG policies specifically tuned for healthcare vendors and clinical allowlists. Generic security policies often disrupt essential clinical portals and telehealth sessions.
Data Residency. Confirm ability to restrict traffic inspection and log residency to specific regions (UK, US, Canada). Healthcare contracts mandate strict data residency to comply with local privacy statutes.
How does Netify work for healthcare procurement?
Four steps. Select pre-written healthcare RFP questions covering HIPAA, DUAA, EHR integration, imaging, telehealth and multi-branch failover. Publish to 30+ scored vendors and managed service providers. Compare responses with AI-assisted scoring. Shortlist and engage vendors directly, without sales intermediaries or pay-to-play rankings.
Step 1, select healthcare requirements. Choose from pre-written RFP questions covering HIPAA and DUAA 2025 compliance, EHR integration, DICOM and PACS imaging, telehealth QoS, multi-branch failover and IoT device support. Add bespoke questions using AI assistance.
Step 2, publish to scored vendors. The RFP is published to Netify's curated marketplace of 30+ SD-WAN and SASE vendors and managed service providers, each independently assessed using the Netify Market Index methodology.
Step 3, compare responses. Vendors respond directly through the platform. AI-assisted scoring evaluates responses against the stated requirements, producing a side-by-side comparison the buyer can share with procurement stakeholders.
Step 4, shortlist and engage. Move from RFP to vendor engagement without sales intermediaries, gated content or pay-to-play rankings.
Scope and transparency. Netify is not a network or security service provider and does not certify compliance. We translate common requirements (NHS DSPT, HIPAA, clinical safety) into procurement questions and require suppliers to evidence their claims. Final compliance decisions remain with the buyer and their appointed advisors.
Business case: Legacy architecture vs Healthcare SD-WAN
| Feature | Legacy Architecture | Healthcare SD-WAN | Impact on Care |
|---|---|---|---|
| Cost model | High cost per Mbps restricting bandwidth | Broadband aggregation enabling greater bandwidth | NHS trusts report 40 to 60 per cent WAN cost reduction |
| Redundancy | Single carrier dependency, manual failover disrupts EHR | Multi-path (fibre, 5G) with sub-second failover | Eliminates care disruption during circuit failures |
| Deployment | 90 to 120 days for MPLS provisioning | Zero-Touch Provisioning, days to hours | Accelerates urgent care and vaccine centre openings |
| Security | Perimeter-based, vulnerable to lateral movement | Zero Trust (SASE) with micro-segmentation | Isolates IoMT devices from ransomware |
Further reading and references
Glossary
- NHS DSPT (Data Security and Protection Toolkit)
- The NHS information governance assurance framework. Aligned to the Cyber Assessment Framework (CAF). All organisations that have access to NHS patient data or systems must complete an annual DSPT assessment.
- Data (Use and Access) Act 2025 (DUAA)
- UK legislation introducing mandatory data auditing and access control requirements for healthcare organisations processing patient information. Article 22A mandates human-in-the-loop oversight for AI-assisted diagnostics.
- PACS (Picture Archiving and Communication System)
- Clinical imaging system used by radiology departments to store, retrieve and review diagnostic images. PACS workloads can produce burst traffic of 2 to 3 Gbps during morning reporting rounds.
- DICOM
- Digital Imaging and Communications in Medicine. The medical imaging protocol used between PACS, modalities (CT, MRI) and review workstations. Behaves differently than generic SaaS traffic and requires SD-WAN support for non-fragmented MTU and symmetric routing.
- HL7 and FHIR
- Health Level 7 and Fast Healthcare Interoperability Resources. The protocols used to exchange clinical data between EHR systems, lab information systems and other healthcare applications.
- IoMT (Internet of Medical Things)
- Connected medical devices on the clinical network. Often cannot host security agents or support frequent patching, so segmentation and policy enforcement are handled at the network layer.
- EHR (Electronic Health Record)
- The digital clinical record used by clinicians at the point of care. Epic and Cerner are common cloud-hosted EHRs. Sub-50ms round-trip latency is required for clinician screen transitions.
- DCB0129 and DCB0160
- NHS clinical risk management standards. DCB0129 covers manufacturers and DCB0160 covers deploying organisations. Network and security policy changes that affect clinical workflows must be assessed against these standards.
- Customer-managed encryption (CME)
- A model where the healthcare organisation, rather than the transport provider, generates, stores and rotates cryptographic keys for patient data transmissions. Required under NHS DSPT and HIPAA for several patient-data scenarios.
- ZTNA "break glass" access
- A Zero Trust Network Access pattern that provides rapid emergency access for clinicians during a critical incident, without creating permanent security gaps. Required by clinical workflows where waiting on standard access requests would delay patient care.
- Forward Error Correction (FEC)
- SD-WAN capability that reconstructs lost packets in real-time without retransmission. Used to maintain audio and video quality in telehealth and VoIP sessions when packet loss reaches 1 to 2 per cent.
- Netify Healthcare RFP Builder
- The procurement tool used by NHS trusts and healthcare organisations to generate a structured RFP from pre-written healthcare-specific questions and publish it to 30+ scored vendors and managed service providers.
Frequently asked questions
How does SD-WAN optimise DICOM and PACS image transfers?
SD-WAN optimises DICOM and PACS transfers through bandwidth aggregation and WAN optimisation techniques including deduplication and caching. Bandwidth aggregation combines multiple internet connections into unified logical links. UK hospital groups report that caching reduced cross-site image transfer times by 60 to 70 per cent for follow-up examinations.
Can SD-WAN replace private MPLS circuits for patient records?
Yes. SD-WAN can replace private MPLS circuits through packet duplication over dual internet links. UK private hospitals report dual-broadband configurations with packet duplication achieved 99.98 to 99.99 per cent uptime, comparable to MPLS while reducing costs by 50 to 65 per cent.
What are the requirements for cloud-hosted Epic EHR?
Cloud-hosted Epic EHR deployments require under 50ms round-trip latency and high session persistence to prevent disconnects. UK healthcare organisations deploying Epic in AWS or Azure report that SD-WAN path selection ensuring consistent sub-50ms latency eliminated session timeout issues.
How does SD-WAN support the Data (Use and Access) Act 2025?
DUAA introduces mandatory data auditing and access control requirements. SD-WAN platforms support this through centralised logging and policy enforcement. For AI-assisted diagnostics, SD-WAN ensures the sub-50ms latency required for human-in-the-loop intervention as mandated by DUAA Article 22A.
How are mobile ambulances and community clinics supported?
Mobile healthcare delivery is supported through packet bonding across multiple cellular carriers. Ambulances use SpeedFusion-style aggregation to combine bandwidth from multiple SIMs, eliminating dead zones and ensuring paramedics can transmit real-time ECG telemetry and video feeds to emergency department physicians during patient transport.
Does BT deliver SD-WAN and SASE for healthcare on both Cisco Meraki and Fortinet?
Yes. BT's managed service layer wraps both Fortinet and Meraki SD-WAN and SASE stacks, with 24/7 monitoring, managed firewall, incident handling and change management. Fortinet typically fits healthcare environments where segmentation depth and compliance posture are primary drivers. Meraki typically fits distributed community and GP estates where cloud-managed simplicity is the priority.
How does the NHS DSPT alignment work?
Netify's healthcare RFP questions require vendors to provide a mapping for NHS DSPT (CAF aligned) and HIPAA technical safeguards (45 CFR 164.312). Statutory compliance requires clear traceability between network controls and regional data laws, evidenced in the vendor response. Final compliance decisions remain with the buyer and their appointed advisors.
Ready to price your BT Healthcare requirement?
Tell us about your trust or healthcare organisation, current network and target rollout date. We come back with a vendor-fit view on BT Managed SD-WAN and SASE for healthcare (Cisco Meraki or Fortinet) and indicative commercials before RFP. The Netify Healthcare RFP Builder is free to use.
Request a healthcare proposalOr email support@netify.com.