Compliance
DOJ Data Security Program and medical billing: when a vendor’s access to bulk health data is restricted
The DOJ Data Security Program restricts transactions that give a country of concern or a covered person access to bulk U.S. sensitive personal data, and personal health data includes information about payment for health care. A vendor outside the listed countries is not caught by its location alone. A vendor or employment agreement with a covered person that gives access to data on more than 10,000 U.S. persons is restricted, and allowed only with security requirements, a compliance program, an annual audit and ten years of records. The rule has no HIPAA exemption. This is general information, not legal advice. Review your payer contracts and the rules where you practice with your compliance advisor.
Published by OffshoreMeds. Facts last checked October 10, 2026. How we check our numbers.
Scope
What the rule covers, and the threshold
| Term | What the rule says | Source |
|---|---|---|
| Term: Personal health data | What the rule says: Data about a person's past, present or future physical or mental health, the provision of health care, or payment for the provision of health care. DOJ declined to drop payment from the definition and said medical billing statements often come with diagnostic codes showing the services provided. | Source: 28 CFR 202.241 |
| Term: Bulk | What the rule says: More than 10,000 U.S. persons at any point in the preceding 12 months, counted per transaction or across transactions between the same parties. De-identified, pseudonymized or encrypted data still counts. | Source: 28 CFR 202.205 and 202.206 |
| Term: Countries of concern | What the rule says: China (including Hong Kong and Macau), Cuba, Iran, North Korea, Russia and Venezuela. | Source: 28 CFR 202.208 and 202.601 |
| Term: Covered data transaction | What the rule says: A data brokerage, vendor, employment or investment agreement that involves access by a country of concern or covered person to bulk U.S. sensitive personal data. Access is judged without regard to security controls. | Source: 28 CFR 202.201 and 202.210 |

Who is caught
Covered persons: five ways to be one
- A foreign entity organized under the laws of, or with its principal place of business in, a country of concern.
- A foreign entity owned 50% or more, directly or indirectly, by a country of concern or by another covered person.
- A foreign individual who is an employee or contractor of a country of concern or of a covered-person entity.
- A foreign individual primarily resident in a country of concern.
- Any person the Attorney General designates as owned, controlled or directed by, or acting for, a country of concern or covered person.
The first four apply automatically, so a name search is not enough (28 CFR 202.211; DOJ FAQ). A citizen of a country of concern who lives in the United States is a U.S. person, and a citizen who lives in a third country is not covered by nationality alone. When a vendor is itself a covered person, its foreign-person employees are covered persons too (DOJ compliance guide).
What is restricted
Vendor and employment agreements are restricted, brokerage is prohibited
- A U.S. person may not knowingly engage in data brokerage with a country of concern or covered person. Vendor, employment and investment agreements are carved out of the definition of data brokerage (28 CFR 202.214 and 202.301).
- A vendor or employment agreement with a country of concern or covered person that involves access to bulk data is restricted: allowed only if the U.S. person meets the security requirements and the compliance, audit and record rules (28 CFR 202.401). The rule’s own example is a U.S. medical facility that hires an IT services company whose headquarters is in a country of concern, with access to bulk patient data.
- Transactions that evade the rule, and a U.S. person knowingly directing a foreign company to do what would be prohibited, are themselves prohibited. An outsourcing structure that places bulk personal health data with a front company staffed mainly by covered persons is the rule’s example of evasion (28 CFR 202.304 and 202.305).
- The rule does not ban contracting with people in countries of concern; it allows restricted transactions with the security requirements, and DOJ expects that they will not ordinarily amount to a prohibition.
Offshore
Where location matters, and where it does not
- There is no data-localization rule. The trigger is access by a country of concern or covered person, and the rule imposes nothing on transactions that do not involve one (90 FR 1646). A vendor outside the six listed countries is not a covered person because of where it works.
- If a U.S. person contracts with a foreign vendor that is not a covered person, and the vendor gives a covered-person employee access without the U.S. person’s knowledge or direction, neither agreement is a restricted transaction. DOJ does not expect second-level diligence on a foreign vendor’s employment practices absent evasion.
- A U.S. service provider that processes a client’s bulk data and itself employs a covered person with access has a restricted employment agreement, and it has engaged in it knowingly (28 CFR 202.230).
- Hong Kong and Macau are part of China for the rule, so a vendor with its principal place of business there is a covered person.
The conditions
What a restricted transaction needs
The security requirements are CISA’s document dated January 3, 2025. Their goal is that the combination of controls fully and effectively prevents access by covered persons to data that is linkable, identifiable, unencrypted or decryptable using commonly available technology. They include system-level controls such as an asset inventory and named accountable individuals, and data-level controls such as minimization, encryption with keys kept away from countries of concern and access management (CISA requirements). The U.S. person must also have a written data compliance program with certification by an officer, an annual audit by a qualified independent auditor, and records kept for 10 years (28 CFR 202.1001, 202.1002 and 202.1101). General and specific licenses and advisory opinions exist, and DOJ says it will endeavor to answer a license request within 45 days.
Exemptions and HIPAA
No HIPAA exemption, and none for a provider’s vendor
The regulation text contains no reference to HIPAA, to business associates or to covered entities, and no exemption turns on HIPAA status or on a business associate agreement. DOJ says the personal health data definition applies to any data that meets it, regardless of the entity that holds it, and that the program is activity-based and does not take an entity-based approach (DOJ FAQ). The exemptions that touch health data are limited to government business, clinical investigations and regulatory authorization uses. The financial services exemption covers payment processing, and the sources read do not say whether DOJ would apply it to medical billing. DOJ declined to create a safe harbor for due diligence practices. The HIPAA guide covers the separate HIPAA duties.
Dates and penalties
In force, with no published enforcement action found
- The rule took effect on April 8, 2025. The due diligence, audit and reporting duties applied from October 6, 2025, and DOJ’s 90-day period of limited civil enforcement for good-faith efforts ended on July 8, 2025. DOJ’s landing page prints October 5 for the later date, and the rule text says October 6.
- The only amendment since the final rule is a correcting amendment of April 18, 2025. No enforcement action, designation or published advisory opinion was found on DOJ’s pages as of October 10, 2026, which is absence of evidence and not proof.
- Civil penalties are the greater of an inflation-adjusted amount, printed in the rule as $368,136, or twice the amount of the transaction. Willful violations carry a fine of up to $1,000,000 and, for a natural person, up to 20 years in prison (28 CFR 202.1301). The knowledge standard is actual knowledge or reasonably should have known, not strict liability.
In practice
Questions for a practice and its billing vendor
- Who owns the vendor, and is any owner, parent or principal place of business in a listed country?
- Do any employees, contractors or subcontractors with access to our data live in a listed country?
- Which of our systems and how many patient records can each person reach, and over what period?
- How are keys held and access controlled so that unencrypted data stays out of reach?
- What does the contract say if the vendor or a subcontractor becomes a covered person?
The state, payer and Medicaid rules that sit alongside this one are on the offshore medical billing restrictions page, the contract terms are on the business associate agreement page, and the question list is in offshore medical billing vendor questions. This is general information, not legal advice. Review your payer contracts and the rules where you practice with your compliance advisor.
The terms behind each seat
One flat monthly fee per seat, never a percentage of collections. A Business Associate Agreement is signed before anyone touches protected health information. Clinical decisions stay with your US-licensed providers. See all OffshoreMeds services.
Related guides
- HIPAA compliant offshore medical billing
The Business Associate Agreement, the safeguards, and the payer and state rules that can rule offshore work out.
- Business associate agreement for offshore billing
The terms HIPAA requires in the contract, what the practice must do about problems, and what to add for offshore work.
- Vendor questions before you sign
Questions on contract, access, location, payer rules, pay and exit, each tied to the rule or source behind it.
- Offshore restrictions by state and payer
State storage laws, payer consent clauses and Medicaid rules that can restrict offshore billing, and how to check which ones bind you.
Get Started
Book a free 30-minute call.
Pick a time below. Have these ready: the roles you need, your specialty and your EHR. We’ll come back with a fixed seat quote, candidate profiles to interview and a go-live plan.
Calendar not showing? Open the booking page in a new tab.
Please keep patient information out of the booking notes. A Business Associate Agreement is signed before anyone touches protected health information. See how this site handles your details in the privacy policy.