Why OpenScribe exists #7
Replies: 1 comment 1 reply
-
|
Hi @sammargolis I’m a former software engineer (over 10 years in the field), and today I’m an entrepreneur running a small neurology clinic together with my wife. While exploring open-source tools that could help us in our day-to-day clinical workflow, your project immediately stood out as something potentially very useful. I had a couple of questions: Does the project currently support transcription in languages other than English? If so, which ones, and how mature is that support? Would you be open to the idea of providing an official Docker image (or docker-compose setup) to simplify deployment and adoption? That would make experimentation and self-hosting significantly easier for teams like ours. Thanks again for sharing this — I’d be happy to provide feedback from a real clinical environment if that’s useful. Best regards, |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
OpenScribe exists because AI medical scribes are becoming commodity infrastructure, but most implementations are closed, cloud-first, and opaque.
This project treats the medical scribe as developer infrastructure:
The goal is not to compete on features with commercial scribes.
The goal is to provide a transparent, extensible base that teams can self-host, audit, and build on.
If you are here to:
You are in the right place.
Beta Was this translation helpful? Give feedback.
All reactions