Patient Onboarding

The write path in detail — which fields go in, the read-back before anything is saved, the duplicate check, and what happens to a 2 a.m. call

A technical walk through new patient record creation: the exact field set voice AI writes to your EMR, the confirmation step before the write, how a possible duplicate is flagged instead of created, and how records from overnight calls are queued until staff confirm them.

A narrow write surface by design: name, date of birth, phone, address, reason for visit, and the appointment itself — nothing else touches the chart
Read-back before write: "So that's Jane Doe, born 3/14/1990, calling about lower back pain—is that correct?" — the caller confirms before anything is saved
Duplicate check first, where EMR integration allows it: a matching date of birth and similar name alerts your staff instead of creating a second chart
Clinical content is excluded from the write on purpose and returns as a structured summary for staff to review and file
Insurance stays out of the chart write and goes to the MedReception portal for your team to verify and enter into billing
Overnight and weekend calls queue as pending; the record is created once your staff confirm the booking in the morning

How it pays back

One chart per patient, not two to merge later

Duplicate charts are expensive to unwind and dangerous to leave alone. Checking for an existing record before creating one — and handing a possible match to a human rather than resolving it automatically — keeps the merge queue from growing every time the phone rings.

Errors get caught on the call, at the cheapest moment

The AI confirms what it heard before writing. A misheard date of birth is corrected by the patient in the same breath, instead of surfacing weeks later as a failed eligibility check or a chart nobody can match.

A write path you can explain to your EMR vendor

The field set is fixed and small, the order of operations is the same on every call, and everything outside that set arrives as a summary or a portal item. That predictability is what makes the integration reviewable rather than something to take on faith.

Your front desk stops creating records by hand

Demographics arrive already populated, so staff time moves off typing and onto chart review, prior authorization, and insurance verification — the work that actually needs their training.

New patient created in EMR automatically on first call

Demographics and appointment sync; chart is ready before your staff review

Zero re-entry of patient name, DOB, or phone

AI captures once, EMR stores directly, no manual typing by front desk

Appointment confirmation on the same call

Patient leaves with a booked visit; no callback required

Structured clinical intake ready for staff review

Reason for visit, symptom details, and relevant history organized before the visit

Frequently asked questions

Exactly which fields does the AI write into the EMR?

New patient creation with name, date of birth, phone, and address, plus the appointment itself and the stated reason for visit. Everything else — insurance, clinical history, images — arrives through the portal or as a structured summary for staff to handle.

How does the system avoid creating a duplicate chart for someone we already have?

Where EMR integration is enabled, the AI checks for an existing record — same date of birth, similar name — before creating a new patient. If it finds a likely match it alerts your staff rather than creating a duplicate, and a person decides whether it is the same patient.

What if the caller gets a detail wrong or cannot give a date of birth?

The AI confirms details before writing and asks for clarification immediately when something is unclear. If a field cannot be provided, it is noted rather than guessed, and your staff can collect it before the visit or at check-in.

Does clinical information the AI captures write into the chart directly?

No. Reason for visit, symptom detail, and relevant history return as a structured summary. Your staff review it, decide what belongs in the chart, and file it. A clinician approves clinical content before it becomes part of the medical record.

How are records handled for calls that come in overnight or over a weekend?

After hours, the AI captures the patient information and the appointment request and queues both in the MedReception portal. Your staff review and confirm when you open, and the new patient record is created at that point.

Does the AI capture photo ID or driver's license information for the record?

No. Photo ID and driver's license data are not captured by the AI on this workflow. If your practice requires ID verification, the patient provides it at check-in. The AI stays on demographics, contact details, and reason for visit.