VectorCare ships into Epic on SoFaaS™

Epic Showroom listing 3120. Runtime = SoFaaS™. Written for vendors evaluating the SoFaaS™ runtime. For the customer story, see the VectorCare customer page.

See it live

Watch a SMART on FHIR app launch inside Epic.

Book a live demo of the same runtime VectorCare launches on — launch, auth, and patient context, mapped to your app.

Request a demo

What the app does in Epic

Launches inside Epic with patient context to run care-logistics workflows and write results back to the record.

The problem before the runtime

Care-logistics coordination happened outside the chart, so the work that was ordered, scheduled, and completed never made it back into the patient record.

How the launch works

  1. 1Staff open VectorCare from the Epic activity menu in the patient's chart.
  2. 2SMART on FHIR launch passes patient and encounter context and exchanges the authorization code for a scoped token.
  3. 3The app reads the patient, encounter, and coverage data the workflow needs.
  4. 4Results are written back so the completed logistics work is visible in the record.

FHIR scopes at launch

  • Patient.read
  • Encounter.read
  • Coverage.read
  • DocumentReference.write
  • launch (EHR launch context)

What this proves about SoFaaS™

  • A production Epic launch with real patient context, including write-back.
  • One SMART on FHIR app definition reused across each health system that turns it on.
  • Epic Showroom listing 3120 is distribution — the runtime underneath is SoFaaS™.

Epic Showroom listing

Listing id 3120 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. For the customer story, see the VectorCare customer page.

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.