Exodus™ Migration & Consolidation Controller


Exodus is a powerful data orchestration tool that can enable your organization to solve a variety of archive migration and consolidation challenges that may result from product lifecycle management or mergers and acquisitions.

Exodus works with other Laurel Bridge software applications to empower your health system to strategically manage your own migration and consolidation efforts and allows you the option to bring the necessary expertise in-house. This enables your organization to have ongoing control and management of legacy archives, which is vital to ensuring that clinical staff has access to historical medical images.

We provide the flexibility you need to meet your organization’s evolving enterprise imaging workflow needs and the unique challenges that exist due to supporting disparate IT systems. Implement the migration approach that meets your unique needs:

  • Self-conducted through your internal expertise.
  • Service provider managed through our expertise.
Add To Quote
SKU: LBS-EXODUS Category: Brand:


Pair the Exodus Migration Controller with our Compass DICOM Router to:

  1. Temporarily store the migrated data before sending to final migration destination (often referred to as a “forklift” migration).
  2. Multiplex the migrated studies to more than one destination.
  3. Generate an out-bound HL7 ORM order message to the destination archive before sending the migrated studies.
  4. Load-balance the C-Move Requests to multiple AE titles on the source archive  (may improve the rate at which source archive can deliver exams)
  5. Load-balance the C-Store to multiple ingestion nodes/ports on the destination archive (may improve rate at which destination archive can ingest/store migrated exams)

Pair the Exodus Migration Controller with our Navigator Prior Fetching Solution to:

  1. Fetch and migrate prior exams for scheduled patients, from multiple archives (not just from the primary archive that you are migrating) while also performing a full migration from a single primary source.
  2. Incorporate a Master Patient Index (MPI) or PIX query into your prior exam fetching process to allow updating of the patient demographics as part of the migration process.


The Exodus Migration and Consolidation Controller can support various migration methodologies. Each has unique benefits that are intended to take advantage of the information available and the capabilities of the existing archives:

Traditional DICOM
Source of information:
(about files to be migrated)
DICOM query response from legacy archive
Benefits: • Uses DICOM to identify and track progress
• Includes latest database data
Limitations: • Speed
• System performance
• Single source
Source Of Truth
Source of information:
(about files to be migrated)
Client supplier list
Benefits: Based on a pre-defined list
Limitations: • List requires compilation
• Static
• Single source
File Import
Source of information:
(about files to be migrated)
Legacy archive file system
Benefits: Enables migration of older archives that don’t support DICOM Query/Retrieve
Limitations: • Includes all files, including undesired files
• Single source
Source of information:
(about files to be migrated)
Modality worklist of scheduled patients
Benefits: Ensures prior data is available when needed
Limitations: Limited to a single source, except when paired with Navigator

Which of these migration challenges can Exodus solve for you?

  • Merger of two or more archives
  • Access to relevant priors
  • Mismatched patient/study information
  • Archive vendor proprietary issues
  • Private DICOM tag handling
  • Non-compliant/inconsistent DICOM data
  • Unknown size of the job
  • Uncertainty of completeness
  • Inability to validate the data moved
  • Excessive manual effort
  • Inability to pre-fetch relevant priors

Recommended Minimum Requirements

  • Intel i5 Processor or better
  • 4 GB RAM (min.)
  • 256 GB HD (min.)
  • Windows 7, Windows 8.1, Windows Server 2008 R2, or Windows Server 2012 R2
  • SQL Server 2008 R2 x64, SQL Server 2012 x64, or SQL Server 2014 x64. Express edition may be used in most installations.
  • Microsoft .NET Framework 3.5 SP1
  • Microsoft SQL Management Studio