SOC 2 vs HIPAA for Healthcare SaaS: What Do You Need First?
Check HIPAA status from the service and data flow, then ask buyers whether they also need a SOC 2 report. One does not replace the other.

If you sell software to healthcare customers, settle the HIPAA question from your service and data flow before promising to handle patient information. Then ask the buyer whether it also needs a SOC 2 report. HIPAA duties depend on whether your company is a covered entity or business associate under the HHS rules. A SOC 2 report is a separate CPA examination of a described service and its controls. Neither answer substitutes for the other.
SOC 2 vs HIPAA: what question does each answer?
HIPAA follows the regulated relationship
- Your legal role and the protected health information your service handles determine which duties apply.
- The relationship, data flow, applicable HIPAA Rules, and agreements set the scope. Management and qualified counsel assess those duties; HHS enforces the Rules.
- A healthcare customer may ask for a BAA and facts about how the service meets its duties.
SOC 2 follows the described service
- A company engages a CPA firm to examine a service and its controls for report users.
- The system description, selected Trust Services Criteria, report type, and date or period set the scope.
- Management operates the controls; an independent CPA firm examines them and issues a report for the stated scope, subject to its use terms.
HHS explains that the HIPAA Security Rule calls for administrative, physical, and technical safeguards for electronic protected health information, or ePHI. The AICPA’s SOC suite describes SOC 2 as a report on a service organization’s controls relevant to Security, Availability, Processing Integrity, Confidentiality, or Privacy. A SOC 2 report can give a healthcare buyer useful information about controls, but it does not decide whether the company meets HIPAA’s legal requirements.
Is your software company a HIPAA business associate?
Do not decide from the words “healthcare SaaS” alone. Map who sends data, what the service does with it, whose behalf it acts on, and which party controls the relationship. HHS says that merely selling software to a covered entity does not create a business associate relationship if the vendor has no access to the entity’s protected health information. Hosting patient information or accessing it to support the service can change that answer.
Use these questions with your customer and counsel:
- Is the customer a HIPAA covered entity or another business associate?
- Does your service create, receive, maintain, or transmit protected health information on that party’s behalf?
- Which application, database, backup, support, logging, analytics, and cloud providers can hold or access that information?
- What uses, disclosures, incident notices, access rights, and return or deletion duties will the agreement assign?
“We encrypt everything” does not settle the role. HHS says its cloud guidance also applies to a provider that maintains encrypted ePHI on behalf of a regulated customer even when it lacks the key. On the other hand, HHS says an individual choosing an independent app to receive their own information does not by that fact alone make the app a business associate. The relationship and purpose matter. If your company sells both provider-facing and direct-to-consumer products, map their data flows separately.
What should happen before you handle protected health information?
When the arrangement makes your company a business associate, resolve the business associate agreement, or BAA, and the actual operating duties before the service starts handling protected health information. HHS’s BAA guidance describes terms for permitted uses, safeguards, incident reporting, individual rights support, subcontractors, and return or destruction at termination. Counsel should check the specific contract and data flow rather than treating a sample agreement as a signed control.
HHS also says regulated entities need a risk analysis for the ePHI they create, receive, maintain, or transmit. That work needs input from the people who know your architecture and source systems. Identify where ePHI enters, where it is copied, who can access it, how it leaves, and what happens during an incident. Confirm which cloud and other downstream services also need agreements. Do not put patient records or secrets into a general GRC repository to prove the work occurred.
If counsel determines that your service is not a HIPAA regulated entity, do not call it “HIPAA compliant” for sales. Other privacy, security, contract, or consumer health data rules may still apply; the HIPAA label alone does not answer those questions.
When should you start the SOC 2 work?
Ask the healthcare buyer what it actually needs to review. A BAA does not produce a SOC 2 report, and a SOC 2 report does not sign the BAA. Some buyers ask for both; others accept a different security review at this stage. Get the requested report type, scoped product, criteria, period or date, and deadline in writing. The customer request guide has a short reply you can use before the report exists.
For SOC 2, define the service boundary and assess the risks and controls you will describe. Management operates those controls and keeps evidence. The CPA firm tests them and decides whether evidence is sufficient for its examination. A SOC 2 report limited to one product does not automatically cover every healthcare integration or data flow. Compare the final report’s scope with the buyer’s request instead of relying on the company name on its cover.
The startup SOC 2 guide helps decide when the business case supports that work. You can reuse facts such as system diagrams, access reviews, vendor records, and risk decisions across internal reviews, but keep HIPAA’s legal requirements and the SOC 2 examination criteria clear in each record.
Where does FileGRC fit?
FileGRC is a Git-native GRC workspace for SOC 2 work. JSON holds structured records, Markdown holds long-form work, and Git supplies the change history. You can keep your SOC 2 scope, controls, risk decisions, and approved evidence references reviewable there. Starter records are proposals, not compliance claims.
FileGRC does not determine HIPAA status, provide a BAA, run the underlying security or privacy systems, or perform the SOC 2 examination. Keep patient data in approved source systems, work with qualified counsel on HIPAA, and use the CPA firm’s procedures to prepare and deliver SOC 2 evidence.
If you also accept card payments, map that payment flow separately. The SOC 2 versus PCI DSS guide explains why a hosted checkout can narrow PCI DSS work without replacing a customer’s SOC 2 report request.
Run your SOC 2 program as files in Git.
Keep policies, controls, work, and evidence indexes in a repository your team and agents can inspect. Add optional FileGRC Autopilot email and Slack reminders to keep work moving.
Frequently asked questions
Does a SOC 2 report make a healthcare SaaS company HIPAA compliant?
No. A SOC 2 report is a CPA firm's examination of a described service and controls against selected Trust Services Criteria. It does not determine whether a company meets the HIPAA Rules. Check the legal role, data flow, contracts, and HIPAA duties separately.
Does every healthcare SaaS startup need HIPAA?
No. The HIPAA Rules apply to covered entities and business associates. HHS says merely selling software to a covered entity does not by itself create a business associate relationship. Have qualified counsel assess whether your service creates, receives, maintains, or transmits protected health information on behalf of a regulated customer.
Can a SaaS vendor need HIPAA even if it cannot read encrypted patient data?
Yes. HHS says a cloud provider that maintains encrypted electronic protected health information on behalf of a covered entity or business associate can still be a business associate without the decryption key. Review the actual service and agreements with counsel.
Does HIPAA require a SOC 2 report?
The HHS HIPAA guidance does not make a SOC 2 report the test for whether a business associate meets its duties. A customer may separately require a SOC 2 report for procurement. Ask what type, scope, criteria, and date or period it will accept.
When does a healthcare SaaS vendor need a business associate agreement?
A business associate arrangement generally needs a written agreement when the vendor creates, receives, maintains, or transmits protected health information on behalf of a covered entity or another business associate. The role and agreement terms depend on the actual service and parties. Review them with qualified counsel before handling the information.
Can FileGRC run a HIPAA program?
FileGRC is a Git-native GRC workspace for SOC 2 work. It can organize SOC 2 records and evidence references, but its starter records are proposals, not HIPAA or SOC 2 compliance claims. It does not replace legal review, source systems, or the independent CPA firm that performs a SOC 2 examination.