Difference between revisions of "DICOM:Interface"
Line 71: | Line 71: | ||
== Progress == | == Progress == | ||
− | [[image:CtkDICOM-prototype-2010-03-14.png|thumb| | + | [[image:CtkDICOM-prototype-2010-03-14.png|thumb|center|500px|At the end of the [http://www.na-mic.org/Wiki/index.php/Events:CTK-Pre-Hackfest-2010 CTK prehackfest] the a non-functional Qt based interface had 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.]] |
Revision as of 15:58, 14 March 2010
Home < DICOM:InterfaceGoals
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.
A very nice dicom browser implementation also exists in DeVIDE from Delft University. The DeVIDE project provides a screencast of the browser in action.
Design Discussion
Wendy has Design Discussion| done a review and created a design that generalizes the DICOM concepts while maintaining the core concepts used in clinical applications.
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 |