User guide

8. Remove the IMPAX AS300 CD.
Running PSARMT to mark studies as PACS archived8.
Note:
If the site does not use an external PACS, you can skip this topic.
The PACS Store and Remember Migration Tools enable a site to migrate from an external PACS system
to IMPAX by allowing the external system to act as an archive server to IMPAX.
Run these commands on the migrated IMPAX Database Server.
For more information regarding the configuration and execution of the PSARMT Migration Tools, refer
to the PSARMT readme document that can be found in the C:\mvf-mig6 directory.
To run PSARMT to mark studies from an external PACS as PACS archived
1. Navigate to the C:\mvf directory.
2. Build the PSARMT database tables by running build-mvf-psarmt-database.bat.
3. Install the PSARMT Tools as services by running install_psarmt.bat.
4. Specify the migration configuration by running mvf_psarmt_config_manager.exe.
Parameters are as follows:
• -C configuration_file_with_all_parameters —Default is installed as mvf-psarmt.cfg. The
attributes of this file are described in the PSARMT readme document.
• -R study_status —Retries studies with the given status for migration. Possible study_status
values are conflict (C), error (E), and unknown (U). To retry all at once, specify -R EUC.
• -A {STOP | RESTART | KILL}—Performs the specified action command.
5. Start the PSARMT services by running start_psarmt.bat.
6. Perform the migration, based on the configuration defined in step 4, by running mvf_psarmt.exe.
At some later date, when studies are retrieved from the PACS, update the missing information in the
database from incoming study object by running mvf_study_fixer.exe.
Once the migration is complete and all studies have been fixed by the Study Fixer tool—this may be
several months later—the PSARMT services halt automatically. If you want to remove the PSARMT
Tools as services, on Windows, run remove_psarmt.bat.
Detecting and correcting IMPAX cache corruption9.
The Cache Check and Repair Tools are used to identify missing cache files and to repair or remove
damaged ones. These tools are normally run across all of the cache file systems on the affected server,
because files missing from a damaged cache can sometimes be found on another cache. Performance
of the tools is hardware-dependent.
AS300 Upgrade Guide—IMPAX 6.2 or later to IMPAX 6.4 61
AGFA COMPANY CONFIDENTIAL