AGFA HE/001132 Benutzerhandbuch
HE/001132
Page 10 of 92
Document No. 001132, Revision 2.0
Agfa HealthCare
NodeID Livelink : 14140190
14 June, 2007
successfully obtained. An image that has been successfully sent to an archive cannot be sent to that archive
again.
again.
2.1.2.2
Functional Definition of DICOM Print Application Entity
The DICOM Print Application Entity prints images on a remote AE (A configured Printer). It is associated with
the local real-world activity “Request to print film sheets”. A job will only be marked as “successful” when the
sheet is successfully printed.
the local real-world activity “Request to print film sheets”. A job will only be marked as “successful” when the
sheet is successfully printed.
2.1.2.3
Functional Definition of RIS Application Entity
The RIS Application Entity receives Worklist information from a remote AE. It is associated with the local
real-world activity “Query RIS”. This can be triggered manually by clicking the “Query RIS” button or triggered
automatically at a specified interval. When properly configured, the RIS can also be queried by Accession
Number.
real-world activity “Query RIS”. This can be triggered manually by clicking the “Query RIS” button or triggered
automatically at a specified interval. When properly configured, the RIS can also be queried by Accession
Number.
The RIS query can be configured in different ways (for the possible configurations, see §
). The
two that are relevant for DICOM are described in the following paragraphs:
2.1.2.3.1
DICOM Modality Worklist
The use of DICOM Modality Worklist (DMWL) queries the RIS by means of query keys. The query keys can
be changed by the user in the configuration tool (see §
be changed by the user in the configuration tool (see §
). Based on these keys, the worklist will be
populated during the next RIS query.
2.1.2.3.2
DICOM Modality Worklist query on Accession Number
By querying by Accession Number, only the worklist items that contain the specified Accession Number are
returned. These results are parsed, mapped and shown as a Worklist.
returned. These results are parsed, mapped and shown as a Worklist.
2.1.2.4
Functional Definition of MPPS Application Entity
The MPPS Application Entity sends MPPS information to a remote AE when MPPS reporting is configured.
The local real-world activities “Acquire Images”, “Archive Images” and “Print Images” can trigger the creation
of an MPPS instance. This can also be done by adding a new SOP Instance UID to a MPPS, by adding a
Dose to a MPPS or by adding a Print Sheet to a MPPS. The local real-world activity “Close Session” or the
modification of the session’s Accession Number will complete the MPPS. This happens completely
automatically and no user intervention is possible.
The local real-world activities “Acquire Images”, “Archive Images” and “Print Images” can trigger the creation
of an MPPS instance. This can also be done by adding a new SOP Instance UID to a MPPS, by adding a
Dose to a MPPS or by adding a Print Sheet to a MPPS. The local real-world activity “Close Session” or the
modification of the session’s Accession Number will complete the MPPS. This happens completely
automatically and no user intervention is possible.