What's the difference between Epic Showroom, a runtime, and an integration platform?

Three different jobs. Epic Showroom is distribution — hospitals find and request the app. A runtime (SoFaaS™) is what actually launches the app inside Epic: SMART App Launch, OAuth, FHIR, HIPAA hosting, BAA, SOC 2 evidence, and per-hospital deploy. An integration platform (Redox and similar) translates data between systems and does not put a clinician-facing app in the chart. You typically need the listing and a runtime; you need Redox only if you also have non-Epic data flows.

Do I still need Redox if I use SoFaaS™?

Only if you still have a data-translation problem. SoFaaS™ is not a Redox replacement. If the app launches in Epic, reads and writes FHIR in that launch context, and does not need HL7 v2 or other-EHR/payer/device pipes, you may not need Redox. If you do, run it alongside SoFaaS™ for those flows.

Is Epic Showroom the same as App Orchard?

Same role, new name and tighter program. App Orchard (later App Market) was Epic's older third-party program; it was restructured into Epic Showroom (the public catalog) and Vendor Services (developer enrollment and sandboxes). A Showroom listing is still required for multi-hospital third-party apps; it still does not host or comply the app.

Do I still need a Showroom listing if I run on SoFaaS™?

Yes, for any third-party app a hospital will deploy into Epic. SoFaaS™ does not replace Showroom; it files the submission and is the runtime the listing points at. Internal tools built by a health system for its own Epic instance can use Internal App Registration and skip Showroom.

What about HIPAA, a BAA, and SOC 2?

Hospitals will ask for all three before go-live; Showroom supplies none of them. SoFaaS™ is SOC 2 Type II audited (report under NDA), operates as a HIPAA Business Associate, and puts a BAA in place on day one — typically one platform template hospitals review at organization level, with per-hospital amendments when a health system requires its own. Vendors inherit that posture for traffic through the runtime; they still own security of their own application code and any data they handle outside SoFaaS™.

How long does it actually take to go live?

Day 1 in Epic, Week 2 on Showroom, Week 3+ live at the hospital: signup provisions a workspace and Epic-connected sandbox the first day, SoFaaS™ files the Showroom submission in the first two weeks, and a hospital that is ready deploys onto the already-reviewed runtime in about a week. Two honest caveats: Epic's Showroom review queue can run into additional weeks (intake in weeks 1–3, Epic review typically weeks 2–8), and a first hospital can pilot on the runtime in parallel while the listing is in flight. DIY from-scratch builds are cited at 12–18 months to first hospital.

Do we need our own Epic relationship?

You need enrollment in Epic's Showroom / Vendor Services program, not a pre-existing personal relationship with Epic. SoFaaS™ customers do not have to have that enrollment already — VectorCare runs submission and the vendor process as part of the engagement. You still own the clinical product, the hospital relationship, and the customer contract.

Who owns the code and the data?

The vendor owns the application code and IP. The hospital owns its clinical data. SoFaaS™ operates the runtime in between — auth, FHIR mapping, hosting, audit logs — and does not take the product or the chart.

404

Page not found

The page you're looking for doesn't exist or has moved. Here's where most people are heading:

What is SoFaaS™Documentation Journal

Return to the homepage