Why hospitals cannot open inbound ports for cloud services
- Hospitals usually cannot open inbound firewall ports because clinical devices are treated as a high-trust, tightly protected network zone.
- Stateful firewalls track outbound TCP sessions, so only replies to connections the hospital itself started are allowed back in.
- Classic DICOM C-MOVE retrieval fails over the internet because the archive must open a new inbound connection to the requester.
- C-GET avoids this problem by sending instances back over the same association the requester already opened.
- Outbound-only push design means historical study retrieval needs a separate plan, such as a local connector or export project.
Hospitals usually cannot open inbound firewall ports for a cloud service. Their security teams expect clinical systems to start outbound connections instead.
That answer can feel like a blocker when your product needs images from a PACS or scanner. It is workable. DICOM supports push workflows, and modern integrations can receive studies without asking the hospital to expose its local network.
This article explains why hospital network security policies block inbound ports, how stateful firewalls handle traffic, and which outbound patterns give your product a clean way forward.
Why do hospitals block inbound ports?
Hospital local area networks host medical equipment that needs strong protection. A clinical subnet may include CT scanners, MRI systems, bedside monitors, infusion pumps, and legacy picture archiving and communication system (PACS) servers.
Many of these devices run embedded operating systems. Some receive patches slowly because downtime affects patient care. If an external attacker can reach a vulnerable modality, that device can become a foothold inside the hospital network.
So hospital IT teams treat the clinical network as a high-trust zone. They use strict boundary defense at the perimeter. Under least privilege, an outside host cannot start a session into an internal subnet.
Regulatory guidance supports that stance. NIST SP 800-66 Rev. 2 gives HIPAA Security Rule implementation guidance. It highlights access control, network segmentation, and protection of electronic protected health information.
The useful point for a product team is this: you do not need to persuade the hospital to weaken that model. Design the connection so the hospital sends out.
How do stateful firewalls and NAT track connections?
Most enterprise firewalls are stateful. They remember outbound Transmission Control Protocol (TCP) sessions in a state table.
Hospital LAN Perimeter Firewall Public Cloud
[Modality / Gateway] [State Table] [Cloud Endpoint]
| | |
|---- 1. TCP SYN (Outbound) --------->| |
| Creates state entry: |---- 2. TCP SYN (Outbound) ----->|
| Src: 10.0.1.50:49152 | |
| Dst: 198.51.100.20:2762 | |
| |<--- 3. TCP SYN-ACK -------------|
|<--- 4. TCP SYN-ACK -----------------| |
| Matches existing state entry | |
| | |
|---- 5. TCP ACK -------------------->|---- 6. TCP ACK ---------------->|
| Bidirectional data transfer | Bidirectional data transfer |
When an internal device opens an outbound connection, the firewall records the source IP, destination IP, and ports. It also translates the private address to a public address through Network Address Translation (NAT), as described in RFC 5382.
Reply packets can come back because they match an existing session. The same connection then carries data in both directions.
An unsolicited inbound connection is different. If a cloud server sends the first TCP SYN into the hospital network, the firewall has no matching state entry. It drops the packet.
A static port forward fixes that technically, but it creates a permanent hole. It exposes an internal IP address and port to unsolicited traffic. Hospital security teams are right to avoid that.
Why does classic DICOM retrieval hit this wall?
The problem often appears when a cloud product wants to retrieve studies from a hospital archive.
DICOM defines 2 common retrieval commands: C-MOVE and C-GET. C-MOVE is common in older PACS deployments, but it uses 2 network associations.
First, the requesting client connects to the archive and asks it to move a study. Then the archive reads the destination Application Entity (AE) title from its own configuration. It opens a new TCP connection back to that destination, often on port 104 or port 11112, and sends images with C-STORE.
That second connection is the issue. If your cloud service is the destination, the hospital PACS must initiate a new connection to the public internet. If the flow is reversed, and your cloud service tries to push into the hospital network, the firewall drops the inbound SYN.
C-GET avoids that shape. The requester opens one association to the archive, and the archive sends the instances back over the same association. The firewall sees replies on a connection that the hospital side already started.
The limitation is real: many legacy PACS systems do not support C-GET well. Historically, vendors built for trusted local networks where C-MOVE worked fine. For cloud products, that means outbound push is usually the cleaner design.
Which outbound patterns work for cloud products?
You have a few workable patterns. I would start with direct outbound push when the sender supports it. It keeps the network design simple, and it matches how hospital firewalls already operate.
Modern scanners, PACS routers, and vendor gateways can often send DICOM studies directly to an external endpoint. The modality or router opens an outbound TCP connection. It then sends the study after acquisition or by routing rule.
Use mutual TLS (mTLS) when the sender supports it. The hospital device verifies the server certificate, and your endpoint verifies the client certificate. The IHE ATNA Profile describes this kind of authenticated network communication for healthcare systems.
For a practical view of this pattern, read receiving DICOM from a hospital over the internet.
If older equipment cannot send safely over the internet, teams often deploy an on-premises edge connector. Local devices send to the connector on the hospital local network. The connector then opens outbound encrypted sessions to the cloud.
This works, but it has a cost. Someone must provision the appliance or virtual machine, patch the operating system, monitor it, and pass local security review. That is fine for some enterprise deals. It is heavy if you plan to connect many hospitals.
A managed gateway such as Dicomly DICOM endpoints handles the outbound hospital connection. It delivers each instance to your HTTPS destination, so your team can work on the product itself. The trade-off is less control than running every connector yourself, plus a monthly service cost. Dicomly also does not parse or change DICOM tags, so tag cleanup still belongs in your pipeline.
Site-to-site IPsec VPN tunnels are another option. They avoid a public port on the hospital side, but they create private routing work. Security approvals, subnet collisions, and tunnel maintenance can take months per site. We cover that decision in site-to-site VPNs vs internet-facing endpoints for DICOM.
What changes when you choose outbound-only?
Outbound-only design changes the product workflow. Your cloud service cannot assume it can query any hospital archive at any time.
Instead, you design around push. The hospital sender pushes a study when an exam finishes, when a routing rule matches, or when an operator sends it manually. Your service receives the study and continues from there.
This is a strong default for new products. It reduces security friction for hospital onboarding. It also makes failure ownership clearer: if a transfer fails mid-stream, the sender retries on its own schedule, or the hospital team resends the study.
The limitation is historical access. If your product needs old studies on demand, you need a separate plan. That may mean a local connector, an export project, or an agreed manual workflow. Do not hide that from the hospital. Put it in the integration plan early.
For many products, current and future studies are enough to start. Push first, then add historical retrieval only when the product truly needs it. That order keeps your first hospital connection small and testable.
What should you do next?
Ask your first hospital contact one concrete question today: which system can send DICOM studies outbound, and can it use mutual TLS? Then map that answer against how to connect a hospital sender before you design the endpoint.
Dicomly builds infrastructure for healthcare software teams that receive DICOM studies from hospitals. Why we built Dicomly →