Custom Software
Clinic operations software that sits beside the EHR instead of fighting it
Oak & River’s EHR handled charts. Everything around the visit — rooms, devices, referral packets — did not. We built an operations layer the front desk uses all day.
The operational problem
The EHR was fine for clinical notes and billing codes. It was a poor fit for “which room is free” and “did the referral packet leave.”
Staff kept a second system in their heads. Patients waited while someone walked the hall.
What was breaking down
- Room status on sticky notes
- Referral packets assembled at the end of the day
- Device checkout on a clipboard
How Striders Tech approached it
We did not rip out the EHR. We built the missing operations objects: rooms, devices, packets, and hand-offs, synced on patient identifiers the clinic already uses.
What we built
- Room and chair status board
- Referral packet checklist with owner
- Device checkout tied to a visit
- Read-only EHR identifiers, no double charting
Results the team can measure
- Hall walks down because room state is on the board
- Packets leave the same day as the visit
- No EHR rip — clinical workflow stayed put
Who this case study is for
Clinics that will not replace their EHR but need the building to run like an operation.
Oak & River Clinic operates in healthcare operations. The work is a custom system designed around their process, not a generic template with extra fields bolted on.
What changed after the system went live
down because room state is on the board
leave the same day as the visit
— clinical workflow stayed put