Troubleshooting: KOSD objects not visible on the IMPAX Client

Issue

Occasionally, a user cannot see a study's KOSD DICOM objects for one of the following reasons:

A KOSD DICOM object was not created in the system.
A KOSD DICOM object was not created and the study was exported from the system without a KOSD DICOM object.

Details

If the job responsible for either creating or registering the KOSD DICOM object has been deleted from the MVF_OBJECT_CREATOR queue, a PACS Administrator can use CLUI to re-create the job.

Solution

Determining whether a KOSD DICOM object was created for a study

If a KOSD object cannot be seen on a Client station, it may be because the system did not create a KOSD DICOM object for the study. You can detect whether the system created a KOSD object for the study by running a SQL query.

To determine whether a KOSD DICOM object was created for a study

Open a SQL editor.
Type the following query:
select kosd_ref from dosr_kosd where study_ref = study_ref and object_ref is NULL
where study_ref is the study’s reference number.
If the query returns a kosd_ref value, use this value to create a CREATE_KOSD job as described in the section Creating a CREATE_KOSD job with CLUI.

Determining whether a study has unregistered KOSD DICOM objects

If a KOSD object cannot be seen on a Client station, you can use SQL queries to detect whether the study contains unregistered KOSD objects.

To determine whether a study has unregistered KOSD DICOM objects

Open a SQL editor.
Type the following query:
select object_ref from dosr_object where sop_class_uid = '1.2.840.10008.5.1.4.1.1.88.59' and study_ref = study_ref
where study_ref is the study’s reference number.
Type the following query:
select kosd_ref from dosr_kosd where object_ref = object_ref
where object_ref is the value returned by the query you ran in step 2.

If no kosd_ref value is returned, the study contains a KOSD DICOM object that is not registered. In this case, use the object_ref value returned by the query you ran in step 2 to create a REGISTER_KOSD job, as described the section Creating a REGISTER_KOSD job using CLUI.

Creating a CREATE_KOSD job using CLUI

If the system did not create a KOSD DICOM object for a particular study, create a CREATE_KOSD job using CLUI. To do this, you will need the study's kosd_ref value which you can get by running the queries in the section Determining whether a KOSD DICOM object was created for a study..

To create a CREATE_KOSD job using CLUI

Log into the IMPAX Server and open a command prompt.
Change to the C:\mvf\bin directory.
At the command prompt, type
clui
At the prompt, type
go menu
To open the Job Manager menu, at the SELECTION: prompt, type
5
To select Recreate CREATE_KOSD job from the Job Manager Menu, at the SELECTION: prompt, type
13
At the enter refs to process prompt, type the kosd_ref value.

Creating a REGISTER_KOSD job using CLUI

If the system did not register a KOSD DICOM object for a study, create a REGISTER_KOSD job using CLUI. To do this, you need the study’s object_ref value(s) which you can obtain by running the queries in the section Determining whether a study has unregistered KOSD DICOM objects.

To create a REGISTER_KOSD job using CLUI

Log into the IMPAX server and open a command prompt.
Change to the C:\mvf\bin directory.
At the command prompt, type
clui
At the prompt, type
go menu
To open the Job Manager menu, at the SELECTION: prompt, type
5
To select Recreate REGISTER_KOSD job from the Job Manager Menu, at the SELECTION: prompt, type
14
At the enter refs to process prompt, enter KOSD DICOM object's object_ref value.

Important!

If the job responsible for either creating or registering the KOSD DICOM object fails for any reason (for example, a KOSD object received from a third-party system is not DICOM-compliant), any KOSD objects that are created for that study and then subsequently marked for deletion are removed from the Image area and are no longer visible to the user.

However, because of the failed job, Autopilot Manager, which controls the timing of image deletion from cache, considers the job outstanding and the invisible objects are not deleted. If the study is then transmitted to another IMPAX system, the invisible objects are transmitted as well, resulting in a discrepancy in the number of objects between the two systems, and causing the invisible objects to be visible on the system the study was transmitted to.