Lyft ships into Epic on SoFaaS™
Epic Showroom listing 3237. Runtime = SoFaaS™. Written for vendors evaluating the SoFaaS™ runtime, not for hospital transport buyers comparing ride programs.
Watch a SMART on FHIR app launch inside Epic.
Book a live demo of the same runtime Lyft launches on — launch, auth, and patient context, mapped to your app.
What the app does in Epic
Launches inside Epic with patient context so staff can arrange a Lyft Healthcare ride without leaving the chart.
The problem before the runtime
Ride ordering lived in a separate portal, so staff left the chart, retyped patient and appointment details, and the ride never tied back to the encounter.
How the launch works
- 1Staff open the app from the Epic activity menu in the patient's chart.
- 2SMART on FHIR launch passes patient and encounter context and exchanges the authorization code for a scoped token.
- 3The app reads the patient demographics and appointment details it needs to place the ride.
- 4The ride request is handed off to Lyft Healthcare and the confirmation is surfaced back to the user in Epic.
FHIR scopes at launch
- Patient.read
- Encounter.read
- Appointment.read
- launch (EHR launch context)
What this proves about SoFaaS™
- A production Epic launch with real patient context, not a sandbox demo.
- One SMART on FHIR app definition reused across each health system that turns it on.
- Epic Showroom listing 3237 is distribution — the runtime underneath is SoFaaS™.
Epic Showroom listing
Listing id 3237 — view on Epic Showroom. Showroom is distribution; the app itself runs on the SoFaaS™ runtime.
Who this page is for
Written for vendors evaluating the SoFaaS™ runtime, not for hospital transport buyers comparing ride programs.
Where to go next
Shipping your app into Epic next?
SoFaaS™ is the same SMART on FHIR runtime behind every app on this page — launch, auth, patient context, and Epic Showroom submission support, without building an integration team.