SOC 2 for health-tech
SOC 2 for health-tech: why hospitals ask for it and how to get there
HIPAA is the law you must follow when you handle PHI, but it produces no independent report a buyer can read. That is why many hospital and payer security teams also ask for a SOC 2 Type II report: it is an independent CPA firm’s opinion on whether your controls were designed and operating as described. This guide explains what they are asking for and how to sequence it with HIPAA.
Key takeaways
- SOC 2 is an AICPA attestation. Only an independent CPA firm can issue the report; software platforms, including Shieldra, help you get ready for it.
- Type I covers control design at a point in time. Type II covers design and operating effectiveness over a period, usually 3 to 12 months.
- Hospitals ask for SOC 2 because HIPAA itself provides no independent evidence of your controls.
- HIPAA and SOC 2 share much of the technical work, but SOC 2 does not replace BAAs, the HIPAA risk analysis or breach notification.
- If you handle PHI, start with HIPAA, then build toward a SOC 2 Type II window on the same controls.
Why hospitals ask for SOC 2 Type II
A hospital’s third-party risk team has to decide whether your product is safe to connect to patient data. Your own questionnaire answers are self-reported. A SOC 2 Type II report is the most widely recognised independent evidence for a SaaS vendor: a CPA firm tested your controls over a period and reports any exceptions it found.
Some health systems accept a SOC 2 Type I, a completed questionnaire plus a recent penetration test, or a roadmap with dates for an early pilot. Others require a Type II before production access to PHI. Larger systems sometimes ask for HITRUST instead of, or in addition to, SOC 2. Ask early which the buyer will accept.
SOC 2 Type I vs Type II
Every SOC 2 covers the Security category (the Common Criteria, CC1 to CC9). Availability, Confidentiality, Processing Integrity and Privacy are added when they match commitments you make to customers. For health-tech, Availability and Confidentiality are common additions.
| Type I | Type II | |
|---|---|---|
| What it tests | Whether controls are suitably designed | Whether controls are suitably designed and operated effectively |
| Time covered | A single date | An observation period, typically 3 to 12 months |
| What buyers think of it | A useful first step, often accepted for early pilots | What most hospital security teams ultimately want |
| Issued by | An independent CPA firm | An independent CPA firm |
Where SOC 2 and HIPAA overlap, and where they do not
Because so much of the technical work is shared, one set of controls and one body of evidence can serve both. Mapping them once avoids running two parallel programs.
| Area | HIPAA Security Rule | SOC 2 |
|---|---|---|
| Risk assessment | Required risk analysis, 164.308(a)(1) | CC3 risk assessment |
| Access control and MFA | 164.312(a) and (d) | CC6 logical access |
| Logging and monitoring | Audit controls, 164.312(b) | CC7 system operations |
| Incident response | Security incident procedures, 164.308(a)(6) | CC7 incident response |
| Vendor management | BAAs with subcontractors, 164.308(b) | CC9 vendor and business partner risk |
| Training | Security awareness and training, 164.308(a)(5) | CC1 and CC2 control environment and communication |
| BAAs and PHI use limits | Required | Not covered |
| Breach notification to customers and patients | Required, 164.400–414 | Not covered |
| Independent testing and report | Not required, no report exists | Required, issued by a CPA firm |
How to sequence HIPAA, then SOC 2
1. HIPAA foundations
Security officer, risk analysis, policies, training, BAAs, breach process. These are legal obligations once you handle PHI, and they are also most of what SOC 2 will test.
2. SOC 2 readiness
Pick your Trust Services Categories and system boundary, map controls to the criteria, fill the gaps (change management and vendor reviews are common ones) and collect evidence.
3. Choose a CPA firm
Engage an independent audit firm. Decide whether to start with a Type I or go straight into a Type II observation period.
4. Operate the controls
Run access reviews, vendor reviews, training and incident drills on schedule during the window, and keep the evidence. A Type II samples what happened, not what was written.
5. Share the report
Share the report under NDA, typically through a trust center with gated access, and keep the controls running for the next period.
How Shieldra helps with SOC 2 readiness
Shieldra prepares you for the audit. The audit itself, and the SOC 2 report, come from an independent CPA firm you engage.
- HIPAA and SOC 2 in one workspace, with a readiness score per framework.
- Policies, training records, risk analysis and vendor reviews stored as evidence your auditor can sample.
- GitHub, KnowBe4 and MDM integrations (Jamf, Kandji, Intune, JumpCloud, Google) to pull in evidence. Cloud and identity-provider integrations are on the roadmap; today that evidence is uploaded.
- A trust center to share your report and policies with buyers through gated access requests.
- HITRUST and NIST CSF are available as optional add-on frameworks for buyers that ask for them.
Working toward your first hospital security review?
We are looking for a small number of health-tech design partners. We will work with you hands-on to get your first hospital or payer security review done, and your feedback shapes what we build next.
This guide is general information, not legal advice. Shieldra helps you prepare and organise evidence; it does not certify compliance, and HHS does not approve or endorse any private HIPAA credential.
Frequently asked questions
Do hospitals require SOC 2 from vendors?
Not universally, and it is not a legal requirement. Many health systems ask for a SOC 2 Type II report in their vendor security review because HIPAA provides no independent report. Some accept a Type I, a questionnaire plus penetration test, or HITRUST instead. Ask the buyer early.
Is SOC 2 the same as being HIPAA compliant?
No. SOC 2 is an attestation against the AICPA Trust Services Criteria. It does not cover BAAs, HIPAA breach notification or the HIPAA risk analysis. The technical controls overlap substantially, so the work supports both.
Can Shieldra issue our SOC 2 report?
No. Only an independent CPA firm can issue a SOC 2 report. Shieldra helps you get ready: controls, policies, evidence and a readiness view you can bring to your auditor.
Should we start with SOC 2 Type I or Type II?
A Type I gives you a report sooner and is often enough for early pilots. If your buyers insist on Type II, you may prefer to go straight into an observation period once your controls are in place.
Do we need HIPAA first if we already have SOC 2?
If you handle PHI, HIPAA obligations apply regardless. Add the HIPAA-specific pieces: a HIPAA risk analysis, BAAs with customers and subprocessors, HIPAA-specific policies and breach notification procedures.