After configuring IMPAX to handle change context (cc) objects correctly, you can perform a test to ensure that data is being updated as expected.
To verify the cc object configuration, you can perform a split, then check that the database has been correctly updated, the appropriate notifications have been sent from Task Scheduler, job queues created, and objects received.
To verify that IMPAX cc object synchronization is correctly configured
Using test data, perform a study split at an IMPAX Client. (For details, refer to “Splitting images from one study into another study” (topic number 11592) in the IMPAX 6.5.1 Client Knowledge Base: Extended.)
To verify that the database has been updated with attribute changes for the new studies, launch CLUI and run the following command:
select * from change_context,change_context_detail where
change_context.change_context_id=change_context_detail.change_context_id order by
change_context.date_time_created desc
After the changes are recorded in the database, an mvf_task_scheduler process runs to create the notify jobs.
To verify that the notify jobs have been created, in CLUI, run select * from map_event order by date_time_created desc
or
In Administration Tools, select Job Manager and monitor the notify job queue.
Note:
Do not stop the Transmit/Retrieve/Print queue. It must be active for the NOTIFY job to be created.
Once the notification jobs have a status of Done, ensure that STORE jobs appear for storing the cc objects to PACS Store and Remember. You can check the study on the PACS Store and Remember to ensure a new object has a modality of CC.
You can enable Change Context object synchronization to a routing destination instead of to a PACS Store and Remember. In this case, ensure that SEND jobs appear for storing the new studies with their cc objects to the routing destination.
At the PACS Store and Remember destination, check to see whether the objects are received.
Store jobs to IMPAX Data Center are dependent on the spoke’s archiving window configuration. Therefore, you might not see notify and store jobs until the archiving windows are valid.