dcm4chee reject image with modified window level parameter's

[Dhaval Joshi]

Hi

Is there a way for dcm4chee to reject image if same image is sent again with modified window level parameter's

Thanks

[Nicolas Roduit]

If the same image (has the same SOPInstanceUID) is sent again, it is automatically rejected by dcm4chee. Modifying W/L values should be sent to the PACS as a Presentation State (DICOM object) because the stored images must not be modified.

[Dhaval Joshi]

what if window level is not changed and images is processed with different processing algorithm second time and then sent to dcm4chee will it accept or reject the processed image ?

--
You received this message because you are subscribed to a topic in the Google Groups "dcm4che" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/dcm4che/euYRxJ6mGvc/unsubscribe.
To unsubscribe from this group and all its topics, send an email to dcm4che+u...@googlegroups.com.
To post to this group, send email to dcm...@googlegroups.com.
Visit this group at https://groups.google.com/group/dcm4che.
For more options, visit https://groups.google.com/d/optout.

--

Thanks
Dhaval Joshi

[Arnold Maderthaner]

afaik whatever you do to the image it is rejected by default if the SOP Instance UID already exists - however you can configure it to store an additional copy if the MD5 sum of the 2 instances are different (look at the StoreSCP settings for this - something like StoreDuplicatesIfDifferentMD5).

Am Freitag, 15. Januar 2016 18:23:44 UTC+1 schrieb Dhaval Joshi:

what if window level is not changed and images is processed with different processing algorithm second time and then sent to dcm4chee will it accept or reject the processed image ?

On Fri, Jan 15, 2016 at 1:22 AM, Nicolas Roduit <nicolas...@gmail.com> wrote:

If the same image (has the same SOPInstanceUID) is sent again, it is automatically rejected by dcm4chee. Modifying W/L values should be sent to the PACS as a Presentation State (DICOM object) because the stored images must not be modified.

Le vendredi 15 janvier 2016 01:01:45 UTC+1, Dhaval Joshi a écrit :

Hi

Is there a way for dcm4chee to reject image if same image is sent again with modified window level parameter's

Thanks

--
You received this message because you are subscribed to a topic in the Google Groups "dcm4che" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/dcm4che/euYRxJ6mGvc/unsubscribe.

To unsubscribe from this group and all its topics, send an email to dcm4che+unsubscribe@googlegroups.com.

To post to this group, send email to dcm...@googlegroups.com.
Visit this group at https://groups.google.com/group/dcm4che.
For more options, visit https://groups.google.com/d/optout.

--

Thanks
Dhaval Joshi

[Dhaval Joshi]

Thanks for your help

On Fri, Jan 15, 2016 at 10:00 AM, Arnold Maderthaner <arn...@maderthaner.me> wrote:

afaik whatever you do to the image it is rejected by default if the SOP Instance UID already exists - however you can configure it to store an additional copy if the MD5 sum of the 2 instances are different (look at the StoreSCP settings for this - something like StoreDuplicatesIfDifferentMD5).

Am Freitag, 15. Januar 2016 18:23:44 UTC+1 schrieb Dhaval Joshi:

what if window level is not changed and images is processed with different processing algorithm second time and then sent to dcm4chee will it accept or reject the processed image ?

On Fri, Jan 15, 2016 at 1:22 AM, Nicolas Roduit <nicolas...@gmail.com> wrote:

If the same image (has the same SOPInstanceUID) is sent again, it is automatically rejected by dcm4chee. Modifying W/L values should be sent to the PACS as a Presentation State (DICOM object) because the stored images must not be modified.

Le vendredi 15 janvier 2016 01:01:45 UTC+1, Dhaval Joshi a écrit :

Hi

Is there a way for dcm4chee to reject image if same image is sent again with modified window level parameter's

Thanks

--
You received this message because you are subscribed to a topic in the Google Groups "dcm4che" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/dcm4che/euYRxJ6mGvc/unsubscribe.

To unsubscribe from this group and all its topics, send an email to dcm4che+u...@googlegroups.com.

To post to this group, send email to dcm...@googlegroups.com.
Visit this group at https://groups.google.com/group/dcm4che.
For more options, visit https://groups.google.com/d/optout.

--

Thanks
Dhaval Joshi

--

You received this message because you are subscribed to a topic in the Google Groups "dcm4che" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/dcm4che/euYRxJ6mGvc/unsubscribe.

To unsubscribe from this group and all its topics, send an email to dcm4che+u...@googlegroups.com.

To post to this group, send email to dcm...@googlegroups.com.
Visit this group at https://groups.google.com/group/dcm4che.
For more options, visit https://groups.google.com/d/optout.

--

Thanks
Dhaval Joshi