Security · Google Cloud
HIPAA-aligned Google Cloud hosting for ABA clinical operations
Production deployments run on Google Cloud Platform with encryption, audit logging, role-based access, BAAs where required, and Gemini configured for assistive clinical documentation — clinicians review every output.
What is HIPAA-aligned Google Cloud hosting for ABA software?
HIPAA-aligned Google Cloud hosting means your ABA center's clinical documents, form data, and infrastructure run on Google Cloud Platform under configurations intended to support healthcare privacy — encryption, access control, audit logging, and Business Associate Agreements where PHI is processed. TargetFlo uses GCP for production storage and processing and Google AI (Gemini) for assistive documentation features. PHI is isolated in a dedicated schema; clinicians review and sign every report before it reaches families or payers.
HIPAA and Google Cloud
TargetFlo is built on a HIPAA-aware architecture designed for protected health information. Production deployments use Google Cloud Platform for document storage, processing, and infrastructure, with Google AI (Gemini) for assistive features under configurations intended to support healthcare privacy requirements. Organizations execute appropriate Business Associate Agreements (BAAs) with Google Cloud where required. Access controls, audit logging, encryption in transit and at rest, and role-based permissions are core to the platform. AI features are assistive — clinicians review all clinical documentation before signature and submission.
Compliance posture depends on your deployment, BAAs, policies, and configuration. TargetFlo does not provide legal advice.
Compliance posture depends on your deployment, BAAs, policies, and configuration. TargetFlo does not provide legal advice.
Trust controls
Google Cloud and Gemini on TargetFlo
Text badges only — no unofficial Google logos. These map to the production hosting and assistive AI story.
Google Cloud Platform hosting
Document storage, processing, and infrastructure run on GCP in production deployments.
BAA framework
Organizations execute Business Associate Agreements with Google Cloud where required for PHI workloads.
Encryption in transit and at rest
TLS for every connection; encrypted storage for documents, form data, and backups.
Role-based access control
Permissions scoped by role, location, and record; guardians see only their own child.
Audit logging
Views, edits, signatures, and exports on clinical documents are logged with actor and timestamp.
Gemini as assistive AI
Compose assistant, OCR, and MCQ generation run under configurations intended to support healthcare privacy requirements. Clinicians review every output.
Separate PHI schema
PHI is isolated from operational data at the schema level to narrow access and simplify audit.
Configurable retention
Document and log retention configured per organization policy.
Clinical AI
Gemini under healthcare privacy configurations
Compose assistant, fax OCR, and training MCQ generation run as assistive workflows — not autonomous clinical agents. Outputs are proposals until a licensed clinician accepts them.
- Compose modes: fill empty, refine, draft section — on ADOS-2, assessment, and POC fields
- OCR extracts fax content for human confirmation before linking to a client
- Separate PHI schema narrows which components can read client records
- Audit logging on views, edits, signatures, and exports
Broader platform security: Security & compliance · HIPAA notice & BAA · Clinical documentation
FAQ
Frequently asked questions
See Google Cloud hosting in your demo environment
Book a 30-minute demo. We cover where documents live, how Gemini assistive features work, and how clinician review fits the signature chain.