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.
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’shipaa_us policy covers them:
| # | Identifier | Blindfold Entity Type | Covered |
|---|---|---|---|
| 1 | Names | Person | ✅ |
| 2 | Geographic subdivisions (smaller than state) | Address | ✅ |
| 3 | Dates (except year) related to individual | Date of Birth | ✅ |
| 4 | Phone numbers | Phone Number | ✅ |
| 5 | Fax numbers | Phone Number | ✅ |
| 6 | Email addresses | Email Address | ✅ |
| 7 | Social Security Numbers | Social Security Number | ✅ |
| 8 | Medical Record Numbers | Medical Record Number | ✅ |
| 9 | Health plan beneficiary numbers | Health Insurance ID Number | ✅ |
| 10 | Account numbers | Bank Account Number | ✅ |
| 11 | Certificate/license numbers | License Number | ✅ |
| 12 | Vehicle identifiers | Vehicle ID | ✅ |
| 13 | Device identifiers | Device ID | ✅ |
| 14 | Web URLs | URL | ✅ |
| 15 | IP addresses | IP Address | ✅ |
| 16 | Biometric identifiers | Biometric Data | ✅ |
| 17 | Full-face photographs | — | N/A (text-only API) |
| 18 | Any other unique identifying number | Custom entities | ✅ |
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
| Entity Type | Examples |
|---|---|
| Person | Sarah Johnson, Dr. Emily Chen |
| Social Security Number | 123-45-6789 |
| Medical Record Number | P-4532, MRN-78901 |
| Health Insurance ID Number | BC-9876543 |
| Date of Birth | 03/15/1978 |
| Email Address | sarah.johnson@email.com |
| Phone Number | (555) 234-5678 |
| Address | 123 Oak Street, Springfield |
| Medical Condition | chest pain, diabetes, hypertension |
| Medication | metformin, lisinopril |
| Insurance Company | BlueCross, Aetna |
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
| Mode | Method | Reversible | Use Case |
|---|---|---|---|
| Tokenize | blindfold.tokenize() | Yes | AI chat, summarization — restore PHI in responses |
| Redact | blindfold.redact() | No | Logs, storage — permanently remove PHI |
| Encrypt | blindfold.encrypt() | Yes (with key) | Secure archives — AES-256 encrypted PHI storage |
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
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
Sign a BAA with Blindfold
Contact hello@blindfold.dev to execute a Business Associate Agreement.