source: EDIS/trunk/java/README@ 1314

# Emergency Department Integration Software

Emergency Department Integration Software (EDIS) incorporates several Web-based views that extend the current Computerized Patient Record System (CPRS) to help healthcare professionals track and manage the flow of patient care in the emergency- department setting.

## How to build

This project is built using maven (currently version 3.0.3).  You can download
and install maven from http://maven.apache.org.  The whole build can be invoked
from the command line from the tracking-parent directory:

        $ mvn clean package

The Flex user interface artifacts are built with the "flexmojos" maven plugin (currently version 4.0).
In order for maven to run the Flex unit tests you will also need Adobe's Flash Player installed and in
your PATH.  See <https://docs.sonatype.org/display/FLEXMOJOS/Running+unit+tests> for more info.  To skip
the unit tests, use:

        $ mvn clean package -DskipTests=true
        
## Build Artifacts      
        
The main web application artifact produced by the build will be at:

        tracking-server-main/target/main.war                    Main EDIS web application (including bigboard require user login)

Optional artifacts include:

        tracking-server-help/target/help.war                    Help files
        tracking-server-bigboard/target/bigboard.war    EDIS big board designed for use with no logged in user (requires configuration)
        tracking-server-ear/target/edis.ear                             main.war, help.war, bigboard.war packaged as an .ear
        
Pick and choose which are appropriate depending on your deployment platform and configuration.

## Configuring VistALink

Currently, VistALink connection settings are "baked in" to the web application in the following file:

        tracking-server-main/src/main/web-app/WEB-INF/config/vistalink-config.xml
        
You can either edit this before performing a build so that main.war contains your connection settings, or do it after deploying main.war to your servlet container in "exploded" mode.

Possible future development could store this connection information with some alternative implementation, like in a relational database, for example. One could potentially write a VistALink connection info administration UI as well.

## Configuring SSL

Currently, EDIS is not configured to enforce channel security over SSL, though it should be able to run over SSL if you have configured your servlet container to serve it over SSL, which you most certainly should do.  If you'd like it to serve user-friendly welcome pages over port 80 and still require SSL for other bits, you will need to tweak the spring-security configuration located at:

tracking-server-main/src/main/web-app/WEB-INF/config/security-config.xml

The main web application uses the spring security framework (version 2.0.7) to implement its security layer.  You can read more about it here:
http://static.springsource.org/spring-security/site/docs/2.0.x/reference/springsecurity.html

## EDIS Big Board Automatic Login with No User

Currently the EDIS Big Board web application (bigboard.war) has no authentication mechanism configured at all.  VA's implementation was a WebLogic specific 2-way SSL authentication mechanism.  If you want automatically authenticating big boards you will need to implement the equivalent yourself.

The main EDIS application (main.war) contains a copy of the Big Board that runs as a signed-in user, which should work as a starting point.