Eureka! Clinical Analytics Service
Georgia Clinical and Translational Science Alliance (Georgia CTSA), Emory University, Atlanta, GA
What does it do?
It provides backend services for managing phenotypes, cohorts and running phenotyping jobs.
Version 2.0
Support the new job modes, and update dependencies.
Version 1.0
This service is a refactoring of the eureka-services module of the eureka project. It replaces the eureka-services module. The current functionality is the same as in the last release of the eureka project.
Build requirements
Runtime requirements
- Oracle Java JRE 8
- Tomcat 7
- Also running
- The eurekaclinical-analytics-webapp war
- The eurekaclinical-protempa-service war
- The eurekaclinical-user-webapp war
- The eurekaclinical-user-service war
- The cas-server war
REST APIs
Building it
See the parent project's README.md.
Performing system tests
See the parent project's README.md.
Installation
Configuration
This webapp is configured using a properties file located at /etc/eureka/application.properties
. It supports the following properties:
cas.url
: https://hostname.of.casserver:port/cas-servereureka.common.callbackserver
: https://hostname:porteureka.common.demomode
: true or false depending on whether to act like a demonstration; default is false.eureka.common.ephiprohibited
: true or false depending on whether to display that managing ePHI is prohibited; default is true.eureka.support.uri
: URI link for contacting support. Could be http, https, or mailto.eureka.support.uri.name
: Display name of the URI link for contacting support.eureka.services.url
: URL of the server running the services layer; default is https://localhost:8443/eurekaclinical-analytics-service.eureka.services.callbackserver
: URL of the server running the services layer; default is https://localhost:8443.eureka.services.defaultprops
: concept subtrees to show in the concept tree: default is Patient PatientDetails Encounter ICD9:Diagnoses ICD9:Procedures ICD10:Diagnoses ICD10:Procedures LAB:LabTest MED:medications VitalSign
A Tomcat restart is required to detect any changes to the configuration file.
WAR installation
- Stop Tomcat.
- Remove any old copies of the unpacked war from Tomcat's webapps directory.
- Copy the warfile into the Tomcat webapps directory, renaming it to remove the version if necessary. For example, rename
eurekaclinical-analytics-service-1.0.war
toeurekaclinical-analytics-service.war
. - Start Tomcat.
Maven dependency
<dependency>
<groupId>org.eurekaclinical</groupId>
<artifactId>eurekaclinical-analytics-service</artifactId>
<version>version</version>
</dependency>
Developer documentation
Getting help
Feel free to contact us at [email protected].