Integration Guide

Epic SMART on FHIR Integration Guide

Whether you're a vendor building for health systems or a health system building internal tools — this guide walks you through how VectorCare abstracts the complexity of SMART on FHIR integration.

What is SMART on FHIR?

SMART on FHIR is an open standard that lets applications securely access patient data from EHR systems. It combines:

  • FHIR (Fast Healthcare Interoperability Resources): A modern data format for health information — think of it as the API standard for healthcare.
  • OAuth 2.0: A secure authentication protocol that lets users authorize third-party apps to access their data without sharing passwords.

Without SMART on FHIR, you'd need custom point-to-point integrations with every EHR vendor. With SMART on FHIR, one integration pattern works across Epic, Cerner, and others.

VectorCare's role: We handle the SMART launch flow, OAuth token management, and FHIR resource mapping. Your app makes simple API calls.

FHIR Resources Available via VectorCare

When you build on VectorCare, you get authenticated access to these core FHIR resources from Epic:

ResourceUse Case
PatientDemographics, name, date of birth, contact info
EncounterVisit details, timestamps, encounter type, location
ConditionPatient diagnoses and clinical problems
ObservationLab results, vital signs, assessment scores
MedicationRequestActive and historical medication orders
ServiceRequestReferrals, orders for procedures or therapies
AppointmentScheduled appointments and availability
LocationFacility information and care settings
CoverageInsurance and eligibility data
OrganizationHealthcare provider organizations and departments

All resources are fetched with the patient's current authorization context — you never see data beyond what the logged-in user is permitted to access.

How the OAuth 2.0 / SMART Launch Flow Works

Here's what happens when a clinician launches your app from within Epic:

1

User clicks your app in Epic's app gallery

2

Epic redirects to VectorCare with a launch code

3

VectorCare exchanges the code for an OAuth access token (you don't see this step)

4

Your app receives a token and the patient context

5

Your app calls VectorCare's FHIR API with the token

6

VectorCare returns FHIR data directly from Epic

You don't manage tokens, refresh logic, or error handling. VectorCare's SDK handles it in 3 lines of code.

Epic Showroom Listing and Timeline

A Showroom listing is not go-live, and a hospital can deploy you without one. A listing needs at least one live production connection. VectorCare prepares the submission materials; you file and hold the listing.

Weeks 1–2

You provide app metadata (name, description, logo)

Weeks 2–4

Epic's app team reviews your security documentation (VectorCare provides templates)

Weeks 4–6

Epic runs technical validation against their sandbox environment

After first hospital

Once your first hospital is live, you can file a Showroom listing. It is optional, and it is how multi-hospital distribution works.

Day 1: working SMART launch in Epic. Week 2: Showroom submission packet ready. You file it once your first hospital is live. Intake typically lands in weeks 1–3 and Epic review in weeks 2–8. A listing needs at least one live production connection, so the first hospital goes live before any listing.

Data Access Scopes and Least Privilege

SMART on FHIR uses scopes to control what data your app can access. VectorCare enforces least privilege — your app only requests the scopes it actually needs.

patient/Patient.readRead patient demographics
patient/Encounter.readRead encounter history
patient/Observation.readRead observations (labs, vitals)
patient/Condition.readRead active conditions
patient/MedicationRequest.readRead medications

You declare scopes once when you create your app on VectorCare. Epic sees exactly what you're asking for, and clinicians approve it at launch time. No hidden permissions, no scope creep.

Security: HIPAA, SOC 2 Type II, BAA

VectorCare operates as a HIPAA Business Associate. Your data is covered by a Business Associate Agreement (BAA) before your first user launches an app.

HIPAA Compliance

A Business Associate Agreement is in place with every hospital deployment. The BAA is available on day one.

SOC 2 Type II

SoFaaS™ is SOC 2 Type II audited. The full report is available under NDA.

Encryption

All in-flight traffic is TLS 1.2 or higher. All at-rest data is encrypted with managed keys.

Access Logs

Every request through the runtime is logged with caller identity, requested scope, FHIR resource, and outcome.

When you use VectorCare, you inherit the runtime's controls. You still own security of your own application.

Internal App Registration (Health Systems)

If you're a health system building internal tools, you don't go through Epic Showroom. Instead, your app is registered directly within your own Epic instance using Internal App Registration.

This means:

  • No Showroom listing required — your app is private to your organization
  • Faster deployment — skip the public review process
  • Same FHIR capabilities — full access to Patient, Encounter, ServiceRequest, and other resources within your instance
  • Your IT team controls access — scopes and permissions are managed internally

VectorCare handles the technical setup — OAuth client configuration, FHIR resource mapping, and security compliance — so your clinical informatics team can focus on the workflow, not the plumbing.

FAQ

Ready to Build?

Get started free — no credit card required.