MDLand integration
An AI receptionist for MDLand iClinic practices.
Independent physician practices on a cloud EHR, many of them in and around New York and part of a wider physician network, where the phone rings in more than one language and the front desk is already stretched before nine.
Writing to MDLand
Real time, on the call
Writing…
Encrypted in transit, audit-logged
Who runs MDLand
MDLand practices are mostly independent physicians: primary care, internal medicine, paediatrics and specialists who chose a cloud EHR so they could stay independent without running a server. Many sit inside an IPA, ACO or similar network, which brings quality measures and reporting on top of the daily work. The desk is small, the patient list is long, and a good share of callers would rather speak Spanish than English.
The problem
What is actually breaking.
The things practices tell us cost them the most, in the order they raise them.
The morning rush lands on one or two people
Bookings, refill requests, result questions and insurance checks all arrive in the first two hours, and whoever is on the desk is also checking patients in. The overflow goes to voicemail and stays there until the afternoon.
Callers who prefer Spanish wait longer
When only one person on the team speaks Spanish, those calls queue for that person or end with a callback. The patients who most need a clear answer get the slowest one.
Open slots go unfilled
Cancellations and no-shows leave gaps that nobody has time to backfill, and the visits a network expects to see happen, annual and follow-up visits included, slip quietly.
Nobody wants another system
The practice already works in iClinic every day and has no appetite for another login, another schedule or a migration. Anything new has to fit around what is there.
How it connects
Real time
Written while the patient is still on the line. Every write logged and reversible.
How 2care solves it
One platform, not a point fix.
Inbound answering, outbound outreach, write-back and escalation are the same agent - which is why the whole problem moves rather than one part of it.
Every call answered as it arrives
There is no limit on simultaneous calls, so the morning rush is answered at the same speed as a quiet afternoon. Bookings are made on the call against live availability, and there is no voicemail pile waiting after lunch.
English and Spanish on the same line
Callers are answered in English or Spanish without waiting for the one bilingual person on the team, and what they said is written back the same way whichever language they used.
Gaps filled, visits brought back
Cancellations are offered to patients who want an earlier slot, and outreach for annual and follow-up visits runs against your existing patient list, booked straight into iClinic.
Nothing changes inside iClinic
No new screens, no migration, no retraining. Appointments and captured details land where your team already looks for them, as structured data, logged and reversible.
At a glance
The MDLand connection, in the terms a review will ask about.
MDLand practices are mostly independent physicians on a cloud EHR, many in the New York area and many inside an IPA, ACO or similar network. The desk is small, the phone rings in more than one language, and the busiest hour is the first one.
The difference
What changes on the MDLand phone.
An independent practice rarely loses a patient to a hard call. It loses them to the one that went to voicemail at nine in the morning.
How it runs today
With 2care on MDLand
The morning rush lands on one or two people
Bookings, refills, results and insurance questions all arrive while the desk is checking patients in, and the overflow waits in voicemail
Every call is answered as it arrives, with bookings made against live iClinic availability on the call
Callers who prefer Spanish wait longer
Those calls queue for the one bilingual person on the team or end with a callback
Answered in English or Spanish on the same line, with nobody waiting for a particular person to be free
Open slots go unfilled
Cancellations leave gaps nobody has time to backfill, and annual and follow-up visits slip
Cancellations are offered to patients who want an earlier slot, and outreach for due visits books straight into iClinic
Nobody wants another system
The team already lives in iClinic and has no interest in another login or a migration
No new screens, no migration, no retraining
Straight answers
What MDLand practices ask before connecting it.
We are independent and do not want another system to manage.
There is not one. Everything lands in iClinic, your team keeps working where they always have, and nothing needs installing on your machines.
A lot of our patients call in Spanish.
Calls run in English and Spanish, so those patients are answered straight away instead of waiting for whoever on the team speaks Spanish.
Will it recognise patients who have been with us for years?
Yes. Callers are matched against the record iClinic already holds, so an existing patient is picked up rather than entered a second time.
We are not granting broad access to our EHR.
Nor should you. Access is limited to scheduling and demographics. Clinical documentation sits outside the scope entirely.
Scope
What it touches in MDLand.
Three passes. An independent practice should insist on seeing the third before connecting anything.
- Schedule
- Live provider availability, as it stands right now.
- Visit types
- Appointment types and lengths exactly as your practice has defined them.
- Patient identity
- Existing records, to recognise somebody who has been coming for years.
- Coverage on file
- Insurance already held, so returning patients are not re-interviewed.
Go live
Weeks, not quarters.
Most practices on MDLand are live inside a few weeks of authorising the connection.
Authorise the connection
Your MDLand administrator approves API access. Nothing is installed, and nothing changes about how your team uses MDLand.
Map your rules
We map your providers, locations, appointment types, booking rules and escalation paths - the things that make your schedule yours.
Test, then go live
We run your real scenarios against a test environment with your team watching, fix what surfaces, then switch the line over and monitor.
See it work
A call, a booking, and a write-back into MDLand.
Recorded end to end. The system on screen is not yours, but the flow is the one described above.
Before you connect it
Questions about MDLand.
No. Appointments, patient details and everything captured on the call land in iClinic where they always did, as structured fields. Nobody has a new screen to learn and nothing is migrated.
Yes. It reads live availability from iClinic and applies your booking rules before it offers a slot, so it cannot create a conflict.
Yes. Calls run in English and Spanish, and the booking and call record are written back the same way whichever language the patient used.
Yes, from the way the caller explains it rather than a menu. Bookings are made on the call, refill and result requests go to the queue your team already works, and anything clinical is escalated with the transcript attached.
An answering service covers the phone. An integration connects one system to another. Here they are one product: cover for the line that reads your iClinic schedule and writes the booking straight into it.
No. Callers are matched against what iClinic already holds before anything new is created.
See 2care book into MDLand.
30 minutes, on your own workflows. No commitment.
- 95+ integrations and EHRs
- ·Live in weeks, not months
- ·HIPAA, GDPR and DPDP