Interactive demo

Three ways the imaging chain breaks — and how the OCL routes around each.

A CT/MRI study has to travel from the modality, through the hospital PACS, and out to the radiologist — either by remote access into the hospital, or by replication to the reading practice's PACS. Connectivity can break at three different points. Pick one and watch what happens without PortGarrison versus with the OCL.

Illustrative simulation of the architecture — not a live system or real device telemetry.
The path: CT / MRI → hospital PACS → either a remote radiologist logging in over the hospital's ISP/VPN (DMZ proxy) or replication over VPN to the rad-practice's own PACS. The OCL sits inline at the modality with independent sub-GHz mesh and per-device cellular paths.
Simulate a break at:
local network ISP / VPN replication VPN sub-GHz mesh per-device cellular (out-of-band) per-device cellular (out-of-band) CT / MRI OCL HospitalPACS Remoteradiologist Rad-practicePACS
Sense Decide Enforce Degrade Report

Normal operation — studies flow from the modality through the hospital PACS and on to the radiologist. Pick a break above to see what happens.

WithoutThe study can't leave the modality — it queues locally. The radiologist has nothing to read, and the team can't tell whether it's the device, the cable, or the network.
With OCLThe OCL reroutes the modality over its sub-GHz mesh path to an alternate route into the PACS — studies keep moving and reads continue. Fault localized: local network / last meter.
WithoutThe hospital's remote-access path (ISP, VPN concentrator, or DMZ proxy) is down — the remote radiologist can't reach the PACS at all.
With OCLThe OCL pushes priority studies out over per-device cellular — an egress path independent of the hospital's ISP and VPN — so the radiologist still receives them. Fault localized: hospital infrastructure, not the modality.
WithoutThe replication VPN between the hospital and the rad-practice PACS is down — the study never reaches the practice where the radiologist reads.
With OCLThe OCL carries the study out over per-device cellular, bypassing the broken inter-site link, to reach the practice PACS. Fault localized: inter-site replication link.

What just happened

In every case the unprotected modality had no fallback — its data stopped at the break, and no one could immediately tell where it broke. The OCL runs a continuous control loop at the device edge: it detects the failure, classifies where it is, keeps enforcing from cached policy, and arbitrates across transport paths — mesh for a local break, cellular for an upstream one — without touching or reconfiguring the device.

Sense

Detect

Device-perspective telemetry classifies the failure at the boundary.

Decide

Localize

Six-cause classification pins down which link failed — device, last meter, infrastructure, or inter-site.

Enforce

Stay inline

The appliance keeps enforcing as the device's network endpoint.

Degrade

Reroute

Mesh for a local break; per-device cellular, out-of-band, for an upstream one.

Report

Log it

The failover and its root cause are recorded as active compliance evidence.

Device-edge resilience isn't about preventing failures — it's about maintaining care delivery through them, with the evidence to prove it.