The Connector

Our medical-records system is a closed box — it has no easy, reliable way for our own software to read the schedule or book an appointment. So when our AI texts a patient "Thursday at 2 works — booked," that only means something if it can actually reach into the records system and put it on the calendar.

I built the connector that lets every other system we run talk to the medical-records system in plain, dependable terms: check who's free, find an open slot, create a real appointment, pull a patient's history. It's the quiet layer underneath the texting AI, the staff dashboard, and the booking tools — the thing that turns "the AI said it booked you" into an appointment that's actually on the schedule.

1. When the AI agrees on a time with a patient, the connector creates the appointment directly in the records system — no clunky scheduling link, no front-desk re-typing.
2. It reads the live schedule so the AI never offers a time that's already taken or a day we're closed.
3. It carries patient details both ways, so a text conversation, the records system, and the patient database all stay in sync.
4. We run our own copy of this wiring on hardware we control, instead of depending on an outside vendor's server we couldn't see or fix.
5. It's built to fail safely: if the connection ever hiccups, the patient still gets a clean fallback instead of a broken or duplicate booking.

Patients can now book and reschedule by text and have it land as a real appointment in seconds, with no staff member in the middle. The practice owns the wiring instead of renting a fragile one — which also clears the path to drop a costly outside connector.