1. Evolution of WADO towards Web Services Emmanuel Cordonnier ETIAM, emmanuel.cordonnier@etiam.com Emmanuel Cordonnier ETIAM, emmanuel.cordonnier@etiam.com Berlin, June 28st, 2007, WG10 Strategy Advisory Group

2. emmanuel.cordonnier@etiam.com WG10 – June 2007 – WADO to WS Missions of DICOM because no specific Ad Hoc Group on Biomedical Imaging will be set up in ISO / TC215, new works on medical imaging must be done into DICOM (with a Categorie A Liaison Group between both) More and more it will be important that DICOM makes recommendations on the medical imaging aspects within non «pure» DICOM protocols DICOM «world» non DICOM world DICOM «object» DICOM WG10 NEMA Vienna - March 20, 1999 -

3. emmanuel.cordonnier@etiam.com WG10 – June 2007 – WADO to WS Proposals for DICOM WGxx studies Recommend the MIME type and file extension for DICOM part10 files on disks (if DICOM doesn't, the practice will do it). The file name can stay «open». Other topics canceled or postponed: –Work on the URL reference to DICOM part 10 files accessible from the local platform, and check if some recommendations must be made by DICOM. –Work on the URL reference to DICOM services accessible from the IT world (web, email...). –Work together with medical informatics organizations to include DICOM references into XML documents. DICOM WG10 NEMA Washington - June 15-16, 1999 -

4. emmanuel.cordonnier@etiam.com WG10 – June 2007 – WADO to WS page 4 Present limitation of WADO One SOP Instance (no way for retrieving all the images of a series/study in one call) Suited for Web Browser based solution, less for direct communication to DICOM server The URL based query is easy to write, but not adapted for being parsed No easy way to help the application development through WSDL mechanism

5. emmanuel.cordonnier@etiam.com WG10 – June 2007 – WADO to WS page 5 Web Services… why now? The WS are now in the “maturing process” The deployment beyond web server to web server is emerging (appli. to appli.) The WS-I Profiles are defining a real interoperable solution, including (more or less!) the security and reliability aspects The MTOM mechanism for conveying binary content is now supported by development platforms (.Net, Java…)

6. emmanuel.cordonnier@etiam.com WG10 – June 2007 – WADO to WS page 6 Web Services for Dummies When submitting a form to a Web Server, you are using http POST based structured message, containing the « input fields » It may also contain files to be uploaded WS are using such mechanism for the request and the response, and define the structure of message in XML SOAP A WSDL (XML) file defines the syntax of the communication (request and response)

7. emmanuel.cordonnier@etiam.com WG10 – June 2007 – WADO to WS page 7 MTOM for Dummies Date: Thu, 09 Sep 2004 18:47:52 GMT Server: Apache/2.0.48 (Win32) mod_ssl/2.0.48 OpenSSL/0.9.7d Keep-Alive: timeout=15, max=100 Connection: Keep-Alive Transfer-Encoding: chunked Content-Type: Multipart/Related;boundary=MIME_Boundary;type=application/xop+xml;charset=UTF-8;start-info="application/soap+xml" --MIME_Boundary Content-ID: Content-Type: application/xop+xml;charset=UTF-8;type="application/soap+xml" Content-Transfer-Encoding: binary --MIME_Boundary Content-ID: Content-Type: image/jpeg Content-Transfer-Encoding: binary ÿØÿàJFIF, (IMAGE 1 in BINARY) --MIME_Boundary Content-ID: Content-Type: image/jpeg Content-Transfer-Encoding: binary ÿØÿàJFIFÿÛ (IMAGE 2 in BINARY) --MIME_Boundary--

8. emmanuel.cordonnier@etiam.com WG10 – June 2007 – WADO to WS page 8 WADO in WS, which form? IHE ITI defined a White Paper on WS implementation of profile, based on WS-I The XDS.b Retrieve Document Set transaction is similar to WS/WADO All the WADO query parameters can be directly transposed « as is » in WS The response structure can be derived from the Retrieve Document Set structure

9. emmanuel.cordonnier@etiam.com WG10 – June 2007 – WADO to WS page 9 Draft of the WSDL (1) Service Binding

10. emmanuel.cordonnier@etiam.com WG10 – June 2007 – WADO to WS page 10 Draft of the WSDL (2) Ports Retrieve an objectContent from a PACS server Messages

11. emmanuel.cordonnier@etiam.com WG10 – June 2007 – WADO to WS page 11 Draft of the WSDL Schema (1) Request

12. emmanuel.cordonnier@etiam.com WG10 – June 2007 – WADO to WS page 12 Draft of the WSDL Schema (2) Response Object

13. emmanuel.cordonnier@etiam.com WG10 – June 2007 – WADO to WS page 13 Conclusion (for today) Passing from WADO to WSDO is easy However, it has to be done in the general context of the WS ad hoc work of DICOM TO AVOID INCONSISTENCY … between WS-WADO and future general WS mapping of DICOM services (if we go) First candidate is the DICOM Query to serve as a “hook” to WS-WADO