Radiation Dose Follow-up Presentation at Berlin meeting White Paper by Joël Chabriais on July 15 IHE Profile proposal by July 31. Accepted for 2007/2008

Radiation Dose Follow-up

• Presentation at Berlin meeting• White Paper by Joël Chabriais on July 15• IHE Profile proposal by July 31. Accepted for

2007/2008 development cycle.• Supported by: ACR, SFR, ESR, SNM, RSNA,

ASN, IRSN, SEFM…• Documents on WG 10 ftp site:ftp://medical.nema.org:21//medical/private/

dicom/WORKGRPS/Wg10/2007/2007-06-28/

Radiation Dose Follow-up

• It seems that some vendors doesn’t understand the interest to move from MPPS and Image IODs to Radiation Dose SR:

Informative action is needed.• Informative event for Radiologists is planned

for JFR’08 and ECR’09. Demo at JFR’09.

Why should we add?

Performance, cost, compatibility, new capabilities, development schedule, customer integration

WS enable to integrate with many off the shelf products (e.g. dashboard, switchboard)

Developers familiar with WS are more available than developers familiar with DICOM

IT managers are more familiar with WS than DICOM long term development Internet configuration is more familiar (routers,

firewalls…) Because DICOM is service based, it would be logical to

define WS for DICOM communication New technologies we want to integrate with are often based on

WS

DICOM WG10/Web Services, Intermediary Report

Web Services… can we add now?

The WS are now in the “maturing process” The deployment beyond web server to web server is emerging

(application to application) The WS, which are mature in other industries, are now emerging

in Healthcare, especially to integrate multiple applications The WS-I Profiles are defining a real interoperable solution,

including (more or less!) the security and reliability aspects There are emerging mechanisms for conveying binary content

(MTOM/XOP, Fast Infoset) now supported by multiple development platforms (.Net, Java…)


WADO in WS, which form?

IHE ITI defined a White Paper on WS implementation of profile, based on WS-I

The IHE ITI 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

Additionally to the Retrieve Dicom Object operation, two additional transactions might be defined in order to enable a “non DICOM protocolenabled” application to communicate with a DICOM equipment:

Notification of the availability of DICOM Object(s) Query based on ID(s) for DICOM Objects (and not only based on UIDs)


Planning

Initial discussion on the topic at the RSNA 2007 DSC meeting

Elaboration of the NWIP at the January 2008 WG10 meeting (at the HL7-ISO week)

Approval of NWIP at the April 2008 Chengdu DSC meeting

Finalization of the supplement early in 2009.
