About
A specialty IT shop, on purpose.
Most healthcare IT vendors take any client. We don't. We work with reproductive health and abortion care providers because that's the corner of medicine we know deeply — and that depth is why we're worth hiring.
What sets us apart
Our medical director is also a software engineer.
The thing that distinguishes MAHT from generalist healthcare IT vendors is small but load-bearing: our medical director, Ro Tucker, DNP, is a practicing nurse midwife who spent ten years in software engineering before going into medicine.
That's why we talk like clinicians instead of like vendors. It's why our questions about your workflow are specific — Ro has worked the shifts you're describing. It's why we don't accidentally build software that looks great in a demo and then frustrates the staff who actually have to use it eight hours a day.
Most healthcare IT teams have to translate between people who understand the technology and people who understand the work. We do less of that translation, because the same person on our team is doing both jobs.
The team
Four people who've each been in this work a long time.
Medical Director
Ro Tucker, DNPthey/she
Ten years building high-volume cloud platforms — email systems, e-commerce, inventory, and CMS — before moving into medicine. Now thirteen years into reproductive health.
Ro is a practicing Certified Nurse Midwife and Women's Healthcare Nurse Practitioner, with a Doctorate in Nursing Practice and a Master of Public Health. The reason MAHT can talk fluently about clinic workflows is that they've worked them.
Chief Cloud Architect
Russellhe/him
Twenty-five-plus years in IT, focused on cloud architecture and secure application development.
Russell's track record includes HIPAA-compliant healthcare integrations — the kind of cross-system plumbing that has to hold up to long-term audit, not just initial review.
IT Operations Director
Johnhe/him
Healthcare IT operations and support, with direct experience working with reproductive healthcare providers specifically.
John knows the operational and security demands this specialty places on systems because he's been the person on call when those demands are tested.
Junior Developer
Tythey/them
Software developer working across MAHT's integration and patient-facing projects. Ty picks up the parts where careful detail matters most — the small interfaces clinic staff actually click and the plumbing that keeps systems honest about how data moves between them.
We say no often.
We turn down work outside our specialty. Some of it would pay well. None of it would be done as well as the work that's actually inside our wheelhouse, and a small shop's reputation is the sum of every project it's said yes to. So we say no a lot, and we mean it.
We sweat the boring stuff.
The careful patterns — log redaction, tested backups, rehearsed migrations, role-aware access — are where most vendors quietly skip. They're also where most failures hide. The interesting parts of our work depend on the boring parts being right, so we don't separate them.
We keep working after launch.
Software ships and then keeps running. We treat ongoing reliability and improvement as part of the contract, not a separate line item you have to remember to renew. The point isn't a successful go-live; it's a year from now, when nobody on your team has had to think about the system in months.