Google Workspace Integration

HealthCura's Google Workspace integration lets a clinic administrator connect their Google Drive and select one folder for HealthCura to read. New benefit-verification result PDFs uploaded to that folder by the practice's insurance verification vendor are automatically ingested into the patient's record, eliminating the manual download-and-upload step front-desk staff have to do today.

What this integration does

Healthcare clinics typically contract with third-party benefit-verification vendors who deliver insurance eligibility result PDFs by uploading them to a designated folder in the practice's Google Drive - often called the "MOS upload directory" or similar. Today, practice staff manually monitor this folder, download each PDF as it arrives, and re-upload it into their practice management system. This is repetitive, error-prone, and creates delays for time-sensitive insurance verifications.

With HealthCura's Google Workspace integration:

The clinic administrator clicks Connect Google Drive in HealthCura's Settings → Integrations page.
They authorize HealthCura through Google's standard OAuth consent flow.
They select exactly one folder via the Google Drive Picker.
HealthCura polls that single folder on a configurable interval (default: every 15 minutes), downloads any new PDFs, runs OCR (Amazon Bedrock Claude) to extract patient identifiers, and matches the result to a patient record.
High-confidence matches link automatically; ambiguous results land in a review queue for front-desk review.

Permissions HealthCura requests

auth/
userinfo.email

Read the Google account's email address. HealthCura uses this only to display "Connected as [email protected]" in the Settings page so the connecting administrator knows which Google account is linked.

auth/
userinfo.profile

Read the connected user's display name. Used only for the connection-status UI alongside the email above.

auth/
drive.readonly

Read files from the user's Google Drive. HealthCura uses this scope solely to read PDF files inside the single folder the administrator chose via Google Picker. We never list, search, or read files outside that folder.

Why this scope and not drive.file? The drive.file scope only grants access to files created or opened by the app itself. Because the PDFs we need to ingest are uploaded by a third-party verification vendor - not by HealthCura - drive.file would return zero files. drive.readonly is the minimum scope that enables the use case.

What HealthCura does NOT do with your Drive data

We never write to, modify, share, rename, move, or delete any file in your Drive.
We never access files outside the single folder you select via Google Picker.
We never use Drive data for advertising, ad targeting, or any marketing purpose.
We never use Drive data to train, fine-tune, or evaluate machine-learning or generative-AI models.
We never sell, license, lease, or otherwise transfer Drive-sourced data to any third party.
No humans read Drive-sourced files except (a) with the user's affirmative agreement for specific files, (b) for security purposes such as investigating abuse, (c) to comply with applicable law, or (d) when the data has been aggregated and anonymized.

Google API Services User Data Policy — Limited Use compliance

HealthCura's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Drive-sourced data is used only to provide and improve user-facing features (benefit-verification ingestion) for the connecting clinic. Drive-sourced data is not transferred to third parties except as necessary to provide or improve the feature, comply with applicable law, or as part of a merger, acquisition, or sale of assets with the user's continued consent.

Security and HIPAA compliance

OAuth refresh tokens are stored encrypted at rest in HealthCura's database (AES-256-GCM).
All Drive-sourced files are stored in HealthCura's HIPAA-compliant AWS S3 environment, encrypted at rest, with a signed Business Associate Agreement in place with AWS.
All access to Drive-sourced files is logged in HealthCura's audit log, retained for seven years per HIPAA §164.530(j).
The integration is restricted to clinic administrator roles within HealthCura — not all clinic users can connect, change, or disconnect the integration.
You can disconnect at any time from Settings → Integrations → Google Drive → Disconnect. Disconnecting revokes the refresh token at Google and stops all polling immediately.

Setting up the integration

Prerequisites: You must have administrator role within your HealthCura account, and you must be a Google Workspace user (or any Google account with read access to the Drive folder you want to connect).

Sign in to HealthCura at admin.healthcura.ai.
Navigate to Settings → Integrations → Google Drive.
Click Connect Google Drive and complete Google's OAuth consent flow.
After redirect, click Choose folder and use the Google Drive Picker to select the folder your verification vendor uploads to.
Polling begins within one minute of folder selection.

Need help? Contact [email protected] if you have any questions about setup, the data we access, or how to disconnect.

Privacy and Terms

For full details on how HealthCura handles your data, please see our Privacy Policy and Terms of Service. The privacy policy describes our overall data-handling practices for all data we process, including data sourced from Google APIs.