Running a medical practice means treating people while being responsible for staff, IT, purchasing and billing. Those tasks do not disappear when the appointment book is full. They move into the evening or remain with an already busy team.
We want to organise this work differently. Doctors need to make clinical decisions. The infrastructure should support them and help the team with steps that do not need another medical decision.
Software needs to reuse information from the record
When a lab result arrives, the doctor reviews it and discusses it with the patient. For a later report to the referring doctor, they need both the result and the journal entry. The software must make this information available together so they do not have to find and transfer it again.
That is why we build cair.one. Patient records, documentation, appointments, tasks and billing share patient context. AI supports transcription, report preparation and the organisation of incoming documents. The team reviews proposals and approves them.
In practice operations, we also need to establish who reviews findings and follows up open tasks. A software function helps when the team knows how to use it in its own workflow.
Why we run a practice ourselves
We have operated our first pilot practice in Zurich under the medelio name since October 2025. We use the software there and see where workflows help and where they create extra work.
This gives development a short path from an observation to a change. Clinical experience, the practice assistants' perspective and software development meet around the same task. We can check whether a change helps in daily work.
When this article was originally published in February 2026, we planned a second site at Hardbrücke for June 2026. That announcement belongs to that stage of development. Current practice information is available from medelio.
We agree which tasks cair.one takes on
Our ambition extends beyond software. We want to connect medical work and operational assistance with clear responsibilities for the practice team. That includes shared processes and coordinated connections to laboratories and other providers.
The tasks cair.one takes on need to be explicitly agreed. The cair.one practice software is available as a standalone product. Assistance with practice operations is a separate offer. This distinction matters to a practice that operates part of its infrastructure itself.
The treating doctor remains responsible for treatment and the relationship with their patients. The doctor and the team should be able to rely on agreed processes and responsibilities for the work behind it.
Discuss your practice’s tasks with us
We welcome conversations with professionals who want to organise their practice work differently. Bring the tasks that occupy your team today. A specific workflow gives us a useful starting point for discussing what software and operational assistance can contribute.
