Playbooks / Healthcare
Multi-location dental groups in LA: where the operating layer leaks.
The LA dental groups we work with run between 2 and 8 offices spread across LA County and the Gateway Cities. Their patient management software was usually chosen office-by-office, sometimes acquired with a practice purchase, almost never by design. This playbook covers what the stack actually looks like, where HIPAA scope creates work most operators underestimate, and what happens when you collapse the moving parts.
The default LA dental-group stack.
A 4-office group spread across Whittier, Pico Rivera, Downey, and Cerritos typically runs:
- · Dentrix or Open Dental at each office, sometimes on different versions, often with separate patient record databases that don't talk to each other.
- · Yapi or Modento for patient communications — appointment reminders, post-visit care instructions.
- · NexHealth or LocalMed for online booking from the website.
- · Weave or RingCentral for office phones with a "missed-call text-back" feature.
- · A separate website per office, often built by a different vendor and out of sync with each other.
- · An EHR review tool (BirdEye, PatientPop) that fires post-visit review requests.
- · A spreadsheet the group manager maintains to track which office is meeting which production target.
Combined: $1,200–$3,500/month for a 4-office group, depending on which version of each tool. Plus the labor to keep them in sync.
What HIPAA actually requires (and where the stack fails it).
HIPAA scope is wider than most dental groups configure for. The pieces operators routinely under-handle:
- Business Associate Agreements (BAAs). Every vendor that touches Protected Health Information needs one. Most multi-tool stacks have a BAA with Dentrix and a half-finished one with the website host. The text-back vendor and the review tool often slip through.
- Audit logs. HIPAA expects a complete record of who accessed which patient record when. Multi-system stacks fragment the audit log; reconstructing access during an incident becomes a several-day exercise.
- Patient communication channels. SMS appointment reminders that include a procedure name are PHI. Most office stacks send these through tools that aren't BAA-covered.
- Front-desk role-based access. When a front desk turns over (which happens about every 2 years), de-provisioning across four to seven systems is the kind of task that gets done partially.
Note: this is operating guidance, not legal advice. Your compliance counsel should review specific BAA arrangements.
What the consolidated layer changes.
Under Rehost's Enterprise tier (which is the right shape for a multi-location healthcare group), the consolidated layer is:
- One patient-facing app and website per group, branded uniformly. Patients book at any office through the same interface; their record follows them across offices.
- A unified BAA covering the operating layer. One business associate, one audit log, one access-control system. De-provisioning a former front desk is one revocation, not seven.
- Per-office routing inside one shell. Each office has its own scheduling rules, its own provider roster, its own production dashboards — but the patient experience and the data substrate are shared.
- Group manager dashboard. The spreadsheet the group manager maintains gets replaced by a single weekly summary written in English: which office is on track, which is drifting, where production targets are being missed.
- Dentrix / Open Dental stays. We don't replace the EHR — that's clinical software. We replace the patient-facing communication layer and the multi-tool sprawl around it.
For a 4-office group, the typical engagement collapses $1,800–$3,500/mo of stitched tools into a custom Enterprise scope — usually somewhere in the $1,500–$2,400/mo range depending on production volume and integration complexity. We scope it case-by-case.