# HIPAA-Compliant Models

Which AI models are covered by Chipp's Business Associate Agreements (BAAs), how to choose a HIPAA-eligible model for your app, and what the Launch > Access HIPAA Compliance setting does and does not guarantee.

---

If you build healthcare apps on Chipp, you need to know which AI models are covered by a signed Business Associate Agreement (BAA) and how to keep your app's chat on those models. This page answers both questions.

## Which models are HIPAA-eligible?

Chipp holds BAAs with two model providers:

| Provider | Model family | HIPAA-eligible? |
|----------|--------------|------------------|
| **Google** | Gemini models | Yes |
| **Anthropic** | Claude models | Yes, **except Claude Fable** |

- **Google Gemini** -- Chipp has a BAA in place with Google covering the Gemini model family used for chat.
- **Anthropic Claude** -- Chipp has a BAA in place with Anthropic covering the Claude model family used for chat, **excluding Claude Fable**. Claude Fable is not covered and is not offered as a HIPAA-eligible option.
- **All other providers** (OpenAI, xAI, Meta, and any OpenRouter-routed model) are **not** covered by a Chipp BAA today and are not HIPAA-eligible model choices.

> **Warning:** The HIPAA Compliance setting is a technical control: it does not reroute AI providers and it does not change how supporting services process data. Voice transcription, speech-to-text, and default text embeddings (used for RAG/knowledge retrieval and memory) route through OpenAI regardless of your chat model or HIPAA setting, and Chipp does not hold an OpenAI BAA today. If your app uses voice, knowledge sources, or memory, talk to your Chipp contact about your specific compliance requirements before treating the app as covered end-to-end.

## Choosing a HIPAA-eligible model for your app

To keep your app's chat on a BAA-covered provider, set your app's model to a Google **Gemini** model or an Anthropic **Claude** model (any Claude model other than **Claude Fable**). Chipp does not automatically swap your chat model based on the HIPAA Compliance setting, so choose a covered model yourself.


  **1.** 
    <strong>Open your model settings</strong>

    In the Chipp app builder, open the model picker for your app.
  


  **2.** 
    <strong>Select a covered model</strong>

    Choose a Google **Gemini** model or an Anthropic **Claude** model (any Claude model except **Claude Fable**). Avoid OpenAI, xAI, and other providers for a HIPAA app's chat model -- Chipp does not hold BAAs with them today.
  


  **3.** 
    <strong>Enable HIPAA Compliance under Launch &gt; Access</strong>

    Go to your app's **Launch** page → **Access** tab and turn on the **HIPAA Compliance** toggle. This enforces required authentication and shortens sessions to a 4-hour inactivity timeout with a logout warning -- see [Access Control: HIPAA Compliance](/docs/guides/access-control#hipaa-compliance) for the auth-mode side effects. This toggle does not itself limit which chat model you can pick, so make sure you selected a covered model in step 2.
  


## What HIPAA Compliance does -- and does not -- guarantee

Turning on HIPAA Compliance is a **technical control**, not a substitute for your own compliance program:

- It tightens authentication: only **Required** or **Restricted** auth modes are available (see [Access Control](/docs/guides/access-control#hipaa-compliance)), and it shortens sessions to a 4-hour inactivity timeout with a logout warning.
- It does **not** restrict which chat model you can select, and it does **not** reroute AI providers. Keeping your app's chat on a BAA-covered provider is your choice of model (a Gemini model, or a Claude model other than Fable), not an automatic effect of the toggle.
- It does **not** automatically make your app, workflow, or overall use of Chipp HIPAA compliant. HIPAA compliance depends on how you configure and use the product, the data you send, and your own obligations as a covered entity or business associate -- Chipp's BAA coverage for a chat model is one input to that, not the whole answer.
- It does **not** extend BAA coverage to every part of the product. Voice, transcription, and default embeddings can still involve providers Chipp does not hold a BAA with.

You remain responsible for configuring and using Chipp appropriately for your own compliance obligations, including deciding whether additional configuration (for example, avoiding voice or default embeddings for PHI-bearing apps) is required for your use case. If you have questions about your specific setup, contact your Chipp representative.

## Related

- [Access Control](/docs/guides/access-control) -- the four auth modes and how HIPAA Compliance restricts them.
- [Choosing a Model](/docs/guides/choosing-a-model) -- general model selection guidance for non-HIPAA apps.