Configurations

Exodus comes in various configurations to suit your specific assessment/migration needs.

Every DICOM migration presents unique challenges and Exodus offers a flexible approach to defining and processing an archive migration. Each operation is highly configurable to allow for custom queries, moves, and validations to ensure that you have full knowledge and control of the migration process at every step. Detailed information about the size and quality of your source data as well as the current state of the migration can all be obtained from a single easy-to-use view. Every exam is moved how and when you define and verified automatically.

Exodus Screen Captures

From start to finish, the goal of Exodus is to provide a complete and transparent view of the migration process by providing options to exactly control the migration of the DICOM data archive in a simple, high-level way, freeing you to concentrate on other tasks. Custom services and support are available to address your specific DICOM archive migration related needs.

Check out these screen captures to get a small taste of what Exodus can do.

Main window.	Segment configuration.
Filtering configuration.
Query configuration.	Move configuration.

Migration Overview

A DICOM archive migration is defined as the process of transferring data from one archive (source archive) to another (destination archive). Sometimes called DICOM PACS Migration, these DICOM archive migrations generally consist of a data migration tool or application issuing requests known as queries (C-FIND) to the source archive to get a list of appropriate exams (i.e., study or series) to move.

For each exam found, a request known as a move (C-MOVE) is issued to the source archive to move the particular exam to the destination archive. It is the responsibility of the source archive to process the move request and inform the move requestor of the status of that request. To ensure that the exam was processed properly by the destination archive, a query may be issued to the destination to verify the existence and/or validity of the exam.

Controller Overview

Exodus manages DICOM PACS migrations, and other DICOM archive migrations, by creating a database, known as a session, that contains all the configuration information as well as all the state and tag information for every exam it knows about. Groups of exams are viewed and operated upon by creating configurable views known as segments within a session.

A session represents a separate database that stores configuration information about a DICOM archive migration. Information about the source, destination, and validation archives is included, as well as settings for each of these operations (e.g. timeouts, schedules, delays, etc.). In addition to this information, the list and state of every query and exam is contained within a session which represents the work that has been done for a given migration. While multiple sessions can be configured, typically only one is needed for a given migration.

A segment provides the definition of what to query and represents a logical grouping of exams to migrate based on those queries. There are multiple types of segments available allowing for various methods by which to gather listings of exams to work on. A given migration can be broken up into multiple segments or left as one segment representing the entirety of the migration.