Skip to content
This repository

An Open Source electronic patient record system

branch: master
Octocat-spinner-32 assets Clean up .gitignore
Octocat-spinner-32 bin Fix quoting on git wrapper
Octocat-spinner-32 cache Prop cache folders
Octocat-spinner-32 docs + tweaks to css layout for highlight-fields (op note)
Octocat-spinner-32 features Merge branch 'release/1.6' of in…
Octocat-spinner-32 grunt [OE-3731] Fixed grunt build and bower paths
Octocat-spinner-32 junit_behat_reports [OES-125] - adding junit reports for the behat jobs
Octocat-spinner-32 pdf replaced pdf with new help pdf.
Octocat-spinner-32 protected Merge branch 'master' into release/1.6
Octocat-spinner-32 puppet Ci copy test.sample.php into test.php
Octocat-spinner-32 shared [OE-3731] Removed images from shared images directory and added a .gi…
Octocat-spinner-32 .bowerrc [OE-3731] Fixed grunt build and bower paths
Octocat-spinner-32 .editorconfig Merge branch 'master' into develop
Octocat-spinner-32 .gitignore [OE-3731] Fixed grunt build and bower paths
Octocat-spinner-32 .gitmodules Use https for yii
Octocat-spinner-32 .htaccess.sample Don't rewrite assets
Octocat-spinner-32 .travis.yml Disable travis builds
Octocat-spinner-32 COPYING GPLv3 COPYING file.
Octocat-spinner-32 Gruntfile.js Removed debug
Octocat-spinner-32 Update
Octocat-spinner-32 RELEASE Merge branch 'master' into release/1.6
Octocat-spinner-32 UPGRADE + add details of changes to yii dependency in the project
Octocat-spinner-32 Vagrantfile [OE-3966] Removed /tmp/behat dependency from Vagrantfile, moved scree…
Octocat-spinner-32 behat.yml [OE-3377] - added test suites in phpunit.xml and extra CI profile to …
Octocat-spinner-32 bower.json Import flot.
Octocat-spinner-32 composer.json [OES-125] - adding abstract OpenEyesPage class to autoloader
Octocat-spinner-32 composer.lock update composer.lock to the latest tag of code-coverage
Octocat-spinner-32 favicon.ico updated favicon to nice blue colour version
Octocat-spinner-32 index.example.php Change yii path in example index file
Octocat-spinner-32 package.json Renamed grunt docs tasks to createdocs and replace matchdep with load…



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 documentation section of the website

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.

Something went wrong with that request. Please try again.