Skip to content
HIPAA INTAKE PLAYBOOK

Set Up Secure Electronic Patient Forms with Google Workspace

This zero-fluff guide shows dental teams how to collect new-patient intake data in Google Forms while staying inside HIPAA guardrails, from executing the BAA to locking down Shared Drives, Vault, DLP, and staff training.

What you’ll accomplish

Google Workspace Becomes a HIPAA-Safe Intake Hub

Every section links back to the same locked Shared Drive so your team can configure, review, and ship the intake flow without breaking compliance.

  • Use Google Forms (part of Google Workspace) to collect ePHI from new patients.
  • Store every response in a locked Shared Drive with strict permissions, retention, and auditing.
  • Operate only within services covered by Google’s HIPAA Business Associate Amendment (BAA).
  • Avoid landmines like emailing PHI, open-link sharing, or file-upload misconfigurations.

Reality check

As of September 30, 2025, Google confirms that Forms is part of the “Included Functionality” once the BAA is signed and the Workspace tenant is configured correctly. Always verify the latest list before you launch.

Source: Google Workspace HIPAA Included Functionality.

PREREQUISITES

Don’t Skip These Foundations

  • Paid Google Workspace tenant (Business or Enterprise). Free Gmail is out.
  • Practice acknowledges it is a HIPAA Covered Entity/Business Associate handling PHI in Workspace.
  • Workspace super admin available to configure security and compliance settings.
  • Documented policies and training for staff handling PHI (minimum necessary, no PHI via email, etc.).
  • Executed Google HIPAA BAA in the Admin console.

These steps anchor your compliance story. Auditors will ask for proof of BAA execution, policies, and staff readiness before they even look at Forms.

Need Google Workspace?

We negotiated a partner discount so you can launch a covered Workspace edition and keep every intake workflow inside the HIPAA-ready toolset we outline below.

Buy Google Workspace

IMPLEMENTATION GUIDE

Follow Each Step; Document Every Change

Every configuration should be captured in your operations log. Screenshots, Admin audit entries, and Vault retention proofs make your compliance story defensible.

01Compliance

Execute the Google Workspace HIPAA BAA

  1. Sign in to admin.google.com as a super admin.
  2. Navigate to Account → Account settings → Legal & compliance and review/accept the HIPAA Business Associate Amendment (BAA).
  3. Download or screenshot the executed terms for your compliance binder.

Resources: Google Admin Help and Google HIPAA overview [Google Help].

02Coverage Check

Scope the Included Functionality

Confirm which Google services are covered under the BAA. As of September 30, 2025, Google lists Gmail, Drive (Docs, Sheets, Slides, Forms), Calendar, Chat, Meet, Sites, Keep, Vault, Voice (managed), Cloud Search, Admin, Apps Script, AppSheet, Gemini in Workspace, and more.

Action: Keep PHI inside covered services only. Do not copy PHI into tools that are not on Google’s HIPAA list.

Reference: Google Workspace HIPAA Included Functionality.

03Drive Security

Create a Locked “PHI – Intake” Shared Drive

  1. In the Admin console go to Apps → Google Workspace → Drive and Docs. Create a Shared Drive named PHI – Intake.
  2. Add only essential team members (e.g., office manager, doctor). Apply least-privilege membership.
  3. Configure sharing settings:
    • Disable external sharing for the Shared Drive.
    • Disable link sharing (“Anyone with the link”).
    • Prevent download/print/copy for viewers when appropriate.
  4. Apply a “PHI” Drive label and enable Drive DLP to block external sharing when identifiers (SSNs, insurance IDs) are detected.
  5. Ensure Drive audit logs are retained (tie into Vault in Step 5).

Implementation guidance: Google Workspace HIPAA Implementation Guide.

04Identity

Enforce Identity and Device Security

  • Require 2-Step Verification for any staff with PHI access.
  • Use Context-Aware Access (if your edition supports it) to limit PHI access to managed devices or trusted networks.
  • Mandate strong passwords and enable suspicious login alerts.
  • Use least-privilege admin roles; nobody should operate daily work as a super admin.

General Workspace HIPAA security practices: Spin.AI HIPAA guidance.

05Retention

Configure Google Vault for Retention

  • Enable Google Vault (included in Business Plus and Enterprise plans).
  • Create retention rules covering the PHI – Intake Shared Drive and relevant user accounts based on your record-retention policy.
  • Set up matters/holds to support audits, legal requests, or disputes.

Reference: Google Workspace HIPAA Included Functionality.

06Google Forms

Build the HIPAA-Aligned Google Form

  1. Create the form from a Workspace account; name it “New Patient Intake” and structure sections such as Contact, Medical History, Medications, Allergies, and Consent.
  2. In Settings → Responses, link responses to a new Google Sheet stored inside the PHI – Intake Shared Drive.
  3. Notifications: if you rely on add-ons for alerts, only send a “new submission received” email. Do not include PHI in the message. Link back to the secure Sheet instead.
  4. Settings → Presentation & Defaults:
    • Avoid collecting patient email addresses unless disclosed and necessary.
    • Do not “Limit to 1 response”; that forces Google sign-in and blocks most patients.
    • Ensure the form is accessible to anyone with the link (patients are external) and not restricted to your domain.
File uploads have major constraints

Google Forms requires respondents to sign in with Google for file uploads. Many practices skip uploads in Forms and collect images or IDs in person or through a dedicated HIPAA intake product. Google continues to improve cross-domain settings, but sign-in remains standard for uploads.

References: Jotform on Google Form uploads & Workspace Updates.

Domain access guidance: Google Forms sharing help.

07Sheets

Lock Down the Linked Google Sheet

  • Keep the response Sheet inside the PHI – Intake Shared Drive.
  • Share only with the intake group; disable link sharing entirely.
  • Protect sensitive ranges (e.g., calculated fields, internal notes) with sheet protections.
  • Review File activity to confirm auditing captures viewers/editors (retained via Vault).

Refer back to Google’s HIPAA implementation whitepaper for Drive configuration patterns.

08Email Policy

Put Guardrails on Email

  • Never email PHI in plaintext.
  • Submission alerts should be PHI-free (“new intake received, open the Sheet”).
  • Enforce TLS for outbound mail; if you ever send PHI, configure S/MIME and document exceptions (safer approach: don’t email PHI).

Email posture recommendations: Google HIPAA implementation guide.

09DLP

Deploy DLP and Alerting

  • Create Drive DLP rules that flag PHI identifiers (SSN, insurance IDs, DOB) and block external sharing from the Shared Drive.
  • Enable Alert Center notifications for mass downloads, sharing attempts, or DLP violations.

More detail: Google HIPAA implementation guide.

10Audit

Test Like an Auditor

  • Submit multiple dummy entries and confirm they land in the correct Sheet inside the Shared Drive.
  • Attempt to access responses with a non-authorized account. Access should be denied.
  • Export audit logs and confirm activity appears in Admin reports and Vault.
11Team Training

Train Front-Office Staff

  • Staff access PHI only inside the locked Shared Drive and Sheet.
  • No copy/paste of PHI into email, chat, or non-covered tools.
  • When patients request the intake form, send the secure form link, not a PDF attachment.
Optional: AppSheet Intake
Optional

AppSheet sits on the Included Functionality list. If you want conditional logic, a mobile app experience, or tighter workflows, build an app that writes to the same secure Shared Drive and Sheet. Apply the same DLP, Vault, and sharing controls, and still avoid emailing PHI.

If You Must Collect Files From Patients
Heads-up

Consider a dedicated HIPAA intake vendor (IntakeQ, Formstack HIPAA, Jotform HIPAA). They can notify your team without attaching PHI. If you insist on Google Forms uploads, patients must log in with Google, a non-starter for many.

TRUTH TABLE

What This Setup Does, and Doesn’t

It Does

  • Keep PHI inside covered Workspace apps and a locked Shared Drive.
  • Deliver auditability via Vault, Drive audit logs, and alerting.
  • Meet the technical and administrative expectations in Google’s HIPAA playbooks.

It Doesn’t

  • Make email magically safe for PHI. Never send PHI in plaintext.
  • Solve anonymous file uploads in Forms (that’s a platform limitation).

APPENDIX

Why Google Forms Works in 2025

Google’s HIPAA documentation explicitly includes Forms under Drive once you operate under the BAA. HIPAA is always about configuration and usage: Shared Drives, Vault, access controls, and policy training complete the story.

Google publishes a Workspace + Cloud Identity HIPAA implementation guide. Your admin should treat it as the playbook for structure, access, and data protection.

ONE-PAGE CHECKLIST

Copy into Your Ops Doc

0/10 Completed

0/10 Completed

REFERENCES

Bookmark the Source Material

  1. HIPAA Included Functionalityref

    Lists covered Google Workspace apps (including Forms) as of Sept 30, 2025.

    View HIPAA Included Functionality
  2. HIPAA Compliance with Google Workspaceref

    Overview of signing the BAA and Workspace obligations.

    View HIPAA Compliance with Google Workspace
  3. Google Admin Help: Review & accept BAAref

    Step-by-step instructions to execute the HIPAA BAA.

    View Google Admin Help: Review & accept BAA
  4. Google Workspace & Cloud Identity HIPAA Implementation Guideref

    Official whitepaper covering configuration, access, and DLP patterns.

    View Google Workspace & Cloud Identity HIPAA Implementation Guide
  5. Spin.AI: HIPAA Compliance for Google Workspace Administratorsref

    Practical admin tips for tightening Workspace security posture.

    View Spin.AI: HIPAA Compliance for Google Workspace Administrators
  6. Google Forms access helpref

    How domain restrictions and sign-in requirements impact Form access.

    View Google Forms access help
  7. Jotform: Google Form file upload without sign-inref

    Explains the Google account requirement for uploads and alternatives.

    View Jotform: Google Form file upload without sign-in
  8. Workspace Updates: DLP for file uploadsref

    Details on protecting file uploads to external forms with Drive DLP.

    View Workspace Updates: DLP for file uploads

Ready for a Done-for-You Setup?

Prism can stand up the entire HIPAA-aligned intake system, deliver staff training, and monitor changes so your practice stays compliant while patients get a frictionless onboarding experience.