Skip to main content
The Health Insurance Portability and Accountability Act (HIPAA) protects medical information in the United States. Any AI application that processes Protected Health Information (PHI) must comply with HIPAA’s Privacy and Security Rules. Blindfold helps by tokenizing PHI in the US region before it reaches any AI provider. The LLM only sees anonymized tokens — never real patient names, SSNs, or medical records.

Who Must Comply

Covered Entities

Healthcare providers, health plans, and healthcare clearinghouses that transmit health information electronically.

Business Associates

Any organization that creates, receives, maintains, or transmits PHI on behalf of a covered entity — including AI/software vendors.
If your AI application processes patient data for a healthcare organization, HIPAA likely applies to you.

The 18 HIPAA Identifiers

HIPAA’s Safe Harbor method (45 CFR § 164.514(b)(2)) requires removal of 18 types of identifiers for de-identification. Blindfold’s hipaa_us policy covers them:

How Blindfold Helps

Minimum Necessary Rule

HIPAA requires that only the minimum necessary PHI is used for any given purpose. With Blindfold:

Safe Harbor De-Identification

Blindfold’s tokenization satisfies the Safe Harbor method by removing all 18 identifier types. The tokenized output is considered de-identified data under HIPAA, which is no longer subject to the Privacy Rule.

US Region + hipaa_us Policy

Region Selection

Use the US region to ensure PHI is processed on US-based servers:

What hipaa_us Detects

Code Examples

Tokenize a Patient Record

Multi-Turn PHI-Safe Conversation

Maintain PHI mappings across a multi-turn healthcare chat:

Batch PHI Redaction

Permanently remove PHI from multiple records for safe storage or logging:

Three Modes of PHI Protection

Audit Trail

Every Blindfold API call is logged, supporting HIPAA’s audit requirements (45 CFR § 164.312(b)):
  • Who: Which API key made the request
  • What: Entity types detected and count
  • When: Timestamp of every PHI operation
  • Where: Processing region (US)
  • How: Which privacy method and policy was used
Export audit logs from the Blindfold Dashboard.

BAA Readiness

Blindfold is ready to sign a Business Associate Agreement (BAA) with covered entities and their business associates. A BAA is required under HIPAA when a third party handles PHI. Contact us at hello@blindfold.dev to request a BAA.

Cookbook Example

For a complete, runnable HIPAA healthcare chatbot, see the cookbook:

HIPAA Healthcare Chatbot Example

Full working example with US region, hipaa_us policy, single queries, multi-turn chat, and batch redaction.

HIPAA Compliance Checklist

1

Use the US region

Set region="us" to ensure PHI is processed within the United States.
2

Apply the hipaa_us policy

Use policy="hipaa_us" on all calls handling patient data.
3

Tokenize before AI calls

Always call blindfold.tokenize() before sending PHI to any AI provider.
4

Redact PHI in logs

Use blindfold.redact() to remove PHI from application logs and audit records.
5

Encrypt PHI at rest

Use blindfold.encrypt() for PHI stored in databases or file systems.
6

Sign a BAA with Blindfold

Contact hello@blindfold.dev to execute a Business Associate Agreement.
7

Implement access controls

Use separate API keys for different applications and teams.
8

Review audit logs

Regularly export and review audit logs from the dashboard.