如何从 CMOVE 正确存储 dicom 的像素数据？

Question

I have 1 running server for handle C-Move, 2 running server for handle C-Store and remote pacs server(GEPACS)

When i tried to C-Move command from remote pacs to C-Store handler, 1 server(py-netdicom) is build and save the file properly and 1 server(go-netdicom) is not.

So there was couple of problems in go-netdicom. I fixed the code can handle hexadecimals. It originally not supported on go-netdicom. This was fix almost every problems in my case but still cannot store pixel data properly.

For example, I got 9117252 bytes from original signal from remote pacs and I saved the data itself, but actually it needs to be 18000000 bytes(got an error). even CT images are short for 3 times(got approximately 180000, but need 524288)

I think the problem caused by might be the encapsulation of pixel-data but not sure.

Is there any tip or some help?

Thank you.

EDIT 4 : I've got a clue. link here

Somehow C-STORE command have a kind of transfer syntax. This offer to scp type(compressed or not) of data scu get. But still I don't have a idea which part of go-netdicom has to be changed. I'll delete "python" tag because this is not related with python anymore.

Answer 1

I found the solution.

Somehow, GEPACS send the certain transfer syntax for JPEG compression. if go-netdicom doesn't have the TransferSyntaxUID then pick the GEPACS's first transfer syntax and that was for JPEG compression.

i just put bigendian and explicitvr (GEPACS default) when transfersyntax is empty.

which placed in contextmanager.go line 101 on AssociateRequest, line 127

Hope this result help someone.

Thank you

Answer 2

The problem here is that go-netdicom uses the first PresentationContext sent in the A_ASSOCIATE_RQ (As you can see in the last image). So it accepts "2.16.840.1.113709.1.2.2" which is a privative Transfer Syntax and it is not in the DICOM standart, so no one can manage the C-STORE at the end.

If you are reading this.. maybe you do not use go-netdicom but the problem could be the same if the error involves the transfer Syntax "2.16.840.1.113709.1.2.2", in the Centricity PACs documentation says: "It is expected that other vendors' applications will ignore all Presentation Context proposed with the GE Private Compress Express Transfer Syntax"

And that is what we are suppose to do. I see a list of PRs in go-netdicom so I suppose it is not mantained, so I will post the change for go-netdicom here. I made this changes in contextmanager.go and works like a charm: