Specialty
Dentist-wise scheduling, multi-visit treatment, and per-procedure billing.
Dentistry is procedure-led: a treatment plan often runs across several sittings, each booked with a dentist and billed as it is done. Radiographs, consent and what the patient is ready to pay for all shape what happens next.
The operational problems a system has to answer, before any feature list.
Treatment runs across several appointments, so the plan matters as much as the visit.
Scheduling is chair- and dentist-bound, and a missed appointment costs a whole slot.
Billing is per procedure, often part-paid across visits.
Radiographs come from different machines and have to stay with the right patient.
Grouped the way the day runs. Every line says whether it is in the product today or planned.
Available todayPlanned, not available yet
Clinical pathways are reference content your clinical team reviews and edits as its own; nothing is ordered or prescribed until a doctor chooses it. Calculators inform a decision and do not write to the record. A line that needs a particular module names it.
A treatment case keeps the visits of a course together, so the next dentist sees what was done and what is left.
Part payments show what is paid and what is outstanding at every sitting.
Procedure and sedation consents print numbered, on your letterhead, ready to sign.
Notes, prescriptions, radiographs and bills under one patient, across every visit.
Modules are entitlements: enable what you need now and add the rest when you are ready. Nothing is re-implemented per specialty.
One record per patient, from first visit onward.
Booking against a doctor's slots, without double-booking.
Front desk to consult, with a live token queue.
Consultation notes, ICD-10-CM coding, and prescriptions.
One invoice across consultation, pharmacy, and lab.
Dispensing against prescriptions, on batch-aware stock.
Care plans, bedside procedures, consents with a printed form, and your clinical protocols under document control.
Most specialties differ in configuration rather than code: the same modules are enabled and set up differently. Where a specialty has a module of its own (twenty-three today, from Pediatrics, Obstetrics and Dentistry to Cardiology, Oncology and Nephrology), it is switched on per hospital. Where a specialty needs a capability the platform does not have yet, we say so during the demo rather than after you buy.
Yes, with the Dentistry module: each finding is recorded on a tooth by FDI code and surface, and the dental chart and each tooth’s history are drawn from them, beside procedures by sitting and treatment plans by phase. Its forms are being reviewed by a dentist before customer use.
Schedules are kept per dentist today, so a chair is booked through the dentist using it. Chair-wise scheduling is planned.
Yes. Part payments and a running balance are built into billing, so a plan is paid down across visits.
Radiographs are attached to the patient as documents and opened from the record. Viewing them inside the product, or tagging them to a tooth, is not built yet.
Book a walkthrough and we will map your clinic or hospital onto the platform, module by module.