Developed by at The Children's Hospital of Philadelphia Research Institute

Discover Harvest

Explore your data, not your database.

Designed by and for biomedical researchers, The Harvest Stack is an open source BSD-licensed toolkit for building web applications for integrating, discovering, and reporting data.

Try A Demo Watch Read More

Open Source & Available on GitHub

We believe in open source software and open-source our work. Harvest is licensed under BSD 2-clause License.

Web-Based Technologies

Harvest comes with an HTML5 web client backed by a set of discoverable REST APIs.

Designed for Biomedical Data First

Created by the Department of Biomedical and Health Informatics at The Children's Hospital of Philadelphia Research Institute, Harvest addresses the unique needs of biomedical researchers.

Nationally Funded

Eunice Kennedy Shriver National Institute of Child Health and Human Development (NICHD), National Institute on Deafness and Other Communication Disorders (NIDCD), National Heart, Lung and Blood Institute (NHLBI), and others have funded Harvest applications.


The Harvest manuscript has been published in the Journal of the American Medical Informatics Association (JAMIA). See other press and media about Harvest on our resources page.

Mailing List

Stay in touch! Sign up for our email list to get periodic updates on Harvest, blog posts, and invitations to future webinars.

Don't worry! We will never spam you or give your email to anyone else.


Do you have any questions about Harvest? Hop into the Harvest chatroom to talk to members of the Harvest team.

Latest Article

Setting Up a Development Environment

This page provides instructions for setting up a local environment for developing and testing Avocado, Cilantro, and Serrano. To begin, checkout a local copy of the following repositories:

Navigate to the OpenMRS directory and switch to the demo branch with:

git checkout demo 

I suggest doing the following steps after setting up a virtual environment so all the modules installed with pip won't conflict with other projects. Whether you choose the virtualenv approach or not, the remaining instructions remain the same. Also, for the remainder of this page, I will assume you have a common directory containing all the repos checked out above. If... continue reading