Why do these 5 DICOM tags give a java.lang.UnsupportedOperationException when used with dcmsnd ?

[Joey]

I painstakingly went through my dicom anonymize procedure and tried to find out what was causing the Unsupported Operation Exception.

Also see the last comment in my older post.

I coerce and send DICOM files to the pacs like so:

c:/Users/server/application/utils/dcm4che-2.0.29/bin/dcmsnd.bat DCM4CHEE@127.0.0.1:11112 d:/webservice/dicom/e5415cc0-53c3-456d-af85-49321bc23696-f3d1096d -set 00100020=P.123.456.78 00080050=00080080= 00080081= 00080090= 00080092= 00080094= 00081010= 00081030= 0008103E= 00081040= 00081048= 00081050= 00081060= 00081070= 00081080= 00082111= 00100010=Anonymized 00100030= 00100032= 00100040= 00101000=00101001= 00101010= 00101020= 00101030= 00101090= 00102160= 00102180= 001021B0= 00104000= 00181000= 00181030= 00204000= 00400275= 0040A730= 00100005= 00100050= 00101040= 00101050= 00101040= 00101080= 00101081=00102152= 00102154= 00324000= 00400006= 00081052= 00401102=

The following tags in the command somehow 'do not work' in our windows environment using dcmsnd.bat.

• 00400275 (Request Attributes Sequence)
  
• 0040A730 (Content Sequence)
  
• 00100005 (Parient's Birth Name)
  
• 00100050 (Patient's Insurance Plan Code Sequence)
  
• 00081052 (Performing Physician Identification Sequence)
  

I removed them from the anonymize procedure for now. However, I'm wondering why these throw an exception, because the entire works in our Linux environment with dcmsnd.

If anyone could explain this, that would be very helpful.

Thank you

[Jon Ander Zuccaro]

I've noticed that most of those are sequences, can you send another sequence without issues? What happens if you do 00400275="" instead of 00400275= ?

[Joey]

Thanks to your tip I got it to work.

You were right about the tags mostly being sequences.

• 00400275=""  Works.
  
• 00400275='' Throws the exception. Not entirely sure why, but presumably because it's not a string
  
• 00400275= Throws the exception, but works on Linux using dcmsnd

Anyhow, I'm glad the application is able to anonymize according to procedure again.

Thank you!

[Joey]

I have noticed that "Anonymized" gives the following error on Windows.

 Exception in thread "main" java.lang.IllegalArgumentException: Unknown Tag Name: Anonymized

This happens with these three 

• 00080080="Anonymized"
  
• 00080080='Anonymized'
  
• 00080080=Anonymized
• "00080080=Anonymized"

It's appears to think Anonymized is a tag name instead of a value. Is there a way to make the command assign Anonymized

as a value instead of thinking it's a tag name?

Thanks