Image Orchestration · capability matrix

One capability set, purpose-built products.

The day-to-day imaging fleet, delivered across focused applications rather than one overloaded router — every mark below verified against our own source code, not a datasheet. The goal is more, but not less: meet the competitive baseline and add the depth a single-product tier ladder can’t show — marked ★.

8 products 48 capabilities Code-verified 2026-10-02 Non-device · §520(o)(1)(D)
Full — implemented & code-verified Partial — one-directional or limited scope Not present — by design or absent Fleet baseline — depth a tier ladder doesn’t list

How the tiers map to a single-product ladder

Where the incumbent approach sells one product in five ascending tiers, we ship purpose-built applications — so a capability the routers don’t carry appears in its dedicated product’s column instead of a greyed-out tier. The four ★ rows — encryption at rest, enterprise auth, a hash-chained HIPAA audit trail, and configuration backup & DR — are baseline across our whole fleet, on every product regardless of tier.

De-identification reads as two rows rather than one because they are two different jobs. Every router can pseudonymize on export — reversibly, under your own key, so a downstream system holding that key can restore the identifiers. Irreversible de-identification is the one-way job: a HIPAA Safe Harbor tag policy, burned-in pixels found by OCR and redacted, dates shifted while the intervals between them survive, free text and SR narratives scrubbed, and a fail-closed gate that quarantines anything it cannot clean rather than forwarding it half-cleaned. Two products do it, from the same shared implementation. The XyDromatics Router applies it per destination, so one archive can receive identified images while another receives de-identified ones from the same study. The XyDromatics De-Identification Engine is that job as a dedicated inline stage — put it in front of any router, including the tiers that do not carry it, when de-identified output has to fan out.

Streaming tier Essential Router
Store-and-forward tier Core Router
Full / professional tier XyDromatics Router
Enterprise / edge tier Core Router + XyDromatics Router
Image-exchange tier SynthCloudConnect
— no equivalent tier — De-Identification Engine · Encounter Engine · Core MWL · SR Engine
Image Orchestration capability matrix — 8 products across 48 capabilities, each mark verified against product source code on 2026-10-02.
Capability Essential Router Streaming Core Router Store & forward Core MWL Worklist XyDromatics Router Full platform De-Identification Engine De-identification SR Engine Reporting Encounter Engine Order workflow SynthCloudConnect Cross-site relay
Core routing & transformation
DICOM DIMSE image routing C-STORE SCP / SCU ● ● — ● ● ◐ 1 ● —
Configurable inbound listener types one service per listener · DICOM · passthrough proxy · MWL · Q/R · HL7 · SR — — ◐ 32 ● — — — —
Configurable, priority-based routing rules ● ● — ● — ● — —
Rule-based scheduling of routing time-of-day / day-of-week windows decide when a rule applies — ● — ● — — — —
Tag-morphing & filtering — 2 ● — ● ◐ 16 — ● —
Order reconciliation study tags ↔ authoritative order (local orders or an external Modality Worklist — no HL7 needed) · identity/laterality flagged — ● 15 — ● — — — —
Pseudonymization on export reversible · customer-keyed · restorable downstream — ● — ● ● ● ● —
Irreversible de-identification HIPAA Safe Harbor tag policy · burned-in-pixel redaction · date shifting · free-text scrub — — — ● ● — — —
Compression / transfer-syntax conversion — ● — ● — — — —
Non-DICOM encapsulation capture a photograph or upload a JPEG / PDF / TIFF → DICOM — — — ● — — ● —
Patient lookup at the point of capture confirm bedside identity against the patient registry over IHE PDQm · any conformant registry or MPI — — — ● 28 — — ● 28 —
Multiplex routing to archives / VNAs cloud + on-prem ● ● — ● ◐ 18 ● ● —
Operational depth
Store-and-forward durability durable spool · retry · dead-letter — ● — ● ● ● ● ◐ 4
Streaming (non-buffered) dispatch listener → source node → routing rule → destination, with nothing spooled ● — 30 — ● 31 — — — —
Load-aware routing & destination failover — ● — ● — ● ◐ 5 —
Load-balanced destination pools study-affinity sending · per-member health & failover — ● — ● — — — —
Hold queue / manual-review gate — ● — ● ● 20 — ● —
IHE IOCM duplicate & correction reconciliation query the destination before sending · re-send when a correction supersedes the archived copy — — — ● 19 — — — —
Queryable study cache local C-FIND / C-MOVE + QIDO / WADO — ● 6 — ● — — — —
Passive device / modality inventory auto-harvested equipment identity · reachability — — — ● 14 — — — —
Orders & worklist
HL7 messaging (ingest / route) ORM · ORU · ADT — — ● ● ◐ 21 ● 7 ● —
Provide Modality Worklist (MWL C-FIND SCP) serve worklist from HL7 orders — — ● ● — — — —
MWL query proxy / relay to upstream RIS proxy · merge with local worklist — — ● ● — — — —
Federated Modality Worklist one C-FIND fanned to many worklist providers · de-duplicated merge · per-member health — — ● ● — — — —
MPPS — Modality Performed Procedure Step N-CREATE / N-SET SCP · start, complete & discontinue tracked per step ● 29 ● 29 — ● 29 — — — —
Order generation from inbound exams e.g. POCUS — — — ● — — ● —
Security, exchange & compliance
Mutual TLS — inbound associations peer client certificate validated against the customer’s own CA · fail-closed ● ● ● ● ● ● ● ● 25
Mutual TLS — outbound associations client certificate presented to the receiving peer ● 26 ◐ ◐ 27 ◐ ◐ — 1 ◐ — 11
★ Encryption at rest customer-keyed key-escrow ● ● ● ● ● ● ● ●
★ Enterprise auth (LDAP + RBAC / custom roles) ● ● ● ● ● ● ● ◐ 9
★ HIPAA audit trail hash-chained · 6-yr retention ● ● ● ● ● ● ● ●
DICOM ↔ DICOMweb (STOW / QIDO / WADO) — ● 13 — ● ◐ 22 ◐ 10 — ● 11
Cross-site / cloud image exchange outbound-initiated — — — ● — — — ●
AI workflow & cloud result delivery — — — ● — — — —
Reporting, analytics & support
Report rendering / file conversion SR · encapsulated PDF → PDF — — — ◐ 12 — — — —
Outbound report fax delivery render SR / encapsulated PDF / HL7 ORU → PDF → fax · recipient allow-list · review gate — — — ● 23 — — — —
DICOM SR & dictation / report integration — — — ● ◐ 24 ● — —
Dose-monitoring integration — — — ● — ● — —
Analytics integration (SynthInSight) — ● ● ● ● ● ● —
Query/Retrieve prefetch (pull priors) C-FIND / C-MOVE — — — ● — — — —
Federated prefetch across prior archives one rule searches many archives · retrieve returns to the archive that answered — — — ● — — — —
Configurable prefetch priority drain rank by modality, patient class, location, procedure & HL7 order priority — — — ● — — — —
★ Configuration backup & DR sealed config-sync hub ● ● ● ● ● ● ● ●
Remote support & telemetry via SynthGateway ● ● ● ● ● ● ● ●
Fleet console management via SynthConstellation ● ● ● ● ● ● ● ●
Deployment & platform
Windows Server (MSI installer) ● ● ● ● ● ● ● ●
Linux (self-installing tarball + systemd) ● ● ● ● ● ● ● ●
Virtual appliance (OVA / VHDX / VMDK) turnkey VM image ● ● ● ● ● ● ● ●

● code-verified full · ◐ partial · — not present · ★ fleet baseline · marks from source, not marketing.

Above the grid

The fleet-operations layer.

Two products sit above the router matrix — the load-balancing and fleet-console layers the incumbents sell as separate SKUs, answered head-on. Neither is a peer to a router: SynthIQ fronts any DICOM backend; SynthConstellation runs the whole XyDromatics fleet from one board.

SynthIQ High availability & business continuity — for any DICOM fleet, not just ours Patent Pending · 2 US applications

Competitors fold load balancing into their router tiers. We ship it as a distinct, vendor-neutral product — SynthIQ is our high-availability & business-continuity layer in front of any DICOM-conformant backend: a heterogeneous, multi-vendor pool of our routers and third-party PACS, VNAs, and cloud endpoints — not one vendor’s boxes. It balances two lanes — DICOM image traffic (C-STORE, on persistent Study-Instance-UID affinity so every study stays on one backend across associations, follow-ups days later, and restarts) and Modality Worklist queries (MWL C-FIND, health-aware) — and its three-tier waterfall (affinity → least-busy → fallback) keeps imaging flowing when a backend goes down. That’s why it isn’t a column in the matrix: it’s the layer above the grid.

Provides
High availability + business continuity
Balances
DICOM (C-STORE) + Modality Worklist (MWL C-FIND)
Backends
Any DICOM router — heterogeneous, multi-vendor
Health
JSON API for integrators; SynthPulse black-box probing for backends that can’t / won’t
Deploys
Windows · Linux · OVA/VHDX/VMDK
SynthConstellation One console for the whole fleet

The incumbent sells fleet monitoring as a separate SKU. We ship SynthConstellation — a single pane of glass that pulls every product’s health, queues, and config-sync posture into one board: routers, engines, archives — the whole fleet, not just the routers. Open any product’s own console right from it with single sign-on, and run the fleet from one place instead of logging into each. It also hosts the customer-controlled Config Backup Hub: every enrolled product seals its configuration on a schedule, so a lost or replaced host reseeds its exact config for disaster recovery. It moves no images, but its fleet queues surface the patient identifiers your products report — so it is PHI-bearing (sealed, hash-chained audit trail, encrypted at rest; a HIPAA Business Associate under your BAA). Non-device software.

See
Health · queue depth · config posture — every product in the fleet
Reach
Open any product’s console via single sign-on
Recover
Config Backup Hub — sealed config → reseed for DR
Scope
Whole fleet, not just routers · no images · PHI-bearing (fleet queues show patient identifiers; sealed at rest; BAA)

Evidence & scope

  1. 1SR Engine receives via DIMSE C-STORE SCP (+ C-ECHO) but forwards over STOW-RS — no C-STORE SCU.
  2. 2Essential Router does object filtering (drop rules, per-source allowed-modalities) but no tag morphing / coercion — streaming by design.
  3. 4SynthCloudConnect holds studies in a transit spool with a TTL (bridge relay), not a durable archive.
  4. 5Encounter Engine emits a load-aware health score for the SynthIQ pool, but has no internal destination failover.
  5. 6Core Router: a bounded, transient, sealed local Query/Retrieve cache of recently-received studies — DIMSE C-FIND / C-MOVE plus QIDO-RS / WADO-RS — so a site with no archive can run Query/Retrieve without a VNA. A cache, not an archive: TTL / size eviction is a hard delete.
  6. 7SR Engine routes HL7 ORU^R01 over MLLP; it does not serve a Modality Worklist.
  7. 9SynthCloudConnect authenticates via identity-provider / OTP access (Cloudflare Access), not LDAP; RBAC and custom roles still apply.
  8. 10Outbound STOW-RS delivery only (a DICOMweb destination) — not a full bidirectional STOW / QIDO / WADO proxy.
  9. 11SynthCloudConnect exposes full STOW-RS / QIDO-RS / WADO-RS over the bridge, but no DIMSE C-STORE.
  10. 12The flagship renders / extracts DICOM SR & encapsulated-PDF report objects to PDF. It does not author SR objects; it does author encapsulated documents, via the Encapsulation page (see Non-DICOM encapsulation above).
  11. 13Core Router serves QIDO-RS + WADO-RS (read) from its bounded transient study cache, delivers outbound STOW-RS to DICOMweb destinations, and accepts inbound STOW-RS ingest — a token / mutual-TLS machine door that feeds each pushed instance into the same routing pipeline as a C-STORE.
  12. 14The flagship passively inventories every device that connects — PHI-free equipment identity (manufacturer, model, station, modality) plus on-demand C-ECHO reachability — license-gated. Essential Router, Core Router and Core MWL sites get the same capability from the standalone XyDromatics Device Registry product.
  13. 15Core Router has no local HL7 order store, so it reconciles a received study’s tags against an external provider’s Modality Worklist — fetched by an initiating C-FIND — with no HL7 ingest. The flagship reconciles against its own HL7 order store and can additionally fall back to an external worklist for accessions the local store does not have.
  14. 16The De-Identification Engine rewrites tags under a fixed HIPAA Safe Harbor policy (plus private-tag handling and interval-preserving date shifting) rather than operator-authored coercion rules — a de-identification policy, not a general tag-morphing engine.
  15. 18The De-Identification Engine forwards to one downstream archive — it is an inline de-identification stage, not a multiplexing router. Put it in front of a router when de-identified output needs fanning out.
  16. 19The flagship queries each destination before sending (IHE IOCM) to skip objects the archive already holds, and re-sends when the archived copy carries demographics a later correction superseded. Fail-safe by design: any unanswered or refused query resolves to send. Configurable per destination, including a separate query port and AE title.
  17. 20The De-Identification Engine’s gate is fail-closed: an object whose PHI it cannot clean — an encapsulated-document blob, an SR free-text narrative, or a burned-in-pixel risk — is quarantined for operator review rather than forwarded partially cleaned. Per-category action is configurable (quarantine · forward · reject).
  18. 21The De-Identification Engine ingests HL7 v2 ORU results over MLLP, de-identifies them under the same per-patient pseudonym and date shift as the DICOM path, and forwards them downstream. No ORM or ADT ingest, and it serves no worklist.
  19. 22The De-Identification Engine accepts inbound STOW-RS (fail-closed mTLS by default) and acts as a QIDO-RS / WADO-RS client when re-harvesting report objects from an archive; it does not serve QIDO-RS / WADO-RS.
  20. 23The flagship renders a finalized report — DICOM SR, DICOM-encapsulated PDF, or HL7 v2 ORU — to PDF and transmits it through a configured, operator-selectable cloud fax provider. Automatic delivery is anchored to a recipient allow-list, with a review queue for anything unresolved, plus delivery tracking and reconciliation. A licensed add-on.
  21. 24The De-Identification Engine parses DICOM SR to de-identify its narrative and to harvest coded facts under a versioned NLP term pack; it neither authors SR objects nor integrates with a dictation system.
  22. 25SynthCloudConnect’s mutual-TLS door is its DICOMweb and relay endpoints over HTTPS / WSS, optionally behind identity-provider access control. It binds no DIMSE listener, so there is no DICOM association to authenticate.
  23. 26Essential Router ENFORCES its outbound client certificate: configuring one is itself the requirement, so a certificate that cannot be loaded refuses the association rather than connecting without the identity the operator configured. The other products present a configured certificate but cannot yet be told to require it per destination — that enforcement, and a posture report naming which identity is actually on the wire, is on the roadmap.
  24. 27Core MWL’s outbound DICOM leg is its worklist query — the upstream provider and every federated worklist member — not an image destination. It presents a configured client certificate on that leg and can validate the provider against a named CA bundle instead of the host’s machine-wide trust store, and its federation posture reports whether each is configured (presence only, never a path). The identity belongs to the listener and is used for all of its members: one host, one identity, one place to configure it.
  25. 28Identity is confirmed against a patient registry over IHE PDQm, so any conformant registry or master patient index will serve — a site’s existing MPI included. Both products use the same lookup at the point of capture, enabled by giving them the registry’s address. Encounter Engine additionally escalates on its verification screen, where an identity is resolved from its own ADT cache first, then the registry, then an initiating C-FIND, so a patient the registry has never heard of is still resolved and the same confirmed identity is carried into both the image header and the order it requests. XyDromatics CohortaNexus is one such registry, offered as a separate product; its availability is announced separately.
  26. 29All three routers accept MPPS N-CREATE / N-SET from a modality, hold the performed-step record and answer each transition explicitly — an unknown instance, a terminal-state transition and a duplicate create each return a distinct DICOM status rather than a blanket success. They do not relay the step on to an upstream MPPS SCP; proxied pass-through is on the roadmap.
  27. 30Core Router accepts a per-source send_mode - the field is on the shared source type it uses - but nothing in its dispatch path reads it, so any value other than store-and-forward is inert. Marked as none rather than full on the same rule as the IOCM row: an accepted-but-ignored knob is not a capability.
  28. 31XyDromatics Router offers two streaming modes, and they differ in who holds custody. In stream, the acknowledgement to the modality means the instance is on the router spool, and delivery to each destination then proceeds without waiting. In stream_only nothing is spooled at all and the acknowledgement comes only once every targeted destination has taken the instance, so custody stays with the sending modality, which retains and resends.
  29. 32Core MWL has two listener types: an HL7 v2 MLLP order-ingest listener, and a DICOM Modality Worklist C-FIND SCP that serves the stored orders.

Reading the marks

● Full means implemented and verified in the shipping source — not a label on a spec sheet. ◐ Partial flags a real but one-directional or limited implementation, footnoted so you know exactly where the edge is. — means the capability lives in a different product on purpose, so you buy the tool that does it well.

Transport security is TLS + mutual-TLS with cert pinning — there is no OAuth2 / OIDC anywhere in the fleet, so we lead with mTLS rather than claim an OAuth2 checkbox we don’t implement.

Where a capability is only partial on a tier, we mark it ◐ and footnote exactly what is and isn’t there rather than claim a full checkbox. Every ● is verified against our own source code — if a mark isn’t solid, we say so.

More, but not less.

Match the competitive baseline, then add the depth a single-product tier ladder can’t show — durable store-and-forward, per-destination transforms, vendor-neutral high availability, and a single console for the whole fleet. Every capability on this page traces to shipping source code.