MPPS Notification - DICOM

This is a discussion on MPPS Notification - DICOM ; Hello all, I like to add this service into my server, i read about it and i know its purpose and the procedures to perform it but i don't know how the MPPS SCP knows the other PACS addresses that ...

+ Reply to Thread
Results 1 to 5 of 5

Thread: MPPS Notification

  1. MPPS Notification

    Hello all,

    I like to add this service into my server, i read about it and i know
    its purpose and the procedures to perform it but i don't know how the
    MPPS SCP knows the other PACS addresses that it need to notify, i mean
    is there a DICOM method so other PACS register with the MPPS SCP to
    tell it that it wants to be notified? or this is an application
    specific and i need to handle this in the server configuration, like
    writting the adresses that my server should notify in the database?

    Hope my question is clear and thanks for any help.


  2. Re: MPPS Notification

    > I like to add this service into my server, i read about it and i know
    > its purpose and the procedures to perform it but i don't know how the
    > MPPS SCP knows the other PACS addresses that it need to notify, i mean
    > is there a DICOM method so other PACS register with the MPPS SCP to
    > tell it that it wants to be notified?


    This is application specific, i.e. you need to maintain some kind of
    system configuration with the list of SCUs that should be notified.
    Also note that the IHE initiative is actually not using MPPS notification
    and MPPS get, but has defined a different approach called a "PPS manager",
    that is, an application that acts both as a SCP and SCU of the normal
    MPPS SOP class. The PPS manager receives MPPS messages (N-CREATE and N-SET)
    and forwards them to a list of (one or more) MPPS SCPs, thus removing the
    need for the N-GET and N-EVENT-REPORT based services.

    Regards,
    Marco Eichelberg
    OFFIS

  3. Re: MPPS Notification


    Marco Eichelberg wrote:
    > > I like to add this service into my server, i read about it and i know
    > > its purpose and the procedures to perform it but i don't know how the
    > > MPPS SCP knows the other PACS addresses that it need to notify, i mean
    > > is there a DICOM method so other PACS register with the MPPS SCP to
    > > tell it that it wants to be notified?

    >
    > This is application specific, i.e. you need to maintain some kind of
    > system configuration with the list of SCUs that should be notified.
    > Also note that the IHE initiative is actually not using MPPS notification
    > and MPPS get, but has defined a different approach called a "PPS manager",
    > that is, an application that acts both as a SCP and SCU of the normal
    > MPPS SOP class. The PPS manager receives MPPS messages (N-CREATE and N-SET)
    > and forwards them to a list of (one or more) MPPS SCPs, thus removing the
    > need for the N-GET and N-EVENT-REPORT based services.
    >
    > Regards,
    > Marco Eichelberg
    > OFFIS


    Thanks Marco for your reply, yah i noticed that the IHE didn't mention
    anything about the MPPS Notification or GET and thats why i have
    questions that i didn't find answer on.
    Also i noticed the MPPS Manager and how it works, and i also found some
    softwares implement the forwarding like IHE recommend, but still can't
    figure how forwarding to the N-CREATE and N-SET will remove the need
    for N-GET and N-EVENT-REPORT, maybe we won't need the Reporting but not
    the N-GET, also forwarding may cost more than just reporting.

    I believe that i need to implement all these services together since
    they are all important and each one serve a specific different need.

    Thanks again.
    Zaid H. Safadi


  4. Re: MPPS Notification

    > Also i noticed the MPPS Manager and how it works, and i also found some
    > softwares implement the forwarding like IHE recommend, but still can't
    > figure how forwarding to the N-CREATE and N-SET will remove the need
    > for N-GET and N-EVENT-REPORT [...]


    All imaging modalities I have ever seen that support MPPS do this in the form of the normal MPPS SOP
    class, i.e. using N-CREATE and N-SET messages. In this context, The MPPS notification and retrieve
    services are useful if and only if the MPPS information needs to be distributed to more than one
    recipient (e.g. the PACS and the RIS). The modality will typically only send the MPPS messages to a
    single SCP. This SCP could now maintain a list of secondary recipients and, for each incoming
    N-CREATE or N-SET message, issue an N-EVENT-REPORT to each of them. The secondary recipients could
    then connect to the primary MPPS server and use N-GET to retrieve the latest information. Note that
    N-GET is only useful when combined with N-EVENT-REPORT because the N-GET client needs to know the
    SOP Instance UID of the MPPS instance to retrieve, and the event report is the only way of making
    this information available. With the construct of the PPS manager, the information is distributed to
    all interested "parties" using N-CREATE and N-SET messages, so there is no point in doing the same
    thing with N-EVENT-REPORT and N-GET messages.

    Regards,
    Marco Eichelberg
    OFFIS


  5. Re: MPPS Notification

    > All imaging modalities I have ever seen that support MPPS do this in the form of the normal MPPS SOP
    > class, i.e. using N-CREATE and N-SET messages. In this context, The MPPS notification and retrieve
    > services are useful if and only if the MPPS information needs to be distributed to more than one
    > recipient (e.g. the PACS and the RIS). The modality will typically only send the MPPS messages to a
    > single SCP. This SCP could now maintain a list of secondary recipients and, for each incoming
    > N-CREATE or N-SET message, issue an N-EVENT-REPORT to each of them. The secondary recipients could
    > then connect to the primary MPPS server and use N-GET to retrieve the latest information. Note that
    > N-GET is only useful when combined with N-EVENT-REPORT because the N-GET client needs to know the
    > SOP Instance UID of the MPPS instance to retrieve, and the event report is the only way of making
    > this information available. With the construct of the PPS manager, the information is distributed to
    > all interested "parties" using N-CREATE and N-SET messages, so there is no point in doing the same
    > thing with N-EVENT-REPORT and N-GET messages.
    >
    > Regards,
    > Marco Eichelberg
    > OFFIS


    I believe you are right, forwarding may be able to replace the need for
    the N-GET and N-EVENT-REPORT but it should be standardized so everyone
    can implement with forwarding customization, I mean some PACS system
    may need to store the MPPS SOP other may need to retrieve related
    images and so on, but until this became a standard then we should
    support the other services mentioned in the standard so all DCIOM
    systems can integrate together.

    Anyway thanks a lot this was so useful.

    Zaid H. Safadi


+ Reply to Thread