A small team from Louisiana, building the record around the work.

How it started.

Dr. Jibran Atwi practised medicine with software that recorded what he did and never helped him do it. The idea behind Breeze was an EHR that takes part in the diagnostic process: one that suggests what the record implies, checks what the clinician enters, follows up on what is ordered, and otherwise stays out of the way while a person writes.

The first decision was to build the record on FHIR, the healthcare data standard, from the start rather than adopt it later as a translation layer. Every part of Breeze reads and writes that record through the same interface. That is what made the system modular from the beginning, and it is what now makes it a platform other software, including AI, can build on.

How we build.

We are a small team, so we build things once and reuse them. The record is a written contract that the platform is assembled from. Actions with rules are named once and shared by the EHR, partner applications and agents. Decision support is deterministic and its rules are data a practice can read. The server at the center is open source. And we keep three statements apart in everything we say: built, verified in a deployment, and available to outside developers.

Where we are.

Breeze is built in Louisiana and is in daily use in medical practices. The platform underneath it is being opened so that a practice can choose the tools that help its team, including which AI, and change them as its needs evolve. The builder's view of that work is at breezehealthplatform.com.