Instance delete message in DICOM?? - DICOM

This is a discussion on Instance delete message in DICOM?? - DICOM ; Does anyone know of work going on to define an Instance delete message in DICOM? This woudl be used to tell a DICOM system to delete an image, series or study instance. Thanks SomeHuman...

+ Reply to Thread
Results 1 to 4 of 4

Thread: Instance delete message in DICOM??

  1. Instance delete message in DICOM??

    Does anyone know of work going on to define an Instance delete message
    in DICOM?
    This woudl be used to tell a DICOM system to delete an image, series
    or study instance.

    Thanks
    SomeHuman

  2. Re: Instance delete message in DICOM??

    On Oct 17, 5:57*pm, SomeHuman wrote:
    > Does anyone know of work going on to define an Instance delete message
    > in DICOM?
    > This woudl be used to tell a DICOM system to delete an image, series
    > or study instance.
    >
    > Thanks
    > SomeHuman


    DICOM does not define services (SOP Classes) for deletion of stored
    Composite Objects.

    But current draft of IHE Radiology Scheduled Workflow II White Paper
    [ ftp://ftp.ihe.net/Radiology/iheyr10-...h%20review.doc
    ]
    announces to define a transaction (RAD-66: Image Rejection Note
    Stored) using a Key Object Selection Document with a particular
    Document Title "Rejected for Patient Safety" which refers the objects
    which shall be deleted (or otherwise hidden) by the Image Manager. (s.
    p.30f).

    gunter

  3. Re: Instance delete message in DICOM??

    On Oct 20, 10:55*am, gunter zeilinger wrote:
    > On Oct 17, 5:57*pm, SomeHuman wrote:
    >
    > > Does anyone know of work going on to define an Instance delete message
    > > in DICOM?
    > > This woudl be used to tell a DICOM system to delete an image, series
    > > or study instance.

    >
    > > Thanks
    > > SomeHuman

    >
    > DICOM does not define services (SOP Classes) for deletion of stored
    > Composite Objects.
    >
    > But current draft of IHE Radiology Scheduled Workflow II White Paper
    > [ftp://ftp.ihe.net/Radiology/iheyr10-.../2008.09.15-SW...
    > ]
    > announces to define a transaction (RAD-66: Image Rejection Note
    > Stored) using a Key Object Selection Document with a particular
    > Document Title "Rejected for Patient Safety" which refers the objects
    > which shall be deleted (or otherwise hidden) by the Image Manager. (s.
    > p.30f).
    >
    > gunter


    any idea when this will become final ?

    yours arnold

  4. Re: Instance delete message in DICOM??

    Hi Arnold

    The CP to add the code for "Rejected for Patient Safety" has already
    been added to the DICOM standard and is final text. See CP 885:

    ftp://medical.nema.org/medical/dicom/final/cp885_ft.pdf

    Note, however, that this is only a means of conveying from one
    system to another that a set of instances is somehow "bad".

    It does NOT imply or require any specific action on the part of
    the recipient, such as to remove from visibility or to delete
    the set of "bad" instances. There is nothing in DICOM about that
    (yet).

    As for IHE, the use of this code in a KOS in a more formally
    defined "transaction" is specified in the Draft for Trial
    Implementation for Mammography Acquisition Workflow:

    http://www.ihe.net/Technical_Framewo...2008-07-03.pdf

    Look towards the end of the document for Image Rejection Note Stored
    (transaction RAD-66), which addresses the use of two codes:

    - (113001, DCM, "Rejected for Quality Reasons")
    - (113037, DCM, "Rejected for Patient Safety Reasons")

    Note the difference in expected actions of the Image Manager/Archive
    defined therein:

    - for quality issues - either return the KOS, or hide the KOS & images
    - for patent safety - hide the KOS and the images

    The "hiding" is defined with respect to queries to and instance
    availability notification from the IM/IA. The MAWF supplement
    does not specifically mention that anything hidden should not
    be burned on PDI by Media Creators (will need to add a CP for
    that).

    The MAWF profile is to all practical intents and purposes "finished"
    as per IHE procedures, and vendors are expected to implement it for
    connectathons and in products now.

    Progress on generalizing this in SWF 2.0 can be expected to be slower
    for many reasons, but now that the precedent has been established
    for handling rejected images this way, there is no reason for
    folks not to implement it (even though there may be other more
    sophisticated mechanisms available in the future, perhaps).

    David

    Arnold Maderthaner wrote:
    > On Oct 20, 10:55 am, gunter zeilinger wrote:
    >> On Oct 17, 5:57 pm, SomeHuman wrote:
    >>
    >>> Does anyone know of work going on to define an Instance delete message
    >>> in DICOM?
    >>> This would be used to tell a DICOM system to delete an image, series
    >>> or study instance.
    >>> Thanks
    >>> SomeHuman

    >> DICOM does not define services (SOP Classes) for deletion of stored
    >> Composite Objects.
    >>
    >> But current draft of IHE Radiology Scheduled Workflow II White Paper
    >> [ftp://ftp.ihe.net/Radiology/iheyr10-.../2008.09.15-SW...
    >> ]
    >> announces to define a transaction (RAD-66: Image Rejection Note
    >> Stored) using a Key Object Selection Document with a particular
    >> Document Title "Rejected for Patient Safety" which refers the objects
    >> which shall be deleted (or otherwise hidden) by the Image Manager. (s.
    >> p.30f).
    >>
    >> gunter

    >
    > any idea when this will become final ?
    >
    > yours arnold


+ Reply to Thread