What makes a good orthodontic admin

Orthodontic admin runs on a different rhythm than every other dental vertical. A general-family practice operates visit-by-visit; the relationship with most patients is transactional and intermittent. An ortho practice operates treatment-by-treatment; the relationship is multi-year, with monthly adjustment visits, between-visit communication, and a lifecycle that the front desk has to track without inventing a system. The admin layer for ortho needs to surface the things that change — virtual consult queue, pending appointment changes, treatment milestones — without forcing the staff to context-switch between unrelated tools.

The virtual consult review queue is the highest-leverage surface. A patient (or parent) submits photos and a few sentences; the orthodontist reviews and decides whether to schedule a real consultation. Done well, this saves the orthodontist hours per week of in-person evaluations on cases that aren't a fit. Done badly — meaning, with automated treatment estimates from photos — it creates legal exposure and patient mistrust simultaneously. The platform's rule is simple: the platform never auto-generates a treatment estimate from photos. The review UI surfaces the photos and the patient's concerns; the orthodontist provides a recommendation manually. That constraint is permanent.

Photo handling at the admin layer mirrors how the schema models them: PHI-encrypted at rest, masked-by-default in the studio review list, audit-emit on every reveal click. The reveal posture matches how Dream Create handles every PHI surface — bookings, intake, gallery consent records. An orthodontist who's used to the platform anywhere else recognizes the pattern instantly: click reveal, see the patient details, your reveal is logged. No new mental model.

Status flow is the second axis of the admin layer. A consult moves from PENDING_REVIEW to REVIEWED to APPOINTMENT_SCHEDULED (or DECLINED). Each transition audit-emits with the reviewing operator's identity. The lifecycle isn't pure DAG — sometimes a declined case re-emerges six months later as a different scope. The schema permits the round-trip; the audit log captures why.

What ortho admin doesn't need at v1: integrated between-visit messaging, treatment-progress photo capture, retainer-replacement dispatch. Those are real workflow needs, but they're Phase 7+ adjacencies. The admin layer's v1 job is to make the year-plus relationship traceable without inventing a parallel system; everything else can wait for the patterns to reveal themselves through real use.