Implementation Guide
Google Calendar integration boundaries
No real Google Calendar credentials are needed during the paid validation pilot. Real calendar setup is deferred until the clinic decides to proceed, required approval and paperwork are complete, and a secure onboarding method is available.
No real Google Calendar credentials are needed or accepted during the paid validation pilot.
Calendar access is configured only after approval, paperwork, and secure onboarding are complete.
Do not email credentials, calendar secrets, patient data, exports, screenshots, or PHI to DentSignal.
Before You Start
Do not send calendar credentials during evaluation
The validation pilot uses fictional scheduling scenarios only. No real Google Calendar, PMS, patient data, screenshots, exports, secrets, or PHI should be sent to DentSignal.
- Use the validation pilot with fictional scheduling scenarios only.
- Do not connect a real clinic calendar during the pilot.
- Do not provide patient names, appointment data, exports, screenshots, secrets, or credentials during evaluation.
- Production integration setup waits for go-live approval, required paperwork, and a secure onboarding method.
- Calendar behavior must be verified later with a controlled production-readiness task.
Credential boundary
DentSignal will not request real Calendar or PMS credentials for the validation pilot. Production integration onboarding must wait for approval, paperwork, and an approved secure exchange path.
Pilot Boundaries
Use simulated calendar workflows only
These steps keep the paid pilot no-PHI. Real availability lookup and appointment writes remain production-only work.
Run the validation pilot without real credentials
Use fictional calendar examples and sandbox workflows only. No real Google Calendar, Open Dental, or patient communication path is connected during evaluation.
Decide whether production setup should proceed
If the clinic wants to move beyond the pilot, complete approval, paperwork, and security review before any real integration onboarding begins.
Wait for a secure onboarding method
DentSignal will not ask clinics to email calendar secrets. Production integration details should be exchanged only through an approved secure path.
Validate only after approval
Real availability lookup and appointment-write tests belong in a later production-readiness task after the clinic is approved for go-live.
Keep pilot data fictional
Use fake names, fake appointment examples, and sandbox scenarios until production approval is complete.
Warnings and Limits
Keep evaluation traffic away from real systems
Pilot accounts are blocked from saving, testing, reading, or writing real Google Calendar integrations. Production onboarding is a separate approved task.
No real integration during the paid validation pilot
Pilot accounts cannot save, test, read, or write against real Google Calendar integrations.
No credential exchange by email
Do not email calendar credentials, PMS credentials, patient exports, screenshots, or PHI to DentSignal.
Production onboarding is deferred
Real integration setup waits for clinic approval, required paperwork, and a secure onboarding method.
Future verification still required
A later bounded production-readiness task must validate real availability, booking, cancellation, timezone, and error behavior.
Production Later
Real calendar verification is not part of the pilot
When a clinic later moves toward production, real booking behavior must be validated in a bounded production-readiness task after approval and secure onboarding are complete.
Later production checks
- Secure credential exchange path is approved.
- Required paperwork and go-live approval are complete.
- Availability, booking, cancellation, and timezone behavior are tested with controlled production-readiness checks.
- Patient-facing use remains blocked until that later work passes.
If setup stalls
- A prompt asks for real credentials during pilot: stop and contact support.
- A workflow asks for patient data during pilot: use fictional data instead.
- A clinic wants production setup: confirm approval and secure onboarding first.
- You are unsure whether a file contains PHI or secrets: do not send it.