RideMMT ships into Epic on SoFaaS™
Epic Showroom listing 3535. 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 RideMMT launches on — launch, auth, and patient context, mapped to your app.
What the app does in Epic
Launches inside Epic with patient context to coordinate RideMMT medical transport requests against the encounter.
The problem before the runtime
Transport requests arrived by phone and fax with details rekeyed from the chart, which meant delays, mismatched patient data, and no record of the request against the encounter.
How the launch works
- 1Staff open RideMMT 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 demographics, encounter, and appointment data to prefill the transport request.
- 4The request is dispatched to RideMMT and the status 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 3535 is distribution — the runtime underneath is SoFaaS™.
Epic Showroom listing
Listing id 3535 — 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.