Is MiOpsAI HIPAA compliant for healthcare clients?

MiOpsAI is HIPAA-aware and on track for full HIPAA compliance with BAA support in 2026, but is not yet certified for storing or processing Protected Health Information (PHI) in the current private beta. If you're a healthcare practice today, you can use MiOpsAI for non-PHI workflows (general operations, marketing, scheduling without diagnoses) but should not store PHI until BAA support ships.

What "HIPAA-aware" means today

• Tenant isolation — your data is logically separated from every other tenant
• Encryption — at rest (AES-256) and in transit (TLS 1.3)
• PII redaction — sensitive fields can be redacted before AI calls
• Role-based access — granular permissions per user
• Audit logs — full trail of who accessed what and when
• U.S.-based hosting — no offshore data residency

What's coming for full HIPAA compliance

1. Signed BAA with MiOpsAI (MiOpsAI, LLC) for Enterprise+ tier
2. Signed BAAs with downstream AI providers (OpenAI, Anthropic) — both already offer enterprise BAAs to MiOpsAI
3. Annual third-party HIPAA audit with attestation report
4. HITRUST CSF certification on the longer-term roadmap (12-18 months out)
5. Configurable PHI categories with stricter routing rules
6. HIPAA-compliant SMS gateway for appointment reminders

What healthcare practices use MiOpsAI for today

Beta customers in healthcare run general operations (HR, marketing, billing communications without account numbers, vendor management, project tracking) on MiOpsAI while keeping clinical workflows in their EHR. LizziAI is fenced off from clinical data via tenant configuration.

Timeline transparency

BAA support is targeted for Q3 2026. We commit to that publicly because healthcare prospects deserve dates, not vibes. If your team can use MiOpsAI for non-PHI work now and add HIPAA workflows when BAA ships, request beta access and tell us you're in healthcare. See Enterprise+ tier for HIPAA-tier pricing details.