AppertaFoundation / openeyes

An Open Source electronic patient record system. This is the Gold Master "Community Edition" release. Please note that this could be up to 3 months behind the latest development tip. If you are interested in being involved with latest developments, please email openeyes@apperta.org or visit
https://openeyes.apperta.org
GNU Affero General Public License v3.0
74 stars 44 forks source link
epr eyecare openeyes

OpenEyes logo

OpenEyes

OpenEyes™ is the leading open source Electronic Patient Record (EPR) for ophthalmology.

Table of contents


Description

OpenEyes is a collaborative, open source, project led by the Apperta Foundation (http://openeyes.apperta.org). The goal is to produce a framework which will allow the rapid, and continuous development of an electronic patient record (EPR for ophthalmology in particular and eye care in general). Clinical and technical contributions are made by 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. OpenEyes should also be of value for use by non-medical staff such as optometrists in the delivery of shared programs of eye care.

Disclaimer


OpenEyes is provided under an GNU Affero GPL v3.0 (AGPL v3.0) license and all terms of that license apply (https://www.gnu.org/licenses/agpl-3.0.en.html). Use of the OpenEyes software or code is entirely at user risk. The Apperta Foundation does not accept any responsibility for loss or damage to any person, property or reputation as a result of using the software or code. No warranty is provided by any party, implied or otherwise, for use of the software or code. This software and code is not guaranteed safe to use in a clinical environment; any user is advised to undertake a safety assessment to confirm that deployment matches local clinical safety requirements.

Setup


Detailed installation instructions to build each version can be found on the project wiki page here.

Issues and support

Issues in the core should be logged through the github issues system.

Please be aware that no service level agreement exists for the open source project and no support can be given via github. The team will do their best to fix any critical issues reported, but no guarantees are given.

Official implementation and support is available from our Accredited Professional Services Partner Network. A list of available partners can be found at the following link openeyes.apperta.org.

Resources


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 Accredited Contributors. 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, or for general enquiries, email: openeyes@apperta.org

You can find us on twitter at: http://twitter.com/openeyes_oef

Contributing


If you are thinking of making a contribution to OpenEyes please contact our team at openeyes@apperta.org.

If you need to share repositories with members of the core development team, you can find them listed as organizational members at: https://github.com/openeyes

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.


Copyright and license