Skip to main content

OpenEyes

The leading open source Electronic Patient Record (EPR) for ophthalmology

Key Features

Electronic Patient Records

Comprehensive EPR system designed specifically for ophthalmology clinics and eye care providers

Clinical Modules

Extensive suite of clinical modules covering examinations, operations, prescriptions, and more

Multi-Institution Support

Support for multiple institutions and sites with role-based access control

Worklist Management

Efficient clinical workflow and worklist management for optimal patient care

Document Generation

Automated correspondence and document generation for seamless communication

Integration Ready

RESTful API for integration with external systems and third-party applications

Get Started

Quickstart Guide

Get OpenEyes up and running in your environment quickly

Installation

Detailed installation instructions for production deployment

User Guide

Learn how to use OpenEyes for daily clinical workflows

Clinical Modules

Explore the comprehensive clinical module ecosystem

For Administrators

Configuration

Configure OpenEyes for your institution’s needs

Users & Permissions

Manage users, roles, and access control

Institutions

Set up multi-institution and multi-site configurations

System Settings

Configure system-wide settings and preferences

For Developers

Architecture

Understand the OpenEyes technical architecture

Module Development

Learn how to create custom modules and extend OpenEyes

Testing

Testing strategies and best practices

Contributing

Contribute to the OpenEyes project

API Reference

API Documentation

Explore the OpenEyes REST API for integration and automation

About OpenEyes

OpenEyes is a collaborative, open source project led by the Apperta Foundation. The goal is to produce a framework which allows the rapid and continuous development of an electronic patient record (EPR) for ophthalmology in particular and eye care in general.
OpenEyes is licensed under the GNU Affero General Public License v3.0 (AGPL-3.0). Users should undertake a safety assessment to confirm that deployment matches local clinical safety requirements.

Community & Support

Build docs developers (and LLMs) love