Philips Hd 7 User Manual

							 
DICOM 
Conformance Statement 
 
 
 
   HD7/HD7XE 3.0 
   000245000000008 Rev A 
   2010-09-30 
  
 
© Koninklijke Philips Electronics N.V. 2010 
All rights are reserved.   
						

							 
0.1 REVISION HISTORY  
Document  Version  Date of Issue 
Author  Description 
A Sept. 30,  2010  M. Leif Initial Release 
 
 
HD7/HD7XE 3.0 DICOM Conformance St atement 000245000000008 Rev. A  Page 2   
						

							 
HD7/HD7XE 3.0 DICOM Conformance Statement 000245000000008 Rev. A  Page 3  
1  CONFORMANCE STATEMENT OVERVIEW 
The Philips HD7/HD7XE 3.0 Ultrasound sy stems implement the necessary DICOM® services to download 
worklists from an information system, save acquired  US Images and Structured Reports to a network storage 
device, CD or DVD, print to a networked hardcopy devic e and inform the information system about the work 
actually done.   
Table 1 provides an overview of the supported network services. 
Table 1 
NETWORK SERVICES 
Networking SOP Classes  User of
 Service 
(SCU)  Provider of Service (SCP) 
Transfer   
Ultrasound Image Storage 
Yes* No 
Ultrasound Multiframe Image Storage  Yes* No 
Storage Commitment Push Model  Yes* No 
Comprehensive SR  Yes*  No 
Workflow Management    
Modality Worklist  Yes* No 
Modality Performed Procedure Step  Yes*  No 
Print Management   
Basic Grayscale Print Management  Yes* No 
Basic Color Print Management  Yes* No 
  * Purchasable option.   
Table 2 specifies the Media Storage Application Profiles supported. 
Table 2 
MEDIA SERVICES 
Media Storage Application Profile  Write Files (FSC or FSU)  Read Files (FSR) 
Compact Disk - Recordable    
STD-US-SC-MF(1)-CD-R 
for Ultrasound images, compressed and 
uncompressed  Yes / Yes 
Yes 
                                                      
® DICOM is the registered trademark of the  National Electrical Manufacturers Association for its standards publications relating  to digital 
communications of medical information.  
						

							 
HD7/HD7XE 3.0 DICOM Conformance Statement 000245000000008 Rev. A  Page 4  
STD-GEN-CDR 
for Structured Reports  Yes / Yes 
No 
DVD    
STD-US-SC-MF(1)-DVD 
for Ultrasound images, compressed and 
uncompressed  Yes / Yes 
Yes 
STD-GEN-DVD 
for Structured Reports  Yes / Yes 
No 
(1) Note that the “MF” designator includes both Single Frame (SF) and Mullti-frame (MF) ultrasound images. 
 
 
Table 3 
Supported STRUCTURED REPORT Templates 
Concept Name 
OB-GYN Ultrasound Procedure  Report (Template ID 5000) 
Adult Echocardiography Procedure Report (Template ID 5200)  
						

							 
HD7/HD7XE 3.0 DICOM Conformance Statement 000245000000008 Rev. A  Page 5 
2  TABLE OF CONTENTS 
0.1 REVISION HISTORY .......................................................................\
....................................... . 2 
1 CONFORMANCE STATEMENT OVERVIEW ........................................................................\
................. 3 
2 TABLE OF CONTENTS .......................................................................\
...................................... .............. 5 
3 INTRODUCTION ........................................................................\
....................................................... ....... 7 
3.1 AUDIENCE .......................................................................\
............................................... ........ 7 
3.2 REMARKS .......................................................................\
........................................................ 7 
IMPORTANT NOTE TO THE READER ........................................................................\
........................... 7 
3.3 DEFINITIONS, TERMS AND ABBREVIATIONS  ..................................................................... 8 
3.4 REFERENCES ...................................................................\
................................................. .... 8 
4 NETWORKING .....................................................................\
............................................... .................... 9 
4.1  IMPLEMENTATION MODEL ........................................................................\
........................... 9 
4.1.1 Application Data Flow ........................................................................\
............................ 9 
4.1.2 Functional Definition of AEs ........................................................................\
................. 10 
4.2 AE SPECIFICAT IONS .......................................................................\
....................................  1 4 
4.2.1 Storage Application Entity Specification ...................................................................... 14 
4.2.2 Workflow Application Entity Specif ication ..................................................................\
..  21 
4.2.3 Hardcopy Application Entity Specif ication ..................................................................\
. 32 
4.2.4 Verification Application Entity specification  .................................................................. 39 
4.3 PHYSICAL NETWORK INTERFACES .......................................................................\
...........  44 
4.3.1 Supported Communication Stacks ........................................................................\
...... 44 
4.3.2 Physical Network Interface ........................................................................\
.................. 44 
4.4 CONFIGURATION ...................................................................\
..............................................  44 
AE Title/Presentation Address Mapping ........................................................................\
.................. 44 
5 MEDIA STORAGE .......................................................................\
.......................................... ................ 45 
5.1 IMPLEMENTATION MODEL ........................................................................\
......................... 45 
5.1.1 Application Data Flow ........................................................................\
.......................... 45 
5.1.2 Functional Definition of AEs ........................................................................\
................. 46 
5.1.3 Sequencing of Real-Wor ld Activities ...................................................................\
.........  46 
5.1.4 File Meta Inform ation Options ........................................................................\
.............. 46 
5.2 AE SPECIFICAT IONS .......................................................................\
....................................  4 6 
5.2.1 Media Application Entity Specification ........................................................................\
. 46 
6 SUPPORT OF CHARACTER SETS ........................................................................\
............................. . 48 
6.1 SUPPORT FOR RUSSIAN AND JAPANESE MARKETS ...............................................................  48 
6.2 ADDITIONAL SUPPORT  FOR JAPANESE MARKETS ................................................................\
..  48 
6.3 SUPPORT FOR CH INESE MARKETS ........................................................................\
................... 49 
7 SECURITY ...............................................................\
....................................................... ....................... 49 
8 ANNEXES ................................................................\
.............................................................................. 50 
8.1 CREATED IOD INSTANCES ........................................................................\
......................... 50 
8.1.1 US or US Multi-frame Image IOD ....................................................................\
............ 50 
8.1.2 Comprehensive Structur ed Report IOD ....................................................................... \
51 
8.1.3 Common Modules .....................................................................\
...................................  51 
8.1.4 US or Multiframe  Image Modules ........................................................................\
........ 53 
8.1.5 Comprehensive Structured Report Modules  ................................................................ 60  
						

							 
HD7/HD7XE 3.0 DICOM Conformance Statement 000245000000008 Rev. A  Page 6 
8.2 USED FIELDS IN RECEIVED IOD BY APPLICATION .........................................................  62 
8.3 ATTRIBUTE MAPPING .................................................................\
........................................ 62 
8.4 COERCED/MODIFI ED FIELDS........................................................................\
..................... 63 
8.5 CONTROLLED TERM INOLOGY .......................................................................\
................... 63 
8.6 GRAYSCALE IMAGE CONSISTENCY .......................................................................\
..........  63 
8.7 EXTENSIONS / SPECIALIZATION S / PRIVATIZATIONS ....................................................  63 
8.7.1 Standard Extended / Specializ ed / Private SOPs ........................................................ 63 
8.8 PRIVATE TRANSFER SYNTAXES ........................................................................\
............... 63 
APPENDIX A – Structured Reports ........................................................................\
....................... ............... 64 
A.1 STRUCTURED REPORTS ........................................................................\
............................ 64 
A.1.1  Introduction ...................................................................\
...............................................  64 
A.1.2 OB Measurements .................................................................\
......................................  65 
A.1.3 GYN Measur ements .................................................................\
................................... 72 
A.1.4 Cardiac Measurements ........................................................................\
........................ 75 
  
						

							 
HD7/HD7XE 3.0 DICOM Conformance Statement 000245000000008 Rev. A  Page 7 
3 INTRODUCTION 
3.1 AUDIENCE 
This document is intended for hospital staff, health care system integrators, software designers or implementers. It is 
assumed that the reader has a working understanding of DICOM. 
3.2 REMARKS 
DICOM, by itself, does not guarantee inte roperability. However, the Conformance Statement facilitates a first-level 
validation for interoperability between different applications supporting the same DICOM functionality. 
This Conformance Statement is not intended to replace va lidation with other DICOM equipment to ensure proper 
exchange of information intended. 
The scope of this Conformance Statement is to facilit ate communication between Philips Medical Systems and other 
vendors’ Medical equipment. The Conformance Statement  should be read and understood in conjunction with the 
DICOM Standard [DICOM]. However, by itself it is not guar anteed to ensure the desired interoperability and successful 
interconnectivity. 
The user should be aware of the following important issues: 
—  The comparison of different conformance statements is the first step towards assessing interconnectivity between  Philips Medical Systems and non - Philips Medical Systems equipment. 
—  Test procedures should be defined to va lidate the desired level of connectivity. 
—  The DICOM standard will evolve to meet the users’ futu re requirements. Philips Medical Systems is actively 
involved in developing the standard further and therefore rese rves the right to make changes to its products or to 
discontinue its delivery. 
 
      IMPORTANT NOTE TO THE READER 
Interoperability 
Interoperability refers to the ability of application functions, di stributed over two or more systems, to work successfully 
together. The integration of medical devices into an IT env ironment may require application functions that are not 
specified within the scope of DICOM.  Consequently, using only the information provided by this Conformance 
Statement does not guarantee interoperability of Philips  equipment with non-Philips equipment.  It is the user’s 
responsibility to analyze thoroughly the application requirem ents and to specify a solution that integrates Philips 
equipment with non-Philips equipment. 
Validation 
Philips equipment has been carefully tested to assure t hat the actual implementation of the DICOM interface 
corresponds with this Conformance Statement. Where Philip s equipment is linked to non-Philips equipment, the first 
step is to compare the relevant Conf ormance Statements. If the Conformance  Statements indicate that successful 
information exchange should be possible, additional validation tests will be necessary to ensure the functionality, 
performance, accuracy and stability of image and image related  data. It is the responsibility of the user (or user’s 
agent) to specify the appropriate test suite and to carry out the additional validation tests. 
New versions of the DICOM Standard 
The DICOM Standard will evolve in future to meet the user ’s growing requirements and to incorporate new features 
and technologies. Philips is actively involved in this evoluti on and plans to adapt its equipment to future versions of the 
DICOM Standard. In order to do so, Philips  reserves the right to make changes to its products or to discontinue its  
						

							 
HD7/HD7XE 3.0 DICOM Conformance Statement 000245000000008 Rev. A  Page 8 
delivery.  The user should ensure that any non-Philips pr ovider linking to Philips equipment also adapts to future 
versions of the DICOM Standard. If not, the incorporati on of DICOM enhancements into Philips equipment may lead to 
loss of connectivity (in case of networki ng) and incompatibility (in case of media). 
3.3  DEFINITIONS, TERMS AND ABBREVIATIONS 
Definitions, terms and abbreviations used in this docu ment are defined within the different parts of the DICOM 
standard. 
Abbreviations and terms are as follows: 
AE  DICOM Application Entity 
AET  Application Entity Title 
ASCE  Association Control Service Element 
CD-R  Compact Disk Recordable 
CSE  Customer Service Engineer 
DICOM  Digital Imaging and Communications in Medicine 
FSC File-Set Creator 
FSU File-Set Updater 
FSR File-Set Reader 
GSDF  Grayscale Standard Display Function 
IOD  (DICOM) Information Object Definition 
ISO  International Standard Organization 
LOINC  Logical Observation Identifiers Names and Codes 
MPPS  Modality Performed Procedure Step 
MSPS  Modality Scheduled Procedure Step 
MWL Modality Worklist 
R  Required Key Attribute 
O  Optional Key Attribute 
PDU  DICOM Protocol Data Unit 
PDE  Patient Data Entry 
SCU  DICOM Service Class User (DICOM client) 
SCP  DICOM Service Class Provider (DICOM server) 
SOP  DICOM Service-Object Pair 
SNOMED  Systematized Nomenclature of Medicine (SRT) 
U  Unique Key Attribute 
US Ultrasound 
 
 
3.4 REFERENCES 
[DICOM] Digital Imaging and Communications in Medicine (DICOM), NEMA PS 3.1-3.18, 2008  
						

							 
HD7/HD7XE 3.0 DICOM Conformance Statement 000245000000008 Rev. A  Page 9 
4 NETWORKING 
4.1  IMPLEMENTATION MODEL 
4.1.1  Application Data Flow 
Send
Images, Reports, CommitsStorage
A p plicatio n E ntity
Remote
A p plication
E ntity R eceives
Im ages, R eports,
Com m its; R eturns C om m itm ents
Update
W o rklist
Acquire Im ages
Remote
A p plication
Entity Provides W orklistItem s
Remote
A p plication
E ntity R eceives
M P PS  C reate / S et
Workflow
A p plicatio n E ntity
Film
Im ages
Remote
A p plication
E n tity P rin ts Film SheetsHardcopy
A p plicatio n E ntity
DICOM Standard Interface
Local AEs Connected AEs
 
Figure 1 
APPLICATION DATA FLOW DIAGRAM 
— The  Storage Application Entity  sends Images  to one or two remote AEs and  Structured Reports to a single 
remote AE.  Acquisition of images is associated with the lo cal real-world activity “Freeze” then “Acquire” for single 
frame and “Acquire” for loops or clips.   Sending or exporting of images depends on user configuration, either 
“Send as you go”, or ”Batch” when End Study is pressed, or  Manual.   An exam may be sent by user selection 
from “Review”.  A storage commitment se rver is configured for one of the two image storage servers.  A separate 
commit server is configured for SRs. If the remote  AE is configured for Storage Commitment, the Storage AE will 
request Storage Commitment after End Exam.  If a commitm ent response is successfully obtained, there will be no  
						

							 
HD7/HD7XE 3.0 DICOM Conformance Statement 000245000000008 Rev. A  Page 10 
job remaining in the queue (viewed using CNTL-J) signali ng the Auto-delete function that the exam qualifies for 
deletion. 
 
— The  Workflow Application Entity  receives Worklist information from  and sends MPPS information to a remote 
AE.  It is associated with the local real-world activiti es “Refresh Worklist” or automatic polling and “Acquire” 
images.  When either the “Refresh Wo rklist” or automatic polling are performed, the Workflow Application Entity 
queries a remote AE for worklist items and provides th e set of worklist items matching the query request. 
—  Modality Performed Procedure Step (MPPS) messages are sent from  the system under the following 
circumstances:   
o  MPPS N-Create, Status = IN PROGRESS: 
ƒ  Closing the Patient Data Entry screen will  result in automated creation of an MPPS Instance 
managed by a remote AE.   
o   MPPS N-Set, Status = COMPLETE 
ƒ  Completion of the MPPS is performed as the resu lt of an operator action of ending the exam.   
o   MPPS N-Set, Status = DISCONTINUED 
ƒ  “Cancel” exam causes the “Disco ntinued” status to be sent.  
—  The ability to  Append images and SRs to an ended exam is availa ble. There are two fundamental methods to 
perform append:  
o  Append from Image Review 
ƒ  Select an Ended study from the Patient Directory.   
o  Select the study; choose “Open Study”.  
o   Append from Patient Selection 
•  Select the exam from the Patient Worklist Directory. 
— The  Hardcopy Application Entity  prints images on a remote AE (Printer or pr int server).  It is associated with the 
local real-world activity Acquire when a DICOM Printer is configured in the current preset, or “DICOM print” is 
selected with Right Button on the Exam in the system Pati ent Directory.  Either user action creates a print queue 
containing one or more virtual film sheets composed from  images acquired by the user.  It creates and sends fully 
rendered pages already containing the user’s selected form atting choices.  Only a single image object per sheet is 
sent to the printer.  This print object is rather large compared to sending individual Image Box objects to the 
printer.  If the user has both a BW and Color DICOM pr inter configured and selected, and is using “Send as you 
go”, the images containing no Color Flow or Chroma data will be sent to  the BW printer, all others will be sent to 
the Color printer.   
 
—  Exam data is sent to all selected Store, Print and Workflow  destinations simultaneously in accordance with system 
configuration of “Send as you go” or  “Batch” at End of Exam or Manual. 
 
4.1.2  Functional Definition of AEs 
4.1.2.1  Functional Definition of Storage Application Entity  
The existence of a Network Store queue with associat ed network destination will activate the Storage AE. An 
association request is sent to the destination AE and upon su ccessful negotiation of a Presentation Context the image 
transfer is started. If the association ca nnot be opened, the related queue’s Status  is set to RETRY as displayed in the 
Job Manager (CNTL-J).  The user may need to cancel the  queue, and then restart manually. After the automatic retries 
have failed, the job is set to Failed.  The user may select  “Retry Job” to attempt to send.  Deleting a job does not 
remove the data, as it is still present on the system.  Only  the request to transfer the data is removed.  Once any 
communication issues have been resolved, retry may be select ed or if the jobs were deleted, they may be queued 
again from the Review directory. 
4.1.2.2  Functional Definition of  Workflow Application Entity  
“Refresh Now” attempts to download a  Modality Worklist from a Modality Worklist server with studies matching the 
search criteria by sending a C-Find Request containing  user-definable Query parameters. Query parameters are 
stored in the Advanced tab adjacent to the MWL SCP se lection in the “Servers and Roles” setup page.  10 
Customizable Queries may be us ed, 5 are factory defaults.