EHRServer is the first open source Clinical Data Management and Sharing Platform, compliant with the openEHR standard. Use it as a:

• Primary clinical data repository for web and mobile clinical apps.
• Secondary repository for backup or analysis.
• Centralized repository to share clinical information between many systems.
• Fast prototyping of new health related apps, removing the need of creating the clinical repo yourself.
• Main or proxy repository for wearable and other monitoring-based clinical data.
• Standardized aggregation repository as a data source for ETL to datawarehouses and analytics tools.
• Research and training clinical data repository.
• Backend for Clinical Decision Support tools (e.g. rule engines)

EHRServer was designer for developers by developers. You don't need to be an openEHR guru to use it. Easy to install, use, manage and integrate.

Quick look at what is happening in the EHRServer.

Manage clinical document definitions from the Template Manager, defining what data could be stored and queried.

Very simple point and click query creation in seconds, no programming needed.

Mobile friendly user interface, adapts to small screens.

• REST API provides services to integrate the EHRServer to your systems and apps (documentation).
• Web Console provides a user interfaces for administrators of the EHRServer (check the screenshots above).
• Query Builder is the component in charge of creating, managing and executing queries over openEHR data stored in the EHRServer.
• SNOMED Query is a component in charge of processing the terminologic constraints in queries that contain SNOMED CT Expressions. This component is part of the SNQUERY tool developed by VeraTech
• EHR Base is where data is managed, indexed, versioned and stored.

• openEHR compliant clinical data repository
• Administrative Web Console
• Simple but powerful REST API
• Supports XML and JSON
• Full audit access for traceability
• Versioned clinical documents
• Query Builder from the Web Console to create data queries (no programming needed!)
• Support of SNOMED CT Expressions on openEHR queries (simplifies complex queries)
• Supports any structure of clinical document (following the openEHR standard information model)
• Vendor Neutral Archive
• Multitenancy

• Grails Framework
• Groovy
• Java
• MySQL

One way of supporting this project and our vision for building a completely open e-health platform, is through community donations. This is used for servers, dev tools, pay for dev time, maintain the website, updated documentation and guides.

• 10 USD
• 20 USD
• 50 USD

Another way of supporting the project is by subscribing to the CloudEHRServer

Thanks for your support!

• Let me know if you are using the EHRServer!
• Asks questions and get support
• Twitter
• LinkedIn Group
• Facebook Group

• Installing EHRServer
• Subscribe to CloudEHRServer

This guide is based on a Linux environment, should be adapted for other OS.

1. curl -s get.sdkman.io | bash
2. source "$HOME/.sdkman/bin/sdkman-init.sh"
3. sdk install grails 2.5.6
4. set version by default: Y
5. grails -version

Note: Grails should be 2.5.6!

1. install MySQL
2. copy the default root password
3. cd /usr/local/mysql/bin
4. ./mysql -u root -p
5. enter default root password
6. ALTER USER 'root'@'localhost' IDENTIFIED BY 'NEW-ROOT-PASSWORD';
7. CREATE DATABASE ehrserver;
8. exit

1. cd ehrserver/grails-app/conf
2. nano DataSource.groovy
3. change development password to NEW-ROOT-PASSWORD
4. save

Mandatory:

  export EHRSERVER_REST_SECRET="6067dba9-1417-41c5-b1af-92208c77ce77"
  export EHRSERVER_SNQUERY_KEY="22222222-2222-2222-2222-222222222222"

Optional:

  export EHRSERVER_EMAIL_FROM="[email protected]"
  export EHRSERVER_EMAIL_HOST="mail.yourdomain.com"
  export EHRSERVER_EMAIL_PORT=1234
  export EHRSERVER_EMAIL_USER="[email protected]"
  export EHRSERVER_EMAIL_PASS="youruserpassword"
  export EHRSERVER_ALLOW_WEB_USER_REGISTER=true

1. cd ehrserver
2. grails run-app
3. open http://localhost:8090/ehr
4. login with admin/admin/123456