Previous post is NOT mine, OK?
So I would show you instructions usable UNDER GNU/Linux ONLY USING DCMTK and ORTHANC, you said.
First, The dcmdump tool in DCMTK shows DICOM TAG on the part of my MRI data:
$ dcmdump my_MR_data_name.dcm
Dicom-File-Format
Dicom-Meta-Information-Header
Used TransferSyntax: Little Endian Explicit
(0002,0000) UL 196 # 4, 1 FileMetaInformationGroupLength
(0002,0001) OB 00\01 # 2, 1 FileMetaInformationVersion
(0002,0002) UI =MRImageStorage # 26, 1 MediaStorageSOPClassUID
(0002,0010) UI =LittleEndianExplicit # 20, 1 TransferSyntaxUID
Dicom-Data-Set
Used TransferSyntax: Little Endian Explicit
(0008,0005) CS [ISO_IR 100] # 10, 1 SpecificCharacterSet
(0008,0008) CS [ORIGINAL\PRIMARY\M\ND\MFSPLIT] # 30, 5 ImageType
(0008,0012) DA [20180622] # 8, 1 InstanceCreationDate
(0008,0013) TM [174321.564656] # 14, 1 InstanceCreationTime
(0008,0016) UI =MRImageStorage # 26, 1 SOPClassUID
Second, The storescu tool in DCMTK sent the my MRI data to ORTHANC, and the tool shows this logs:
$ storescu -aet LOCAL_AET -aec ORTHANC_AET --verbose ORTHANC_IP ORTHANC_PORT my_MR_data_name.dcm
I: checking input files …
I: Requesting Association
I: Association Accepted (Max Send PDV: 16372)
I: Sending file: my_MR_data_name
I: Converting transfer syntax: Little Endian Explicit → Little Endian Explicit
I: Sending Store Request (MsgID 1, MR)
XMIT: …
I: Received Store Response (Success)
I: Releasing Association
Third, Downloaded the my MRI data from web UI of ORTHANC, and the dcmdump tool in DCMTK shows this logs :
The Private TAGs have VR values and TAG values (this private TAGs are registered in the “Dictionary” section of Configuratuin.json).
$ dcmdump 15dc5855-d5c3-4c92-b2c8-***********.dcm
Dicom-File-Format
Dicom-Meta-Information-Header
Used TransferSyntax: Little Endian Explicit
(0002,0000) UL 202 # 4, 1 FileMetaInformationGroupLength
(0002,0001) OB 00\01 # 2, 1 FileMetaInformationVersion
(0002,0002) UI =MRImageStorage # 26, 1 MediaStorageSOPClassUID
(0002,0010) UI =LittleEndianExplicit # 20, 1 TransferSyntaxUID
(0002,0012) UI [1.2.276.0.7230010.3.0.3.6.4] # 28, 1 ImplementationClassUID
(0002,0013) SH [OFFIS_DCMTK_364] # 16, 1 ImplementationVersionName
Dicom-Data-Set
Used TransferSyntax: Little Endian Explicit
(0008,0005) CS [ISO_IR 100] # 10, 1 SpecificCharacterSet
(0008,0008) CS [ORIGINAL\PRIMARY\M\ND\MFSPLIT] # 30, 5 ImageType
(0008,0012) DA [20180622] # 8, 1 InstanceCreationDate
(0008,0013) TM [174321.564656] # 14, 1 InstanceCreationTime
(0008,0016) UI =MRImageStorage # 26, 1 SOPClassUID
…(snip)…
(0021,1001) IS [70] # 2, 1 Unknown Tag & Data
(0021,1004) DS [1] # 2, 1 Unknown Tag & Data
(0021,1005) IS [0\0\0] # 6, 3 Unknown Tag & Data
(0021,1006) LO [void] # 4, 1 Unknown Tag & Data
(0021,1008) SH [Normal] # 6, 1 Unknown Tag & Data
(0021,1009) LO [p2 s4] # 6, 1 Unknown Tag & Data
(0021,100a) DS [1] # 2, 1 Unknown Tag & Data
(0021,100d) US 0 # 2, 1 Unknown Tag & Data
…
Forth, The movescu tool in DCMTK requested C-MOVE the my MRI data w/ little Endian explicit to ORTHANC, and the tool shows this logs:
$ movescu -v --propose-little --prefer-little -k 0010,0020=“123456789” -aet LOCAL_AET +P LOCAL_PORT -aec ORTHANC_AET -od ./tmp/ ORTHANC_IP ORTHANC_PORT
I: Requesting Association
I: Association Accepted (Max Send PDV: 16372)
I: Sending Move Request (MsgID 1)
I: Request Identifiers:
I:
I: # Dicom-Data-Set
I: # Used TransferSyntax: Little Endian Explicit
I: (0010,0020) LO [123456789] # 10, 1 PatientID
I:
I: Sub-Association Received
I: Sub-Association Acknowledged (Max Send PDV: 16372)
I: Received Store Request (MsgID 1, MR)
RECV: …
I: Received Final Move Response (Success)
I: Releasing Association
Finery, The dcmdump tool in DCMTK shows the logs of moved the my MRI data:
The log shows changing to “Little Endian Explicit” to “Little Endian Implicit”, and Private TAGs gone (this private TAGs are registered in the “Dictionary” section of Configuratuin.json).
$ dcmdump tmp/my_MR_data_move_from_orthanc.dcm
Dicom-File-Format
Dicom-Meta-Information-Header
Used TransferSyntax: Little Endian Explicit
(0002,0000) UL 212 # 4, 1 FileMetaInformationGroupLength
(0002,0001) OB 00\01 # 2, 1 FileMetaInformationVersion
(0002,0002) UI =MRImageStorage # 26, 1 MediaStorageSOPClassUID
(0002,0003) UI [1.3.12.2.1107.5.2.50.175680.30000018062111274458500041449] # 58, 1 MediaStorageSOPInstanceUID
(0002,0010) UI =LittleEndianImplicit # 18, 1 TransferSyntaxUID
(0002,0012) UI [1.2.276.0.7230010.3.0.3.6.4] # 28, 1 ImplementationClassUID
(0002,0013) SH [OFFIS_DCMTK_364] # 16, 1 ImplementationVersionName
(0002,0016) AE [ORTHANC_AET] # 4, 1 SourceApplicationEntityTitle
Dicom-Data-Set
Used TransferSyntax: Little Endian Implicit
(0008,0005) CS [ISO_IR 100] # 10, 1 SpecificCharacterSet
(0008,0008) CS [ORIGINAL\PRIMARY\M\ND\MFSPLIT] # 30, 5 ImageType
(0008,0012) DA [20180622] # 8, 1 InstanceCreationDate
(0008,0013) TM [174321.564656] # 14, 1 InstanceCreationTime
(0008,0016) UI =MRImageStorage # 26, 1 SOPClassUID
…(snip)…
(0021,1001) ?? 37\30 # 2, 1 Unknown Tag & Data
(0021,1004) ?? 31\20 # 2, 1 Unknown Tag & Data
(0021,1005) ?? 30\5c\30\5c\30\20 # 6, 1 Unknown Tag & Data
(0021,1006) ?? 76\6f\69\64 # 4, 1 Unknown Tag & Data
(0021,1008) ?? 4e\6f\72\6d\61\6c # 6, 1 Unknown Tag & Data
(0021,1009) ?? 70\32\20\73\34\20 # 6, 1 Unknown Tag & Data
(0021,100a) ?? 31\20 # 2, 1 Unknown Tag & Data
(0021,100d) ?? 00\00 # 2, 1 Unknown Tag & Data
…
The instructions have show usable UNDER GNU/Linux ONLY USING DCMTK and ORTHANC, you see?
Any ideas?
Best,
YOKOHAMA
2019年7月29日月曜日 13時57分31秒 UTC+9 Sébastien Jodogne: