DICOM:Interface

Goals

Ideally we will have a nice set of reusable Qt widgets for different aspects of the DICOM interaction process. Since Osirix is widely used (and praised) we are using their interface as an inspiration for our work.

The screenshots show some of the essential functionality.

Osirix local database view

Osirix Query Interface

Related Efforts and Implementations

• A very nice dicom browser implementation also exists in DeVIDE from Delft University. The DeVIDE project provides a screencast of the browser in action.
• The Virtual Physiological Human (VHP) European Network of Excellence has also been looking at new DICOM browser functionality.
  • These design documents describe the project.
  • The effort is an expansion of the CreatTools Image IO Interface.

Design Discussion

Use-case scenarios

We have begun collecting some use-case scenarios with Martin Styner's group on this topic. In these scanarios users want to query an (XNAT) repository of information using DICOM and other relevant metadata: USE-CASE SCENARIOS. Please feel free to add more use-case descriptions to the page.

Manage data & load interface for DICOM & other formats

We are also working on a generalized Load interface, which is both a Slicer component and a stand-alone application for managing data. To manage data, the interface would allow users to import data from a number of sources, including

• disk
• local database
• repository and database (XNAT enterprise instance)
• DICOM SCP (PACS)

To load data into Slicer, the interface would allow users to select from among the sources above, query, browse results, and retrieve and load data into Slicer. This design is currently in progress: MANAGE, QUERY, & LOAD DATA INTERFACE

XNAT Desktop new interface version

Finally, we are working on a new interface for XNAT Desktop which mirrors the data management portion of the functionality above, and presents similar layout and user experience (to maximize knowledge transfer for users among the set of tools: XNAT Desktop design discussion. This work is in progress.

Generalized design for remote resource query

Implementation

Initial implementation tests are happening in the context of Common Toolkit working sessions.

Column Layout

Suggested Osirix-like local database view that uses the database layout proposed by MITK

Name	Age	Scan	Date	Subject ID	Number	Institution	Referrer	Performer
Patient.PatientsName	Patient.PatientsAge		Patient.PatientsBirthDate	Patient.PatientsID
+Studies.StudyDescription		Studies.ModalitiesInStudy	Studies.StudyDate		Studies.AccessionNumber	Studies.InstiutionName	Studies.ReferringPysician	Studies.PerformingPysician
++Series.SeriesDescription		Series.BodyPartExamined	Series.SeriesDate		Series.AcquisitionNumber

Progress

At the end of the CTK prehackfest a non-functional Qt based interface has been developed. The internal structure of the tree browser is close to completion. Many of the other features (searching and query-retrieve) are yet to be done.