A Business Associate Agreement is signed before anyone touches protected health information.

OffshoreMeds logo

Compliance

SOC 2, ISO 27001 and HITRUST for an offshore billing vendor: what HIPAA requires and what each proves

SOC 2, ISO 27001 and HITRUST for billing vendors are not required by HIPAA, which has no certification of its own. A covered entity may let a business associate handle electronic protected health information only after obtaining satisfactory assurances, which a written contract documents. HHS does not endorse or otherwise recognize private organizations’ certifications regarding the Security Rule. The three frameworks can still be useful evidence, because each is an outside examiner’s statement about a defined scope against that framework’s own criteria. 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.

What HIPAA requires

Satisfactory assurances in a written contract

The Security Rule lets a covered entity permit a business associate to create, receive, maintain or transmit electronic protected health information only if the covered entity obtains satisfactory assurances that the business associate will appropriately safeguard it (45 CFR 164.308(b)). The assurances are documented in a written contract that requires the business associate to comply with the Security Rule, to bind its subcontractors and to report any security incident, including breaches (45 CFR 164.314(a)). The same duty runs down the chain to subcontractors.

HHS says no standard or implementation specification requires a covered entity to certify compliance, and that an outside organization’s certification does not stop HHS from later finding a violation (HHS on certification). It also says a business associate cannot self-certify, or be certified by a third party, instead of the contract (HHS on business associate contracts). Using an outside organization for the periodic evaluation is a business decision, not a requirement.

The three

What each one is, and what to check

SOC 2, ISO/IEC 27001 and HITRUST compared by what each is and who issues it
FrameworkWhat it isWho issues itWhat to check
Framework: SOC 2What it is: An examination of a service organization’s description of its system and its controls relevant to security, availability, processing integrity, confidentiality or privacy (AICPA).Who issues it: A CPA firm, not the AICPA.What to check: Type 1 or Type 2: a type 1 report covers the design of controls as of a date, and a type 2 report adds an opinion on how they operated over a period (2016 column). Check the period, the system and locations in scope, and any exceptions.
Framework: ISO/IEC 27001What it is: A standard that sets requirements for an information security management system. Certification is optional (ISO).Who issues it: An outside certification body. ISO does not perform certification or issue certificates (ISO on certification).What to check: The scope statement, the issuing body and whether it is accredited, which is not compulsory, and the certificate date.
Framework: HITRUSTWhat it is: A framework with three assessments, e1, i1 and r2, each able to lead to a certification (HITRUST advisory).Who issues it: HITRUST, after an authorized external assessor inspects evidence.What to check: That the letter certifies a defined assessment scope, its validity period and conditions, and whether any services are carved out.
Table comparing what HIPAA requires with three security frameworks: a written contract with satisfactory assurances and no certification, a SOC 2 examination by a CPA firm of a defined system, an ISO 27001 certificate from an outside body for a stated scope, and a HITRUST certification of a defined scope.
HIPAA asks for a written contract and satisfactory assurances, while SOC 2, ISO/IEC 27001 and HITRUST are each an outside examiner's statement about a defined scope.

The limits

What a report or certificate cannot do

  • It is not named in the rule. None of the three appears in the Security Rule text, in Public Law 116-321, in OCR’s 2022 request for information or in the January 2025 proposal. In the documents read for this guide HHS does not say that any of them maps to the Security Rule.
  • A mapping is not compliance. OCR’s 2016 crosswalk maps the Security Rule to the NIST Cybersecurity Framework and lists ISO/IEC 27001 control numbers among the framework’s references, and it says the mappings do not show compliance (HHS crosswalk). NIST’s HIPAA implementation guide says using it does not ensure compliance either.
  • A report describes a scope. A clean report on one system or one delivery site says nothing about another. A SOC report is generally restricted to the service organization’s management and its users, and does not relieve the user of responsibility for risk.
  • The examiner matters. The AICPA says SOC services should be thoroughly evaluated by service organizations and CPA firms.

The 2021 law

Recognized security practices can help, and are not a safe harbor

Public Law 116-321 requires HHS to consider whether a covered entity or business associate had recognized security practices in place for not less than the previous 12 months when it sets fines, decides how far to take an audit or agrees remedies. The effect may be to mitigate a fine, end an audit early and favorably or mitigate remedies (Public Law 116-321).

  • The practices are NIST standards and guidelines, the approaches under section 405(d) of the Cybersecurity Act of 2015, and other programs that address cybersecurity under other statutory authorities. The entity chooses which.
  • The law names no SOC 2, ISO/IEC 27001 or HITRUST, and it does not limit HHS’s authority to enforce the Security Rule. Nobody is liable for not adopting the practices.
  • OCR said in 2022 that it would be insufficient to document the initial adoption of the practices without showing they were actively in use (87 FR 19833), and HHS has since said the amendment is not an alternative to compliance.

In practice

What to ask a vendor for

  • The report or certificate itself, not a logo, with its date and the period it covers.
  • Its scope: which systems, sites and services, and whether the delivery location and the subcontractors that touch your data fall within it.
  • Who issued it: a CPA firm for SOC 2, an outside certification body for ISO/IEC 27001, an authorized external assessor for HITRUST.
  • Exceptions, qualifications and open corrective actions, and what the vendor did about them.
  • The documents a vendor review needs whatever the vendor holds: the signed business associate agreement, its risk analysis, its policies and its training records, which the training and access rules page covers.

A vendor that holds none of the three is not in breach of the Security Rule for that reason, and a vendor that holds one is not shown by it to meet the Security Rule. The January 2025 proposal would add a written verification from business associates at least once a year; where that stands is in HIPAA Security Rule update for business associates. 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

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.