The work happens outside the chart. The chart still has to know.
The shape of a stuck coordination deal
Operations love the product. Case management is on board. Then it hits the wall: no FHIR-native ServiceRequest flow, no Showroom listing, no clean audit on status changes flowing back into the chart, and no compliance posture the security team will sign off on.
The deal collapses into "we'll revisit next year" — not because the product is wrong, but because the runtime around it isn't ready for the hospital.
What hospital review actually asks coordination vendors
- →How does an order placed in Epic get to your operations system, and what's the audit on the round trip?
- →When a status changes in your system — assigned, dispatched, completed — what gets written back to the chart and by whom?
- →How do case managers launch your tool inside Epic with patient context, without a second login?
- →How do you isolate our hospital's data from your other customers'?
- →Show me your SOC 2 Type II report, your BAA, and your sub-processor list.
What SoFaaS™ handles for you
ServiceRequest + Task flow
Order in, status sync out, with full provenance the case manager can audit.
SMART App Launch
Case-manager view launches inside Epic with patient and encounter context.
Encounter + DocumentReference write-back
Completion notes and outcome documentation land cleanly in the chart.
Multi-tenant isolation
Per-hospital partitioning baked in. Standard answer in every security 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 coordination review actually looks like — the order flow, the status mapping, the audit expectations.
The tenth hospital is what kills internal-build coordination platforms. Each one wants its own SSO, its own EHR version, its own status taxonomy, its own audit format. Without a runtime that absorbs that variance, every hospital becomes another integration project.
SoFaaS™ sits between your coordination product and the long tail of hospital-specific requirements. You ship the same app; we make it deployable into every hospital that asks.
FAQ
Why is care coordination especially hard to ship into Epic?
Care coordination workflows span the chart and the world outside it — transport, DME delivery, home-health visits, post-acute placement. The hospital wants every status change reflected in Epic, every order tied back to a clinician decision, and every external party properly attested. That's a lot of FHIR resources, a lot of write-back, and a lot of audit. Most coordination vendors rebuild that runtime themselves, badly.
What does SoFaaS™ handle for a coordination vendor?
ServiceRequest, Task, and Encounter handling with full audit, status sync back to the chart, SMART App Launch into the case-manager workflow, multi-tenant isolation, the SOC 2 Type II + BAA posture, and the Epic Showroom listing. You keep the matching algorithm, the partner network, the operations layer, and the patient experience — the parts your customers are buying.
How does this work with our existing dispatch or operations system?
Your operations system stays where it is. SoFaaS™ is the integration layer between Epic and that system — it owns the FHIR side, including the per-hospital configuration of what gets written back, when, and by whom. Your back end keeps owning the dispatch and the SLAs.
What about external parties — drivers, DME techs, home-health nurses?
External parties are out of scope for SoFaaS™ — that's your network. SoFaaS™ owns the chart-side: making sure the right resource updates land in Epic when those external parties hit milestones in your system. The hospital sees a clean record; you keep the operational layer.
Is this just for transport or for any coordination workflow?
Any coordination workflow that has to keep Epic in sync — transport, DME, home health, post-acute placement, discharge logistics, longitudinal coordination. The same SoFaaS™ runtime handles them; the FHIR mappings differ per workflow and we configure them per deployment.
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