Routing
Route by sender, by any header value, or by a script. Send to several destinations at once, fail over between them or spread the load, and hold studies until they are complete.
Symmetricare Routes
Every study to the right place, from the modality to the PACS, the archive, the cloud and the AI service. Free.
What Routes does
Section titled “What Routes does”Routes sits between the systems that make images and the systems that need them. Modalities send to Routes; Routes decides where each study goes, changes what has to change on the way, and makes sure it gets there, even when a destination is down for the night.
Cloud and DICOMweb
Send to cloud PACS and VNAs over DICOMweb, including Azure Health Data Services and Google Cloud Healthcare, and take uploads from web viewers and apps.
AI workflows
Send studies to AI services, de-identified if you like, track every job until its results come back, and route the results on with the patient’s identity restored.
HL7 too
Build the modality worklist from HL7 orders, and route and transform HL7 messages between the RIS, PACS, EHR and the systems around them.
Patient safety
Studies whose patient does not match their order wait in a reconciliation queue until someone fixes them; de-identification profiles keep identities from the places that must not have them.
Built to stay up
Any number of nodes behind a load balancer, several central servers, queues on disk that survive restarts, and alerts before anyone notices a problem.
Runs where you do
Section titled “Runs where you do”Windows installers, Linux services or Docker containers, on SQL Server or PostgreSQL. No licence fees, no per-study pricing, no limits on nodes or destinations.
Quick startFrom blank servers to the first routed study in about an hour.
Plan and sizeHow many nodes, how much disk, which database, for your volume.