Approved, build not started
MedPhone for ModMed practices.
MedPhone runs on athenahealth today. We are approved to integrate with ModMed and are prioritizing the build by practice demand.
We will not tell you ModMed works today when it does not. This page updates when it goes live.
What a ModMed front desk fields all day.
Specialty practices. Dermatology, ophthalmology, orthopedics, plastic surgery, gastroenterology, urology and ENT make up most of the base.
- Procedure scheduling, where the slot type and the prep instructions have to match
- Pre op questions in the days before, and post op checks in the days after
- Self pay and cosmetic consultation inquiries, which are revenue that never comes back if the phone rings out
- Pathology and imaging results, where the caller wants a person and a date
- Seasonal surges, because skin checks and allergy seasons do not spread themselves evenly
Specialty calls carry more clinical context than a primary care booking, and the cost of getting one wrong is higher. That is a real constraint on any phone automation, and it is why this build is not a copy of the primary care one.
Where the ModMed integration stands.
ModMed has approved MedPhone to integrate. The build has not started, so nothing is working yet and we are not going to imply otherwise.
What is real today is athenahealth, where MedPhone is answering patient calls in daily use. The call handling, the routing, the transfer rules and the writing back to the chart are all built and working. What changes per EHR is the connection underneath.
Practices on the list get told first when ModMed goes live, and they shape which workflows we build first.
What we would build first for ModMed.
A specialty build is not a primary care build with the name changed. These are the four we would take first on ModMed, chosen because they are where a wrong answer on the phone costs the most.
Procedure scheduling where the slot type, the length and the prep instructions all have to agree, rather than a generic appointment that a human has to correct later
The pre operative and post operative windows, which generate a burst of calls on a predictable schedule and almost never get a dedicated person
Cosmetic and self pay enquiries, which are the callers least likely to leave a message and the ones worth the most when they connect
Pathology and imaging results, where the caller wants a person and a date and a portal message will not settle it
Straight answers about ModMed.
Does MedPhone work with ModMed today?
No. ModMed has approved MedPhone to integrate, and the build has not started. Nothing is working yet and we are not going to imply otherwise. MedPhone is live in production on athenahealth.
Why does a specialty build take longer?
Specialty calls carry more clinical context than a routine booking, and the cost of getting one wrong is higher. Slot types, prep instructions and what may safely be answered without a clinician all differ by specialty, so the rules have to be built for the practice rather than assumed.
What moves ModMed up the queue?
Demand from practices that want it, and access to real scheduling rules to build against. The list is how we decide the order. Telling us your specialty and your call volume genuinely changes where it sits.
What MedPhone does in production today.
Running on athenahealth today. This is what comes to ModMed when the integration lands.
- Answers every inbound patient call on the first ring, on hours and after
- Books, reschedules and cancels appointments against the provider schedule
- Takes prescription refill requests and routes them to the provider inbox
- Collects insurance details and flags mismatches for the front desk
- Transfers complex or urgent calls to your team on rules you set
- Writes a summary of every call back to the patient chart
Be first on MedPhone for ModMed.
Tell us your practice size and call volume. We will tell you honestly where ModMed sits in the queue, and you can see the athenahealth build running in the meantime.