Interactive Multimedia Reporting (IMR)

This template is for one or two page IHE workitem proposals for initial review. To create a new proposal, first log in to the Wiki (or create an account if you don't already have one). Then create an appropriately named new Wiki page (see the editing instructions linked to "Help" at left. Then come back to this page, click "edit" above, select and copy the contents of this page and paste the contents into your newly created page.

<Delete everything in italics and angle brackets and replace with real text. This means delete the angle bracket character and the two quote marks too.>

1. Proposed Workitem: <initial working name for profile/whitepaper/etc>

• Proposal Editor: <Name of author/editor/contact for the proposal>
• Editor: <Name of candidate Lead Editor for the Profile, if known>
• Date: N/A (Wiki keeps history)
• Version: N/A (Wiki keeps history)
• Domain: <Domain name (e.g. Radiology)>

remove this tag [[Category:DomainAbbreviation]] remove this tag too

2. The Problem

<Summarize the integration problem. What doesn’t work, or what needs to work.>

<Now describe the Value Statement: what is the underlying cost incurred by the problem, what is to be gained by solving it>

3. Key Use Case

<Describe a short use case scenario from the user perspective. The use case should demonstrate the integration/workflow problem.>

<Feel free to add a second use case scenario demonstrating how it “should” work. Try to indicate the people/systems, the tasks they are doing, the information they need, and hopefully where the information should come from.>

Summary of Tasks

Category	WADO-URL [RAD-55]	Retrieve Imaging Document Set [RAD-69]
1	Simple HTTP. Usually no additional library required for implementation.	SOAP over HTTP. Usually require some kind of library to handle SOAP messages.
Request	Simple HTTP parameterized URL	Specific SOAP envelop format
Response	Simple DICOM Part 10 object by default	DICOM Part 10 objects returned in MTOM/XOP
Request content	Only a single object per request. Always fully references study/series/image UID	Allow one or more objects per request.
Optional behavior	Supports rendering (e.g. retrieve DICOM images as jpeg or DICOM SR as HTML). This is included in the base DICOM WADO-URL specification, not additional specification in XDS-I.b.	Only supports retrieving DICOM objects as Part 10 object. No rendering support (Note: WADO-WS as defined in DICOM (now deprecated) has additional rendering and retrieve metadata capabilities, but these are not defined in RAD-69)
Authentication	Supports ATNA bi-directional certifcate authentication	Supports ATNA bi-directional certifcate authentication
Additional Security	None	Supports same set of security related functionality as the rest of XDS. e.g. XUA \ XUA++ using SAML token, optional asynchronous response using WS-Addressing, BPPC \ APPC, etc.

4. Standards and Systems

<List existing systems that are/could be involved in the problem/solution.>

<If known, list standards which might be relevant to the solution>

5. Discussion

<Include additional discussion or consider a few details which might be useful for the detailed proposal>

<Why IHE would be a good venue to solve the problem and what you think IHE should do to solve it.>

<What might the IHE technical approach be? Existing Actors? New Transactions? Additional Profiles?>

<What are some of the risks or open issues to be addressed?>

<This is the brief proposal. Try to keep it to 1 or at most 2 pages>

<Delete this Category Templates line since your specific Profile Proposal page is no longer a template.>