Shade verification, smile preview approval, photo gates — three workflows where the lab really does need patient input. How to enable them without bypassing the clinic, breaking HIPAA, or confusing authority.
The clinical authority chain stays intact. The lab never bypasses the dentist. The patient sees only what the clinic forwards. HIPAA-grade encryption end to end. White-label so the patient sees their dentist's brand — not a lab they don't know.
The traditional model is lab-to-clinic-to-patient: the dentist relays everything. It works most of the time. But three workflows expose its limits:
The lab receives a shade designation but the photos don't match. The clinic is closed. The technician needs the patient to retake a photo with the shade tab in better lighting. Routing through phone calls and email loses 24-48 hours and often produces no usable photo.
For aesthetic cases, the patient should see the digital design before fabrication. If the lab presents the preview through a clinic-controlled link, the patient signs off and the lab fabricates exactly what was approved. Without it, every "I don't like the shape" comes after the crown is finished.
When a case comes back as a remake, the lab doesn't always know what the patient actually said. A short patient feedback loop ("tell us what you didn't like") routed through the clinic prevents the same mistake on the second attempt.
Any tool that handles patient identifiers, photos, or clinical data is regulated:
Bottom line: the patient communication tool must (a) be hosted with proper safeguards, (b) be controllable by the clinic, and (c) keep an audit trail of every interaction. WhatsApp, SMS, personal email, or off-the-shelf chat apps don't qualify.
A sixth bonus feature: white-label. The patient never sees the lab's brand — they see the clinic's brand. This preserves the clinical authority chain.
The market splits into three categories. None are perfect; each fits different lab profiles.
| Category | Examples | Strengths | Weaknesses |
|---|---|---|---|
| Clinic-to-patient platforms | Solutionreach, Weave, NexHealth, RevenueWell | Mature, HIPAA-compliant, used by clinics already | Built for clinic workflows, not lab cases. Lab can't initiate or see content. |
| Lab CAD/CAM share tools | 3Shape Communicate, exocad share | Technical file sharing for clinical communication | Designed for lab-to-clinic, not lab-to-patient. No patient-facing UX. |
| Lab-management embedded modules | TrazaLab + TuSonrisa, some emerging providers | Integrated with case file, white-label, clinic-controlled | Newer category, fewer mature options. Locked into the host LMS. |
Labs adopt a generic clinic-to-patient platform like Weave or Solutionreach to handle lab-side communication. Six months later they realize: those platforms are built for the clinic to message its patients about appointments and recalls. The lab is a third party. The platform doesn't model the case file, the technician notes, or the clinic-as-controller relationship.
The result is a tool that works on paper but generates more friction than the WhatsApp it replaced. Specialized lab patient communication apps, integrated into lab management software, are the right shape for the problem.
TuSonrisa is the patient-facing layer of TrazaLab. It was designed specifically for lab-side patient interaction with clinic control:
TuSonrisa is included in the standard TrazaLab subscription — no per-case fee, no separate app. The lab and the clinic share the same case file; the patient sees only what the clinic shares with them.
Most labs do not need direct patient communication — the clinic handles that. But three specific use cases drive demand: shade verification, smile preview approval, and remake prevention. When these workflows happen by phone or WhatsApp, things get lost. A purpose-built app reduces remakes.
Yes. Any tool handling patient identifiers, photos, or clinical data must comply with HIPAA in the US, GDPR in Europe, and local data protection laws elsewhere. The lab does not have a direct treatment relationship with the patient — communication must be routed through the clinic as data controller, or governed by a Business Associate Agreement.
Five: structured photo upload with prompts, approval workflow with patient sign-off, HIPAA-compliant storage, clinic visibility into every message, and case linkage so the conversation lives with the case. Bonus: white-label so the lab does not appear to bypass the clinic.
Three categories: clinic-to-patient platforms (Solutionreach, Weave, NexHealth, RevenueWell), CAD/CAM share tools (3Shape Communicate, exocad share), and lab management embedded modules. TrazaLab includes TuSonrisa as a white-label patient module — clinic-controlled, no separate app.
Almost never. The clinical relationship is between the dentist and the patient. The lab supports the dentist. The right model is a tool the clinic forwards to the patient, with the dentist copied on every reply. White-label and clinic-controlled is the only sustainable approach.
Standalone clinic-to-patient apps run $200-500 per month per practice. Lab-to-patient embedded modules inside lab management software typically add zero cost or a small per-case fee. The hidden cost is integration time: standalone apps mean double-entering data.
Yes. TuSonrisa is TrazaLab's white-label patient-facing layer. The lab generates a token-based URL, the clinic shares it with the patient, and the patient can review the design, upload photos, or approve the smile preview. All logged to the case. Available with the standard subscription, no extra fee. Start a 14-day free trial.
TuSonrisa ships with TrazaLab. White-label, clinic-controlled, HIPAA-grade. 14-day free trial — no credit card.