Skip to content

HIPAA Compliance ​

This guide covers how GhostAI helps healthcare organizations maintain HIPAA compliance when using AI tools.

HIPAA Overview ​

The Health Insurance Portability and Accountability Act (HIPAA) establishes national standards for:

  • Privacy Rule: Protects PHI
  • Security Rule: Technical safeguards
  • Breach Notification Rule: Reporting requirements
  • Enforcement Rule: Penalties and investigations

How GhostAI Supports HIPAA ​

Privacy Rule Compliance ​

RequirementGhostAI Feature
PHI ProtectionAutomatic detection & tokenization
Minimum NecessaryUser prompts, selective sharing
Patient RightsData access logging
AuthorizationAccess controls, audit trail

Security Rule Compliance ​

SafeguardGhostAI Feature
Access ControlRole-based permissions
Audit ControlsComprehensive logging
IntegrityData validation, checksums
TransmissionTLS 1.3, end-to-end encryption
AuthenticationSSO, MFA support

Breach Notification Readiness ​

GhostAI helps prevent breaches and prepares you if one occurs:

  • Prevention: PHI never sent to external AI
  • Detection: Anomaly detection in access patterns
  • Documentation: Complete audit trail for investigations
  • Reporting: Exportable logs for notifications

Covered PHI Types ​

18 HIPAA Identifiers ​

GhostAI detects all 18 HIPAA identifiers:

Names (1) ​

Patient: John Smith, Dr. Jane Doe
Detected: ✓ PERSON entity

Geographic Data (2) ​

Address: 123 Main St, Springfield
Detected: ✓ LOCATION entity (sub-state level)

Dates (3) ​

DOB: 01/15/1980, Admission: 03/20/2024
Detected: ✓ DATE_TIME entity

Phone Numbers (4) ​

Contact: (555) 123-4567
Detected: ✓ PHONE_NUMBER entity

Fax Numbers (5) ​

Fax: (555) 123-4568
Detected: ✓ PHONE_NUMBER entity (fax variant)

Email Addresses (6) ​

Email: patient@email.com
Detected: ✓ EMAIL_ADDRESS entity

Social Security Numbers (7) ​

SSN: 123-45-6789
Detected: ✓ US_SSN entity

Medical Record Numbers (8) ​

MRN: 12345678
Detected: ✓ MEDICAL_LICENSE / custom pattern

Health Plan Beneficiary Numbers (9) ​

Insurance ID: BC12345678
Detected: ✓ Custom healthcare patterns

Account Numbers (10) ​

Account: 9876543210
Detected: ✓ ACCOUNT_NUMBER entity

Certificate/License Numbers (11) ​

NPI: 1234567890
Detected: ✓ MEDICAL_LICENSE entity

Vehicle Identifiers (12) ​

VIN: 1HGCM82633A123456 (ambulance records)
Detected: ✓ Custom pattern

Device Identifiers (13) ​

Pacemaker SN: ABC123456
Detected: ✓ Custom medical device pattern

URLs (14) ​

Portal: https://patient.hospital.com/123
Detected: ✓ URL entity

IP Addresses (15) ​

Access from: 192.168.1.100
Detected: ✓ IP_ADDRESS entity

Biometric Identifiers (16) ​

Fingerprint ID: FP-123-456
Detected: ✓ Custom biometric pattern

Full-Face Photos (17) ​

Photo reference: IMG_patient_001.jpg
Detected: ✓ File reference pattern
Note: Actual images processed with facial detection

Unique Identifiers (18) ​

Any number that identifies an individual
Detected: ✓ Context-aware detection

Administrative Safeguards ​

Workforce Training ​

GhostAI supports training with:

  • In-app tooltips explaining PHI protection
  • Guided tours for new users
  • Documentation and help system
  • Audit log review for compliance officers

Access Management ​

RoleCapabilities
ViewerView own chats, no PII export
MemberChat with AI, view protection status
AdminManage users, view org-wide audits
OwnerFull control, BAA access

Contingency Planning ​

GhostAI data export supports:

  • Backup and recovery
  • Data migration
  • Business continuity
  • Disaster recovery documentation

Technical Safeguards ​

Access Control ​

yaml
Authentication:
  - Username/password
  - SSO (SAML)
  - MFA (optional)

Authorization:
  - Role-based access
  - Organization isolation
  - Session management

Audit Controls ​

Every action is logged:

json
{
  "timestamp": "2024-01-15T10:30:00Z",
  "user_id": "user_123",
  "action": "chat_message",
  "phi_detected": ["PERSON", "MRN", "DATE_TIME"],
  "phi_count": 5,
  "tokenized": true,
  "ip_address": "10.0.1.100",
  "session_id": "sess_abc123"
}

Integrity Controls ​

  • Message checksums
  • Token validation
  • Database integrity checks
  • Backup verification

Transmission Security ​

  • TLS 1.3 for all connections
  • Certificate pinning (optional)
  • No data stored on AI provider
  • End-to-end encryption (Enterprise)

Physical Safeguards ​

For cloud deployment:

ControlImplementation
Facility AccessSOC 2 compliant data centers
Workstation UseBrowser-based, no local storage
Device ControlsSession timeout, secure logout

Business Associate Agreement ​

When BAA is Required ​

A BAA is required when GhostAI:

  • Processes PHI on behalf of a covered entity
  • Has access to PHI in production

BAA Availability ​

TierBAA
StarterNot available
PersonalNot available
TeamAvailable
BusinessIncluded
EnterpriseIncluded

Healthcare Shield Add-On ​

The Healthcare Shield add-on provides HIPAA-grade PHI detection, BAA coverage, and healthcare-specific compliance reporting. Available on Personal and above at $15/user/mo.

BAA Terms ​

GhostAI's BAA covers:

  • Permitted uses and disclosures
  • Safeguards implementation
  • Reporting obligations
  • Subcontractor agreements
  • Termination procedures

Compliance Checklist ​

Before Deployment ​

  • [ ] Conduct risk assessment
  • [ ] Review BAA requirements
  • [ ] Train workforce on GhostAI
  • [ ] Configure access controls
  • [ ] Set up audit log review process

Ongoing Compliance ​

  • [ ] Regular access reviews
  • [ ] Monthly audit log review
  • [ ] Annual risk assessment update
  • [ ] Incident response testing
  • [ ] Policy updates as needed

Documentation ​

  • [ ] Privacy impact assessment
  • [ ] Security risk analysis
  • [ ] Training documentation
  • [ ] Audit log retention
  • [ ] Incident response plan

Breach Prevention ​

How GhostAI Prevents Breaches ​

  1. PHI never leaves: Tokenized data goes to AI
  2. Access logging: Know who accessed what
  3. Anomaly detection: Unusual patterns flagged
  4. Data minimization: Only necessary PHI processed

If a Breach Occurs ​

GhostAI provides:

  1. Audit trail export: Complete access history
  2. Affected records: Identify impacted PHI
  3. Timeline: When and how access occurred
  4. User identification: Who was involved

Resources ​

SOC 2 Type II Certified | BAA Available | HIPAA-Ready