Migration Flow

After the installation and configuration of the migration software, an internal database is set up that
can hold all studies available in the old system. The migration software will, during a predefined daily
timeframe, execute DICOM queries on a day-by-day basis to retrieve all studies performed on a
particular day and use this information to construct its internal study database. Alternative queries
can be executed to verify and control the integrity of the database.

Next, a DICOM retrieve operation will collect all images from the old system for every study in the
internal database and will store these images locally. The software can be configured in such a
manner that pauses are introduced between different retrieve operations and that retrieve
operations are only executed during certain timeframes. This avoids network congestion and an
unwanted load on the old PACS.

Depending on the configuration, images will be received, validated or modified according to
predefined procedures and will then be sent to the new archive. A temporary cache of images is
created in case there is no possibility to create a simultaneous connection between the old system
and the new system. Afterwards, the images are transferred from the cache to the new system.
During this operation it is also possible to introduce pauses or to execute the migration during only
certain hours of the day.

Optionally, the migration software can query the new PACS for confirmation of the safe storage of
the images, by means of a DICOM storage commitment message or an ordinary DICOM query.
e-trinity guarantees a correct migration of historical images together with the corresponding patient
information. The project is finalized when all images of all known studies are successfully sent to the
new system whether or not accompanied by the received confirmation messages, depending on the
configuration of the migration software.