More choice as your tools evolve.
Our direction is an open platform that lets your organization choose and change the software working with its clinical systems, including choices about AI, extensions, and who operates the platform.
We will make those choices concrete through published interfaces and explicit release terms. The core server is open source; Breeze-specific clinical definitions are currently proprietary, and the complete platform is not yet offered as an independently deployable package. A demonstration shows which workflows are available in the offered deployment and which integrations are still being developed.
Open at three levels.
Access. Documented interfaces to the record and to the workflow actions, so the tools your team chooses can take part in the work, not only read about it.
Extension. The ability to extend or replace a service: choose the AI provider, the terminology source, a connection, a specialty application, without replacing the record.
Operation. Inspectable software with a viable path to operating the platform independently, so a practice or a partner is not bound to Breeze as an operator in order to keep its record.
The choices that stay yours.
Which AI. A model or an agent is a caller of the same interface as everything else. The platform is not tied to one vendor's model, and changing that choice does not change the record.
Which tools. A specialty application, a patient-facing app or an analytics tool enters at the same boundary the EHR uses, with the same permissions and the same rules applied.
Which connections. A different laboratory, registry or messaging channel is a new connection on the platform, not a new system.
Where your data goes. The complete record, with history, can be exported in the standard bulk format at any time. See Integration.
What is released today, plainly.
The server at the center of the platform is open source. Breeze's own clinical definitions, the contract that describes the record and its actions, are proprietary at present. The complete platform is not yet offered as a package a practice or partner could deploy independently. We will make those terms concrete through published interfaces and explicit release terms, and until then we say so here rather than imply otherwise.
What a demonstration shows.
A demonstration of Breeze EHR shows the workflows available in the deployment you would use and names the integrations still being developed. Bring the workflow where your team needs deeper integration, and we will show which parts exist today and which are direction.