Start from the problem, not the feature list

“Every new connection is a firewall ticket.”

Install the Remote Gateway at the site. It receives locally and relays outbound over mutual TLS, so there is no inbound rule to request and nothing at the remote end listening to the internet.

“Nobody knows what half our routing rules are for.”

Rules live in named rule sets with visible priority, and each interface names the set that evaluates its traffic. Routing decisions and orchestration events share one correlation id, so a study page shows why it went where it went.

“We are moving off our current router and dread retyping it.”

Import a Laurel Bridge Compass 2.6.x XML export or a DICOM Systems Unifier appliance backup. The console previews everything it would create, then applies it disabled so you enable it deliberately rather than discovering it live.

“The AI vendor needs studies, and compliance needs them scrubbed.”

Attach a de-identification profile to the route. Anonymize irreversibly, or pseudonymize with an audited crosswalk so results can find their way back - and hold anything that returns unmatched for an operator instead of guessing.

“We have a legacy archive to empty and a reading day to protect.”

Bulk migration runs over Query/Retrieve with resume and cancel, parallel retrieves, and a per-job reduced-rate window so it backs off during reading hours and runs flat out overnight.

“One reading group is down and studies are queueing behind it.”

Group destinations for round-robin, weighted, or least-connections distribution with automatic failover, retries, and dead-letter handling, so one unavailable target does not stall the others.