Scheduling and open slots
Provider calendars, visit types, and the same slots the portal is allowed to book.
Features
This is the working surface of the product, grouped the way an operator buys it. If a control is partial in a given deployment, your implementation lead will say so before kickoff.
Provider calendars, visit types, and the same slots the portal is allowed to book.
Structured visits with the note, vitals, and orders a clinician expects to find later.
Reconcile what changed in the room and keep the longitudinal chart current.
Track what was ordered and what the patient is allowed to see, including release delays.
Chart documents plus a patient-facing summary and CCD-A download when the record has one.
Staff tasking and workforce tools so front desk, clinical, and billing work does not live in side inboxes.
Room audio becomes a transcript, then a proposed chart: follow-up, problems, meds, encounter, referrals, and a plain-language patient note.
The model proposes. The signed-in clinician accepts. OpenEMR is not updated until that pause is cleared.
Ask about patients, encounters, and appointments in plain language, with cards for the record instead of a wall of text.
Twilio voice for the calls you choose — often after hours — with keys, settings, and transcripts kept in the EMR.
When a referral is discussed, provider search can resolve an NPI before the referral is filed.
After a signed note, the scribe can offer the next roomed patient so the clinician stays in flow.
Each clinic points at its own record. Patients match to an existing chart. The portal does not invent patients.
Authenticator MFA, family and proxy access, consent flags, and a durable audit trail.
Cutoff hours, conflict checks, waitlist, check-in, reminders, and a household calendar.
Front desk, clinical, and billing queues, assignment, canned replies, and a reply clock.
Notes the clinic has released, results after the hold window, allergies, meds, vitals trends, and home readings.
Shoppable prices, an insurance-aware estimate, and installment rows the patient can pay.
PHQ-9, notice of privacy practices, interpreter requests, and education matched to the chart.
The same API as the website: visits, messages, records, care, billing, privacy, and vitals.
Patients, encounters, and coverage come from the clinical record. Billing does not retype the visit.
A checklist has to pass before a claim is built. Staff can verify the exceptions.
Benefits feed a patient-responsibility estimate before the visit becomes a surprise balance.
Coding review, with prior authorization able to hold a charge instead of letting it leak downstream.
Build, scrub, and submit professional claims, including secondary claims with other-subscriber data.
Acknowledgement and remittance import, ERA posting, appeals, resubmit, and admin-approved write-off.
Statements, payment plans, charity screening, referrals, and pay links by email, SMS, or card.
Biller, viewer, and admin paths, clinic assignment, and a record of who opened protected information.