DICOM Conformance Statement - InCenter - Philips

More documents

Recommendations

Info

DICOM Conformance Statement Page 8 of 82 5.1. IMPLEMENTATION MODEL ................................................................................................ 47 5.1.1. Application Data Flow Diagram......................................................................................... 47 5.1.2. Functional Definitions of AE’s ........................................................................................... 49 5.1.3. Sequencing of Real World Activities ................................................................................. 49 5.1.4. File Meta Information for Implementation Class and Version........................................... 50 5.2. AE SPECIFICATIONS .......................................................................................................... 51 5.2.1. VF Workstation AE............................................................................................................ 51 5.2.1.1. File Meta Information for the VF Workstation AE ............................................................. 52 5.2.1.2. Real-World Activities ......................................................................................................... 52 5.2.1.2.1. Display Directory........................................................................................................... 52 5.2.1.2.2. Read Image .................................................................................................................. 52 5.2.1.2.3. Write Image................................................................................................................... 53 5.3. AUGMENTED AND PRIVATE APPLICATION PROFILES ................................................. 54 5.3.1. Augmented Application Profiles ........................................................................................ 54 5.3.1.1. Augmented Application Profile AUG-GEN-DVD-JPEG .................................................... 54 5.3.1.1.1. SOP Class Augmentations ........................................................................................... 54 5.3.1.1.2. Directory Augmentations .............................................................................................. 54 5.3.1.1.3. Other Augmentations.................................................................................................... 54 5.3.2. Private Application Profiles ............................................................................................... 54 5.4. MEDIA CONFIGURATION ................................................................................................... 55 6. SUPPORT OF CHARACTER SETS ......................................................................................... 56 7. SECURITY................................................................................................................................. 57 7.1. SECURITY PROFILES ......................................................................................................... 57 7.1.1. Basic Application Level Confidentiality Profile .................................................................. 57 7.1.1.1. SOP Class Augmentations ............................................................................................... 58 7.2. ASSOCIATION LEVEL SECURITY...................................................................................... 58 7.3. APPLICATION LEVEL SECURITY ...................................................................................... 58 8. ANNEXES VERADIUS AE........................................................................................................ 59 8.1. IOD CONTENTS ................................................................................................................... 59 8.1.1. Created SOP Instances .................................................................................................... 59 8.1.1.1. Secondary Capture Image Storage SOP Class................................................................ 59 8.1.1.2. X-Ray Angiographic Image Storage SOP Class............................................................... 62 8.1.2. Usage of Attributes from Received IOD’s ......................................................................... 65 8.1.3. Attribute Mapping .............................................................................................................. 65 8.1.4. Coerced/Modified fields..................................................................................................... 66 8.2. DATA DICTIONARY OF PRIVATE ATTRIBUTES .............................................................. 67 8.3. CODED TERMINOLOGY AND TEMPLATES...................................................................... 67 8.4. GRAYSCALE IMAGE CONSISTENCY................................................................................ 67 8.5. STANDARD EXTENDED/SPECIALIZED/PRIVATE SOPS................................................. 67 8.5.1. Standard Extended X-Ray Angiographic Image Storage SOP Class............................... 67 8.6. PRIVATE TRANSFER SYNTAXES...................................................................................... 67 9. ANNEXES VF WORKSTATION AE ......................................................................................... 68 9.1. IOD CONTENTS ................................................................................................................... 68 9.1.1. Created SOP Instances .................................................................................................... 68 9.1.1.1. Secondary Capture Image Storage SOP Class................................................................ 69 9.1.1.2. Grayscale Softcopy Presentation State Storage SOP Class............................................ 75 9.1.2. Usage of Attributes from Received IOD’s ......................................................................... 77 9.1.3. Attribute Mapping .............................................................................................................. 77 9.1.4. Coerced/Modified fields..................................................................................................... 77 9.2. DATA DICTIONARY OF PRIVATE ATTRIBUTES .............................................................. 81 9.3. CODED TERMINOLOGY AND TEMPLATES...................................................................... 81 9.4. GRAYSCALE IMAGE CONSISTENCY................................................................................ 81 9.5. STANDARD EXTENDED/SPECIALIZED/PRIVATE SOPS................................................. 81 9.6. PRIVATE TRANSFER SYNTAXES...................................................................................... 82 © Koninklijke Philips Electronics N.V. 2009 XPS031-090132.02 Veradius R1.1 6 Jul 2009
3. INTRODUCTION 3.1. Revision History DICOM Conformance Statement Page 9 of 82 Table 3: Revision History Document Version Date of Issue Status Description 00 18 May 2009 Draft Draft DICOM Conformance Statement for the Veradius R1.1 with integrated VF R6.3 Workstation. 01 28 May 2009 Proposal Updating draft version. 02 6 June Approved Final version 3.2. Audience This Conformance Statement is intended for: • (potential) customers • system integrators of medical equipment • marketing staff interested in system functionality • software designers implementing DICOM interfaces It is assumed that the reader is familiar with the DICOM standard. 3.3. Remarks The DICOM Conformance Statement is contained in chapter 4 through 10 and follows the contents and structuring requirements of [DICOM] PS 3.2. This DICOM Conformance Statement by itself does not guarantee successful interoperability of Philips equipment with non-Philips equipment. The user (or user’s agent) should be aware of the following issues: • Interoperability Interoperability refers to the ability of application functions, distributed over two or more systems, to work successfully together. The integration of medical devices into an IT environment 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 requirements and to specify a solution that integrates Philips equipment with non-Philips equipment. • Validation Philips equipment has been carefully tested to assure that the actual implementation of the DICOM interface corresponds with this Conformance Statement. Where Philips equipment is linked to non-Philips equipment, the first step is to compare the relevant Conformance 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 © Koninklijke Philips Electronics N.V. 2009 XPS031-090132.02 Veradius R1.1 6 Jul 2009
Page 1 and 2: © Koninklijke Philips Electronics
Page 3 and 4: DICOM Conformance Statement Page 3
Page 7: 2. TABLE OF CONTENTS DICOM Conforma
Page 19 and 20: 4.2.1.3.2. Get Worklist DICOM Confo
Page 23 and 24: 4.2.1.3.3. Export DICOM Conformance
Page 33 and 34: 4.2.1.4. Association Acceptance Pol
Page 35 and 36: 4.2.2. VF Workstation AE DICOM Conf
Page 39 and 40: Query Level Series Image DICOM Conf
Page 43 and 44: 4.3. AE Specifications DICOM Confor
Page 47 and 48: 5. MEDIA INTERCHANGE 5.1. Implement
Page 51 and 52: 5.2. AE Specifications DICOM Confor
Page 57 and 58: 7. SECURITY 7.1. Security Profiles
Page 59 and 60:
8. ANNEXES VERADIUS AE 8.1. IOD Con
Page 61 and 62:
DICOM Conformance Statement Page 61
Page 63 and 64:
Page 65 and 66:
Page 67 and 68:
Page 69 and 70:
Page 71 and 72:
Page 73 and 74:
Page 75 and 76:
Page 77 and 78:
Page 79 and 80:
Page 81 and 82:
show all

DICOM Conformance Statement - InCenter - Philips

Create successful ePaper yourself

Delete template?

Save as template?