1h
1health

Blog

Notes from the platform team

Plain-English explainers for people building clinical software on 1health.

You build the app. 1health runs the plumbing. Three layers: your app on top, which you keep; 1health in the middle; a server and database at the bottom, where AWS and Supabase stop.

The backend for healthcare apps: what you keep, what 1health runs

AWS and Supabase give you a server and a database. 1health runs the healthcare layer on top — identity, records, connections, compliance. You keep the app.

Read →
Diagram: one patient's medical record at the center, with the brand, the medical group, the compounding pharmacy, and the lab each sending data into it.

What a peptide clinic actually needs from its software

Peptides are becoming legal to compound again, and the companies selling them are being audited from day one. Here is what their software has to do.

Read →