I'll look into this with the other developers. Will try to get back with an answer.

I downloaded the file and will look into the problem.

DVT 2.3.1 cannot validate ISO_IR 144 response either. Still get to same error: (0010,0010) PN - 2C + 24 Patient's Name \B0^\B5\B5^\B0\BB


Error: Attribute (0010,0010) Could not check extended character set properties.

i have edit files with a hexadecimal editor so :

first i have used the instance wiht uid 100.118.116.2005.2.1.1132055943.781.1 in One^Secondary Capture Image study to my test transfert.

pixel data a file transfert in explicit big endian is named:
B08_0010.pix
pixel data a file transfert in explicit little endian is named:
B08_0020.pix
pixel data a file transfert in implicit little endian is named :
W08L0012.pix

Aaa it sound strange i suppose than 08 is for bits allocated or bits stored . B or W i suppose it is some information refering to data... L or "_" i have no idea end the 4 last caracter for a number.

if i edite all B files raw pixel data i can see before the transfer syntax "BB" and a "*"(the start is not always at teh same place but it is not a probelem for the comparator) but in W file raw pixel data i can see before the transfer syntax "WW" and a "*".
of sure in every pixel data the transfert syntax are different.

To test,
I have add a CT image from INCISIX study find on :
http://pubimage.hcuge.ch:8080
the 3 file tranfered in EBE ELE ILE genered in comparator a W type pixel data file and the comparaison betwen file wore fine et the only diffrence observed is in tag length et tag of syntax transfert

have you an idea about this probleme ??

file are downloadable on :
http://dl.free.fr/ru4Xvghcw

clic on telcharger ce fichier:

thanks

i wasn t be able to send file so you can download file here:
http://dl.free.fr/getfile.pl?file=/ldO8cEtl

i join on of problematic file

thank

The behaviour of the DICOM Compare application you describe sounds incorrect. You van view the raw pixel data since it gets extracted into a separate file. If you look in the Compare application you will see a filename as value for the pixel attribute. If you open that file you will see the raw pixel data.

DVT supports almost all character sets when it comes to communicating. However, there is no support for visualizing the character sets. I believe that the DVT 2.2.1 version had a problem with character sets. You should download the latest DVT version 2.3.1.

There is no conformance statement for DVTk as a project, but there is one for DVT. You can find it in the documentations folder of the application folder.

We dot not use a DICOM Dictionary like most DICOM applications. We have a small part hard coded in the source code, and the rest of the DICOM Dictionary can be found in the definition files.