In development4 min read
Clinical routes and location privacy
Preserve the scheduling experience without sharing clinical details across boundaries.
This is a product-direction guide. Described features may not be available yet.
Overview
Preserve the scheduling experience without sharing clinical details across boundaries.
Step-by-step
- Use the protected workflow to request an eligible appointment slot.
- Review whether the general scheduler needs only non-identifying timing constraints.
- Keep protected addresses and clinical context inside approved services.
- Verify permission boundaries with synthetic test data.
Important checks
- Only necessary non-identifying information may cross the RL/RLH boundary.
- No patient details should be copied into general Google Calendar events.
