What is ready. What is in progress. What is reserved.
Every item below is marked with where it stands in the code today. If it isn’t built, we say so.
Built and working today.
Schedule
Appointments by provider and operatory, on provider calendars. One calendar: every booking channel reads from it, and none of them keeps its own copy.
Website booking requests
New patients choose an open time on your website. The request lands in Appointment Requests. Your staff match or create the patient, then approve, decline, or follow up. If the time was taken in the meantime, the request is refused rather than double-booked.
Patient records
Demographics, insurance and subscriber details, and search. Insurance cards can be scanned so the member ID and group number are read for you.
Claims you can follow
Build a claim from the recorded visit and submit it through Cloud Health Office, our sister claims platform. Status reads Submitted, Accepted, Processing, Information needed, Denied, Paid, or Partially paid, with a timeline and the next step.
Payments posted for you
When a claim pays, the charge, the insurance payment, and the contractual adjustment post to the patient’s ledger. Refreshing twice never posts twice.
Patient ledger and statements
Every balance change is a ledger entry, and corrections are new entries rather than edits. Patients can sign in and see their balance and payment history.
Treatment-plan estimates
Line-by-line insurance estimates for a proposed treatment plan, so the patient hears a number before treatment. Estimates, clearly labeled as not a guarantee. Each payer has to be mapped first.
Review invitations
After a completed visit, every patient gets the same neutral email invitation to leave a review. Off until you turn it on.
Built in part. Not live yet.
Eligibility checks
Staff check a patient’s coverage, deductibles, and maximums from the patient’s record. The check goes to the payer through Stedi, a healthcare clearinghouse, and the answer is kept with the patient. Each practice’s payer connections are being set up for the pilot, so we don’t yet claim real-time eligibility for every payer.
Online card payments
Patients pay their share through Stripe’s hosted checkout, into your practice’s own Stripe account. Refunds and reconciliation are built and tested in Stripe’s test environment. The first live payments come with the pilot.
Zocdoc booking
Your open times are published to Zocdoc from the same calendar your staff use, and bookings come back to your schedule. Built and tested against Zocdoc’s sandbox. Going live needs Zocdoc’s approval. Details →
Planned. Not built.
Room is left for these in the design. Founding practices help decide the order.
Predeterminations
Pre-treatment estimates that come from the payer itself, not a calculation.
Prior authorization
Request and track authorizations from inside the patient’s record.
Multi-location groups
Run several offices as one group, with group-level setup and reporting. On the roadmap, not built.
Text messages
Patient notifications go by email today. Text messages are not built.
Tell us which of these matters most to your office.
Founding practices help set the order of what gets built next.