Patients love it. MyChart won't launch it.
The shape of a stuck patient engagement deal
The marketing team loves it. Patient experience is on board. Then the deal hits the wall: no SMART patient launch context configured, no answer to which FHIR resources your app can read or write on the patient's behalf, no Showroom listing, no clean answer to "what about the next Epic version upgrade?"
The deal stalls. Not because patients don't want it — but because the runtime underneath wasn't ready for the hospital.
What hospital review actually asks engagement vendors
- →Where does the patient launch from — MyChart, inpatient experience, standalone — and what context binds the session?
- →Which FHIR scopes does your app request, and what can the patient actually read and write?
- →What happens when we upgrade Epic next quarter? What breaks?
- →How is patient data isolated from your other customers' patients?
- →Show me your SOC 2 Type II report, your BAA, and your sub-processor list.
What SoFaaS™ handles for you
SMART patient launch
MyChart, inpatient, and standalone launch surfaces, all bound to the same runtime.
Scoped FHIR reads + writes
Standardized scopes for patient-accessible resources, configurable per deployment.
Cross-version stability
FHIR version differences absorbed at the runtime — your app builds against a stable surface.
Multi-tenant isolation
Per-hospital partitioning baked in. Standard answer in every patient-data questionnaire.
SOC 2 Type II + BAA
Full report shareable under NDA the same week procurement asks.
Showroom listing
Submission and ongoing maintenance handled. Distribution open by the time you're cleared.
The first hospital is hard. The tenth is harder.
The first hospital teaches you what patient engagement review looks like — launch context, scopes, identity, consent.
The tenth hospital is what kills internal-build engagement platforms. Each one is on a different Epic version, with a different MyChart configuration, with a different answer to "what scopes do we let patient apps request?" Without a runtime that absorbs that variance, every hospital is another integration project.
SoFaaS™ sits between your engagement product and the long tail of hospital-specific configurations. You ship the same app; we make it deployable into every hospital that asks.
FAQ
Why do patient engagement vendors stall on Epic?
Patient-facing apps that launch from MyChart or the inpatient experience touch a different part of the security review than clinician-facing apps — patient identity, scope of access, what the patient is allowed to see and do, and how data flows to and from third parties. The hospital wants every one of those questions answered before they enable the launch context. Most patient engagement vendors aren't set up to answer them at the runtime level.
What does SoFaaS™ handle for a patient engagement vendor?
SMART App Launch in patient context (including standalone launch flows), scoped FHIR reads and writes for the patient-accessible resources, MyChart and inpatient launch surfaces, multi-tenant isolation, the SOC 2 Type II + BAA posture, and the Epic Showroom listing. You keep the patient experience, the engagement model, and the longitudinal product — the parts that make your app yours.
How does this work across different versions of Epic?
FHIR version differences across hospitals running different Epic versions are absorbed at the SoFaaS™ runtime level. We map the resources your app expects to whatever the hospital is on, and you get a stable surface to build against. You ship the same app; it works across the long tail of versions.
What about patient identity verification and consent?
Patient identity is anchored to the SMART App Launch flow — the patient is already authenticated to the hospital before they hit your app. Consent for any third-party data sharing your product does is handled inside your app's surface, with audit hooks back into the SoFaaS™ runtime so the hospital can see what was disclosed and when.
Can patients use this without an active encounter?
Yes. Standalone launch flows are supported — patients can authenticate to the hospital directly and use your app outside of an active encounter. The same FHIR scoping applies; the app gets a stable runtime regardless of how the patient got there.
Have a deal stuck on Epic?
Tell us about it. Half-hour call. We'll know within 15 minutes whether SoFaaS™ can unblock you.
Talk to us