SOC 2 vs. a HIPAA BAA: What to Ask a Medical Record Review Vendor Before You Upload

By John Mahoney · November 15, 2026 · About 9 minutes

Which AI medical record review tools support SOC 2? Vendors use “SOC 2” to mean different things, so read the exact words. As displayed on November 15, 2026: Superinsight states it is “SOC 2 Type 1 certified”; Medrecords AI lists SOC 2 and publishes a SOC 2 readiness report dated November 3, 2026; MedLegal AI does not hold a SOC 2 report and says so on its security page, signs a business associate agreement before any upload, and runs on AWS, whose SOC 2 report covers AWS’s own controls. SOC 2 is an auditor’s report. The written agreement HIPAA requires is a separate document, and it is the one with legal force.
On this page
  1. What a SOC 2 report is
  2. Four things “SOC 2” can mean on a vendor page
  3. What HIPAA actually requires
  4. What the ethics rules require
  5. Nine questions to ask before the first upload
  6. Where MedLegal AI stands
  7. Frequently asked questions

A security questionnaire for a records tool usually has one line that reads “SOC 2: yes / no.” The honest answer to that line takes a paragraph, and the difference matters to the lawyer whose client’s chart is in the upload. This page sets out what the report is, what the law requires independently of it, and the questions that separate a vendor who has done the work from one who has a badge on a footer.

What a SOC 2 report is

SOC stands for System and Organization Controls. The AICPA describes it as “a suite of service offerings CPAs may provide in connection with system-level controls of a service organization.” A SOC 2 report is an independent accountant’s examination of a company’s controls measured against the AICPA Trust Services Criteria. AWS, for example, describes its own SOC 2 report as “a description of the AWS controls environment and external audit of AWS controls that meet the AICPA Trust Services Criteria for Security, Availability, Confidentiality, and Privacy.”

Three features follow from that definition.

One more reason to ask who signed the report: the AICPA’s SOC page currently carries a notice that it “is looking into allegations published anonymously about the business practices of a compliance vendor that offers” SOC services, and that SOC services “should be thoroughly evaluated by service organizations and CPA firms.” The name of the CPA firm and the period covered are fair questions.

Four things “SOC 2” can mean on a vendor page

What the page saysWhat it meansWhat to ask for
SOC 2 Type 2An auditor tested the vendor’s controls over a period.The report, the period, the auditor, and any exceptions noted.
SOC 2 Type 1An auditor examined the design of the vendor’s controls as of a date.The report date and whether a Type 2 period is under way.
SOC 2 readiness reportA self-assessment or compliance-platform output mapping controls to the criteria. It is not an auditor’s opinion.Whether an audit is engaged, with which CPA firm, and the expected date.
“Hosted on SOC 2 infrastructure”The cloud provider has a SOC 2 report. The vendor does not.What the vendor itself does for access control, logging, deletion and incident response.

None of the four is disqualifying. A two-person company with a readiness report and a signed agreement may handle a file more carefully than a large one with a Type 2 report and a broad subprocessor list. The point is to know which of the four you are being told.

What HIPAA actually requires

HIPAA does not mention SOC 2. It requires a contract. The Privacy Rule, at 45 C.F.R. § 164.502(e)(1)(i), lets a covered entity disclose protected health information to a business associate only “if the covered entity obtains satisfactory assurance that the business associate will appropriately safeguard the information,” and § 164.502(e)(2) requires that the assurance “be documented through a written contract or other written agreement.” The Security Rule repeats the requirement for electronic records at § 164.308(b).

Whether a law firm is in that chain depends on the client. The definition of business associate at 45 C.F.R. § 160.103 includes a person who provides “legal” services “to or for such covered entity” where the service involves disclosure of protected health information. A defense firm representing a hospital or physician fits that definition, and a software vendor the firm uses to read the chart is the firm’s subcontractor: under § 164.502(e)(1)(ii) the business associate must obtain the same written assurances from it. A plaintiff’s firm that receives records on the patient’s authorization is not providing services to a covered entity, so its duty to protect the file comes from the ethics rules and state law. Most firms on both sides ask for the agreement anyway, and they should.

The contract itself must, under § 164.504(e)(2), “establish the permitted and required uses and disclosures of protected health information by the business associate.” Read that clause in the vendor’s agreement. It is where a right to use uploaded records for product improvement would appear.

What the ethics rules require

ABA Model Rule 1.6(c) is one sentence (Pennsylvania adopted it as Rule 1.6(d)): “A lawyer shall make reasonable efforts to prevent the inadvertent or unauthorized disclosure of, or unauthorized access to, information relating to the representation of a client.” Reasonable efforts toward a vendor means asking the questions below and keeping the answers. A SOC 2 report is one piece of evidence for that file. It does not replace the questions.

Nine questions to ask before the first upload

  1. Will you sign a business associate agreement before I upload, and can I read it first?
  2. Which SOC 2 document do you have: Type 1, Type 2, or a readiness report? Who was the auditor and what period does it cover?
  3. Who are your subprocessors, and is there a signed agreement with each one that touches the records?
  4. Are uploaded records used to train or tune any model, yours or a subprocessor’s?
  5. Where are records stored, and how are they encrypted at rest and in transit?
  6. Can one customer’s account ever read another’s case, and how is that enforced?
  7. Can I delete a case myself, and what happens to extracted text and backups when I do?
  8. What is logged about who opened a record, and can I export that log?
  9. If there is a breach, how and how fast will I be told?

Then one question that is not about security at all: can every finding be traced to a page? A tool that is locked down and wrong is still wrong. See how to verify a software-built chronology for that half of the review.

Where MedLegal AI stands

Stated the way we would want a vendor to state it to us:

The detail is on the security page. If your client or carrier requires a vendor SOC 2 Type 2 report by contract, we are not yet the right choice for that matter, and it is better you hear that from us before the upload than after.

Frequently asked questions

Which AI medical record review tools have SOC 2?

As displayed on vendor sites on November 15, 2026: Superinsight states it is SOC 2 Type 1 certified; Medrecords AI lists SOC 2 and publishes a SOC 2 readiness report dated November 3, 2026; MedLegal AI does not hold a SOC 2 report, signs a business associate agreement before upload, and runs on AWS, which has its own SOC 2 report. Ask any vendor for the report itself, the auditor and the period covered.

Is SOC 2 required by HIPAA?

No. HIPAA does not mention SOC 2. Under 45 C.F.R. § 164.502(e), a covered entity may disclose protected health information to a business associate only with satisfactory assurances documented in a written contract, commonly called a business associate agreement. A SOC 2 report is voluntary evidence about a vendor's controls.

What is the difference between SOC 2 Type 1 and Type 2?

In the usual description, a Type 1 report addresses whether a company's controls are suitably designed as of a specific date, and a Type 2 report also addresses whether those controls operated effectively over a period of months. A readiness report is neither; it is a self-assessment prepared before an audit.

Does a law firm need a business associate agreement with a records review vendor?

A firm that represents a covered entity, such as a hospital or physician, is a business associate under 45 C.F.R. § 160.103 and must obtain written assurances from any subcontractor that handles the records under § 164.502(e)(1)(ii). A plaintiff's firm holding records on the patient's authorization is not a business associate, but the duty of reasonable efforts under Model Rule 1.6(c) points to the same agreement.

If a vendor runs on AWS, is the vendor SOC 2 compliant?

No. The AWS SOC 2 report is an external audit of AWS's controls. A vendor hosted on AWS benefits from those infrastructure controls, but its own application, access rules and staff practices are outside the AWS report unless the vendor has been examined separately.

Read the agreement before you upload anything

The business associate agreement is public, the security page says what we do and what we have not earned yet, and a synthetic demo case lets you see page-cited output before any real record is involved.

Read the security page →

Sources. 45 C.F.R. § 164.502(e), § 164.504(e), § 164.308(b) and § 160.103, eCFR text current to November 12, 2026 (quoted). AICPA, System and Organization Controls: SOC Suite of Services (quoted, read November 15, 2026). AWS, SOC FAQs (quoted). Pa. R. Prof. Conduct 1.6(d), 204 Pa. Code ch. 81 (text quoted; the same sentence as ABA Model Rule 1.6(c)). Superinsight and Medrecords AI security statements as displayed November 15, 2026. The Type 1 and Type 2 descriptions follow the common summary of the AICPA attestation standards and were not read from the AICPA guide itself.

MedLegal AI is software, not a law firm. This article is general information for attorneys, paralegals, legal nurse consultants and patients; it is not legal or medical advice and does not create an attorney-client relationship. Verify every statute, rule, price and figure against the current source before relying on it. Questions: [email protected]