Philips Hd 7 User Manual

							 
HD7/HD7XE 3.0 DICOM Conformance Statement 000245000000008 Rev. A  Page 11 
Settings that may be customized are: 
Query Title, Start Date or Date Range, AE Title (This sys tem, Any or Another specific), and Modality (Ultrasound only 
or All Modalities).  When the Workflow AE establishes an As sociation to a remote AE, a MWL C-Find-Rq message is 
sent to the MWL server.  The server will transfer all matchi ng worklist items via the open Association. The results of a 
successful Worklist Update  will overwrite the data in the Worklist display.   
There is no queue management for Worklist. 
The Workflow AE performs the creation of a MPPS Instance automatically when the PDE is closed causing an MPPS 
N-Create-Rq message to be sent to t he MPPS server containing the status of “IN PROGRESS”.  At the end of the 
exam, when “Completed” or “Cancel” ar e selected, an MPPS N-Set- Rq message is sent containing “COMPLETED” or 
“DISCONTINUED” respectively.  MPPS message queues  are listed in the Job Manager (CNTL-J) window. 
4.1.2.3  Functional Definition of  Hardcopy Application Entity  
The existence of a print queue will activate the Hardcopy AE.   An association is established with the printer(s) and the 
printer’s status determined.  If the pr inter is operating normally, the film sheet  print requests will be sent.  If the printer 
is not operating normally, the print queue will set to a “Fa iled” state and can be restarted by the user via the queue 
management interface.  In the case that a user has both  a BW and a Color DICOM printer configured, during an exam 
with “Send as you go Print/Capture” selected, the images that contain color data,  i.e., Color Flow Doppler or Chroma, 
will be sent to the Color printer only, and  all other images sent only to the BW printer.  There is an embedded retry 
mechanism that retries User Recoverable errors fo r up to 1 hour, waiting 20 seconds between attempts. 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
  
						

							 
HD7/HD7XE 3.0 DICOM Conformance Statement 000245000000008 Rev. A  Page 12 
Sequencing of Real-World Activities 
StorageHardcopyWorkflowDepartment 
SchedulerPrinterImage 
Manager
1  Query Worklist
 2  Receive Worklist
3 Create MPPS
9 Complete MPPS  6 Print Film Sheet 5 Image Commit Request 
12 Accept Commitment Response(s)
user update 
or poll
10  Store SR Document
4 Store Image(s) as aquired
Close PDE
end exam
store 
completion 
acquire image
end exam
sheet full
commit status  update
8 Discontinued MPPS cancel exam
7 Print Film Sheet (remaining images)
end exam
acquireimages
11 SR Commit Request 
   Note:  Step 8 may occur prior to acquisition of the first image.  
FIGURE 2A: 
SEQUENCING CONSTRAINTS –SEND AS YOU GOCONFIGURATION  
						

							 
HD7/HD7XE 3.0 DICOM Conformance Statement 000245000000008 Rev. A  Page 13 
Figures 2a and 2b illustrate normal scheduled workflow conditions.  
•  Printing to DICOM printers may occur independent of any other DICOM activity. 
•   All selected store, print and workflow devices are sent  data during the exam when configured for “Send as you 
go” or at “Batch” at end of exam or Manually. 
•   Selecting a study from Review for expo rt will send to all selected devices. 
Other workflow situations (e.g. unsch eduled procedure steps) will have other sequencing cons traints.  Printing or 
storage could equally take place after image acquisition. Printi ng could be omitted completely if no printer is connected 
or hardcopies are not required. 
StorageHardcopyWorkflowDepartment
SchedulerPrinterImage
Manager
1  Query Worklist
 2  Receive Worklist
4 Create MPPS
7 Discontinue or Complete MPPS 6 Print All Film Sheets
8 Image and SR Document Commit Request
10 Accept Commitment Response
user update
or query
5 Store All Images and Report
end exam
store
completion
end exam
commit status
update
end exam
cancel or
end exam
optional
append 9 Optional Append (no PPS)
 3  Acquire Images
 
FIGURE 2B: 
SEQUENCING CONSTRAINTS – CLOSE STUDY CONFIGURATION  
						

							 
HD7/HD7XE 3.0 DICOM Conformance Statement 000245000000008 Rev. A  Page 14 
4.2 AE SPECIFICATIONS 
4.2.1  Storage Application Entity Specification 
4.2.1.1 SOP Classes 
HD7/HD7XE 3.0 provide Standard Extended Conformance to the following SOP Classes: 
Table 3 
SOP CLASSES FOR AE STORAGE 
SOP Class Name  SOP Class UID SCU SCP 
US Image Storage  1.2.840.10008.5.1.4.1.1.6.1 Yes  No 
US Multiframe Image Storage  1.2.840.10008.5.1.4.1.1.3.1 Yes  No 
Comprehensive Structured Report Storage 1.2.840.10008.5.1.4.1.1.88.33  Yes No 
Storage Commitment Push Model  1.2.840.10008.1.20.1  Yes No 
 
4.2.1.2 Association Establishment Policy 
4.2.1.2.1 General 
The DICOM standard application context name  for DICOM 3.0 is always proposed: 
Table 4 
DICOM APPLICATION CONTEXT FOR AE STORAGE 
Application Context Name  1.2.840.10008.3.1.1.1 
 
 
The PDU size is configurable with a minimum size of 100 and a maximum size of 16,000.                                          
The default PDU size is 16,000. 
4.2.1.2.2 Number of Associations 
HD7/HD7XE 3.0 initiates one Association at a time for each destination to which a transfer request is being processed 
in the active job queue list. Three ‘Arc hive’ destinations may be selected simultaneously, but only one job will be active 
at a time, the other(s) remain pending until t he active job is completed or failed.  
Table 5 
NUMBER OF ASSOCIATIONS INITIATED FOR AE STORAGE 
Maximum number of simultaneous Associations  5, 1 for each configured storage device 
One Primary Storage Server, one Secondary Storage Server, one Storage Commitment Server, one SR Storage 
Server and one SR Storage Commitment Server. 
HD7/HD7XE 3.0 accepts Associations  for N-EVENT-REPORT notifications for the Storage Commitment Push Model 
SOP Class. 
Table 6 
NUMBER OF ASSOCIATIONS ACCEPTED FOR AE STORAGE 
Maximum number of simultaneous Associations  1 
 
4.2.1.2.3 Asynchronous  Nature 
HD7/HD7XE 3.0 does not support asynchronous communication (multiple outstanding transactions over a single 
Association). 
Table 7 
ASYNCHRONOUS NATURE AS A SCU FOR AE STORAGE 
Maximum number of outstanding asynchronous transactions  1 
  
						

							 
HD7/HD7XE 3.0 DICOM Conformance Statement 000245000000008 Rev. A  Page 15 
4.2.1.2.4 Implementation Identifying Information 
The implementation information for this Application Entity is: 
Table 8 
DICOM IMPLEMENTATION CLASS  AND VERSION FOR AE STORAGE 
Implementation Class UID  1.3.46.670589.14.3000.300 
Implementation Version Name  HD7_300 
 
4.2.1.3 Association Initiation Policy 
4.2.1.3.1 Activity – Store Images, Loops and Structured Reports 
4.2.1.3.1.1 Description and Sequencing of Activities 
A user may select exams or individual images from Review and r equest them to be sent to multiple destinations       
(up to 2). Reports may not be selected individually, but are sent when “Close Study” is  pressed, or when an entire 
study is selected from the Review Directory . When the “Send as you go” option is active, the queue is serviced 
continuously during the exam.  There is a default 5-minute tim eout for “Send as you go,” after which the association is 
closed.  Any additional images acquired during the  exam will be sent on a subsequent association.  
If the C-STORE Response from the remote Application contains a status other than Success or Warning, the 
Association is aborted and the related Job is  switched to a failed state. It can be restarted any time by user interaction.   
When a system configured with selected network destinations  is used without the network connected, it is considered 
in “Portable” mode.  Each network status Icon will be Yellow  with status of “Pending” for each study acquired while the 
network was not connected. When returning from portable,  reconnecting the network cable will initiate transfer again. 
If a device is configured for Storage Commitment serv ice, the Storage AE will transmit a separate Storage 
Commitment request (N-ACTION) for images and one for the repo rt, over two separate Associations.   The Storage AE 
can only receive an N-EVENT-REPORT request in a separate subsequent association initiated by the SCP employing 
PDU 54H SCP/SCU Role Negotiation in the SCP’s Associ ation Request.  It cannot receive N-Event-Report-Rq 
messages on the same association as the N-Action-Rq. 
Structured reports will contai n all supported measurements an d calculations created by HD7/HD7XE 3.0 even if they 
are not selected for display in the on-system report. Measur ements or calculations that are not supported for export 
are listed in Appendix A in the Mapping Tables for each report and indicated by “Not Mapped” 
OB-GYN study types generate OB-GYN Ultrasound Proce dure Reports and the Adult Echo Study creates Adult 
Echocardiography Reports.  Note that there can be more than  one report instance per exam, so long as they are from 
different study types. 
  
						

							 
HD7/HD7XE 3.0 DICOM Conformance Statement 000245000000008 Rev. A  Page 16 
Storage
AEImage
Manager
1. Open Association
2. C-STORE (Images)
5. C-STORE (Str uctured Report)
8. N-ACTION (Storage Commitment Request for Images)
14. Close Association
end
exam
3. Close Association
12. N-EVENT-REPORT (Storage  Commitment Response - Images)
4. Open Association
6. Close Association
7. Open Association
10. Close Association
11. Open Association
acquire
image
store
completion
commit status
updated
9. N-ACTION (Storage Co mmitment Request for SR)
13. N-EVENT-REPORT (Storage  Commitment Response - SRs)
(Acquire at least one image, make measurements)
 
Figure 3 
SEQUENCING OF ACTIVITY – SEND  IMAGES AND STRUCTURED REPORT 
The sequence of interactions between the Storage AE and an Image Manager is illustrated in Figure 3 for the “Store” 
configuration option “Send as you go.”   The alternative option, “Close Study” differs only in the removal of the loop 
symbol on the ‘acquire images’ activity 
 
   
						

							 
HD7/HD7XE 3.0 DICOM Conformance Statement 000245000000008 Rev. A  Page 17 
4.2.1.3.1.2  Proposed Presentation Contexts  
  HD7/HD7XE 3.0 are capable of proposing the Pres entation Contexts shown in the following table: 
Table 9 
PROPOSED PRESENTATION CONTEXTS  FOR ACTIVITY SEND IMAGES AND SR 
Presentation Context Table 
Abstract Syntax  Transfer Syntax  
 
Role  
Ext. 
Neg. 
Name  UID Name List  UID List 
US Image Storage 1.2.840.10008.5.
1.4.1.1.6.1 Implicit VR Little Endian*
Explicit VR Little Endian 
JPEG Lossy Baseline 
RLE Lossless  1.2.840.10008.1.2 
1.2.840.10008.1.2.1 
1.2.840.10008.1.2.4.50 
1.2.840.10008.1.2.5 
SCU None 
US Multiframe 
Image Storage 
1.2.840.10008.5.
1.4.1.1.3.1 Implicit VR Little Endian 
Explicit VR Little Endian 
JPEG Lossy Baseline 
RLE Lossless  1.2.840.10008.1.2 
1.2.840.10008.1.2.1 
1.2.840.10008.1.2.4.50 
1.2.840.10008.1.2.5 
SCU None 
Comprehensive 
Structured Report 
Storage 
1.2.840.10008.5.
1.4.1.1.88.33 
Implicit VR Little Endian 
Explicit VR Little Endian  1.2.840.10008.1.2 
1.2.840.10008.1.2.1 
SCU None 
Storage 
Commitment Push 
Model 1.2.840.10008.1.
20.1 
Implicit VR Little Endian 
Explicit VR Little Endian  1.2.840.10008.1.2 
1.2.840.10008.1.2.1 
SCU None 
 
*The following applies to both US Image and US Multiframe Images 
JPEG used if image Photometric Interpretation is: 
 YBR_FULL_422 
RLE Lossless is used if image formats are any of: 
  Palette Color, RLE Compressed 
  RGB, RLE Compressed 
  MONOCHROME2, RLE Compressed 
Implicit Little Endian (ILE) transfer Syntax is used when: 
  Palette Color, Uncompressed ILE 
  RGB, Uncompressed ILE 
  MONOCHROME2, Uncompressed ILE 
Explicit Little Endian (ELE) transfer syntax is used when: 
  Palette Color, Uncompressed ELE 
  RGB, Uncompressed ELE 
  MONOCHROME2, Uncompressed ELE 
 
Storage Commitment N-Action Requests  are only sent to devices that are configured as the Storage Commitment 
server, associated with the Primary or Secondary Storage SC Ps that images are sent to. SRs are sent to their own 
configured SCP and are Storage Commitment for  SRs are handled separately from images. 
 
4.2.1.3.1.3  SOP Specific Conformance for Image and Comprehensive Structured Report Storage  
       SOP Classes 
All Image and Comprehensive Structured Report Storage SO P Classes supported by the Storage AE exhibit the same 
behavior, except where stated, and are des cribed together in this section. 
  
						

							 
HD7/HD7XE 3.0 DICOM Conformance Statement 000245000000008 Rev. A  Page 18 
Table 10 describes C-Store response behavior. 
Table 10 
STORAGE C-STORE R ESPONSE STATUS HANDLING BEHAVIOR 
Service  Status  Further Meaning 
Error Code Behavior 
Success Success  0000 The SCP successfully  stored the SOP Instance.  If all SOP 
Instances succeed, the job is marked as complete. 
* *  Any other 
status code. The Association is aborted using A-ABORT and the transfer fails.  
The status is logged. 
 
The behavior of Storage AE during communication failure is summarized in Table 11.
 
Table 11 
STORAGE COMMUNICATION FAILURE BEHAVIOR  
Exception Behavior 
Timeout  Same as Service Status “Refused” in Table 10 above. 
Association aborted by the SCP or network layers Same as Service Status “Refused” in Table 10 above. 
 
The contents of US Image, US Multi-frame Storage and Co mprehensive Structured Report Storage SOP Instances 
conform to the DICOM IOD definitio ns described in Section 8.1.  
4.2.1.3.1.4  SOP Specific Conformance for  Storage Commitment Push Model SOP Class 
4.2.1.3.1.4.1 Storage Commitm ent Operations (N-ACTION) 
The Storage AE will request storage commi tment for the configured device.  
Table 12 summarizes the behavior of Storage  AE when receiving response status codes. 
Table 12 
STORAGE COMMITMENT N-ACTION RESPONSE STATUS HANDLING BEHAVIOR 
Service Status  Further Meaning  Error Code  Behavior 
Success Success  0000  The system waits for the N-Event-Report. 
* *  Any other status code. The commit status remains incomplete for all objects. 
 
Table 13 summarizes the behavior of Storage AE during communication failure. 
Table 13 
STORAGE COMMITMENT COMMUNICATION FAILURE BEHAVIOR 
Exception Behavior 
Timeout  Same as non-success status in Table 12. 
Association aborted by the SCP or network layers Same as non-success status in Table 12. 
 
4.2.1.3.1.4.2  Storage Commitment Tags (N-ACTION) 
The Storage AE will request storage co mmitment using the following tags 
NOTE: Storage Commitment may only be automatically r equested by the system at the end of a study.  
  
						

							 
HD7/HD7XE 3.0 DICOM Conformance Statement 000245000000008 Rev. A  Page 19 
 
Table 13a 
STORAGE COMMITMENT N-ACTION-R EQUEST MESSAGE CONTENTS 
Action Type  Name  Action 
Type ID  Attribute Tag  Requirement Type 
SCU 
Request 
Storage 
Commitment  1 
Transaction UID  (0008,1195) 1 
Referenced SOP Sequence  (0008,1199) 1 
>Referenced SOP Class UID (0008,1150)  1 
>Referenced SOP Instance UID (0008,1155)  1 
 
4.2.1.3.1.4.3 Storage Commitment Notifications (N-EVENT-REPORT) 
The Storage AE can receive an N-EVENT-REPORT notification  received from the SCP via Reverse-role negotiation.  
Table 14 summarizes the behavior of  Storage AE when receiving Event Types within the N-EVENT-REPORT. 
Table 14 
STORAGE COMMITMENT N-EVENT-REPORT BEHAVIOUR 
Event Type Name  Event 
Type ID  Behavior 
Storage Commitment Request 
Successful 
1 
The commit status is set to complete for each object.  
Storage Commitment Request Complete 
– Failures Exist  2 The commit status remains incomplete. The commit 
comment for each object is logged. 
 
The reasons for return
ing specific status codes in an N-EVENT-RE PORT response are summarized in Table 15. 
Table 15 
STORAGE COMMITMENT N-EVENT-REPORT  RESPONSE STATUS REASONS  
Service Status  Further Meaning  Error Code Reasons 
Success Success  0000 The storage commitment  result has been successfully received.  
 
 
4.2.1.3.1.4.4 Storage Commitment Tags  (N-EVENT-REPORT) 
Tags supported for receiving an N-Event-Report message.  
Table 15a lists the tags that are  supported within the N-EVENT-REPORT. 
Table 15a 
STORAGE COMMITMENT N-EVENT-REPORT MESSAGE CONTENTS 
Event Type 
Name  Event 
Type ID Attribute Tag 
Requirement Type 
SCU 
Storage 
Commitment 
Request 
Successful  1 Transaction UID 
(0008,1195) None 
Retrieve AE Title  (0008,0054) None 
Storage Media File-Set ID  (0088,0130) None 
Storage Media File-Set UID  (0088,0140) None  
						

							 
HD7/HD7XE 3.0 DICOM Conformance Statement 000245000000008 Rev. A  Page 20 
Referenced SOP Sequence (0008,1199) None 
>Referenced SOP Class UID (0008,1150)  None 
>Referenced SOP Instance UID (0008,1155)  None 
>Retrieve AE Title  (0008,0054) None 
>Storage Media File-Set ID  (0088,0130) None 
>Storage Media File-Set UID  (0088,0140) None 
Storage 
Commitment 
Request 
Complete – 
Failures Exist 2 Transaction UID 
(0008,1195) None 
Retrieve AE Title  (0008,0054) None 
Storage Media File-Set ID  (0088,0130) None 
Storage Media File-Set UID  (0088,0140) None 
Referenced SOP Sequence  (0008,1199) None 
>Referenced SOP Class UID (0008,1150)  None 
>Referenced SOP Instance UID (0008,1155)  None 
>Retrieve AE Title  (0008,0054) None 
>Storage Media File-Set ID  (0088,0130) None 
>Storage Media File-Set UID  (0088,0140) None 
Failed SOP Sequence  (0008,1198) None 
>Referenced SOP Class UID (0008,1150)  None 
>Referenced SOP Instance UID (0008,1155)  None 
>Failure Reason  (0008,1197) None 
 
 
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  Sequencing of Activities 
The Storage AE accepts associations for pending response s to a Storage Commitment Request only using SCP/SCU 
Role Negotiation; explicitly stating that  the association is initiated by the SCP to the SCU. Any other will be rejected. 
4.2.1.4.1.2 Accepted  Presentation Contexts 
Table 17 summarizes Presentation Cont exts that the Storage AE accepts. 
Table 17 
ACCEPTABLE PRESENTATI ON 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 
Implicit VR Little Endian 
Explicit VR Little Endian  1.2.840.10008.1.2 
1.2.840.10008.1.2.1 
SCU None