Difference between revisions of "Geneva-The IHE Registration System"

From MircWiki
Jump to navigation Jump to search
Line 43: Line 43:
  
 
====Class hierarchy====
 
====Class hierarchy====
The various types of products and data objects which appear in a demonstration are reflected in classes which are organized as in this list:
+
The products and data objects which appear in a demonstration are reflected in classes which are organized as in this list:
  
 
* ConfigElement
 
* ConfigElement

Revision as of 15:33, 6 January 2010

This article captures information about the IHE Registration System, a tool used in IHE Connectathons and demonstrations. The intended autience for this article is developers working on the project and vendor participants using the system.

This article is intended for software developers who wish either to participate in the development project or simply to adapt the software for a special purpose.

1 Obtaining the RegSys2010 Source Code

The software for the program is open source. It is released under the RSNA Public License. It is maintained on a CVS server at RSNA headquarters. To obtain the source code, configure a CVS client as follows:

Protocol:           Password server (:pserver)
Server:             mirc.rsna.org
Port:               2401
Repository folder:  /RSNA
User name:          cvs-reader
Password:           cvs-reader
Module:             RegSys2010

Together, this results in the following CVSROOT (which is constructed automatically if you use something like Tortoise-CVS on a Windows system):

:pserver:cvs-reader@mirc.rsna.org:2401/RSNA

This account has read privileges, but it cannot write into the repository, so it can check out but not commit. If you wish to be able to commit software to the CVS library, contact the project manager.

2 Building the Software

When you check out the RegSys2010 module from CVS, you obtain a directory tree full of the sources and libraries for building the program. The top of the directory tree is RegSys2010. It contains several subdirectories. The source code is in the source directory, which has two child directories, one each for the Java sources and the files required by the program.

Building RegSys2010 requires the Java 1.6 JDK.

The Ant build file for RegSys2010 is in the RegSys2010 directory and is called build.xml. To build the software on a Windows system, launch a command window, navigate to the RegSys2010 directory, and enter ant all. This does a clean build. On a reasonably fast computer, a clean build takes about five seconds. The result is a file called RegSys2010-installer.jar in the products directory.

3 Installing the Program

To install the program, place the installer on a computer which has the Java 1.6 JRE and run it. The result will be a folder called RegSys2010 containing all the necessary files.

4 Running the Program

To run the program itself, it is best to run it from a command window because that allows you to provide more heap space for large images than the default provided by Java. Launch a command window and enter the command:

java -Xmx256m -jar RegSys2010.jar

For testing, or for situations which do not require additional heap space, the program can be running by double-clicking the RegSys2010.jar file.


5 Notes

The following are random notes to help developers.

5.1 Class hierarchy

The products and data objects which appear in a demonstration are reflected in classes which are organized as in this list:

  • ConfigElement
    • Product
      • DataSystem
        • EHRSystem
          • DCMSystem
        • PDQMgr
        • PIXMgr
          • Registry
      • Repository
    • Study
    • DocSet