Project Description
General project description with introduction and overview

Group Members
The MIND Project contractors, position titles, and tasks, as well as links to homepages and email addresses

Contract
The contract to which the MIND Project contractors, clients, and boss have agreed

Schedule
Various scheduling aspects of the project. Includes charts, weekly reports, and boss meetings.

Documentation
The documentation for the MIND Project. This is the same whether in the following online format or if taken in a hard copy form.

Related Links
Outside pages relating to DICOM, CTN and other related pages.

Mail the Team
Send mail to the entire group.

The MIND Project Contract

January 29, 1999


Contractor Team Members:

  • Jeff Brubaker
  • Travis Burnette
  • Casey Hadden
  • David Lamb
  • Brian McKendrick

Client:

  • Stephen Aylward
  • Liz Bullitt

Boss:

  • David Stotts

Proposal:

The Radiology department at UNC has a very large DICOM database of medical images and other patient information called Magic Store. However, this data is patient sensitive and therefore, very few individuals are allowed access to it; however, there are many groups and individuals that would like access to these files. The Radiology department has no other database on which to store the files for others to access. The MIND group proposes to establish such a database for Stephen Aylward and Liz Bullitt to move to a machine in the Radiology department. Currently the software for accessing the database is provided by a free library called CTN. This software, particularly the GUI is very crude, and in need of an upgrade. The MIND team also agrees to build this new interface. Included will be methods to get to as fine a granularity as possible within the database before actually sending the data across the network.

Primary Requirements:

1. Create a DICOM Server for use in Radiology:
  • use CTN library as server
  • use miniSQL database
  • should contain DICOM files
2. Graphical User Interface:
    The GUI shall contain the following capabilities:
    • ability to access DICOM database through queries and retrieves
    • ability to specify IP address of the database server (i.e., be able to access Magic Store as well as the secondary database)
    • ability to obtain as fine a granularity as possible before sending the request to the database
    • ability to view images
    • provide several different hierarchies for searching the database (i.e., patient name->date->series or date->patient name->series, etc...)
    • display as much information about a file or set of files, before sending the request to the database

    The GUI shall have the following properties:
    • be based on FLTK
    • be cross-platform for X-Windows and Microsoft Windows
    • exporting of images to disk
    • allow the user to obtain as fine a granularity as possible before sending request the file request to the server

Secondary Requirements:

1. Build new libraries on top of CTN including:
  • basic query/retrieve operations
  • image format conversions, via Image Magick
  • ability to specify options to retrieve data in smaller groups than whole studies
2. Image Manipulation:
  • rotation, zooming, scaling
  • 3D image viewing
3. C Wrapper to Libraries
  • provide integration with MatLab and AVS

Client Obligations:

The party of Stephen Aylward and Liz Bullit, hereafter referred to as the client, agrees to provide the contractors with access to existing data files, necessary libraries, disk space, and any existing source code pertinent to the project.

1. Libraries
  • FLTK
  • Image Magick
  • CTN
2. Data
  • DICOM format data files
3. Disk Space
  • Sufficient space to work with large DICOM data objects
4. Documentation
  • CTN, DICOM, Image Magick and FLTK

Risks:

1. Insufficient access to the network or a DICOM server could make it impossible or extremely difficult to foresee all issues relating to the Magic Store transactions. An in-house DICOM server has been set up; however, we cannot possibly imitate every possible aspect of the Radiology department's server and network.
2. Existing libraries (CTN) could be incapable of transferring smaller parts of the studies, thereby making it impossible to break up large data objects. This is quite likely, and as such we will deal with moving large DICOM objects across the network should it be so.
3. Insufficient documentation for existing libraries, which must be used, could create additional difficulty in designing the library and thus dramatically increase development time. Documentation initially appears sufficient; however, it is almost overly specific and lacks any introductory information.

Glossary:

1. CTN - Central Test Node. A complete implementation of the DICOM specification. This contains libraries and Motif based GUI tools.
2. DICOM - Digital Imaging and Communciations in Medicine. A specification defining the storage and retrieval of patient data and related images.
3. FLTK - Fast, Light Tool Kit. A tool kit, distributed under the GNU Public License, for creating graphical user interfaces. This library is cross-platform for X-Windows and Microsoft Windows.
4. Image Magick - An image manipulation library, distributed under the GNU Public License. It has facilities for format conversions between many different image formats. Also included are methods for loading and saving images.

Signatures:

Team:
Jeff Brubaker _____________________________
Travis Burnette _____________________________
Casey Hadden _____________________________
David Lamb _____________________________
Brian McKendrick _____________________________
Client:
Stephen Aylward _____________________________
Liz Bullitt _____________________________
Boss:
David Stotts _____________________________

Date:_____________________