PacsOne Server

It appears that Selenia is limited in its ability to identify a patients name. The techs are using the last name field to enter "Lastname,firstname". Obviously, with mammo, most of these patients are screened annually so if the patient name isn't entered exactly as it was previously, PACSONE issues an alert that the patient ID and patient name do not match. This apparently causes Selenia to stop sending images to PACSONE. So that, now they have a real mess, believing that images had been archived, when really all that is on PACSONE is the first image (R CC).

To make things even more complicated, it appears that some of the studies that have appended study names (by PACSONE) do have more than one image. Not always the total of four, but more than one.

Can you help me troubleshoot this problem to try to figure out what is going on so that I can ask for some help from Hologic in setting up their machine correctly?

Is there anything we can do from the PACSONE side to make sure these images are archived? For instance, ignore the problem and not send the warning?

Thanks,

hyounker

You seem to be running into the common issue of duplicate Patient IDs, where the newly received Patient ID is the same as an existing patient record, but the newly received Patient Name is different from the existing record (e.g., due to human error or typos by the technicians, etc). In this case, PacsOne Server will store the newly received study under a duplicate Patient ID by appending the "$SourceAE-$Timestamp" suffix to the shared/conflicting Patient ID, and return a Warning C-STORE-RSP status to the sending AE to warn against the duplicate.

Some of the legacy modalities may not understand the Warning C-STORE-RSP status properly, and would abort as if an Error status has been received. If this is the case and you want to disable the Warning C-STORE-RSP status returned by PacsOne Server, you can add/set the following Registry value:
Set/Add the DWORD value to 0, and restart PacsOne Server. Then PacsOne Server will no longer return the Warning C-STORE-RSP status to the sending AE, even if there is data element coerced in the received Dicom images (e.g., from the defined Data Element Coercion rules or duplicate Patient ID identified).

That's pretty much what I was thinking, I just didn't know all those details! Thanks.

I do not have that key in the registry. Does that mean my PACSONE 6.1.1 is outdated already!!??

hyounker

This Registry value is optional as the default behavior is to return the Warning C-STORE-RSP status when one or more data elements are coerced. This Registry setting has been available since version 4.x of PacsOne Server including the latest version 6.2.1.

I've sent an email with a screen shot of the registry keys.

Also, is there any explanation as to why some of these studies make it to PACSONE, while others are stopped?

hyounker

It depends on how the sending AE is interpreting the Warning C-STORE-RSP status returned from PacsOne Server, as some of them would treat it as an error condition and thus not proceed to send the rest of the images, while others may interpret the Warning correctly and complete sending the entire study despite the Warning status.

Understood, but this is only one modality. Sometimes the images are sent completely, other times only one image is sent.

Thanks again for your help,

hyounker

The single image received suggests this modality was interpreting the Warning C-STORE-RSP status as an Error condition and had aborted the association. To verify if this is the case, you can check if there's any error indication or message from this input modality, or the corresponding PacsOne Server logs to see if the association from this modality was aborted.

It sounds like you believe that the Selenia is interpretting the warning message differently with different studies. I'll have to look a little different to see if I can spot the commonalities of the rejected vs. accepted studies.

hyounker