Community

JupyterHealth follows the Jupyter Code of Conduct. See jupyterhealth.org to talk to the team about a deployment or integration.

• Chat in the #jupyterhealth channel on the Jupyter Zulip.

• Use GitHub Discussions to ask questions, share your experience, or report problems you run into.

• Code lives at github.com/jupyterhealth.

• Software discussion that spans components goes in jupyterhealth-software. Components generally have their own repositories and issue trackers.

• The JupyterHealth Team Compass has meeting notes and how the team works.

• Initiatives tracks larger project goals.

Contributing¶

JupyterHealth is an open project, and we welcome contributions from anyone. While it began with the core team described in Origins and governance, it aims to grow its community and welcome new contributors and co-leads.

There are many ways to help! Reporting a bug, improving the docs, sharing how you use JupyterHealth, and answering questions in Zulip all make a difference.

Open an issue in a component’s repository, or ask in Zulip if you’re not sure where something belongs. Fixes to this site go to jupyterhealth.github.io.

Origins and governance¶

JupyterHealth was founded at UC Berkeley and UCSF, and is developed with partners in open source scientific computing and digital health. JupyterHealth is governed as a JupyterHub subproject. The JupyterHealth website shows the team and participating institutions.

Learn more about JupyterHealth¶

• Platform page on jupyterhealth.org: the platform’s components and the standards it uses.

• JupyterCon 2025 talk: a platform overview from the project leads.

• IEEE Pulse article: an interview with co-director Ida Sim on open infrastructure for health wearables.

• Berkeley launch announcement: the initiative that started the project.