Philips Hd 7 User Manual
Have a look at the manual Philips Hd 7 User 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+.
HD7/HD7XE 3.0 DICOM Conformance Statement 000245000000008 Rev. A Page 41 Presentation Context Table Abstract Syntax Transfer Syntax Role Ext. Neg. Name UID Name List UID List Verification 1.2.840.10008.1.1 Explicit VR Little Endian Implicit VR Little Endian 1.2.840.10008.1.2.1 1.2.840.10008.1.2 SCU /SCP None 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 Modality Worklist Information Model – FIND 1.2.840.10008.5.1. 4.31 Explicit VR Little Endian Implicit VR Little Endian 1.2.840.10008.1.2.1 1.2.840.10008.1.2 SCU None Modality Performed Procedure Step 1.2.840.10008.3.1. 2.3.3 Explicit VR Little Endian Implicit VR Little Endian 1.2.840.10008.1.2.1 1.2.840.10008.1.2 SCU None Basic Grayscale Print Management Meta 1.2.840.10008.5.1. 1.9 Explicit VR Little Endian Implicit VR Little Endian 1.2.840.10008.1.2.1 1.2.840.10008.1.2 SCU None Basic Color Print Management Meta 1.2.840.10008.5.1. 1.18 Explicit VR Little Endian Implicit VR Little Endian 1.2.840.10008.1.2.1 1.2.840.10008.1.2 SCU None Presentation LUT* 1.2.840.10008.5.1. 1.23 Explicit VR Little Endian Implicit VR Little Endian 1.2.840.10008.1.2.1 1.2.840.10008.1.2 SCU None *Requested only in “Verification” associations . This SOP Class’s objects are not stored. HD7/HD7XE 3.0 initiate an Association in order to issue: — C-ECHO request according to the Verification SOP Class.
HD7/HD7XE 3.0 DICOM Conformance Statement 000245000000008 Rev. A Page 42 1. Open Association 2. C-ECHO Request 4. Close Association Verification SCUVerification SCP 3. C-ECHO Response Figure 8a SEQUENCING OF ACTIVITY – ISSUE VERIFY SCP: The system listens on the port configured on the “This System” configuration screen for Verification requests initiated by other remote devices. The calling device AE must already be configured as a remote device in HD7/HD7XE 3.0 or the association is rejected. 1. Open Association 2. C-ECHO Request 4. Close Association Verification SCPVerificationSCU 3. C-ECHO Response Figure 8b SEQUENCING OF ACTIVITY – RECEIVE VERIFY
HD7/HD7XE 3.0 DICOM Conformance Statement 000245000000008 Rev. A Page 43 4.2.4.3.3 Proposed Presentation Contexts HD7/HD7XE 3.0 will propose Presentation Contexts as shown in the following table: Table 51.6 PROPOSED PRESENTATION CONTEX TS FOR ACTIVITY VERIFICATION Presentation Context Table Abstract Syntax Transfer Syntax Role Ext. Neg. Name UID Name List UID List Verification 1.2.840.10008.1.1 Implicit VR Little Endian Explicit VR Little Endian 1.2.840.10008.1.2 1.2.840.10008.1.2.1 SCU /SCP None 4.2.4.3.4 SOP Specific Conformance for Verification Table 51.7 summarizes the behavior of HD7/HD7XE 3.0 when receiving status codes in a C-ECHO response. A message will appear on the user interface if HD7/HD7XE 3.0 receive any other SCP response status than “Success.” Table 51.7 VERIFICATION C-ECHO RESPON SE STATUS HANDLING BEHAVIOR Service Status Further Meaning Error Code Behavior Success 0000 Device Status is set to: Verified Refused Out of Resources A700 Device Status is set to: Not Verified Failed Unable to Process C000 – CFFF Same as “Refused” above. * * Any other status code. Same as “Refused” above. 4.2.4.3.4.1 Verification SOP Class Operations (C-ECHO) 4.2.4.3.5 Association Acceptance Policy 4.2.4.3.5.1 Verification SOP Class Notifications Association Negotiation Request messa ge contents for each DICOM device: Device Type SOP Classes Requested Additional Notes DICOM Archive Server US Image Storage US Multi-frame Storage Storage Commitment Comprehensive Structured Report Storage DICOM Commit Server Storage Commitment DICOM PPS Server Modality Performed Procedure Step DICOM Worklist Server Modality Worklist MWL query settings are located in Setups > System > DICOM > DICOM Preset > Change Settings for current preset > Modify in Roles > MWL SCP – Advanced > Set Modality Worklist Query page. Search window of the Patient Data
HD7/HD7XE 3.0 DICOM Conformance Statement 000245000000008 Rev. A Page 44 Entry screen. DICOM Structured Report Server Comprehensive Structured Report Storage SR Storage Commit SCP Storage Commitment DICOM BW Printer Basic Grayscale META Print All bw printers configure this entry. If the printer supports both BW and Color, then this must be configured to allow BW on that printer. DICOM Color Printer Basic Color META Print May be the same printer if color is also supported. 4.3 PHYSICAL NETWORK INTERFACES 4.3.1 Supported Communication Stacks 4.3.1.1 TCP/IP Stack The HD7/HD7XE 3.0 provide DICOM TCP/IP Network Communi cation Support as defined in Part 8 of the DICOM Standard. 4.3.2 Physical Network Interface HD7/HD7XE 3.0 support a single network interface. The following physical network interface is available: Table 52 SUPPORTED PHYSICAL NETWORK INTERFACE Ethernet 10/100BaseT, RJ-45, UTP, STP; AutoDetect Speed, Full or Half Duplex 4.4 CONFIGURATION AE Title/Presentation Address Mapping The Devices Configuration section allows the following device types to be configured: Device Type Supported SOPs DICOM Archive Server Ultrasound Store Ultrasound Multi-frame Store Comprehensive Structured Report Store Storage Commitment Push Model DICOM Commit Server Storage Commitment Push Model DICOM PPS Server Modality Performed Procedure Step DICOM Worklist Server Modality Work List DICOM Structured Report Server Comprehensive Structured Report Store DICOM BW Printer Basic Grayscale Print Meta DICOM Color Printer Basic Color Print Meta 4.4.1.1 Local AE Title All local DICOM Presets use the same AE Title and TCP/IP Po rt configured via the Network Settings in DICOM setup. The system listens on the configured Port only for Verifi cation requests and Storage Commitment N-Event reports. The system supports Static Addressing or DHCP to receive its IP A ddress, Subnet Mask and Default Gateway address.
HD7/HD7XE 3.0 DICOM Conformance Statement 000245000000008 Rev. A Page 45 4.4.1.2 Remote AE Title/Presentation Address Mapping The AE Titles, IP Addresses and Port numbers of remote applications are manually confi gured using the DICOM setup screen. The remote system’s IP Address may be entered ma nually if known or the Host Name of the remote device may be entered and resolved by the DNS if the network includes this service. 4.4.1.2.2 Workflow Setup is used to set the AE Title, port-number and IP Address the remote MWL SCP. Multiple MWL SCPs may be defined, but only a singl e remote MWL SCP can be selected at a time. All default MWL queries use Modality = US. This may be changed to in the MWL Query definition page. AE Title may be selected as Any, This System, or Another as a query value. Automated queries may be set for a specific time interval, 1- 99,999 minutes. Automated queries use Today, All Dates or Date Range, (0-99 day(s)/hour(s) plus today, plus the next 0-99 day(s).) Setup is used to set the AE Title, port-number and IP Address of the remote MPPS SCP. Multiple MPPS SCPs may be defined, but only a singl e remote MPPS SCP can be selected at a time. 4.4.1.2.3 Hardcopy Setup is used to set the AE Titles, Port numbe rs and IP Addresses for the remote Print SCPs. Multiple remote Print SCPs can be defined. One Grayscale and one Color Print SCP may be selected at a time. 5 MEDIA STORAGE 5.1 IMPLEMENTATION MODEL 5.1.1 Application Data Flow Media Application Entity Export toMedia Media Storage Medium Import from Media FSC FSU FSR* Figure 9 APPLICATION DATA FLOW DIAGRAM FOR MEDIA STORAGE — The Media Application Entity exports Images and Structur ed Reports to a disk Storage medium. It is associated with the local real-world activity “Export to Media”. “E xport to Media” is performed upon user request for selected
HD7/HD7XE 3.0 DICOM Conformance Statement 000245000000008 Rev. A Page 46 patients, studies, series or instances (images, or Structured Reports). Throughout this section, the term “Media” refers to any of the media listed below which is in use. HD7/HD7XE 3.0 will support the use of most writable media including CD-R, CD-RW, DVD-R, DVD+R, DVD-RW and DVD+RW. DICOM structure will be t he same regardless of media used. 5.1.2 Functional Definition of AEs 5.1.2.1 Functional Definition of Media Application Entity Using “Export Studies” will pass the current ly selected patients’ exams or individually selected images to the Media Application Entity. The SOP Instances asso ciated with the selection will be collected into one or more export jobs. The contents of each export job will be written to the installed media. If the capacity of a disk is exceeded, the user is provided a dialog, stating capacity exceeded and to insert another disk. 5.1.3 Sequencing of Real-World Activities At least one image must exist and be selected before the Medi a Application Entity can be invoked. The operator can insert new media at any time. The Media Application Entity will wait indefinitely for media to be inserted before starting to write to the device. 5.1.4 File Meta Information Options The implementation information written to the File Meta Header in each file is: Table 65 DICOM IMPLEMENTATION CLASS AND VERSION FOR MEDIA STORAGE Implementation Class UID 1.3.46.670589.14.3000.300 Implementation Version Name HD7_300 5.2 AE SPECIFICATIONS 5.2.1 Media Application Entity Specification The Media Application Entity provides standard conformance to the DICOM Interchange Option of the Media Storage Service Class. The Application Profiles and roles are listed in Table 66 APPLICATION PROFILES, ACTIVITIES AND ROLES FOR OFFLINE-MEDIA Application Profiles Supported Real World Activity Role SC Option STD-US-SC-SF&MF-CDR Send to….Media FSC, Interchange STD-US-SC-SF&MF-DVD FSC, U** STD-US-SC-SF&MF-CDR STD-US-SC-SF&MF-DVD Send to … Hard Disk R* * File Set Reader functionality is limited only to media created by other HD7/HD7XE 3.0 systems. ** Update functionality requires DVD+RW 5.2.1.1 File Meta Information for the Application Entity The File-Set Identifier included in the File Meta Header is “Data Not Stored”. 5.2.1.2 Real-World Activities 5.2.1.2.1 Activity – Send to Media The Media Application Entity acts as an FSC using the interchange option when requested to export SOP Instances from the local database to media.
HD7/HD7XE 3.0 DICOM Conformance Statement 000245000000008 Rev. A Page 47 The contents of the export job will be written together with a corresponding DICOMDIR to media. The user can cancel an export job in the job queue. Writing in multi-session format to CDs and DVDs is supported. Each export job is written as one session. 5.2.1.2.2 Activity – Import from Media The Media Application Entity acts as an FSR using the interchange option when requested to import SOP Instances from media to the local database. The Patient Directory UI presents the di rectory of the system or the offline media. Selected exams are transferred from the media to the system for review. Objects transferred to the system retain their original SOP Instance UIDs. Note: Structured Reports may not be read back into the HD7/HD7XE 3.0. 5.2.1.2.3 Activity – Update to Media The Media Application Entity acts as an FSU using the interchange option when requested to export SOP Instances from the local database to media upon which DICOM data already resides. The system user selects exams from the system’s directory for transfer to media that already contains data. The DICOMDIR is updated allowing access to original and new data. DVD +RW media may be erased at any time, removing all previously recorded data. 5.2.1.2.3.1 Media Storage Application Profiles See Table 66 for supported Application Profiles. 5.2.1.2.3.2 Options The Media Application Entity supports the SOP Cl asses and Transfer Syntaxes listed in Table 67. Table 67 IODS, SOP CLASSES AND TRANSFE R SYNTAXES FOR OFFLINEMEDIA Information Object Definition SOP Class UID Transfer Syntax Transfer Syntax UID Media Storage Directory Storage 1.2.840.10008.1.3.10 Explicit VR Little Endian 1.2.840.10008.1.2.1 US Image Storage* 1.2.840.10008.5.1.4.1.1.6.1 Explicit VR Little Endian JPEG Lossy Baseline JPEG Lossless Baseline 1.2.840.10008.1.2.1 1.2.840.10008.1.2.4.50 1.2.840.10008.1.2.4.70 US Multi-frame Image Storage* 1.2.840.10008.5.1.4.1.1.3.1 Explicit VR Little Endian 1.2.840.10008.1.2.1 JPEG Baseline Lossy Compression 1.2.840.10008.1.2.4.50 JPEG Baseline Lossy Compression 1.2.840.10008.1.2.4.50 Comprehensive Structured Report Storage 1.2.840.10008.5.1.4.1.1.88.33 Explicit VR Little Endian 1.2.840.10008.1.2.1 * See details listed in Table 9.
HD7/HD7XE 3.0 DICOM Conformance Statement 000245000000008 Rev. A Page 48
6 SUPPORT OF CHARACTER SETS
All HD7/HD7XE 3.0 DICOM applications support the
ISO_IR 100 Latin Alphabet No. 1
ISO-IR 87 Japanese Kanji (ideographic), Hi ragana (phonetic) and Katakana (phonetic
ISO-IR 13 Japanese Katakana (phonetic)
ISO-IR 159 Supplementary Kanji (ideographic)
ISO-IR 144 Russian Cyrillic
6.1 SUPPORT FOR RUSSIAN AND JAPANESE MARKETS
HD7/HD7XE 3.0 use Code-extension tech niques to encode Japanese stroke ba sed characters and Russian Cyrillic
characters in DICOM tags with value repr esentations of SH, LO, ST, LT, UT, and PN.
The technique requires two things in a DICO M file that contains these characters:
1. Add the Optional Specific Character Set tag (0008,0005) and set the value to the list of identifiers for all the non-standard character sets that will appear in any string in the file separated by backslashes. For example:
For Japanese systems: (0008,0005) = ISO 2022 IR 13\ISO 2022 IR 87\ISO 2022 IR 159\ISO 2022 IR 100
For Russian systems: (0008,0005) = ISO 2022 IR 144\ISO 2022 IR 100
For English systems: (0008,0005) = ISO 2022 IR 100
2. Embed escape sequences in the strings that contain Asian or Cyrillic characters to cause the DICOM interpreting code to switch from one character set to another.
The escape sequences to be used are defined as:
$B ISO - IR 87 Japanese Kanji (ideog raphic), Hiragana (phonetic), Katakana (phonetic)
(B ISO - IR 6 ASCII - DICOM default character set
$(D ISO - IR 159 Supplementary Kanji (ideographic)
(J ISO - IR 144 Russian Cyrillic
6.2 ADDITIONAL SUPPORT FOR JAPANESE MARKETS
Japanese markets will have additional fields to the Patient ID screen so that the user can enter the Roman,
Ideographic, and Phonetic represent ations of a patient’s name.
The DICOM patient name field, tag (0010,0010) of type PN, is a single string field that contains up to five components
(last, first, middle, title, honorific) in up to three language variants (Roman, Idiographic, and Phonetic.) The format of
the patient name field is:
“Roman-last^Roman-first^Roman-middle^Roman-prefix^Roman-suffix=
Ideographic-last^Ideographic-first^Ideographic- middle^Ideographic-prefix^Ideographic-suffix=
HD7/HD7XE 3.0 DICOM Conformance Statement 000245000000008 Rev. A Page 49 Phonetic-last^Phonetic-first^Phonetic-middle^Phonetic-prefix^Phonetic-suffix” In the above string the five components are separated with the ‘^’ Ascii character and the three language variants are separated by the ‘=’ Ascii character. The only required co mponent is the Roman Last name. All other components are optional. Trailing ‘^’ and ‘=’ characters can be excluded. When this string is encoded in a DICOM image file or DICOMDIR directory file, the escape sequences appropriate for the character sets used are inserted into the string for storage as a single-byte string. On media import the escape sequences are removed. 6.3 SUPPORT FOR CHINESE MARKETS The current DICOM standard as of this release of HD7/HD7XE 3.0 does not support Chinese character sets. HD7/HD7XE 3.0 however provides support for Chinese cu stomers so that they can enter text using Chinese characters. If the system is set up for Chinese, then (unlike for Japan ese markets) the user can enter just one version of the patient name. This would make Chinese systems work in the same way as Russian, English, French, Italian, and Spanish systems. The Chinese user will be able to enter the patient name using a combination of Chinese and Roman characters – all of the characters will appear wherever the system displays the patient name (image, report, Search for Study window, etc.). Since the DICOM Standard does not offer support for Chines e characters, all Chinese characters entered into the Patient ID screen will be lost if a user exports or backs up a study to media. This will be noticed when the study is imported back into the system; upon import, each Chinese ch aracter will be replaced with a question mark (“?”) character. The question marks will make it obvious to the user th at the characters were lost. If the user enters a patient name that consists entirely of Chinese characters, then the name will come back as “??????”. In this case, the user will ha ve to identify the study in the “Import Study” and “Search for Study” windows by the MRN. If the user enters a patient name that consists of a combination of Roman and Chinese characters, then Roman characters will be preserved, and the name will co me back as something like “Lee ????????”. This will give users who like to back up their studies the flexibility of entering a patient name with a combination of Roman and Chinese characters, and have at least part of the name come back during import. Note that the original Chinese name will be “bur ned into” study images that are exported to media. These Chinese characte rs will remain on the images when the st udies are imported back into the system. 7 SECURITY DICOM security is not implemented on the HD7/HD7XE 3.0 at this time. HD7/HD7XE 3.0 incorporate an internal firewall that only ac cepts incoming traffic on the designated listening port, as configured in the DICOM… > Change Settings for current preset > This System tab.
HD7/HD7XE 3.0 DICOM Conformance Statement 000245000000008 Rev. A Page 50 8 ANNEXES 8.1 CREATED IOD INSTANCES Table 69 specifies the attributes of an Ultrasound Ima ge transmitted by the HD7/HD7XE 3.0 storage application. Table 70 specifies the attributes of a Comprehensive St ructured Reports transmitted by the HD7/HD7XE 3.0 storage application. The following tables use a number of abbreviations. The abbreviations used in the “Presence of …” column are: VNAP Value Not Always Present (attribute se nt zero length if no value is present) ANAP Attribute Not Always Present ALWAYS Always Present EMPTY Attribute is sent without a value The abbreviations used in the “Source” column: MWL the attribute value source Modality Worklist USER the attribute value source is from User input AUTO the attribute value is generated automatically MPPS the attribute value is the same as t he Modality Performed Procedure Step service CONFIG the attribute value source is a configurable parameter 8.1.1 US or US Multi-frame Image IOD Table 69 IOD OF CREATED US OR US MULTIFRAME SOP INSTANCES IE Module Reference Presence of Module Patient Patient Table 71 ALWAYS Study General Study Table 72 ALWAYS Patient Study Table 73 ALWAYS Series General Series Table 74 ALWAYS Equipment General Equipment Table 75 ALWAYS Image General Image Table 76 ALWAYS Pixel Plane Table 76-a ANAP Image Pixel Table 77 ALWAYS Palette Color Lookup Table Table 77-a ANAP Cine Table 78 Only if Multi-frame Multi-frame Table 79 Only if Multi-frame US Region Calibration Table 80 ANAP US Image Table 81 ALWAYS VOI LUT Table 82 Only if Single frame SOP Common Table 83 ALWAYS