Slicer3/DICOM import mechanism

From Slicer Wiki
Revision as of 20:05, 9 March 2010 by Lorensen (talk | contribs) (Created page with 'Some DICOM-enabled applications have import mechanisms that run in the background. One system, the GE Advantage Windows Workstation, monitors a specific directory and imports dic…')
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search
Home < Slicer3 < DICOM import mechanism

Some DICOM-enabled applications have import mechanisms that run in the background. One system, the GE Advantage Windows Workstation, monitors a specific directory and imports dicom files that arrive into that directory.


Proposal 1:

Create a program (without a user interface) that monitors a specific directory for dicom files. When a file arrives in this directory, the program parses the file and populates an SQL database. This database can be accessed by other applications that may or may not have a user interface. For example, Slicer3 could provide a GUI to browse the database and load user selected DICOM series.

Issues

  1. Should the program move the DICOM files to another location once they arrive
  2. On startup, should the program synchronize the database with existing files. For example, if a user deletes the DICOM files with an OS command like rm, should the program delete the corresponding entries in the database, or, should the sync be user driven.