|
VA storage commitment requirements
QUESTION:Based on the VA modality spec 1.2 and other discussions, the
understanding I have, and a few others, is that there are some
interesting restrictions in terms of association handling with the VistA
system, esp. version 2.5. Specifically, an inability to use the same
port for both DICOM store and storage commitment. I believe this is due
to an inability to differentiate study start/end correctly or just plain
desiring clients to "serialize" storage and storage commitment request
and only use one association/port. Any real world experience or advice
would be helpful.
ANSWER: You totally miss the point. The requirement is placed to totally eliminate
the race condition inherent to storage commitment. You guys out there are
just plain refusing to implement an absolute requirement to accept a reverse
role negotiated connection at the SCU. It is an absolute requirement for
the SCU as you discover if you read the standard carefully. The VA
requirements just enforce this by stating that the system will never attempt
to send an N-EVENT report on the association initiated by the SCU , and will
force the SCU to honor the required acceptance of the reverse role
negotiated connection. So keep complaining because it will fall on deaf ears.
|
|
|
|
