Compare DICOM routers
Compare DICOM routers: a buyer’s guide
How to evaluate enterprise DICOM routing software, with a checklist you can use with any vendor and a side-by-side of RadFuzion, Laurel Bridge Compass and Dicom Systems Unifier built from each vendor’s published documentation.
Start here
How to evaluate a DICOM router
A DICOM router receives imaging studies and sends each one to the right PACS, archive, cloud store or workstation by rule. Every product on this page does that. The differences that matter in a purchase are around it: how orders and results are handled, which cloud stores are supported, what happens when a destination is down, how traffic is secured, how many sites one person can manage, and what the vendor puts in writing.
Start from your own workflows, not a feature list. Write down the studies, orders and results that move today, the systems on each end, and what has to keep working during an outage. Then put the same questions to every vendor and ask each one to show the answer on a running system.
What this comparison is
The Laurel Bridge Compass and Dicom Systems Unifier columns paraphrase what each vendor publishes on its own website, checked on , and every documented cell links its source. We have not tested those products. “Not publicly documented” means we could not find it on the pages we checked, not that the product lacks it. The RadFuzion column comes from our own product, including what it does not do today. Vendors change their products and pages; if something here is wrong or out of date, tell us and we will correct it.
Checklist
Questions to ask any DICOM router vendor
Eighteen questions, grouped by topic. Ask for a demonstration or a document for each answer, not just a yes.
Routing and rules
- What can a rule match on: any DICOM tag, private tags, calling and called AE titles, the sender’s IP address? Which operators are there: exact, contains, numeric ranges, regular expressions?
- Can you test a rule change against a real study, without sending anything, before it goes live?
HL7 and orders
- Which HL7 v2 message types does it accept (for example ORM, ORU, ADT, SIU), and what does each one change?
- How are images matched to their orders: by accession number only, or also by MRN and issuer?
Cloud and DICOMweb
- Which cloud stores does it send to by name, and which sign-in methods does each connector support (service account, client credentials, managed identity)?
- Is it a DICOMweb client only, or does it also offer STOW-RS, QIDO-RS and WADO-RS endpoints that other systems can call?
Priors and worklist
- What starts a prior fetch (a new order, a scheduled exam, arriving images), how are relevant priors chosen, and which archives can it pull from?
- Is the modality worklist part of the router, or a separate product with its own license?
Reliability and queues
- What happens to a study when a destination is down: is it queued, for how long, and how does it recover when the destination returns?
- Are images ever deleted before they are delivered (drop rules, timeouts, retention limits), and is each deletion logged?
Downtime and reading
- If the PACS is unavailable, can staff still open recent studies and record preliminary reads, and how do those reads reach the RIS afterward?
Security
- Is DICOM TLS supported for sending and receiving? HL7 over TLS? HTTPS for the web console, and is it on by default?
- How do administrators sign in (local accounts, LDAP or Active Directory, SSO, MFA), and is there an audit trail of who viewed or changed what?
Management across sites
- Can one console show and change every site’s rules, exams and updates, and does each site need a VPN to reach it?
Deployment and OS
- Which operating systems, databases and virtualization platforms are supported, and is high availability or automatic failover available?
Documentation
- Is a current DICOM conformance statement public (and a DICOMweb one, if it applies)? Is the user manual public or by request?
Support and licensing
- What are the support hours, response targets and escalation path, and are they in a published document?
- How is it licensed (per server, per site, per study, subscription), and what costs extra: modules, high availability, more sites?
Side by side
RadFuzion, Laurel Bridge Compass and Dicom Systems Unifier
Each competitor cell paraphrases that vendor’s public documentation as of November 3, 2026. The RadFuzion column shows what RadFuzion does today, gaps included, and was updated on .
- Documented
- The vendor describes it on a public page we link to.
- Not publicly documented
- We did not find it on the pages checked. It may still exist; ask the vendor.
- Separate product
- The vendor documents it as a different product.
- Supported
- RadFuzion does this today.
- Limited
- RadFuzion does part of this; the note says which part.
- Not supported
- RadFuzion does not do this today.
| Criterion | RadFuzion | Laurel Bridge Compass | Dicom Systems Unifier |
|---|---|---|---|
| DICOM routing | RadFuzionSupported Receives DICOM (C-STORE) and forwards by C-STORE, DICOMweb STOW-RS, or to cloud and object storage. More: DICOM router | Laurel Bridge CompassDocumented Described as a DICOM router that automates the ingestion, distribution, tracking and access of imaging studies. Source: Compass page | Dicom Systems UnifierDocumented Described as a vendor-neutral, enterprise-grade DICOM router and imaging workflow engine. Source: Unifier solutions page |
| Rule-based routing | RadFuzionSupported Rules match any DICOM tag and the calling or called AE title, run in priority order, and can be limited to set days and hours. Rules can be tested on a real exam without sending it. No regular-expression operator. | Laurel Bridge CompassDocumented Configurable, priority-based routing rules; routes or multiplexes store jobs based on any DICOM tag. | Dicom Systems UnifierDocumented Metadata-driven routing with multi-destination rules and workflow customization using Lua scripting. Source: Unifier solutions page |
| HL7 processing | RadFuzionSupported HL7 v2 orders over MLLP, or MLLP over TLS, fill the worklist, start prior fetching and can release images held for their order (matched by accession). Results go out as HL7 ORU. From 6.8.5, ADT patient updates and merges, and order updates that change the patient, correct exams not yet sent. RadEngine7, a separate no-code HL7 v2 interface engine, comes with every license. More: HL7 and DICOM | Laurel Bridge CompassDocumented Can route, schedule and alter HL7 messages and tie events and actions to HL7; HL7 routing and automation is listed among its feature upgrades. Source: Compass page | Dicom Systems UnifierDocumented Bidirectional HL7 message exchange for patient updates, orders, results and status messages. Source: Unifier solutions page |
| FHIR | RadFuzionLimited RadSR, a separately licensed module, can post measurement results as FHIR R4 Observations to a REST endpoint. There is no FHIR server or FHIR API. More: RadSR | Laurel Bridge CompassNot publicly documented | Dicom Systems UnifierDocumented FHIR-based APIs; FireBridge translates between FHIR and HL7 or DICOM. Source: Unifier solutions page · FHIR page |
| DICOMweb | RadFuzionSupported Client and server. As a client: STOW-RS to send, QIDO-RS and WADO-RS to search and retrieve. As a server: other systems send with STOW-RS (routed like C-STORE) and search and retrieve, including metadata and frames, over the image cache, each with its own API key. No rendered or thumbnail resources. More: DICOM conformance | Laurel Bridge CompassDocumented Supports DIMSE and DICOMweb and converts between them. Its DICOMweb conformance statement covers STOW-RS, QIDO-RS and WADO-RS as both user agent and origin server. Source: Compass page · Compass DICOMweb conformance statement (PDF) | Dicom Systems UnifierDocumented Built on standards including DICOMweb; the AWS listing describes a DICOMweb-enabled RESTful API. |
| Cloud archive support | RadFuzionSupported Google Cloud Healthcare API DICOM stores, the Azure Health Data Services DICOM service, other DICOMweb stores, Amazon S3 and Google Cloud Storage buckets. Store results are checked per image, and corrected studies can be replaced in Google, Azure and DICOMweb stores. AWS HealthImaging is not supported. More: Google Cloud · Azure | Laurel Bridge CompassDocumented Compass Edge, a feature upgrade, links hospital and cloud archives; the product page also covers AWS HealthImaging support. Source: Compass page | Dicom Systems UnifierDocumented Deploys on cloud and hybrid infrastructure; Dicom Systems lists Unifier on the AWS, Google Cloud and Azure marketplaces. Source: Unifier solutions page · How to purchase page |
| Prior retrieval (prefetch) | RadFuzionSupported RadFetch, a separately licensed module, starts on an HL7 order, from the exam’s own DICOM, or on demand, and pulls from up to six sources: DICOM archives by C-FIND and C-MOVE, or Google, Azure and DICOMweb stores by QIDO-RS and WADO-RS. It skips priors already at the destination. It has no scheduled runs. More: RadFetch | Laurel Bridge CompassDocumented Trigger-based ad hoc and scheduled prefetching. Laurel Bridge’s prefetch solution combines Compass with Navigator and Waypoint. Source: Compass product description (PDF) · Prior fetching page | Dicom Systems UnifierDocumented Rule-based relevant priors; a fetch starts when a new order is assigned to a radiologist. Source: Relevant priors page |
| Modality worklist | RadFuzionSupported RadList, a separately licensed module, answers DICOM Modality Worklist (C-FIND) queries from HL7 orders and can limit each modality to its own entries. It takes MPPS from modalities and passes it on to the RIS. More: RadList | Laurel Bridge CompassSeparate product Laurel Bridge Waypoint, an encounter and modality worklist manager. Source: Waypoint page | Dicom Systems UnifierDocumented Unifier functions as a DICOM Modality Worklist server and HL7 broker. Source: Modality worklist page |
| Tag modification | RadFuzionSupported Rules set, add, remove and copy tags, or fill them from lookup tables, while studies are in flight. More: Tag Editor | Laurel Bridge CompassDocumented Tag morphing and filtering. | Dicom Systems UnifierDocumented Real-time DICOM and HL7 tag transformations. Source: Unifier solutions page |
| De-identification | RadFuzionLimited The DICOM PS3.15 Basic Profile with its date, patient, device, institution and UID options, plus tag rules, private tag removal, stable new UIDs and salted hashing. No pixel de-identification: text burned into images is not removed. More: Anonymization | Laurel Bridge CompassDocumented De-identification of metadata and pixel data (image overlays), with a public anonymization conformance statement. Source: Compass product description (PDF) · Anonymization conformance statement (PDF) | Dicom Systems UnifierDocumented Removes PHI from DICOM metadata and pixel data. Source: Unifier solutions page · De-identification page |
| Central management and monitoring | RadFuzionSupported RadHub is built in: one console for every site’s exams, stats, rules and updates. RadHub Connect links sites through a relay with no VPN. More: RadHub · RadHub Connect | Laurel Bridge CompassSeparate product Laurel Bridge Lighthouse, for centralized job management, monitoring and diagnosis. Source: Lighthouse page | Dicom Systems UnifierDocumented Unifier Command Center for centralized monitoring; Unifier Rapid+ lists SNMP and web-based management. Source: Unifier solutions page |
| High availability and failover | RadFuzionNot supported Runs as a single server. No clustering or automatic failover today. A full backup of settings and the built-in SQLite database can be restored on a replacement server; with PostgreSQL, the database is backed up separately. | Laurel Bridge CompassDocumented Supports high-availability configurations on a Windows Failover Cluster. Source: Compass technical specifications | Dicom Systems UnifierDocumented Active/passive clustering of two or more appliances behind a virtual IP. Source: High availability page |
| Downtime support | RadFuzionSupported An on-site image cache, optional query/retrieve over that cache, and RadRead (a separately licensed module) for preliminary reads. Studies for a down destination are held and sent when it returns, and RadRead and its viewer open them from the server while they wait. More: PACS downtime | Laurel Bridge CompassNot publicly documented The product description lists an intelligent, queryable cache; the pages checked do not describe its use during PACS downtime. | Dicom Systems UnifierDocumented Clinical Backup Viewer for browser access during PACS downtime, optionally paired with the Lifeboat backup archive. Source: Clinical Backup Viewer page |
| Local or preliminary reporting | RadFuzionSupported RadRead, a separately licensed module, records preliminary reads with templates and dictation, and sends them as HL7 ORU or by fax. Its viewer is non-diagnostic and not FDA cleared. More: RadRead | Laurel Bridge CompassNot publicly documented The pages checked describe Dictation Integration, which inserts modality measurements into report templates. Source: Compass page | Dicom Systems UnifierNot publicly documented The pages checked describe integration with Nuance PowerScribe One for reporting workflows. Source: Unifier solutions page |
| Deployment options | RadFuzionSupported Windows service; 64-bit Linux (systemd or Docker) on request. On a physical server or a virtual machine, on site or in the cloud. More: Platform | Laurel Bridge CompassDocumented Dedicated hardware or a virtual machine; Windows 10 or Windows Server 2016 or newer, with Microsoft SQL Server. Source: Compass technical specifications | Dicom Systems UnifierDocumented Physical, virtual, cloud and hybrid deployments, including VMware, Hyper-V, Xen and Nutanix. Source: Unifier solutions page |
| Transport encryption (DICOM and HL7) | RadFuzionSupported DICOM TLS on the receiver, Query/Retrieve and worklist ports and per destination, and HL7 over TLS on the order and ORU receivers and every HL7 sender, with optional client certificates. Off by default. Certificate revocation (CRL or OCSP) is not checked. Traffic between sites over RadHub Connect is encrypted end to end. More: DICOM conformance | Laurel Bridge CompassDocumented Its DICOM conformance statement describes the BCP195 TLS secure transport profile; the product description lists TLS 1.0 to 1.3. Source: Compass DICOM conformance statement (PDF) · Compass product description (PDF) | Dicom Systems UnifierDocumented Data transmission over TCP/IP, TLS and HTTPS; the AWS listing describes DICOM standard TLS. |
| Console sign-in and access control | RadFuzionLimited Local accounts with role-based permissions and a user access audit trail. HTTPS for the web console is available but off by default. No MFA, SSO or LDAP today. | Laurel Bridge CompassNot publicly documented The pages checked describe OAuth2 with TLS for DICOMweb exchange (Compass Exchange), not console sign-in. Source: Compass page | Dicom Systems UnifierDocumented LDAP, MFA and single sign-on integration. Source: Unifier solutions page |
| Public documentation (conformance statements) | RadFuzionLimited A DICOM conformance overview is published. A formal DICOM PS3.2 conformance statement is being prepared and is not yet available. More: DICOM conformance | Laurel Bridge CompassDocumented Public DICOM, DICOMweb and anonymization conformance statements, technical specifications and release notes. The user manual is by request. Source: Laurel Bridge product library · Compass DICOM conformance statement (PDF) | Dicom Systems UnifierNot publicly documented No Unifier conformance statement found on dcmsys.com. A public technical specifications page gives hardware and VMware or Hyper-V sizing; the resource center lists white papers, articles, case studies, webinars, FAQs, videos and a glossary. Source: Resource center · Technical specifications page |
| Support model | RadFuzionPublished Phone and email, 8 AM to 6 PM US Central on weekdays, with response targets by severity. Premium Support adds around-the-clock reporting for Severity 1. More: Support terms | Laurel Bridge CompassDocumented Phone, email and a web form. Its support plan overview gives a one-business-day response for production support during normal business hours, and per-incident Priority Support with 24x7 access at three response levels. Source: Laurel Bridge support page · Support plan overview (PDF) | Dicom Systems UnifierDocumented Phone and email support for sites under a current license; the AWS Marketplace listing describes support 24 hours a day, 7 days a week. Response targets not found on the pages checked. |
| Pricing transparency | RadFuzionNot published Pricing is quoted on request. More: Contact | Laurel Bridge CompassNot publicly documented Quotes are requested through sales. Source: Laurel Bridge support page | Dicom Systems UnifierNot publicly documented Priced on an annual license, quoted by sales. Dicom Systems says its marketplace listings offer bring-your-own-license or pay-as-you-go options; the AWS listing checked is bring-your-own-license. Source: How to purchase page · Dicom Systems FAQ · AWS Marketplace listing |
| Scale (vendor-reported) | RadFuzionNot published RadFuzion does not publish installation or volume figures. | Laurel Bridge CompassVendor-reported Laurel Bridge reports “thousands of installs in over 35 countries.” | Dicom Systems UnifierVendor-reported Dicom Systems reports “more than 3000 installations worldwide.” Source: dcmsys.com home page |
Laurel Bridge, Compass, Navigator, Waypoint, Lighthouse, Dicom Systems, Unifier, FireBridge, Lifeboat and other product and company names on this page are trademarks of their respective owners. RadFuzion is not affiliated with them. Competitor columns last checked ; RadFuzion column updated .
Honest fit
Where RadFuzion fits, and where it doesn’t
RadFuzion brings DICOM routing, HL7 order workflows, automated prior retrieval, cloud image management and on-site downtime reading into one platform, with RadHub to run several sites from one console. That suits some networks well and others less so.
RadFuzion is a good fit when
- You want DICOM routing, HL7 order workflows, prior retrieval, cloud destinations and on-site downtime reading on one server, adding modules as you need them.
- You send to Google Cloud, Azure or another DICOMweb store as well as to on-site PACS.
- You run several sites and want one console for all of them, without a site-to-site VPN.
- You also need a no-code HL7 v2 interface engine for everyday interfaces: RadEngine7 comes with every RadFuzion license.
- You want to test rule changes on real exams before they go live.
Another vendor may fit better when
- You need active/passive clustering or automatic failover.
- You need FHIR APIs or patient identity reconciliation across many systems (a master patient index).
- You need burned-in pixel de-identification.
- Console sign-in must use MFA, SSO or LDAP.
- You need AWS HealthImaging.
- Procurement requires many large-enterprise references before a pilot.
Alternatives
Alternatives to Laurel Bridge Compass and Dicom Systems Unifier
If you are replacing or benchmarking either product, the options fall into three groups. None is right for every network; the checklist above will help narrow them down.
Commercial DICOM routers and workflow platforms
Products such as Laurel Bridge Compass, Dicom Systems Unifier and RadFuzion. They differ in which HL7, cloud, prior-fetch, worklist, downtime and high-availability features are in the base product and which are separate products or add-ons, so compare them line by line with the checklist above.
Tools from cloud imaging providers
Cloud DICOM services publish their own ways to bring DIMSE traffic in. For example, Google’s Cloud Healthcare API supports C-STORE through an open-source adapter (Google Cloud documentation). These move images into that one cloud; rules, HL7, priors and downtime reading are left to other tools.
Open-source DICOM toolkits and servers
Orthanc (a lightweight DICOM server with a REST API and plugins), dcm4che (a Java DICOM toolkit, also behind the dcm4chee archive) and DCMTK (a C++ DICOM toolkit with command-line tools). Capable building blocks; your team takes on configuration, upgrades and security patching, and support comes from your team or a support contract.
FAQ
DICOM router comparison questions
What should I ask a DICOM router vendor?
Ask what a routing rule can match on and whether a rule can be tested on a real study before it goes live; which HL7 messages it accepts and how images are matched to orders; which cloud stores it sends to and how it signs in to each; what happens to studies when a destination is down and whether images are ever deleted before delivery; whether DICOM TLS, HTTPS and SSO or MFA are supported; how many sites one console can manage; which operating systems and high-availability options are supported; whether a current DICOM conformance statement is public; and which support hours and licensing terms are in writing.
Which DICOM routers support HL7?
RadFuzion, Laurel Bridge Compass and Dicom Systems Unifier all document HL7 message handling (for Compass, HL7 routing and automation is listed as a feature upgrade), according to each vendor’s documentation as of November 2026. What each does with HL7 differs, so ask which message types it accepts, such as ORM, ORU or ADT, and what each message changes. In RadFuzion, HL7 v2 orders fill the modality worklist, start prior fetching and can release images held for their order; ADT updates and merges correct exams not yet sent (from 6.8.5); and results go out as HL7 ORU messages. RadFuzion’s routing rules match DICOM tags and AE titles, not HL7 fields.
Which DICOM routers support cloud storage?
Supported cloud services differ from product to product. RadFuzion sends to Google Cloud Healthcare API DICOM stores, the Azure Health Data Services DICOM service, other DICOMweb stores, Amazon S3 and Google Cloud Storage buckets, and does not support AWS HealthImaging. Laurel Bridge documents AWS HealthImaging support for Compass and a Compass Edge upgrade that links to cloud archives. Dicom Systems documents cloud and hybrid deployment of Unifier and lists it on the AWS, Google Cloud and Azure marketplaces. Confirm the exact store and sign-in method with each vendor.
What are alternatives to Laurel Bridge Compass?
Alternatives to Laurel Bridge Compass fall into three groups: other commercial DICOM routers and imaging workflow platforms, such as Dicom Systems Unifier and RadFuzion; DICOM ingestion tools from cloud imaging providers, such as the open-source adapter Google documents for its Cloud Healthcare API; and open-source DICOM toolkits and servers such as Orthanc, dcm4che and DCMTK, which a team configures, patches and supports itself or through a support contract. Which fits depends on your HL7, cloud, prior-fetch, downtime, security and high-availability requirements.
What are alternatives to Dicom Systems Unifier?
Alternatives to Dicom Systems Unifier fall into three groups: other commercial DICOM routers and imaging workflow platforms, such as Laurel Bridge Compass and RadFuzion; DICOM ingestion tools from cloud imaging providers, such as the open-source adapter Google documents for its Cloud Healthcare API; and open-source DICOM toolkits and servers such as Orthanc, dcm4che and DCMTK, which a team configures, patches and supports itself or through a support contract. Which fits depends on your HL7, cloud, prior-fetch, worklist, downtime, security and high-availability requirements.
Does RadFuzion support DICOM TLS?
Yes. The DICOM receiver, Query/Retrieve and Modality Worklist can each open a TLS port beside the plain one (2762 for the receiver), with optional client certificates, and each DICOM destination and Q/R source has a TLS switch that checks the server by system trust or a pinned certificate. HL7 can run over TLS on the order and ORU receivers and every HL7 sender. TLS is off by default, and certificate revocation (CRL or OCSP) is not checked. The web console supports HTTPS, and traffic between sites over RadHub Connect is encrypted end to end.
Does RadFuzion offer high availability or failover?
Not today. RadFuzion runs as a single server and does not offer clustering or automatic failover. It holds studies for a destination that is down and sends them when the destination returns, and a full backup of its settings and built-in SQLite database can be restored on a replacement server; with PostgreSQL, the database is backed up separately. If active/passive failover is a requirement, compare vendors that document it; Laurel Bridge and Dicom Systems both publish high-availability configurations.
How was this DICOM router comparison put together?
The Laurel Bridge Compass and Dicom Systems Unifier columns paraphrase each vendor’s own public web pages and documents, checked on November 3, 2026, with a link to each source. RadFuzion has not tested those products. “Not publicly documented” means a capability was not found on the pages checked, not that the product lacks it. The RadFuzion column is written from RadFuzion’s own product, including what it does not support, and was last updated on November 4, 2026. Corrections are welcome through radfuzion.com/contact.
Sources
Vendor documentation we checked
Every page below was opened on . Statements on this page are paraphrases; the vendor’s own wording is the authority.
- Laurel Bridge: Compass Routing Workflow Manager product page
- Laurel Bridge: Compass product description (PDF)
- Laurel Bridge: Compass technical specifications
- Laurel Bridge: product library (specifications, conformance statements, release notes)
- Laurel Bridge: Compass DICOM conformance statement, v3.12.0 (PDF)
- Laurel Bridge: Compass DICOMweb conformance statement, v3.12.0 (PDF)
- Laurel Bridge: DICOM anonymization conformance statement (PDF)
- Laurel Bridge: DICOM prior fetching solution
- Laurel Bridge: Lighthouse centralized monitoring and management
- Laurel Bridge: Waypoint encounter and modality worklist manager
- Laurel Bridge: support
- Laurel Bridge: software maintenance and support plan overview (PDF)
- Dicom Systems: home page
- Dicom Systems: solutions (Unifier platform)
- Dicom Systems: relevant priors
- Dicom Systems: DICOM modality worklist
- Dicom Systems: Clinical Backup Viewer
- Dicom Systems: FHIR (FireBridge)
- Dicom Systems: de-identification
- Dicom Systems: high availability for enterprise imaging workflows
- Dicom Systems: resource center
- Dicom Systems: technical support
- Dicom Systems: purchase software and services
- Dicom Systems: frequently asked questions
- Dicom Systems: technical specifications
- AWS Marketplace: Unifier Medical Image Workflow Cloud Appliance and Archive (BYOL), seller Dicom Systems, Inc.
- Google Cloud: Cloud Healthcare API DICOM concepts
Laurel Bridge, Compass, Navigator, Waypoint, Lighthouse, Dicom Systems, Unifier, FireBridge, Lifeboat and other product and company names on this page are trademarks of their respective owners. RadFuzion is not affiliated with them. Found an error? Send a correction.
Put RadFuzion through the checklist
Open the live preview to see cloud destinations, HL7 orders and the worklist on sample data, or ask us for the answers in writing.