XyDromatics™ SR Engine — structured reports, specialized.

Two reasons. First: footprint -- many customers (single-purpose dose-tracking deployments, CAD-finding distributors, AI-finding aggregators) need only the SR-specific slice of router-pattern capabilities. Deploying the full Router for them is overkill on cost and on operational surface. Second: specialization -- SR Engine is template-aware in ways that the general Router is not. Treating an RDSR or a Mammography CAD SR as opaque DICOM works, but losing the template awareness loses cross-vendor normalization quality and dose-tracking conformance. SR Engine optimizes for the SR workflow specifically.

Yes -- common pattern. Router handles general DICOM routing; SR Engine handles the SR slice with specialized transformation. Router can forward SR objects to SR Engine for specialized handling, then SR Engine fans out to dose-tracking, CAD, reporting, etc. A customer running both gets the platform consistency benefit (shared admin shell, shared audit, shared site encryption key for the keyed-hash pseudonymization).

Often no. SR Engine routes the RDSR; what destination satisfies your requirements depends on what your institution has. Three common shapes: (a) Epic Radiant institutions: Epic's Radiology module has integrated dose tracking, ACR DIR submission, automatic RDSR capture, and XR-29 / XR-25 Dose Check alerts. SR Engine forwards RDSR to Epic Radiant and Epic handles ACR compliance + abnormality alerting -- no separate dose-tracking platform required. (b) Non-Epic-Radiant institutions wanting full dose-abnormality monitoring + longitudinal tracking + QI reports -- you need a dose-tracking platform (Bayer Radimetrics, Sectra DoseTrack, Siemens teamplay), and SR Engine forwards to it. (c) Institutions whose only requirement is ACR Dose Index Registry submission -- SR Engine submits encrypted to the registry directly, no separate platform required. SR Engine's value is the routing flexibility; the analytical / monitoring features themselves live in Epic Radiant or in dedicated dose-tracking platforms, not in SR Engine.

Yes. For consumers that want HL7 ORU rather than DICOM SR (common for EMR-side integration), SR Engine transforms the SR content into HL7 ORU and emits HL7 messages. Same for PowerScribe -- SR Engine pushes report tokens to a reporting platform over REST JSON or SOAP XML. The producer does not have to know or care which destination expects which format; SR Engine handles the per-destination shape.

Yes. Voice-recognition / dictation platforms take SR content as template inputs to populate the radiologist's draft report. This includes the established platforms (Microsoft Nuance PowerScribe, Jacobian M*Modal Fluency for Imaging) and the rapidly-expanding field of AI-driven dictation systems (DAX Copilot, Abridge, Nabla, Suki, Heidi, and a steady stream of new entrants). SR Engine routes to whichever platform(s) the institution uses, alongside the other consumer destinations. A single RDSR or measurement SR can land in the dictation platform (template input) AND the dose-tracking platform (compliance) AND the PACS (image-context retrieval) simultaneously. The dictation-platform landscape is moving fast; SR Engine's job is to keep routing to whatever the institution picks without constraining the choice.

SR Engine is a routing and format-translation engine. It does NOT track dose abnormalities, does NOT do longitudinal dose tracking per patient, does NOT generate QI / radiation-safety reports, does NOT do clinical decision support on SR content. Those are the analytical / monitoring features that dose-tracking platforms (Bayer Radimetrics, Sectra DoseTrack, Siemens teamplay) or EMR-native dose-tracking (Epic) provide. SR Engine's job is making sure the right SR content gets to the right destination in the right format.

Template-version migration is a core capability. Older modality firmware emits older versions of TID 1500, TID 5200, and other templates; current consumers expect newer versions. SR Engine recognizes the source template version and migrates forward to the consumer-expected version, preserving the measurement / finding semantics. The transformation is audit-trailed.

No -- SR Engine is an ingest / transform / forward engine, not an SR-creation tool. If your reporting platform produces free-text reports rather than SR, the place to address that is the reporting platform itself or the integration layer between reporting and PACS. SR Engine handles the routing and transformation of SR objects that already exist somewhere in the workflow.

Same family-wide mechanism as the Router and the archive siblings. SR Engine uses keyed-hash pseudonymization on the way out (to the AI vendor). The re-identification envelope travels inside the exported object; SR Engine itself performs only the one-way outbound leg, and identity is restored by the product that receives on the way back. AI vendor sees only anon-IDs; findings get linked to the right patient. A multi-product customer's site encryption key is shared, so anon-IDs from SR Engine are consistent with anon-IDs from the Router or XyDromatics Migration in the same deployment.

Non-device software under FD&C Act §520(o)(1)(D), the 21st Century Cures Act §3060 carve-out for software that transfers, stores, converts, or displays device data without interpreting or analyzing it. Same framework as Router, XyDromatics Repository, and XyDromatics Migration -- SR Engine handles storage and forwarding of SR objects without modifying clinical interpretation. Tag transformations are constrained to non-interpretive scope (template migration, anonymization, normalization).

Yes -- Windows and Linux, same as the rest of the router-pattern family. MSI installer for Windows, self-contained Linux tarball for Linux. Both supported equally.