How to Sync AdvancedMD Appointments to Google Calendar Without Exposing PHI

To sync AdvancedMD appointments to Google Calendar without a HIPAA problem, put an export layer between the two that copies each appointment's time and a de-identified label into Google, and nothing else. Names, visit reasons, notes, and locations stay in AdvancedMD. This guide explains why that boundary matters, what a safe calendar event looks like, and the settings that most often leak PHI by accident.

Why not just connect AdvancedMD to Google Calendar directly?

AdvancedMD's scheduler is a clinical system covered by your BAA with AdvancedMD. Google Calendar is a general-purpose productivity tool. Google will only sign a BAA for Calendar under a paid Google Workspace plan, and even then every person and device that can see the calendar becomes part of your PHI footprint. Free Gmail calendars are never covered.

Generic automation tools can copy an AdvancedMD appointment into a calendar event, but by default they copy what the appointment contains: the patient's name in the title, the reason for visit in the description, sometimes the patient's email as a guest. That is the exposure you are trying to avoid.

What a PHI-safe calendar event contains

Orisan Connect builds every Google Calendar event through a single redaction step, then re-checks the finished event and refuses to send it if any protected value slipped through. You choose one of three redaction levels per calendar connection:

• Time only: the event says "Appointment" and blocks the slot. Nothing else.
• Minimal (the default): patient initials and appointment type, for example JaDo — Follow-up, plus the AdvancedMD appointment ID so staff can look it up.
• Detailed: everything in Minimal plus a link that opens the appointment in AdvancedMD.

At every level, the patient's full name, reason for visit, notes, and location are removed. Events are created as private, and guests cannot see or invite other guests.

The three settings that cause most calendar PHI leaks

Update notifications. Google can email every attendee whenever an event is created or changed. If patients are attendees, a reschedule sends them a Google email from your staff member's account. Keep Google's update notifications set to none unless you have a specific reason to change it.

Patient invites. Adding the patient as a guest puts their email address on the event. Orisan Connect keeps patient invites off until a compliance acknowledgement is recorded for that connection, and staff calendars can be invited independently.

Which calendar you authorize. Connect a dedicated practice calendar under the practice's Google Workspace account, not a provider's personal Gmail. Events land wherever the authorized account points them.

How the sync runs day to day

The export is one-way: AdvancedMD stays the source of truth, and edits made in Google Calendar are never written back. Each scheduled run imports appointments that changed in AdvancedMD, then pushes only the ones whose content changed since the last delivery. Reschedules update the existing event instead of creating a duplicate, and cancellations remove it. Google OAuth tokens are refreshed before they expire, and you are notified if the connection needs re-authorization.

Each connection can also set one of Google Calendar's 11 event colors so synced appointments stand out from staff's personal events, or inherit the calendar's own color.

Checklist before you turn it on

1. Create or pick a dedicated practice calendar in Google Workspace.
2. Decide on a redaction level: start with Minimal and only go further if staff need it.
3. Leave Google update notifications off and patient invites disabled.
4. List the staff calendars that should receive events.
5. Pick an event color, then verify a test appointment end to end before going live.

For the full feature list, see the EHR to Google Calendar sync and AdvancedMD integration pages, or read the guide to HIPAA-compliant data synchronization.