Dental and orthodontic clinics run on clinical detail that generic ERP screens simply don't capture. A front-desk team juggling chair availability across operatories, a dentist who needs to record a distal-occlusal amalgam on tooth 36 in FDI notation, and a billing clerk who has to split a crown-and-buildup into insurance-covered and patient-pay portions are all working against ERPNext's stock Healthcare module. ERPNext core gives you Patient, Patient Appointment, Clinical Procedure, and Healthcare Practitioner DocTypes, but it has no concept of a tooth, no odontogram, no recall cadence, and no dental-specific fee schedule. Teams end up tracking tooth-level history in spreadsheets or free-text notes, which breaks reporting, insurance claims, and continuity of care.

ECOSIRE builds a dedicated Frappe app (for example dental_clinic) that extends ERPNext Healthcare rather than fighting it. The centerpiece is an interactive odontogram rendered by a Client Script / custom Frappe page: a clickable adult and pediatric dental chart (FDI, Universal, or Palmer notation, configurable per clinic) where each surface (mesial, distal, occlusal, buccal, lingual) is addressable. Charting a finding or completed procedure writes structured child-table rows against a Dental Chart Entry DocType linked to the patient, so tooth-level history is queryable, not buried in prose. Treatment plans are modeled as a parent Dental Treatment Plan DocType with procedure lines drawn from a Dental Procedure catalog (ADA/CDT-style codes, default fee, estimated chair time, default insurance coverage). A hooks.py doc event on plan acceptance can auto-generate the ERPNext Sales Order / Sales Invoice lines and the scheduling backlog.

Scheduling is handled as an extension of Patient Appointment with an operatory/chair dimension and the practitioner's working hours, so the front desk books against a real resource, not just a clinician. Imaging and consent forms attach through the standard Frappe File / attachments framework against the patient and the specific tooth entry, so an X-ray sits next to the finding it documents. Billing uses ERPNext's native Sales Invoice and pricing engine, but we add a per-procedure insurance-estimate layer: a whitelisted server method (@frappe.whitelist()) computes the estimated insurance portion versus patient responsibility from the procedure's coverage rule and the patient's plan, exposed to the chart UI and to the invoice. Everything respects Frappe's permission model — role profiles for Dentist, Hygienist, Front Desk, and Billing scope who can chart, who can schedule, and who can post invoices — and a scheduler event drives recall: patients due for a six-month cleaning are flagged and can trigger a reminder Notification or email.

Because this is build-to-order, nothing is a shrink-wrapped download. We start with a short scoping call, confirm your notation standard, procedure catalog, insurance rules, and role structure, then build against your ERPNext version (v15 or v16). You get the app validated on a staging bench, a UAT pass, and then installation on your instance with the git repository handed over. Typical delivery is 2 to 4 weeks from confirmed scope, and you own the source.