Hi, When a patient ID exists on the pacsone server and the server receives a duplicate patient ID with patient name information that does not match what pacsone already has, the patient ID is coerced to append to the end of the patient ID something that identifies the AE title from which it was received.
What's happeneing for me is that the sending station is not recognizing that Pacsone has received the file. So it keeps on re-sending the file. Meanwhile, my pacsone is set to autoforward to another system. Each subsequent time the image is received, the pacsone forwards the image off again.
A related question.......Is there any way that a patient name or ID can be change after the pacsone server has received it?
Duplicate Patient ID Data Element Coercion
Yes, other users have reported similar behavior with some acquisition modalities (e.g., Fuji CR).
What's happening is when PacsOne receives the new image with the duplicate patient id but different patient name, PacsOne will send back a Warning status (Warning: Element Coerced) in the C-STORE-RSP instead of the normal Success status. Some modalities such as the Fuji CR would interpret the Warning status as failure, and would retry sending the same image again or even forever.
On the other hand, this behavior is actually good since it gives the user some indication of a problem, so that users can fix the duplicate at the modality instead of letting the duplicate propogate through to the PACS. .
In the next coming release (version 3.1.7), we've added a menu in the Tools page to resolve duplicate patient ids, where you can either fix the wrong name for the duplicate patient id, or assign a new patient id if they are not really duplicates.
What's happening is when PacsOne receives the new image with the duplicate patient id but different patient name, PacsOne will send back a Warning status (Warning: Element Coerced) in the C-STORE-RSP instead of the normal Success status. Some modalities such as the Fuji CR would interpret the Warning status as failure, and would retry sending the same image again or even forever.
On the other hand, this behavior is actually good since it gives the user some indication of a problem, so that users can fix the duplicate at the modality instead of letting the duplicate propogate through to the PACS. .
In the next coming release (version 3.1.7), we've added a menu in the Tools page to resolve duplicate patient ids, where you can either fix the wrong name for the duplicate patient id, or assign a new patient id if they are not really duplicates.