You are here

Project Wizard

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

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.

ImageJ

Rating: 
Your rating: None Average: 3.4 (14 votes)

ImageJ is a public domain Java image processing program inspired by NIH Image for the Macintosh. It runs, either as an online applet or as a downloadable application, on any computer with a Java 1.4 or later virtual machine. Downloadable distributions are available for Windows, Mac OS, Mac OS X and Linux.

RT_Image

Rating: 
Your rating: None Average: 4 (4 votes)

RT_Image is an application developed in the Department of Radiation Oncology and MIPS at Stanford University. Coded in the Interactive Data Language (IDL, ITT Visual Information Solutions), RT_Image was originally designed in 2003 to generate radiotherapy target volumes from positron emission tomography (PET) datasets. It has since evolved to embody a variety of tools for visualizing, quantitating, and segmenting three-dimensional images.

Ruby HL7

Rating: 
Your rating: None Average: 2.4 (5 votes)

Ruby HL7 is a simple library for parsing and generating HL7 2.x messages. 3.x support is planned in the future.

cancer Biomedical Informatics Grid (caBIG)

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

The National Cancer Institute (NCI) has launched the caBIG initiative to accelerate research discoveries and improve patient outcomes by linking researchers, physicians, and patients throughout the cancer community.

Bots

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

"Bots for the translations and communication needed in Electronic Data Interchange (EDI). Bots has three main functions: 'Any-to-any-format' data conversions, (Secure) communications and manage and overview EDI data flows."

Chiapas

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

Chiapas is an enterprise level HIPAA data translation package. It supports all major healthcare transactions and a variety of SQL databases and file types, and incorporates a script parser and a GUI studio for development and maintaining specifications.

Dataserver

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

"DataServer is an open source XML gateway, specially tailored for the medical domain. DataServer is middleware, situated between clients and traditional Health Information Systems (HIS), Radiology Information Systems (RIS) and Picture Archive and Communication Systems (PACS). It supports relational (SQL), SOAP, and HTTP data sources out of the box, but is highly extensible for custom types."

REMITT

Rating: 
Your rating: None Average: 5 (1 vote)

REMITT is a revolutionary medical information translation and transmission system, which is primarily used for preparing and submitting medical billing data.

REMITT works independent of any specific electronic medical record (EMR) or practice management (PM) system, and can interface with any EMR or PM system which implements its application programming interface (API). The first system to do so has been FreeMED.

Currently Supported Formats

  • HCFA-1500/CRM-1500
  • ANSI NSF X12 837 Professional

Currently Supported Output Types

IDRT - Integrated Data Repository Toolkit

Rating: 
No votes yet

i2b2 has turned out to be a very valuable component for secondary use of routine clinical data. Its pragmatic database schema allows merging of data from heterogeneous data sources, and the intuitive user interface enables easy querying and powerful processing. However, it's a component rather than a complete solution: The user is facing several barriers when integrating i2b2 into the operational workflow.

Pages