You are here

Project Wizard

You can use the category filters given on the right sidebar to narrow down your search results.

BioSig

Rating: 
No votes yet

BioSig is an open source software library for biomedical signal processing, featuring for example the analysis of biosignals such as the electroencephalogram (EEG), electrocorticogram (ECoG), electrocardiogram (ECG), electrooculogram (EOG), electromyogram (EMG), respiration, and so on. Major application areas are: Neuroinformatics, brain-computer interfaces, neurophysiology, psychology, cardiovascular systems and sleep research. The aim of the BioSig project is to foster research in biomedical signal processing by providing open source software tools for many different applications.

ODIN

Rating: 
No votes yet

"ODIN is a C++ software framework to develop, simulate and run magnetic resonance sequences on different platforms."

XMedCon

Rating: 
Your rating: None Average: 1.9 (7 votes)

The project stands for Medical Image Conversion. Released under the (L)GPL licence, it comes with the full C-source code of the library, a flexible command-line utility and a neat graphical front-end using the Gtk+ toolkit. The supported formats are: Acr/Nema 2.0, Analyze (SPM), Concorde/µPET, DICOM 3.0, CTI ECAT 6/7, NIfTI-1, InterFile3.3 and PNG or Gif87a/89a.

Medical Imaging Interaction Toolkit (MITK)

Rating: 
Your rating: None Average: 4.8 (12 votes)

The Medical Imaging Interaction Toolkit (MITK) is a free open-source software system for development of interactive medical image processing software. MITK combines the Insight Toolkit (ITK) and the Visualization Toolkit (VTK) with an application framework. As a toolkit, MITK offers those features that are relevant for the development of interactive medical imaging software covered neither by ITK nor VTK.

Core features of the MITK platform:

PixelMed Java DICOM Toolkit

Rating: 
Your rating: None Average: 3.6 (15 votes)

PixelMed Java DICOM Toolkit is a stand-alone DICOM toolkit that implements code for reading and creating DICOM data, DICOM network and file support, a database of DICOM objects, support for display of directories, images, reports and spectra, and DICOM object validation.

The toolkit is a completely new implementation, which does not depend on any other DICOM tools, commercial or free. It does make use of other freely available pure Java tools for compression and XML and database support.

Snofyre

Rating: 
No votes yet

Snofyre is an open source, service oriented API for creating SNOMED CT enabled applications in Java. It provides a number of SNOMED CT related services out of the box. These services can be used:

  • as a starter for understanding how to add SNOMED CT functionality to an application.
  • to rapidly prototype a SNOMED CT enabled application.

Snofyre API aims to

  • reduce the 'ramp up' time needed to understand
  • and embed SNOMED CT functionality in an application.

Charrua DICOM Toolkit

Rating: 
Your rating: None Average: 3 (2 votes)

DICOM basic constructs used to create the tools at CharruaSoft.com. Its C++ code is a re-interpretation of the original UCDMC library by Mark Oskin. It tries to be much simpler and compact, also uses many Borland VCL specific structures.

Grassroots DICOM (GDCM)

Rating: 
Your rating: None Average: 3.7 (11 votes)

Grassroots DICOM (GDCM) is an implementation of the DICOM standard designed to be open source so that researchers may access clinical data directly. GDCM includes a file format definition and a network communications protocol, both of which should be extended to provide a full set of tools for a researcher or small medical imaging vendor to interface with an existing medical database.

FreeSHIM

Rating: 
Your rating: None Average: 1 (2 votes)

FreeSHIM is an opensource electronic medical device interface, which aims to allow any EMR/PM system to talk to any medical device attached to a workstation without having to install tons of pesky drivers or “reinvent the wheel” for each additional device manufacturer.

It is written in Java, and has been tested on Linux and Windows workstations (though we’re pretty sure it also runs fine on Mac OS X as well), and exposes both SOAP and REST interfaces. Its only prerequisite is a running J2EE container, such as Apache Tomcat.

Pages