Implementation Version Name && Implementation Class UID Issues - DICOM

This is a discussion on Implementation Version Name && Implementation Class UID Issues - DICOM ; Hi, Please help me with this question: I am sending a Storage IOD (Dicom file) from a SCU to the SCP for storage. When I compare the values of Implementation Class UID (0002,0012) & Implementation Version Name (0002,0013) in the ...

+ Reply to Thread
Results 1 to 4 of 4

Thread: Implementation Version Name && Implementation Class UID Issues

  1. Implementation Version Name && Implementation Class UID Issues

    Hi,

    Please help me with this question:

    I am sending a Storage IOD (Dicom file) from a SCU to the SCP for
    storage.

    When I compare the values of Implementation Class UID (0002,0012) &
    Implementation Version Name (0002,0013) in the SCU and SCP DCM files,
    they are not the same.



    I guess it is happening because the SCP at the time of creating the
    DCM file unpacks the DCM file and then writes it again.
    Can you please tell if what I am saying in the above line is correct?
    And how can i correct this.

    I am using DVTk as the SCP.

    Thanks and Regards,
    LalitSRana


  2. Re: Implementation Version Name && Implementation Class UID Issues

    Hi

    There is nothing to correct, since that is the way it is supposed
    to be.

    Thesre are attributes of the meta-information header, which is
    written when a network dataset is recorded in a file; these are
    not transmitted on the network and they describe the file (set)
    creator, not the originator of the dataset.

    David

    Lalit wrote:
    > Hi,
    >
    > Please help me with this question:
    >
    > I am sending a Storage IOD (Dicom file) from a SCU to the SCP for
    > storage.
    >
    > When I compare the values of Implementation Class UID (0002,0012) &
    > Implementation Version Name (0002,0013) in the SCU and SCP DCM files,
    > they are not the same.
    >
    >
    >
    > I guess it is happening because the SCP at the time of creating the
    > DCM file unpacks the DCM file and then writes it again.
    > Can you please tell if what I am saying in the above line is correct?
    > And how can i correct this.
    >
    > I am using DVTk as the SCP.
    >
    > Thanks and Regards,
    > LalitSRana
    >


  3. Re: Implementation Version Name && Implementation Class UID Issues

    On Jun 4, 3:42*pm, David Clunie wrote:
    > Hi
    >
    > There is nothing to correct, since that is the way it is supposed
    > to be.
    >
    > Thesre are attributes of the meta-information header, which is
    > written when a network dataset is recorded in a file; these are
    > not transmitted on the network and they describe the file (set)
    > creator, not the originator of the dataset.
    >
    > David
    >
    >
    >
    > Lalit wrote:
    > > Hi,

    >
    > > Please help me with this question:

    >
    > > I am sending a Storage IOD (Dicom file) from a SCU to the SCP for
    > > storage.

    >
    > > When I compare the values of Implementation Class UID (0002,0012) &
    > > Implementation Version Name (0002,0013) in the SCU and SCP DCM files,
    > > they are not the same.

    >
    > > I guess it is happening because the SCP at the time of creating the
    > > DCM file unpacks the DCM file and then writes it again.
    > > Can you please tell if what I am saying in the above line is correct?
    > > And how can i correct this.

    >
    > > I am using DVTk as the SCP.

    >
    > > Thanks and Regards,
    > > LalitSRana- Hide quoted text -

    >
    > - Show quoted text -


    Thanks David,

    So this means, whatever I am setting at the SCU is of no relevance to
    the SCP and won't be considered there (because it's not transmitted on
    the network).

    Thanks again...

    Regards,
    Lalit.

  4. Re: Implementation Version Name && Implementation Class UID Issues

    Hello Lalit,

    Lalit wrote:
    [...]
    > So this means, whatever I am setting at the SCU is of no relevance to
    > the SCP and won't be considered there (because it's not transmitted on
    > the network).


    Umh, not really: when setting up an Association, the Implementation
    Version UID and the Implementation Name are in transferred the
    negotiation P-DATA and can be inspected in the application context.

    This could give an Application the ability to fix quirky stuff from a
    well known application (though I never seen that in real wildlife yet).

    So, please do not put nonsense in your SCU's code ;-)

    But the Media Storage Implementation is in you case different from the
    SCU, so the Media File is written with its Implementation Identification
    - if you have quirky Media files, you may react to this...

    However, the DICOM Data Set starts with the (0008,xxxx) Attributes, all
    "lower" Attributes are not result of network transfer, but of the Media
    Storage Application.

    Did you get the point?

    Hope this helps,


    Peter

+ Reply to Thread