Is DeepSeek HIPAA Compliant for Healthcare Organizations?

Short answer

No — DeepSeek is not HIPAA compliant and should not be used for any work task involving PHI. As of early 2026, DeepSeek does not offer a Business Associate Agreement, does not provide the data handling commitments required of a business associate, and operates infrastructure primarily located in China — introducing data residency concerns that go beyond standard HIPAA analysis. Covered entities should issue an organization-wide prohibition on DeepSeek use.

Who makes DeepSeek and where does data go

DeepSeek is developed by High-Flyer, a Chinese quantitative hedge fund that funds AI research. The DeepSeek AI assistant and API operate primarily on servers located in China. When a staff member in a U.S. medical clinic enters a query into DeepSeek’s consumer interface, that data travels to and is processed on infrastructure outside the United States.

This matters for HIPAA for several reasons:

1. No BAA is possible without U.S. legal jurisdiction and HIPAA-specific commitments. A business associate agreement requires specific legal commitments under U.S. law. A Chinese company operating under Chinese law and without a U.S. entity structured to assume those commitments cannot meaningfully execute a HIPAA-compliant BAA.

2. The Security Rule requires covered entities to assess the risks of PHI being accessed by or transmitted to unauthorized parties. Sending PHI to servers in China, without contractual protections and in a jurisdiction with different data access laws, is a significant addition to a covered entity’s risk posture.

3. HHS’s breach notification requirements depend on contractual accountability. If PHI sent to DeepSeek were involved in a security incident, the covered entity would have no contractual channel for notification, no agreed-upon response timeline, and no remediation obligations from DeepSeek.

The data residency concern specific to China

The concern about Chinese data residency is not merely a geopolitical abstraction. China’s National Intelligence Law and related legislation create obligations for Chinese companies and nationals that may, in certain circumstances, require cooperation with Chinese government intelligence requests. Whether this creates actual operational risk for a small medical clinic’s data is uncertain — but it is a risk factor that U.S. federal agencies have treated as material, leading to prohibitions on government device use.

For healthcare organizations, the analysis does not require a conclusion about espionage. The HIPAA Security Rule requires a risk assessment that considers threats to PHI’s confidentiality, integrity, and availability. Data processed on infrastructure in a foreign jurisdiction with different legal frameworks is a recognized risk factor that a diligent security officer must assess and document.

A covered entity that allows DeepSeek use and later faces an OCR investigation will need to explain why this risk was not addressed in its risk analysis. The safest position is a documented prohibition.

No BAA means no compliant path

The critical operating fact is simple: DeepSeek does not offer a BAA. Under HIPAA, a covered entity may not disclose PHI to a vendor that acts as a business associate without a signed BAA. If a staff member uses DeepSeek for any task that involves patient information — any patient name, any diagnosis, any date of service, any record number — that is an impermissible disclosure regardless of how inadvertent it was.

A covered entity cannot solve this through configuration, plan upgrades, or data minimization practices. The absence of a BAA is a structural gap that only DeepSeek could close by offering enterprise HIPAA terms. As of the verification date, they have not done so.

The important distinction: DeepSeek via U.S. API providers

DeepSeek’s open-weight models have been made available by various U.S.-based AI infrastructure providers — including Fireworks AI, Together.ai, and others. When a healthcare organization accesses a DeepSeek model through one of these providers’ APIs, the data handling relationship is with the U.S. provider, not with DeepSeek directly.

This is a meaningfully different situation:

• The U.S. provider processes the API request on U.S. infrastructure
• The U.S. provider may offer its own BAA for its API services
• The U.S. provider is subject to U.S. law and can make contractual commitments under HIPAA
• The DeepSeek company in China is not a party to the data handling arrangement

If a healthcare IT team is building an application on Fireworks AI’s API using a DeepSeek model, the compliance question is: does Fireworks AI offer a BAA, and does that BAA cover this API service? Answer that question directly with Fireworks AI.

This distinction is important because it means the prohibition on DeepSeek consumer products does not automatically extend to every application that happens to use a DeepSeek model architecture. The architecture and the data handling are different questions.

Why a blanket prohibition is the right policy position

Small clinics generally should not attempt to construct nuanced policies distinguishing between “DeepSeek consumer” and “DeepSeek model weights via BAA-covered U.S. API.” That distinction is real and meaningful for healthcare IT development teams, but it is not a distinction that front desk staff, medical assistants, or billing coordinators can reliably apply.

A blanket policy — “staff may not use DeepSeek for any work task” — is:

• Easier to communicate and train on
• Easier to audit and enforce
• Less likely to produce edge-case violations
• More defensible in an OCR investigation

Staff who need AI tools for specific work tasks should submit requests through the organization’s AI tool approval process, where the privacy officer or compliance lead can evaluate the tool against the BAA and data residency requirements appropriate for the specific use case.

Steps to take now

If your organization does not already have a policy addressing DeepSeek:

1. Issue a directive to the workforce explicitly naming DeepSeek as a prohibited tool for any work-related use, effective immediately
2. Add DeepSeek to your AI use policy — if you don’t have one, use the HIPAA AI use policy template as a starting point
3. Review your approved AI tool list and confirm that each approved tool has a signed BAA or an explicit determination that it is not used with PHI
4. Train staff — the prohibition is only effective if staff know it exists and understand why

For a broader analysis of AI tools and PHI risk, see PHI in AI tools and the best HIPAA-compliant AI tools for clinics.

The compliance program requirement

Identifying prohibited tools is the starting point. Maintaining a defensible compliance program requires documentation: a written policy, training records showing staff completed AI use training, incident logs when violations occur, and a process for reviewing new tools as they emerge.