Philips Hd9 Owners Manual
Have a look at the manual Philips Hd9 Owners Manual online for free. It’s possible to download the document as PDF or print. UserManuals.tech offer 619 Philips manuals and user’s guides for free. Share the user manual or guide on Facebook, Twitter or Google+.
HD9 1.1.x DICOM Conformance Statement 989605375630044 Rev. B Page 21 Table 4.2-11 STORAGE COMMITMENT COMMUNICATION FAILURE BEHAVIOR Exception Behavior Timeout The Association is aborted using A-ABORT and the storage commitment job is marked as failed. Association aborted by the SCP or network layers The storage commitment job is marked as failed. 4.2.1.3.1.4.2 Storage Commitment Notification (N-EVENT-REPORT) The Storage AE is capable of receiving an N-EVENT-REPORT notification if it has successfully negotiated a Presentation Context for the Storage Commitment Push Model. Upon receipt of an N-EVENT-REPORT the timer associat ed with the Transaction UID will be cancelled. The behavior of Storage AE when receiving Event Types within the N-EVENT-REPORT is summarized in the Table below. Table 4.2-12 STORAGE COMMITMENT N-EVENT-REPORT BEHAVIOR Event Type Name Event Type ID Behavior Storage Commitment Request Successful 1 The commit status is set to “COMPLETED” for each exam in the exam list. Auto deletion for committed exam is not supported. Storage Commitment Request Complete – Failures Exists 2 The commit status is set to “CN” for each exam in the exam list. The Referenced SOP Instances under Failed SOP Sequence (0008,1198) are logged. A send job that failed storage commitment will not be automatically restarted but can be restarted by user interaction. The reasons for returnin g specific status codes in an N-EVENT-REPORT response are summarized in the Table below. Table 4.2-13 STORAGE COMMITMENT N-EVENT-REPORT RESPONSE STATUS REASONS Service Status Further Meaning Error Code Behavior Success Success 0000 The Storage commitment result has been successfully received. Failure Unrecognized Operation 0211H The Transaction UID in the N-EVENT-REPORT request is not (was never issued within an N-ACTION request). Failure No Such Event Type 0113H An invalid Event Type ID was supplied in the N- EVENT-REPORT request. Failure Processing Failure 0110H An internal error occurred during processing of the N- EVENT-REPORT.
4.2.1.3.1.5 SOP Specific Conformance for Verification The behavior when encountering status codes in a C-ECHO response is summarized in the Table below: Table 4.2-14 VERIFICATION C-ECHO RESPONSE STATUS HANDLING BEHAVIOR Service Status Further Meaning Error Code Behavior Success Success 0000 Verification Status is set to ‘Normal’. Any other status code * * Verification Status is set to ‘Failed’. The behavior of Storage AE during communication failure is summarized in the Table below: Table 4.2-15 VERIFICATION COMMUNICATION FAILURE BEHAVIOR Exception Behavior The Association is aborted using A-ABORT and the verification job is marked as failed. Timeout Association aborted by the SCP or network laye rs The verification job is marked as failed. 4.2.1.4 Association Acceptance Policy 4.2.1.4.1 Activity – Receive Storage Commitment Response 4.2.1.4.1.1 Description and Sequence of Activities The Storage AE will accept associations in order to receiv e responses to a Storage Commitment Request. Storage AEImage Manager 1. Open Association 2. N-EVENT-REPORT (Stora ge Commitment Response) 3. Close Association Figure 4.2-2 SEQUENCING OF ACTIVITY - RECEI VE STORAGE COMMITMENT RESPONSE HD9 1.1.x DICOM Conformance Statement 989605375630044 Rev. B Page 22 A possible sequence of interactions between the Storage AE and an Image Manager (e.g. a storage or archive device
HD9 1.1.x DICOM Conformance Statement 989605375630044 Rev. B Page 23 supporting Storage Commitment SO P Classes as an SCP) is illustrated in the Figure above: 1. The Image Manager opens a new association with the Storage AE. 2. The Image Manager sends an N-EVENT-REPORT request notifying the Storage AE of the status of a previous Storage Comm itment Request. The Storage AE replies with an N-EVENT-REPORT response confirming receipt. 3. The Image Manager closes the association with the Storage AE. 4.2.1.4.1.2 Accepted Presentation Contexts The Storage AE will accept Presentation C ontexts as shown in the Table below. Table 4.2-16 ACCEPTABLE PRESENTATION CONTEXTS FOR ACTIVITY RECEIVE STORAGE COMMITMENT RESPONSE Presentation Context Table Abstract Syntax Transfer Syntax Role Ext. Neg. Name UID Name List UID List Storage Commitment Push Model 1.2.840.10008.1.20. 1 Explicit VR Little Endian Implicit VR Little Endian Explicit VR Big Endian 1.2.840.10008.1.2.1 1.2.840.10008.1.2 1.2.840.10008.1.2.2 SCU* None Verification 1.2.840.10008.1.1 Explicit VR Little Endian Implicit VR Little Endian Explicit VR Big Endian 1.2.840.10008.1.2.1 1.2.840.10008.1.2 1.2.840.10008.1.2.2 SCP None * Reverse-Role Negotiation only. 4.2.1.4.1.3 SOP Specific Conformance for Storage Commitment SOP Class 4.2.1.4.1.3.1 Storage Commitment Notifications (N-EVENT-REPORT) Upon receipt of an N-EVENT-REPORT the timer associat ed with the Transaction UID will be cancelled. The behavior of Storage AE when receiving Event Types within the N-EVENT-REPORT is summarized in Table 4.2-12. The reasons for retu rning specific status codes in an N- EVENT-REPORT response are summarized in Table 4.2-13. 4.2.1.4.1.4 SOP Specific Conformance for Verification SOP Class The Storage AE provides standard conformance to the Verifi cation SOP Class as an SCP. If the C-ECHO request was successfully received, a 0000 (Success) status code will be re turned in the C-ECHO response.
HD9 1.1.x DICOM Conformance Statement 989605375630044 Rev. B Page 24 4.2.2 Workflow Application Entity Specification 4.2.2.1 SOP Classes HD9 provides Standard Conformance to the following SOP Classes: Table 4.2-17 SOP CLASSES FOR AE WORKFLOW SOP Classes SOP Class UID SCU SCP Modality Worklist Information Model – FIND 1.2.840.10008.5.1.4.31 Yes No Modality Performed Procedure Step 1.2.840.10008.3.1.2.3.3 Yes No 4.2.2.2 Association Establishment Policy 4.2.2.2.1 General The DICOM standard application context name for DICOM 3.0 is always proposed. Table 4.2-18 DICOM APPLICATION CONTEXT FOR AE WORKFLOW Application Context Name 1.2.840.10008.3.1.1.1 4.2.2.2.2 Number of Associations HD9 initiates one Association at a time for a Worklist request. Table 4.2-19 NUMBER OF ASSOCIATIONS INITIATED FOR AE WORKFLOW Maximum number of simultaneous Associations 1 4.2.2.2.3 Asynchronous Nature HD9 does not support asynchronous communications (multipl e outstanding transactions over a single Association) Table 4.2-20 ASYNCHRONOUS NATURE AS A SCU FOR AE WORKFLOW Maximum number of outstanding asynchronous transactions 1 4.2.2.2.4 Implementation Identifying Information The implementation information for this Application Entity is: Table 4.2-21 DICOM IMPLEMENTATION CLASS AND VERSION FOR AE WORKFLOW Implementation Class UID 1.3.46.670589.14.2 Implementation Version Name HD9 1.1
4.2.2.3 Association Initiation Policy
4.2.2.3.1 Activity – Worklist Update
4.2.2.3.1.1 Description and Sequencing of Activities
The request for a Worklist Update is initiated by user interact ion or automatically at specific time intervals, configurable
by the user.
The interactive Worklist Query will display a dialog for enter ing data as search criteria. When the Query is started on
your request, only the data from the dialog w ill be inserted as matching keys into the query.
With automated worklist queries the HD9 always requests all items for a Scheduled Procedure Step Start Date (actual
date) or configured value or range, Modality (US) and Scheduled Station AE Title (optional).
Upon initiation of the request, the HD9 will build an Identifier for the C-FIND request, will initiate an Association to send
the request and will wait for Worklist re sponses. After retrieval of all responses, HD9 will ac cess the local database to
add patient demographic data. The results will be displayed in a separate list, which will be cleared with the next
worklist update.
HD9 will initiate an Association in order to issue a C-FIND request according to the Modality Worklist Information Model.
Workflow AEDepartment Scheduler
1. Open Association
2. C-FIND Request (Worklist Query)
3. C-FIND Response (Worklist Item) - Status=Pending
4. C-FIND Response (Worklist Item) - Status=Pending
5. C-FIND Response - Status=Success
6. Close Association
7. Select Worklist Item
Figure 4.2-3
SEQUENCING OF ACTIVITY - WORKLIST UPDATE
A possible sequence of interactions between the Workflow AE and a Departmental Scheduler (e.g. a device such as a
RIS or HIS which supports the Modality Worklist SOP Class as an SCP) is illustrated in the figure above.
HD9 1.1.x DICOM Conformance Statement
989605375630044 Rev. B Page 25
HD9 1.1.x DICOM Conformance Statement 989605375630044 Rev. B Page 26 4.2.2.3.1.2 Proposed Presentation Contexts HD9 will propose Presentation Contexts as shown in the following table: Table 4.2-22 PROPOSED PRESENTATION CONTEXTS FOR ACTIVITY WORKLIST UPDATE Presentation Context Table Abstract Syntax Transfer Syntax RoleExt. Neg. Name UID Name List UID List Modality Worklist Information Model - FIND 1.2.840.10008. 5.1.4.31 Explicit VR Little Endian Implicit VR Little Endian Explicit VR Big Endian 1.2.840.10008.1.2.1 1.2.840.10008.1.2 1.2.840.10008.1.2.2 SCU None 4.2.2.3.1.3 SOP Specific Conformance for Modality Worklist The behavior of HD9 when encountering status codes in a M odality Worklist C-FIND response is summarized in the table below. If any other SCP response status than “Succe ss” or “Pending” is received by HD9, a message, ”Query failed” will appear on the user interface. Table 4.2-23 MODALITY WORKLIST C-FIND RESPONSE STATUS HANDLING BEHAVIOR Service Status Further Meaning Error Code Behavior Success Matching is complete 0000 The SCP has Completed the operation successfully. Pending Matches are continuing FF00 Continue. Pending Matches are continuing - Warning that one or more Optional Keys were not supported FF01 Continue. * * Any other status code. The Association is aborted using A-Abort and the Worklist is marked as failed. The behavior of HD9 during communication failure is summarized in the table below. Table 4.2-24 MODALITY WORKLIST COMMUNICATION FAILURE BEHAVIOR Exception Behavior Timeout The Association is aborted using A-ABORT and the worklist query is marked as failed. Association aborted by the SCP or network la yers The Worklist query is marked as failed. Acquired images will always use the Study Instance UID specified for the Schedu led Procedure Step (if available). If an acquisition is unscheduled, a Study Instance UID will be generated locally. The Table below provides a description of the HD9 Worklist Request Identifier and specifies the attributes that are copied into the images. Unexpected attributes returned in a C-FIND response are ignored.
HD9 1.1.x DICOM Conformance Statement 989605375630044 Rev. B Page 27
Requested return attributes not supported by the SCP are se
t to have no value. Non-matching responses returned by
the SCP due to unsupported optional matching keys are ignore d. No attempt is made to filter out possible duplicate
entries.
Table 4.2-25
WORKLIST REQUEST IDENTIFIER
Module Name
Attribute Name Tag VR
M R Q D IOD
Scheduled Procedure Step
Scheduled Procedure Step Sequence 0040,0100 SQ x
> Scheduled Station AET 0040,0001 AE (S) x x
> Scheduled Procedure Step Start Date 0040,0002 DA S,R x x x
> Scheduled Procedure Step Start Time 0040,0003 TM x x
> Modality 0008,0060 CS S x x
> Scheduled Performing Physicians Name 0040,0006 PN x
> Scheduled Procedure Step Description 0040,0007 LO x x x
> Scheduled Station Name 0040,0010 SH x
> Scheduled Procedure Step Location 0040,0011 SH x
> Scheduled Protocol Code Sequence 0040,0008 SQ x x
> Scheduled Procedure Step ID 0040,0009 SH x x
Requested Procedure
Requested Procedure ID 0040,1001 SH x x x
Reason for the Requested Procedure 0040,1002 LO x x
Requested Procedure Description 0032,1060 LO x x
Study Instance UID 0020,000D UI x x
Referenced Study Sequence 0008,1110 SQ x x
Requested Procedure Code Sequence 0032,1064 SQ x x
Imaging Service Request
Accession Number 0008,0050 SH x x x
Requesting Physician 0032,1032 PN x
Referring Physicians Name 0008,0090 PN x x x
Reason for the Imaging Service Request 0040,2001 LO x x
Visit Status
Current Patient Location 0038,0300 LO x
Patient Identification
Patient’s Name 0010,0010 PN x x x
Patient ID 0010,0020 LO x x x
Patient Demographic
Patients Birth Date 0010,0030 DA x x x
Patients Sex 0010,0040 CS x x x
Patient’s Size 0010,1020 DS x x x
Patients Weight 0010,1030 DS x x x
The above table should read as follows:
Module Name: The Name of the associated module for supported worklist attributes.
Attribute Name: Attributes supported to build a HD9 Worklist Request Identifier.
Tag: DICOM tag for this attribute.
HD9 1.1.x DICOM Conformance Statement 989605375630044 Rev. B Page 28 VR: DICOM VR for this attribute. M: Matching keys for (automatic) Worklist Update. An “S ” indicates that HD9 supplies an attribute value for Single Value Matching or additional specific tags indicated by “(S)”; an “R” will indicate Range Matching. R: Return keys. An ”X” will indicate that HD9 will supply this attribute as Return Key with zero length for Universal Matching. Q: Interactive Query Key. An “X” will indicate that HD9 w ill supply this attribute as matching key, if entered in the Setup Dialog. D: Displayed keys. An “X” indicates that this worklist attribute is displayed to the user during a patient registration dialog. IOD: An “X” indicates that this Worklist attribute is incl uded into all Object Instances created during performance of the related Procedure Step. 4.2.2.3.2 Activity – Acquire Images 4.2.2.3.2.1 Description and Sequencing of Activities An Association to the configured MPPS SCP system is established immediately after the first image is acquired to send the MPPS N-Create message. The “End Exam” button causes a message box in which a user can select “COMPLETED” or “DISCONTINUED” as an MPPS final state. An exam for which an MPPS instance is sent with a state of “COMPLETED” or “DISCONTINUED” can no longer be updated. The HD9 will support creation of “uns cheduled cases” by allowing MPPS Instances to be communicated for locally registered Patients. The HD9 only supports a 1-to-1 relationship between Scheduled and Performed Procedure Steps. HD9 will initiate an Association to issue an: - N-CREATE request according to the CREATE Modality Performed Procedure Step SOP Instance operation, or an: - N-SET request to update t he contents and state of the MPPS according to the SET Modality Performed Procedure Step Information operation. Note: No “DISCONTINUED” status may be sent from HD9.
Workflow AEDepartment Scheduler
2. Open Association
3. N-CREATE (MPPS) - IN PROGRESS
4. Close Association
5. Acquire Images
7. Open Association
9. Close Association
1. Start Exam
6. End Exam
8. N-SET (MPPS) - COMPLETED or DISCONTINUED
Figure 4.2-4
SEQUENCING OF ACTIVITY - ACQUIRE IMAGES
A possible sequence of interactions between the Workflow AE and a Departmental Scheduler (e.g. a device such as a
HD9 1.1.x DICOM Conformance Statement
989605375630044 Rev. B Page 29
HD9 1.1.x DICOM Conformance Statement 989605375630044 Rev. B Page 30 RIS or HIS which supports the MPPS SOP Class as an SCP) is illustrated in the figure above. 4.2.2.3.2.2 Proposed Presentation Contexts HD9 will propose Presentation Contexts as shown in the following table: Table 4.2-26 PROPOSED PRESENTATION CONTEXTS FOR RE AL-WORLD ACTIVITY ACQUIRE IMAGES Presentation Context Table Abstract Syntax Transfer Syntax RoleExt. Neg. Name UID Name List UID List Modality Performed Procedure Step 1.2.840.10008. 3.1.2.3.3 Explicit VR Little Endian Implicit VR Little Endian Explicit VR Big Endian 1.2.840.10008.1.2.1 1.2.840.10008.1.2 1.2.840.10008.1.2.2 SCU None 4.2.2.3.2.3 SOP Specific Conformance for MPPS The behavior of HD9 when encountering status codes in an MPPS N-CREATE or N-SET response is summarized in the Table below. If any other SCP response status than “S uccess” or “Warning” is received by HD9, a message “MPPS failed” will appear on the user interface. Table 4.2-27 MPPS N-CREATE / N-SET RESPONSE STATUS HANDLING BEHAVIOR Service Status Further Meaning Error Code Behavior Success Success 0000 The SCP has Completed the operation successfully. Warning Attribute Value Out of Range 0116H The MPPS Operation is considered successful. * * Any other status code. The Association is aborted using A-Abort and the MPPS is marked as failed. The behavior of HD9 during communication failure is summarized in the table below: Table 4.2-28 MPPS COMMUNICATION FAILURE BEHAVIOR Exception Behavior Timeout The Association is aborted using A-ABORT and the MPPS job is marked as failed. Association aborted by the SC P or network layers The MPPS job is marked as failed.