Building a DICOM Library in C#.ppt

* Steps needs to serialize DICOM data to an output device (like a network or file) Application needs to define which ‘method’ to use: 5 different methods: from none to ‘smart’ Application needs to define in which order ‘legacy’ character sets should be used. Library will scan all encoding sensitive text values. As we use lazy parsing and lazy loading this means that all strings first need to be loaded and converted to Unicode. (private tags with strings of 10 Mbyte) Library needs to scan all characters to build up the required Character Encoding. Optional remove not needed character sets. Library needs to encode all strings using this encoding Still situations that datasets cannot be opened by receiving system. Recommendation: use or create systems that can handle UTF8 Keywords: Requires configuration Performance penalties The second design challenge, I like to present is about doing C-STORE on a Wide Area Network * * Most DICOM system are local: communication between systems in the hospital. Modalities sending images to a PACS and a PACS sends images to a workstation. There is a trend to create images in regional and national DICOM data centers. Wide Area Networks, such as the Internet, have different characteristic. The bandwidth is often slower then a local connection, high speed is however become more and more available. And very important the round trip time is much larger, often in the range from 10 ms to 1 second for satellite connections. Keywords Modality - PACS Trend: (Electronic Patient Record) Different capabilities Round Trip time 3 parts: distance: signal delay, delay routers \ switches, congestion * And in this sampe, I ignore the delays in the sending and receiving systems itself, just looking at the network transmissions. In the formula, N is the number of instances, Tx is the time required to transmit an instance, Trtt is the round trip time. Notes: 100 Mbit/s = 10 Mbyte/s = 10000 Kbyte/s = 10 Kbyte/ms Tx = 125 / 10 Kbyte/ms = 12.5 ms N *