{
  "id": 20997857,
  "title": "Passing Epic's Vendor Security Review: What to Prepare",
  "url": "https://urgent.news/2026/11/21/passing-epics-vendor-security-review-what-to-prepare",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-11-21T04:59:31.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/nirmitee/passing-epics-vendor-security-review-what-to-prepare-3h01"
  },
  "original_language": "en",
  "account": "Passing Epic's Vendor Security Review: Understanding the Two-Stage Process and Required Evidence\n\nHealthtech teams planning an Epic integration often focus on the application development, sandbox testing, and app listing. However, a crucial security review process can stall their progress. This review consists of two distinct stages: Epic's listing review and each hospital's individual review. To successfully navigate these gates, it is essential to prepare the necessary evidence ahead of time.\n\nThe most misunderstood aspect of Epic's integration is that there are two separate security reviews. Gate 1 is Epic's listing review, which determines discoverability on Epic's Showroom and Connection Hub. This process typically takes 8 to 16 weeks and involves an application and technical security review. Gate 2 is the gate that controls go-live, and it is run by the security, privacy, and vendor-management teams at each individual hospital. Because every health system has its own Epic instance and governance, this gate is repeated for every customer, on its own calendar.\n\nThe review process is not a one-time hurdle but rather a recurring cost of selling to hospitals due to the potential risk of a healthcare data breach. A breach can cost an average of $9.77 million in 2024 and $7.42 million in 2025 according to IBM. The review is a hospital's way of evaluating the potential risk of new attack surface before granting approval.\n\nTo pass through the security review more efficiently, healthtech teams should ensure they have the required evidence ready before the first meeting. This includes a SOC 2 Type II report, HITRUST certification (i1 or r2), a penetration test from the past 12 months, a signed Business Associate Agreement (BAA) template, a subprocessor list that matches the BAA, application-level logs of patient data access, and a completed questionnaire from the buyer (Censinet, SIG, or CAIQ). By having these documents ready, the review process can be completed within weeks rather than quarters.",
  "summary": "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…",
  "key_points": [],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}