DEV Community

Nirmitee.io
Nirmitee.io

Posted on Originally published at nirmitee.io

Passing Epic's Vendor Security Review: What to Prepare

You pass the review twice, once with Epic and once at every hospital. The evidence to have ready and the two gaps that stall most deals.

Originally published on Nirmitee.io: Passing Epic's Vendor Security Review: SOC 2, HITRUST, BAA & the Evidence Checklist (2026)

Many healthtech teams plan their Epic integration around the build: the FHIR work, the sandbox, the app listing. Then the deal stalls in a security review nobody scheduled for.

The review is not mysterious. It is a finite list of evidence and a known set of reviewers. Have the evidence ready, and it takes weeks. Discover it mid-review, and it takes quarters.

Two reviews, not one

The most misunderstood thing about going live on Epic: you pass a security review twice, and they are different gates.

  • Gate 1: Epic's listing review. To list on Epic's Showroom and Connection Hub, Epic runs an application and technical security review, typically 8 to 16 weeks. This makes you discoverable. It does not get you live.
  • Gate 2: each hospital's own review. This is the gate that controls go-live, run by that customer's security, privacy and vendor-management teams.

Because every health system runs its own Epic instance and governance, Gate 2 repeats for every customer, on its own calendar. The source cites a peer-reviewed study of one decision aid integrated across five academic health systems: the whole process took roughly 18 months, and each institution had a different security risk assessment process.

The review is not a one-time hurdle. It is a recurring cost of selling to hospitals.

Why hospitals take it seriously

A healthcare data breach is the most expensive kind there is. The source cites IBM's average of $9.77 million in 2024, easing to $7.42 million in 2025. Your app is new attack surface plugged into their patient record, and the review is the hospital pricing that risk before it says yes.

Who reviews you

It is not one person with a checklist. Expect:

  • The CISO or security team: your controls, the questionnaire and the evidence.
  • The privacy officer: HIPAA, minimum necessary access and the BAA.
  • Vendor management or procurement: intake, risk tiering and the contract.
  • Legal: changes to the BAA.
  • Clinical operations: workflow and system-dependency risk.

The evidence pack

Have these ready before the first meeting:

  • A SOC 2 Type II report, scoped to the right systems.
  • HITRUST certification (i1 or r2) where the buyer expects it.
  • A penetration test from the last 12 months.
  • A signed BAA template that passes obligations down to your subcontractors.
  • A subprocessor list that matches the BAA.
  • Application-level logs of who accessed patient data.

A few details matter. SOC 2 Type II tests controls over a period: three months is the technical minimum, but hospitals prefer six to twelve. The report's scope must cover your patient-facing app, the API that handles patient data and your data pipeline, or procurement will notice the gap. For HITRUST, r2 is the tier hospital and health-plan buyers most often expect.

Different buyers also use different questionnaires, including Censinet, SIG and CAIQ. The original guide explains each one, along with the HITRUST tiers.

The two gaps that stall most reviews

Across practitioners who have been through this, two gaps block more deals than anything else:

  1. Subprocessor list versus BAA. Procurement compares your full list of subprocessors against what your BAA covers. Any tool that handles patient data and is not listed will be flagged.
  2. Missing patient-data access logs. Hospitals look for application-level logs of who accessed patient information. Their absence is treated as a HIPAA audit control failure.

How to get through faster

You cannot make the hospital move faster, but you can stop adding delay yourself:

  • Have your SOC 2 Type II and BAA ready before you start. A SOC 2 observation window cannot be compressed later.
  • Reconcile your subprocessor list with the BAA up front.
  • Turn on application-level audit logging for patient data.
  • Keep a completed SIG or CAIQ questionnaire on the shelf, so you can answer the same day.

The bar is rising. HHS proposed a HIPAA Security Rule overhaul in January 2025 that would make encryption, multi-factor authentication and annual penetration testing mandatory. As of mid-2026 it was not finalized, but reviewers increasingly ask for these controls anyway. The full guide covers the 2026 regulatory backdrop and what to expect next.


Nirmitee.io helps healthtech products get live on Epic, from the FHIR build and access path to the security review. For the full evidence checklist, read the original: Passing Epic's Vendor Security Review on Nirmitee.io.

Dinesh Thorat is Healthtech Growth Partner at Nirmitee.io.

Originally published at nirmitee.io.

Top comments (0)