Ottehr
masslight · Health & fitness
GitHub stars
336Stats updated
What is Ottehr?
Ottehr packages patient-facing intake and scheduling, a staff-facing clinical application, and backend endpoints into one TypeScript monorepo. It is designed to be adapted to a practice's workflows while retaining required attribution while relying on Oystehr for FHIR storage and hosted platform services. Its current custom license adds restrictions beyond standard open-source terms.
Ottehr is an open-source, modular EHR designed to be forked and white-labeled for health-tech products. It includes a patient portal, a staff-facing EHR, and backend endpoints for appointments and telemedicine.
Core capabilities
- Run patient registration, paperwork, scheduling, messaging, and a portal
- Manage queues, encounters, notes, prescriptions, orders, telehealth, and tasks
- Extend a modular React and serverless architecture backed by FHIR services
Patient, staff, and backend applications
The patient portal handles appointments, check-in, intake, messages, and telemedicine entry. The provider EHR manages schedules, queues, encounters, charting, orders, prescriptions, tasks, and revenue workflows. Serverless Zambdas connect both applications to Oystehr's FHIR and platform services.
- patient portal
- EHR
- Zambdas
- FHIR
A configurable clinical workflow
The monorepo uses React applications, shared packages, configuration schemas, infrastructure code, and backend endpoints so a development team can alter presentation and behavior. The official deployment path requires an Oystehr account, and the custom license constrains attribution and competing uses; it is not a fully independent open-source backend.
- React
- TypeScript
- configuration
- Oystehr
License requires specific review
GitHub cannot assign an SPDX identifier to the current license. The repository text permits broad source use but includes attribution, competing-product, AI-training, and reciprocal obligations and offers a separate commercial arrangement. Adopters should review those terms directly instead of assuming a standard OSI license.
- source-available
- custom license
- attribution
- commercial use
Where it fits
Use cases
- 01
Launch a customized urgent-care record
Adapt the patient and staff applications, configure locations, schedules, paperwork, templates, and clinical workflows, and use Oystehr services for shared FHIR-backed data. Check the custom license before rebranding or commercial deployment.
- 02
Join in-person and virtual visits
Let patients register, complete intake, receive messages, enter a waiting room, and join telehealth while staff manage queues, appointments, charts, tasks, and communication from the provider application.
- 03
Carry a visit into orders and revenue work
Move encounter documentation into prescriptions, laboratory or imaging orders, insurance eligibility, payments, coding, claims, denials, and reporting without building each workflow as a separate front end.