Using DVTk tools in service environment

1. Using DVTk tools in service environment Piyush B DVTk developer

2. DVTk tools in service environment • DVT Tools Overview • Problem Faced by IO Engineers • Possible Solution

3. RIS Emulator • This tool can be set-up to emulate basic functionality of a RIS & MPPS system. • Sending MWL responses based on the input DCM files. • Handling MPPS messages. • It provides clear detail validation results. • It displays the Information model created on the fly as per input DCM files.

4. RIS Emulator

5. 01010101110001 System B System A DICOM via TCP/IP DICOM Network Sniffer and Analyzer • Sniff the live DICOM network stream. • Save DICOM stream to a capture (.cap) file by filtering DICOM communication only between two IP addresses. • Read & analyze cap files (saved network stream).

6. DICOM Network Sniffer and Analyzer RECEIVE ASSOCIATE-RQ SEND ASSOCIATE-AC RECEIVE C-STORE-RQ SEND C-STORE-RSP RECEIVE RELEASE-RQ SEND RELEASE-RP • Evaluate/validate DICOM communication in single/multiple DICOM association and display the overview and detail report in HTML format. • Display Service element list and Association details per association. • Saving the Service element (DICOM object) as DICOM (DCM) file. 01010101110001 DICOM Data

7. DICOM Network Sniffer and Analyzer

8. DCM Editor This tool is used for editing DICOM part-10 files and generating test data. It has the capability to: • Display all DICOM attributes in tabular format with indicating beginning & ending of sequence items. • Add/delete DICOM attributes. • Add/delete DICOM sequence attributes and sequence items. • Modify existing attribute values. • Create a text file of the DICOM Header. • Save modified dataset as DICOM part-10 file.

9. DCM Editor

10. DCM Anonymizer This application anonymize patient characteristics and clinical information from DICOM image.

11. Modality Emulator • This tool can be set-up to emulate basic functionality of all modalities: • MWL Query • Sending MPPS messages • Send Data for Storage • Handling storage commitment • It provides you clear results (logging), with the possibility to view details results.

12. Modality Emulator

13. Storage SCP Emulator

14. Storage SCU Emulator

15. Typical scenarios in field Problem between Modality and a RIS System • The Modality sets up an association with the RIS System and performs a RIS WLM query. The Modality received responses without any error but no patient displayed on screen. • Basic DICOM association handling seems to be OK: AE-titles, Port-Numbers, IP-addresses……

16. How to handle the problem • Make Network capture by DICOM Sniffer. • Analyze Capture in DICOM Sniffer to investigate DICOM Communication. • Check C-FIND RSP(s) saved into DCM file(s) by DICOM Sniffer. • Check validation result of C-FIND RSP and correct DCM file Using DCM Editor. • Supply correct DCM file in RIS emulator to reproduce and investigate the problem.

17. Make a Network Capture

18. Analyze capture and save C-FIND RSP to DCM file

19. Check the validation result of C-FIND RSP in DICOM Sniffer

20. Use the result of the DICOM Sniffer and correct the problem using DCM Editor

21. Supply edited DCM file in RIS Emulator to reproduce and investigate the problem When solution is verified it can be reported to RIS vendor for a bug-fix.

22. DCM Anonymizer • Anonymization can be performed on a CD/Directory or on a single DICOM object. • FSE can view the difference between original and anonymized dicom object. • FSE can generate the DICOMDIR of all anonymized DICOM objects.

23. Demonstrations to follow Demonstrations I • Dynamic compare tool – Marco Kemper • DCM Annonymizer – Piyush B • DVTk Storage emulators – Piyush B • DVTk IHE workflow – Rick Busbridge Demonstrations II • DVTk Gazelle Web service – Rick Busbridge • SR investigation demo – G. van Ballegooijen • DVTk IHE RO – Jorg Wissink