Skip to main content

MyTooth - Common Breakpoints

Michael Satterfield
Updated

This page documents known technical integration checkpoints and configuration requirements for MyTooth with Denticon. These are points in the setup and data flow where misconfigurations commonly cause failures.

1. API Key / Secret Authentication Breakpoint

Where it occurs: Initial PMS Authentication in MyTooth setup

What to verify:

  • The API Key and API Secret entered in MyTooth match exactly what is stored in the Denticon MyToothSetup table (PGID, UserId, APIKey, APISecretHash).
  • Connection Status in Denticon DB must be “connected” — not “disconnected”, “connecting”, or “revoked”.
  • The MyTooth “Test Connection” call must succeed before the system proceeds to sync and save.

Common failure: Credentials mismatch or revoked connection; resolutions require re-running the signup or setup script.

2. Location / OID Mapping Breakpoint

Where it occurs: During initial sync or when adding a new Denticon location

What to verify:

  • Each Denticon Office ID (OID) must have a corresponding entry in the MyToothOfficeMap table (PGID, UserId, APIKey, OfficeId).
  • New locations require a production server script to create the mapping, followed by a master resync.
  • If a location does not appear in MyTooth after resync, verify the OID is present in the MyToothOfficeMap.

Common failure: Missing OID mapping; resolved by running the location-mapping script and triggering a fresh resync.

3. Master Resync Breakpoint

Where it occurs: Post-setup or post-location-add sync

What to verify:

  • Resync must complete successfully for providers, operatories, schedules, appointment types, and patient data to be current.
  • Resync can take significant time depending on practice size; do not interrupt the process.
  • After resync, log out and log back in to ensure session reflects updated data.

Common failure: Incomplete resync due to timeout or network issues; re-trigger from the MyTooth admin panel.

4. DPC / Messaging Hub Integration Breakpoint

Where it occurs: When Denticon users attempt to send MyTooth form links from DPC/MH/TWC

What to verify:

  • MyTooth API endpoint for retrieving form/packet URLs must be reachable from DPC (input: PGID/OID; output: Form ID, Name, URL).
  • MyTooth API endpoint for patient-specific magic link must accept PGID, OID, and PatID and return a valid magic link URL.
  • The “MyTooth Forms” button in TWC and the campaign merge tags in DPC depend on these API endpoints being live and returning data.

Common failure: API endpoint unavailable or misconfigured PGID/OID; check API health and verify practice credentials.

5. Form Deletion Pre-Check Breakpoint

Where it occurs: When an office manager attempts to delete a form or packet in MyTooth

What to verify:

  • Before deletion, MyTooth calls a DPC endpoint to check whether the form URL is referenced in any existing campaign (input: PGID/OID/Form ID; output: “Used” or “Not Used”).
  • If the URL is “Used,” deletion is blocked to prevent broken campaign links.
  • This DPC endpoint must be available for the delete operation to function correctly.

Common failure: DPC endpoint not yet deployed or returning incorrect status; deletion will be blocked.

6. Patient Form Sync to Denticon Breakpoint

Where it occurs: After a patient submits a form via MyTooth

What to verify:

  • Completed form data is written to the Denticon PATNOTES table with CreatedBy = “MyTooth”.
  • Patient must be matched in Denticon before the note can be written (requires valid PGID + OID + PatID or DOB-based matching depending on matching scope settings).
  • Patient Matching Scope and Patient Matching Criteria must be correctly configured in MyTooth Organization settings.

Common failure: Patient not found in Denticon due to mismatched matching criteria; review Organization settings and patient data in both systems.

7. Appointment Booking to Denticon Breakpoint

Where it occurs: When a patient books an appointment via the MyTooth booking site

What to verify:

  • Appointment is written to Denticon’s APPTH table with CreatedBy = “MyTooth”.
  • Appointment Type in MyTooth must be properly mapped to a Denticon production appointment type.
  • Provider must be enabled for online booking in MyTooth settings.
  • Slot-finding logic must be configured to match the provider’s actual schedule and operatory assignments in Denticon.

Common failure: Appointment type mapping missing or provider not enabled for online booking; verify configuration in MyTooth Scheduling settings.

8. Communication (SMS/Email) Breakpoint

Where it occurs: When MyTooth sends confirmation emails or SMS to patients

What to verify:

  • Communications are routed through DPC for Denticon practices; DPC must be configured and active.
  • The Office Phone Number, Transaction Email, and Marketing Email must be configured in MyTooth Communication Settings per location.
  • Use the “Test Communication” feature in MyTooth to validate delivery before going live.

Common failure: DPC not configured for the location or incorrect contact details; update Communication Settings and re-test.

9. MyTooth Toolbar / Utilities Counter Breakpoint

Where it occurs: MyTooth icon counter display in Denticon

What to verify:

  • The Denticon toolbar icon reads from PATNOTES (forms) and APPTH (appointments) filtered by UserID = “MyTooth”.
  • If the counter is not updating, verify that MyTooth is correctly writing records with the right UserID value.
  • The Utilities > MyTooth Forms and Appointments menu item must be present (requires the Denticon-side feature to be deployed).

Related articles