Product Experiences. Cor Loef Philips Healthcare. Contents The challenge of implementing DICOM The product in the clinical environment Software design rules Examples of typical misinterpretations Verification and validation of products Conclusion. The challenge of implementing DICOM.
Part 1 - Introduction and Overview
Part 2 - Conformance
Part 3 - Information Object Definitions
Part 4 - Service Class Definitions
Part 5 - Data Structures & Semantics
Part 6 - Data Element Listing and Typing
Part 7 - Message Exchange Protocol
Part 8 - Network Support for Message Exchange
Part 10: Media Storage and File
Format for Media Interchange
Part 11: Media Storage Application Profiles
Part 12: Media Formats and Physical Media for Media Interchange
Part 14: Grayscale Standard Display Function
Part 15: Security and System Management Profiles
Part 16: Content Mapping Resource
Part 17: Explanatory Information
Part 18: Web Access to DICOM Persistent Objects (WADO)
Patient Centric Workflow and Dataflow
"Interoperability" means the ability of ICT systems, and of the business processes they support, to exchange data and to enable the sharing of information and knowledge1.
1. “Draft Recommendation of the Commission on Union-wide interoperability of Electronic Health Record Systems”
Collect, organize and distribute clinical imaging data in- and outside the hospital
Data acquisition by modalities
Results viewing & distribution
Storage & Archive
The product in the clinical environment
Default Display Protocol
Use of Image number to determine display order
Storage Commitment: Asynchronous
A viable common sense approach exists that vendors should use for the creation of healthcare products that use the DICOM Standard for the communication of medical information.
This will achieve interoperability for the connected products in the healthcare enterprise.