Tier 1 · Implementation

Deploy any imaging system — including ours.

Our flagship service line. Twenty years of deploying clinical imaging infrastructure at hospitals, imaging centers, and academic medical centers means we can move you off any legacy system, stand up new ones, and integrate them into the surrounding EMR / reporting / CVIS landscape. Vendor-agnostic by design — XyDromatics is one option, not the only one.

Discuss an engagement See the timeline
Vendor experience · Engagement timeline · Case studies · Team · FAQ

Vendor experience

The stacks we’ve actually deployed.

Twenty years of cross-vendor implementation work, organized by where the vendor sits in the imaging stack. If you don’t see a vendor here, ask — this is the published list, not the full list.

Every vendor product listed below is a system Synthology principals have implemented, supported, or migrated from — not a vendor-research summary. The product-name precision (and the predecessor lineages where applicable) reflects direct delivery experience, not market-research desk work.

PACS / VNA / RIS

Source-side migrations, target-side stand-ups, parallel-run cutovers. Per-study verification on every move.

  • Siemens Healthineers syngo.plaza, syngo Imaging, predecessor PACS (Cosmos, Magic)
  • Philips IntelliSpace PACS (originally Stentor), Vue PACS (formerly Carestream / Kodak DirectView)
  • Merative (Merge) Merge PACS (formerly Cedara / AMICAS lineage)
  • Optum (Change) Cardiology, Radiology, McKesson Imaging legacy
  • Fujifilm Synapse PACS, Synapse VNA
  • GE Healthcare Centricity PACS, predecessor GE PACS
  • Agfa HealthCare Enterprise Imaging
  • Hyland Acuo VNA, NilRead

EMR / EHR

Imaging-side integration with the EMR — orders, results, context launching, in-context viewing.

  • Epic Radiant (radiology) + Cupid (cardiology)
  • Cerner PowerChart imaging integration

Reporting

Voice-driven structured reporting integration. Outbound report distribution. Speech recognition tuning.

  • Microsoft (Nuance) PowerScribe, Dragon Medical
  • Jacobian (M*Modal) Fluency for Imaging

CVIS

Cardiovascular information system deployments — cardiology workflows are their own beast and we treat them as such.

  • Siemens syngo Dynamics
  • Agfa Enterprise Imaging Cardiology
  • GE MUSE, CardioLab
  • Merative (Merge) Merge Cardio
  • Baxter (Epiphany) Epiphany Cardio

Third-party imaging applications

Specialty viewers, AI applications, image-sharing platforms, advanced visualization. The applications that orbit the core archive.

  • Philips DynaCAD
  • Siemens Syngo.via, syngo Dynamics
  • Materialise Mimics
  • Hyland PowerShare
  • Microsoft Modlink
  • GE HealthCare (Intelerad) InteleShare, IntelePACS
  • Aidoc AI triage suite
  • Riverain ClearRead CT, ClearRead Bone Suppress

Workflow orchestration

Routing, prefetch, hold-and-release, transformation. XyDromatics Router is one option in this space; we also implement third-party platforms.

  • XyDromatics Router (our own)
  • Laurel Bridge Compass, Navigator
  • DicomSys DicomSystems UVR

Engagement timeline

A 16-to-20-week shape, in five stages.

Real engagements vary from 8-week single-site builds to 18-month enterprise rollouts; this is the shape, not a fixed schedule. Every stage has a written gate before the next one starts.

  1. Stage 1

    Discovery

    Week 1–2

    On-site or remote sessions with imaging IT, clinical leads, and integration owners. We map the as-is environment, surface the constraints, and translate the stated goal into a written scope.

    Outputs

    • As-is architecture diagram
    • Workflow map (current state)
    • Risk register
    • Refined SOW (you can stop here if scope changed)

  2. Stage 2

    Design

    Week 3–6

    Target architecture, integration spec, test plan, cutover plan, rollback plan. Design reviews with your team and our engineers; gate to execution requires written sign-off.

    Outputs

    • Target-state architecture document
    • Integration spec (DICOM AE list, HL7 / FHIR mappings, ports)
    • Test plan with synthetic studies
    • Cutover playbook with go/no-go gates
    • Rollback plan

  3. Stage 3

    Build

    Week 6–14

    Stand up the test environment, exercise the cutover playbook in the lab, walk modalities and EMR integrations through staged config changes. UAT happens before production cutover, not during.

    Outputs

    • Test environment operating with synthetic studies
    • Lab-validated cutover rehearsal
    • UAT sign-off from clinical leads

  4. Stage 4

    Cutover

    Week 14–16

    Production go-live with on-site Synthology presence. Cutover gates documented. Daily standups for the first week. Roll forward or roll back is a written decision, not a hallway conversation.

    Outputs

    • Production cutover executed
    • Hypercare daily standups (first 7 days)
    • Defect-tracker tied to the cutover playbook

  5. Stage 5

    Stabilize

    Week 16–20

    30 days of post-go-live stabilization. Knowledge transfer to your operations team. Clinical user training. Closeout document signed by both sides marks the end of our involvement (or, for Managed Services customers, the transition to ongoing ops).

    Outputs

    • User training (clinical + technical, separate tracks)
    • Operations runbook tailored to your team
    • Closeout document signed by both sides

Case-study profiles

Anonymized engagement shapes.

Aggregated profiles from real engagements with identifying details stripped. Named references available under NDA on request.

Multi-hospital VNA replacement

Scope
6-hospital health system, ~28 PB legacy archive, replacing GE Centricity with XyDromatics VNA Repository + Router. Parallel archive operation during the cutover window.
Duration
14 months end-to-end
Outcome
Cutover completed with zero clinical-workflow downtime. 100% of legacy studies migrated and verified. Annual archive cost reduced by ~40% post-cutover.

Long-tail PACS migration

Scope
18 years of Merge PACS data into a target VNA. Source PACS had three generations of tag conventions, two character-set incidents, and a long tail of malformed studies.
Duration
9 months
Outcome
Per-study verification on every migrated study. ~3,200 studies flagged for clinical review (mostly pre-DICOM-spec edge cases); each individually adjudicated rather than silently dropped.

Greenfield ambulatory imaging center

Scope
New ambulatory site, no legacy. Full stack: Epic Radiant + XyDromatics Router + VNA Repository + speech-driven reporting. 4 modalities, 2 reading rooms.
Duration
6 months from kickoff to opening day
Outcome
Site opened on schedule with all integrations operational. Hypercare phase concluded in 21 days vs. the planned 30.

Cardiology workflow integration

Scope
Existing Epic Cupid environment + new Siemens CVIS + structured reporting. Closing the loop from echo / cath lab through to finalized report in EMR context.
Duration
8 months
Outcome
End-to-end report turnaround time reduced from 4.2 to 1.6 days. Structured-reporting adoption reached 87% of cardiology reads within 60 days of go-live.

Named references — including direct conversations with prior clinical and IT leadership — are available under mutual NDA. We prefer phone references over written ones; the questions you actually want to ask aren’t the ones we’d put in a case study.

Team composition

Engineer-led, lead engineer named.

One named lead engineer owns your engagement from kickoff through closeout. Not rotated, not handed off mid-project. Other roles are pulled in as needed for the work in front of us.

Lead implementation engineer

One named engineer owns the engagement end-to-end. Same person in discovery, design, cutover, and closeout. Not rotated.

Integration engineer

DICOM / HL7 / FHIR integration work. Modality interface config, EMR routing, transformation rules.

Project manager

Schedule, risk register, stakeholder communication. Coordinates with your project manager — does not replace them.

Clinical training lead

On-site for clinical training during stabilization. Builds a curriculum around your actual workflow rather than running a generic PowerPoint.

Subject-matter specialists (as needed)

Pulled from the Synthology bench or the IES-Advisors partner roster for specialty work — pathology, AI integration, cardiology CVIS, advanced visualization.

Frequently asked

The questions prospects actually ask.

The discovery-meeting questions, answered ahead of time so the first call can spend its 30 minutes on your situation rather than on these.

Do we have to use XyDromatics products?

No. Implementation Services is vendor-agnostic. About a third of our implementation work involves no XyDromatics products at all — we deploy your selected stack, whether that's Siemens, Philips, GE, Fujifilm, Epic, or others. The product family is one option among many; our delivery model is the same either way.

How do you handle data integrity during a migration?

Per-study verification on every move: source SOP Instance UID + pixel-data checksum is captured at extract, re-verified at insert into the target. Any mismatch routes to a quarantine queue for clinical adjudication rather than silent drop. Verification reports are part of the closeout package.

What does "on-site presence" mean during cutover?

A named Synthology engineer is physically on site at your primary data center / imaging center for the cutover window — typically 48–72 hours covering pre-cutover staging, the cutover itself, and the immediate post-cutover validation. Hypercare continues remote for the following 7 days.

Can you work alongside our internal IT team rather than replacing them?

Yes — most engagements work this way. Your team owns the environment; we bring imaging-IT depth your team doesn't maintain in-house, and we transfer enough knowledge during the engagement that you can run it after we leave (unless you transition into Managed Services).

What's your relationship with the vendors you implement?

Independent. Synthology has no kickback or referral-fee arrangements with any imaging vendor we implement. IES-Advisors (a related entity under common control) has channel relationships with workflow-orchestration vendors (Laurel Bridge, DicomSys, DataFirst); these are disclosed in writing at the start of any engagement where they're relevant. See /about for the full disclosure.

How is pricing structured?

Fixed-fee SOW per scoped engagement. Discovery is billed separately so you can stop after discovery if scope changes shape — a common outcome and not a contractual penalty. Change orders during execution use T&M against named rates.

Who signs the contract — Synthology or IES-Advisors?

Synthology Healthcare Solutions Group, LLC. If IES-Advisors consultants are pulled into the engagement (typically for specialty workflow-orchestration work), that's a subcontract managed by Synthology — you only have one contract to sign.

Talk through an Implementation engagement.

Tell us the shape of the project — current state, target state, rough timeline — and we’ll come back within one business day with a proposed scope and the right engineer on our side.

Discuss an engagement Back to all services