Smita
2007-12-05 05:16:56 UTC
Hi,
Recently while attending a connectivity event in China, I saw a lot of
DICOM RIS and PACS supportig the encoding GBK at the DICOM level.
Meaning that the Specific character set tag(8,5) had the entry GBK and
the strings in the image headers were encoded in GBK. GBK is also a
popular encoding in North China.
The DICOM supported encoding for Chinese are GB18030 and ISO IR
192(Unicode).
GB18030 is a superset of GBK, so even though systems that support
GB18030 and have the capability of understanding GBK, do not accept
DICOM messages with the specific character set tags as "GBK" because
its not in the DICOm standard. This is limiting interconnectivity.
I am not sure why some DICOM RIS and PACS went ahead with GBK encoding
at the DICOM level, but our systems are facing connectivity issues
because we only support the encodings mentioned in the DICOM
standards.
My question is why can GBK not be included in the DICOM standard when
it is so pupular in China.
Thanks
Smita
Recently while attending a connectivity event in China, I saw a lot of
DICOM RIS and PACS supportig the encoding GBK at the DICOM level.
Meaning that the Specific character set tag(8,5) had the entry GBK and
the strings in the image headers were encoded in GBK. GBK is also a
popular encoding in North China.
The DICOM supported encoding for Chinese are GB18030 and ISO IR
192(Unicode).
GB18030 is a superset of GBK, so even though systems that support
GB18030 and have the capability of understanding GBK, do not accept
DICOM messages with the specific character set tags as "GBK" because
its not in the DICOm standard. This is limiting interconnectivity.
I am not sure why some DICOM RIS and PACS went ahead with GBK encoding
at the DICOM level, but our systems are facing connectivity issues
because we only support the encodings mentioned in the DICOM
standards.
My question is why can GBK not be included in the DICOM standard when
it is so pupular in China.
Thanks
Smita