FAQ
Frequently asked questions
Security-specific questions have their own page, so a reviewer does not have to read past pricing to find them.
Is DICOM Assist a PACS?
No. It is the routing, workflow, and integration layer between your imaging sources and every destination. It has no diagnostic viewer and performs no clinical interpretation - it moves studies and it does not read them.
Where does it run?
On infrastructure you control. It is a single Windows service backed by PostgreSQL, with a browser-based management interface. It is not a multi-tenant cloud service.
How do remote sites connect without a firewall change?
The Remote Gateway is installed at the remote site, receives DICOM locally, spools it to disk, and relays it outbound over mutually-authenticated TLS to your HQ install. HQ never connects to the site, and the gateway's own listeners face the site LAN rather than the internet, so there is no inbound firewall rule to negotiate. Traffic going the other way rides the connection the gateway opened.
What can a routing rule match on?
Modality, source AE title, called AE title, source IP or CIDR, SOP class, series description, and DICOM tag values, at study, series, or instance scope. Rules live in rule sets, an interface names the set that evaluates its traffic, and within a set the lowest priority number runs first.
Which destinations are supported?
DICOM PACS and VNAs over C-STORE, Amazon S3, Azure Blob Storage, Google Cloud Storage, DICOMweb STOW-RS, HL7 v2 over MLLP, FHIR REST, a local or UNC folder, and grayscale DICOM film printers. Destinations can be grouped for load balancing and failover.
Can we migrate off our current router without retyping everything?
In most cases yes. The console imports a Laurel Bridge Compass 2.6.x XML export or a DICOM Systems Unifier appliance backup, previews the interfaces, destinations, rule sets, rules, and receive-time tag actions it would create, and applies them. Everything lands disabled so you turn it on deliberately.
Can we move a legacy archive to a new one?
Yes. Bulk study migration runs over Query/Retrieve with resume, cancel, retrieve parallelism up to 16, and a per-job reduced-rate window so the migration backs off during reading hours and runs at full rate overnight. It has its own activity tab so it does not bury the day's traffic.
Can it run on more than one server?
Yes. Several routers can share one PostgreSQL database behind a load balancer. Study completion, routing, and every scheduled poller claim their work, so nothing fires or sends twice. Talk to us about the specific limits before designing around it.
How is it licensed?
Per deployment, with capability licensing for optional modules. There is no per-study or per-image metering. Licences and installers are issued through the customer portal.
How do we evaluate it?
Ask for a demo through the contact form. Evaluations run on your own infrastructure against your own modalities and destinations, because that is the only environment that answers the question you actually have.
Not answered here?
Ask us directly. We would rather tell you what is verified than what is written in the code.