An Open Source electronic patient record system
PHP JavaScript CSS Cucumber HTML Shell
Latest commit 8a665e6 Aug 30, 2016 @mikepargeter mikepargeter committed on GitHub Merge pull request #404 from openeyes/release/v1.15.1
Failed to load latest commit information.
bin + added tags parameter to run-tests command Dec 9, 2015
features Introduce end of line normalisation Jul 15, 2016
grunt Merge remote-tracking branch 'across/feature/reports-dashboard' into … Feb 19, 2016
pdf replaced pdf with new help pdf. Aug 13, 2012
shared/img [OE-3731] Removed images from shared images directory and added a .gi… Jan 15, 2014
.bowerrc [OE-3731] Fixed grunt build and bower paths Jan 15, 2014
.editorconfig Merged master into OEM_169 Aug 4, 2014
.gitattributes Introduce end of line normalisation Jul 15, 2016
.gitignore Fixing issues from merge. Jul 21, 2016
.gitmodules clear out Oct 22, 2015
.htaccess cleanup Oct 22, 2015
.jshintrc OE-5327: Add mocha/chai to jshint file Mar 23, 2015
COPYING Reinstated missing license file Feb 4, 2016
Gruntfile.js Removed debug Sep 6, 2013
RELEASE + update RELEASE file Apr 14, 2016
UPGRADE + add details of changes to yii dependency in the project Sep 26, 2013
Vagrantfile Merge remote-tracking branch 'across/feature/reports-dashboard' into … Feb 19, 2016
bower.json Merge branch 'develop' into feature/worklists Jul 13, 2016
composer.json + introduce rrule library for server side validation May 12, 2016
composer.lock + introduce rrule library for server side validation May 12, 2016
exclude.txt Exclude file for archive building Mar 12, 2015
favicon.ico updated favicon to nice blue colour version Nov 29, 2011
index.php + reinstate autoloader Jun 28, 2016
package.json Moving jshint settings to .jshintrc file for use with linters other t… Feb 11, 2015



OpenEyes is a collaborative, open source, project led by Moorfields Eye Hospital. The goal is to produce a framework which will allow the rapid, and continuous development of electronic patient records (EPR) with contributions from Hospitals, Institutions, Academic departments, Companies, and Individuals.

The initial focus is on Ophthalmology, but the design is sufficiently flexible to be used for any clinical specialty.

Ophthalmic units of any size, from a single practitioner to a large eye hospital, should be able to make use of the structure, design, and code to produce a functional, easy to use EPR at minimal cost. By sharing experience, pooling ideas, and distributing development effort, it is expected that the range and capability of OpenEyes will evolve rapidly.


This is the main repository for development of the core OpenEyes framework. Event type modules are being developed in other repositories both by ourselves and third party developers. The OpenEyes Project Overview provides a list of currently stable modules. You may also be interested in our EyeDraw repository - this code is used by OpenEyes but may also be used independently.

The principal source of information on OpenEyes is the OpenEyes website

If you're interested in the OpenEyes project, join our announcements mailing list by sending a blank email to:

You can also send general enquiries to our main email address:

You can find us on twitter at:

Demo versions of OpenEyes featuring fictional patient data for testing purposes are available at: (u: username p: password).

Developers, developers, developers!

Developers can request to join our discussion list for third party developers by sending a blank email to:

If you need to share repositories with members of the core development team, you can find them listed as organizational members at:

OpenEyes follows the gitflow model for git branches. As such, the stable release branch is always on master. For bleeding edge development, use the develop branch.

Setup and installation documentation is available from the README file in the oe_installer repository.

We are beginning to evolve some documentation for developers on our github wiki including coding guidelines, working with the core team and our Event type module development guide.

Issues in the core should be logged through the github issues system for the moment. Though we will be making our internal JIRA system available in due course, and will transition logged issues across to this so that we can keep everything in one place Links for this will follow when this becomes available.

Dev Setup

To begin development, the simplest approach is:

  1. clone the repository
  2. run vagrant up
  3. run devsetup:

    vagrant ssh cd /var/www/protected ./yiic devsetup --resetfile=../features/testdata.sql


OpenEyes now supports full PDF printing using wkhtmltopdf, but it needs to be compiled with a patched QT library in order to work properly. As of version 1.12 a pre-compiled binary is shipped in the oe_installer repository. However, should you need to re-compile it, you can find instructions for doing this here.