HL7 v2 through Epic Bridges, FHIR R4 APIs, SMART apps in Hyperspace, and a Showroom listing — pick the surface you're integrating against and jump straight to it.
Epic Consulting, HL7, FHIR API, and SMART App Delivery
Four modes of Epic engagement — consulting, HL7 v2 interfaces (Bridges), FHIR R4 APIs, and SMART app delivery. Pick the one that matches where you are in the Epic journey.
Epic advisory + staff augmentation
Epic consulting across the project lifecycle
From pre-go-live roadmap scoping to steady-state optimization, we embed Epic-experienced engineers alongside your team. Our consultants have Vendor Services / Showroom certification experience, Epic build background, and (critically) integration scar tissue — so you get practical "this is what actually works in Epic" advice, not textbook recommendations.
Epic still runs the bulk of its real-time clinical messaging on HL7 v2 through Epic Bridges. ADT, ORM, ORU, SIU, and MDM feeds to labs, radiology, ancillary systems, and downstream HIEs are all v2 — and the interface spec you implement has to match Epic's vendor-specific Z-segments, custom triggers, and MLLP framing. We author the Bridges spec, build the channel on the receiving side (Mirth Connect or OIE), exercise it against an Epic test environment, and run the go-live.
Epic's FHIR R4 endpoint at /api/FHIR/R4/* exposes Patient, Observation, MedicationRequest, Condition, and a growing set of US Core resources. We handle Vendor Services client registration, scope negotiation (patient vs user vs system), token flow with PKCE, Epic-specific quirks (chunked resource bundles, search parameter subsets), and the certification gauntlet.
Hyperspace-embedded SMART apps that clinicians actually use
A SMART app in Epic means more than wiring OAuth — it means fitting into Hyperspace layout, respecting clinician cognitive load, and surviving the Usability Feedback step of Epic's Vendor Services certification. We design the UX around the clinician's task, implement the SMART App Launch handshake, and iterate with real Epic users before submitting for certification.
Saga IT is a healthcare IT consulting firm with deep, hands-on experience across the full Epic integration surface. As an experienced Epic integration partner, we've delivered hundreds of integrations for hospitals, health systems, and digital health companies — from FHIR R4 API connections and MyChart portal integrations to full SMART on FHIR applications listed on Epic's Showroom marketplace.
Our team works across the entire Epic connectivity stack: FHIR R4 APIs with US Core profile conformance, HL7 v2 interfaces through Epic Bridges, Interconnect web services, MyChart patient-facing integrations, and Care Everywhere health information exchange. Whether you're building your first Epic connection or modernizing legacy Bridges interfaces with FHIR, we handle scope negotiation, sandbox development, Epic's security review, and production go-live.
What We Offer
Epic EHR Integration & SMART on FHIR Services
End-to-end Epic connectivity — from FHIR R4 API development and SMART on FHIR apps to Epic Vendor Services / Showroom certification and go-live support.
Click to expand
Click to expand
Click to expand
Click to expand
Click to expand
Click to expand
01/06 US Core · OAuth 2.0 · Cures Act
Epic FHIR R4 API development
Build and consume Epic's FHIR R4 APIs for patient access, clinical data exchange, and population health workflows. We implement the full range of Epic FHIR resources including Patient, Encounter, Observation, MedicationRequest, and DiagnosticReport with proper US Core profile conformance. Our team handles scope negotiation, sandbox testing, and production certification against Epic's FHIR endpoint requirements.
Design, build, and launch SMART on FHIR applications that run inside the Epic Hyperspace workflow or as standalone patient-facing tools — see our broader healthcare app development practice for patient portals, telehealth platforms, and mobile health apps. We implement the full OAuth 2.0 authorization code flow with PKCE, handle EHR launch context parameters, and build responsive UIs that integrate seamlessly with clinical workflows. Our SMART apps support both provider-facing EHR launch and patient-facing MyChart launch contexts.
SMART on FHIR
PKCE
Hyperspace launch
MyChart launch
What we deliver
OAuth 2.0 authorization code with PKCE for EHR launch security
EHR launch context parameter handling (patient, encounter, user)
Hyperspace-embedded provider workflow integration
MyChart-launched patient-facing app contexts
Standalone backend-services apps for population health
03/06 Application · security review · marketplace
Epic Vendor Services & Showroom publishing
Navigate Epic's Vendor Services review and Showroom listing process to publish your application in the marketplace. We guide you through the application questionnaire, security review, and technical validation steps that Epic requires. From initial submission through ongoing compliance, we manage the entire publishing lifecycle so your app reaches Epic's customer network.
Showroom
Vendor Services
Security review
Marketplace
What we deliver
Application questionnaire preparation aligned to Epic reviewer expectations
Build patient-facing integrations with MyChart including appointment scheduling, secure messaging, health record access, and proxy workflows. We implement MyChart OAuth 2.0 for patient authorization, connect third-party portals and mobile apps to MyChart data, and align with the current USCDI version for patient-facing data elements. MyChart integrations let you extend the patient experience beyond Epic's native portal.
Configure Epic Bridges interfaces for HL7 v2 ADT, ORM, ORU, and SIU message flows alongside Interconnect web services for SOAP and REST-based integrations. We build custom data flows between Epic and ancillary systems including labs, radiology, pharmacy, and medical devices. Our team handles Bridges configuration, message mapping, and Interconnect service deployment across Epic environments.
Migrate data from legacy EHR systems to Epic with comprehensive validation, terminology mapping, and reconciliation workflows. We support full go-live readiness including interface activation sequencing, data validation scripts, and parallel testing against production Epic environments. Post-go-live, we provide stabilization support to ensure all integrations are processing messages correctly and clinical workflows are uninterrupted.
Schema mapping
LOINC · RxNorm · SNOMED
Cutover
Stabilization
What we deliver
Legacy EHR data extraction with field-level validation
Epic AI Integration — Scribes, CDS Hooks, Showroom
Production AI deployments inside Epic — ambient scribes via SMART on FHIR, CDS Hooks services with sub-500ms response budgets, and Showroom publishing for AI vendor apps. We bridge the gap between what AI vendors ship and what Epic-side configuration demands.
Click to expand
Pattern 1 / 3
Ambient Scribes via SMART on FHIR
Launch ambient AI scribes (Abridge, Suki, Nuance DAX, Ambience) inside Hyperspace via SMART on FHIR. We handle OAuth context, transcript-to-DocumentReference writeback, Haiku & Canto mobile launch, and the Epic-side configuration that vendors don't deliver out of the box.
SMART on FHIR
DocumentReference
Abridge / Suki / DAX
Hyperspace · Haiku
Click to expand
Pattern 2 / 3
CDS Hooks Service
Build CDS Hooks services that fire on order-sign, patient-view, medication-prescribe, and other Epic-supported hooks. We design the Card response shape, latency budget (under 500ms for chart-open hooks), and SMART app launch path for full-UI follow-ups beyond what a Card can express.
CDS Hooks
order-sign
patient-view
< 500ms response
Click to expand
Pattern 3 / 3
Showroom Publishing for AI Vendors
Get your AI app through Epic Vendor Services review and into the Showroom listing. We shepherd the application questionnaire, security audit, technical scope, and compliance attestation — then handle the customer-facing technical onboarding once you're listed and selling into Epic shops.
Vendor Services
Showroom listing
Security review
Compliance attestation
Integration Architecture
Choosing the Right Epic Integration Path
Epic offers four primary integration methods — each designed for different use cases, data requirements, and system architectures. Choosing the right approach is the first and most important decision in any Epic integration project.
FHIR R4 APIs
REST/HTTPS, JSON
Epic Bridges
HL7 v2 lab orders/results (Epic Beaker), TCP/MLLP
Epic Interconnect API
SOAP/REST API, Custom web services
Care Everywhere
IHE/FHIR, Cross-org
Epic integration methods compared — most new projects start with FHIR R4 unless specific HL7 v2 requirements exist.
Feature
FHIR R4 APIs
Epic Bridges
Epic Interconnect API
Care Everywhere
Protocol
REST/HTTPS
TCP/MLLP
SOAP or REST
IHE XCA/XCPD + FHIR
Data Format
FHIR JSON (R4)
HL7 v2 pipes
XML or JSON
CDA/FHIR bundles
Auth Model
OAuth 2.0 + PKCE
VPN + certificates
API key or cert
Certificate-based trust
Best For
SMART apps, patient access, clinical queries
ADT feeds, Beaker lab orders/results, scheduling
Custom web services, legacy system calls
Cross-org data sharing, record queries
Epic Direction
Primary — actively expanding
Stable — essential for operations
Niche — specific use cases
Growing — TEFCA adoption
Typical Timeline
6–10 weeks
4–8 weeks per interface
4–6 weeks
Varies by network
In practice, most Epic integrations combine these methods. A digital health vendor might use the Epic FHIR R4 Connector for a new patient-facing app while maintaining HL7 v2 interfaces through Bridges for existing lab orders/results (Beaker), ADT, and scheduling feeds. Our team helps you choose the right Epic FHIR R4 integration architecture for your specific use case and environment.
Technical Expertise
SMART on FHIR Launch Sequence
Every Epic FHIR integration follows the SMART App Launch framework — the industry-standard OAuth 2.0 authorization pattern for clinical applications. Understanding this five-step sequence is critical for any application that reads or writes data within an Epic EHR environment.
Phase 1: Launch
The app is launched from Epic Hyperspace, MyChart, or a standalone context. Epic passes an iss parameter identifying the FHIR server and a launch token encoding the clinical context — including the current patient, encounter, and user. For EHR launch, the app receives this context from the embedding frame; for standalone launch, the app initiates the flow directly with the FHIR server’s authorization endpoint.
Epic Ecosystem
Inside the Epic Platform
Beyond the core integration APIs, Epic's platform includes marketplaces, health information exchange networks, data analytics tools, and clinical modules like Beaker that shape how third-party applications connect and deliver value.
Publishing Applications on Epic Showroom
Epic Showroom (formerly App Orchard) is Epic's marketplace where third-party applications are listed for Epic customer organizations to discover, evaluate, and activate. Getting listed requires navigating Epic's multi-stage review process — and the requirements depend on which marketplace tier your application targets.
Epic organizes Showroom into three tiers: Connection Hub for data integrations and system connections, Toolbox for clinical tools and workflow applications, and Workshop for enterprise-level integrations and analytics platforms. Each tier has different technical requirements, security review depth, and compliance expectations.
The listing process typically takes 8 to 16 weeks and follows a structured path: application questionnaire, technical security review, FHIR API compliance validation, and ongoing adherence to Epic's connection hub policies. Once listed, applications must pass periodic recertification reviews as Epic updates its security and interoperability requirements.
Saga IT guides vendors through the entire Showroom submission lifecycle — from initial scope negotiation and application questionnaire preparation through security review responses and production certification. We handle the technical details so your team can focus on building a great product.
Epic Care Everywhere & Health Information Exchange
Care Everywhere is Epic's health information exchange network that enables clinical data sharing between Epic organizations and external health systems. When a patient presents at a facility, Care Everywhere automatically queries connected organizations for available records — returning clinical summaries, medication histories, allergies, and recent encounter data in real time.
Care Everywhere uses IHE profiles (XCA, XCPD) and FHIR APIs to facilitate patient record queries, care document exchange, and event notifications across organizational boundaries. For non-Epic organizations, Care Everywhere connects through Carequality, CommonWell Health Alliance, and TEFCA networks to enable cross-platform interoperability — making it one of the largest health data exchange networks in the United States.
Saga IT helps healthcare organizations optimize their Care Everywhere configuration, troubleshoot query failures, and integrate Care Everywhere data flows with downstream clinical and analytics systems. For organizations building health information exchange strategies, Care Everywhere is often the starting point for cross-organizational data sharing.
Epic Cosmos Data Platform
Epic Cosmos is Epic's de-identified real-world data platform that aggregates clinical data from across the Epic ecosystem — representing more than 280 million patients across Epic organizations worldwide. Cosmos powers research analytics, clinical benchmarking, and population health insights using de-identified data that preserves patient privacy while enabling large-scale analysis.
Organizations use Cosmos for clinical trial feasibility, population health research, outcomes analysis, and AI model training. The platform provides access to longitudinal patient records across demographics, diagnoses, procedures, medications, and lab results — making it one of the largest clinical data repositories available for healthcare research.
For organizations working with Cosmos data, integration typically involves data extraction pipelines, research data network connectivity, and analytics platform integrations. As Epic expands Cosmos capabilities and more organizations contribute data, the platform is becoming increasingly central to healthcare research infrastructure and real-world evidence generation.
Epic Beaker — Laboratory Information System
Epic Beaker is Epic's laboratory information system (LIS) module — the clinical workflow engine where lab orders are placed, results are received, and the order-to-result lifecycle is managed inside the Epic environment. Beaker covers both clinical pathology (chemistry, hematology, microbiology) and anatomic pathology (surgical specimens, cytology), and is the source-of-truth for lab data inside any Epic-using organization.
Epic Beaker integration almost always means HL7 v2 interfaces through Bridges — ORM (Order Message) feeds going outbound from Beaker to external LIS, reference labs, or analyzer middleware, and ORU (Observation Result) feeds coming back with results that post into the patient chart. For high-volume labs these ORM/ORU streams run continuously, and any delay or malformed message immediately surfaces as a clinician-visible problem.
Saga IT builds and maintains Epic Beaker HL7 integrations across hospital and reference-lab settings — new lab-vendor onboarding, instrument-middleware connectivity, order-entry workflow validation, result-routing logic, downtime handling, and bidirectional ADT reconciliation. We also help organizations migrating off legacy LIS systems plan and execute the lab-data cutover into Beaker.
Epic Programs
Epic Connect & Epic EHR Consulting
Beyond FHIR APIs and Bridges interfaces, Saga IT advises on Epic's connectivity programs — Epic Connect (community connect / hosted Epic) and the broader Epic EHR consulting work that goes alongside an integration build.
Community Connect · hosted Epic · affiliate routing
Epic Connect Platform
Epic Connect (Epic's hosted / community-connect program) lets affiliate hospitals, ambulatory practices, and specialty groups run on a host system's Epic instance rather than standing up their own. We advise affiliates on the integration touchpoints that survive the Connect arrangement — interface boundaries, Bridges-vs-Connect routing, identity management across hosting boundaries, and the SMART on FHIR app paths that work cleanly inside a Connect tenant.
Community Connect
Hosted Epic
Bridges routing
SMART on FHIR
Showroom · Vendor Services · release planning
Epic EHR Consulting Services
Epic EHR consulting that wraps the technical integration work — Showroom (App Orchard) program strategy, Vendor Services contract evaluation, Epic Vendor Services release-cycle planning, and the organizational change-management pieces that make external integrations stick at large Epic sites. We bring deep working knowledge of the Epic ecosystem — App Orchard (now Showroom), Hyperspace deployment, Caboodle reporting, Cogito analytics, Bridges middleware — without being a generalist Epic implementation partner.
Showroom (App Orchard)
Vendor Services
Hyperspace
Caboodle · Cogito
Case Studies
Epic Integration in Action
Real-world Epic integrations — from SMART on FHIR apps embedded in Hyperspace to bedside devices streaming through Bridges, to AI-driven CDS Hooks.
SMART on FHIR DME Ordering Inside Epic
A durable medical equipment vendor launching its ordering app directly inside Epic Hyperspace via SMART on FHIR — clinicians select equipment from the patient's encounter context, the app pulls diagnoses and demographics through Epic's FHIR R4 APIs, and orders post back as DeviceRequest resources without ever leaving the chart.
Epic Hyperspace
// SMART launch from chart GET /smart/launch? iss=https://fhir.epic.com launch=eyJhbGciOi…
OAuth + FHIR Read
// Token + patient context GET /Patient/{id} GET /Condition?patient=… GET /Coverage?patient=…
DeviceRequest Posted
ICU Ventilator Streaming into Epic via HL7 v2
A bedside ventilator publishing real-time respiratory metrics every minute via HL7 v2 ORU^R01 messages — a Mirth Connect channel transforms device-specific OBX segments into Epic Bridges interface format and writes flowsheet rows to the right patient encounter automatically.
Ventilator
// ORU^R01 · every 60s OBX|1|NM|76270-8^TidalVol||450|mL OBX|2|NM|76271-6^RR||14|/min OBX|3|NM|19994-3^FiO2||0.40
A clinical decision support service triggered by Epic's order-sign hook — when a clinician signs an order set, Epic posts patient context to an external CDS service, an AI model evaluates sepsis risk against current vitals and labs, and the response renders as an inline card inside Epic with a recommended action.
order-sign Hook
// order-sign → CDS service POST /cds-services/sepsis-risk "context": { patient, draftOrders }
Epic integration projects typically cost $30,000 to $250,000+, depending on integration type and scope. A standalone Epic Showroom (formerly App Orchard) application certification — including SMART on FHIR launch, security review, and Marketplace submission — runs $30K to $80K. Bidirectional Epic FHIR R4 integrations with custom workflows fall in the $75K to $250K range. Enterprise-wide Epic Bridges work (multi-interface HL7 v2 deployments, Care Everywhere extensions, custom MyChart integration) can exceed $500K. Key cost drivers: number of Epic instances, Vendor Services tier required, sandbox availability, hospital site participation, and whether the project requires Epic Hyperspace customization. Contact our Epic team for a scoped estimate.
Epic integration services encompass the design, development, testing, and deployment of technical connections between Epic's EHR platform and external systems. This includes building FHIR R4 APIs for clinical data exchange, developing SMART on FHIR applications that run within Epic Hyperspace, configuring HL7 v2 interfaces through Epic Bridges, and publishing applications to Epic Showroom (formerly App Orchard). Integration partners like Saga IT handle the full lifecycle — from initial scope definition and sandbox development through Epic's security review and production go-live.
SMART on FHIR is an open standard that defines how third-party applications securely launch within an EHR and access clinical data via FHIR APIs. With Epic, the process follows a four-step OAuth 2.0 flow: the app launches from Hyperspace or MyChart with clinical context, redirects to Epic's authorization server to request data scopes, exchanges an authorization code for an access token, and then queries Epic's FHIR R4 endpoint with that token. Epic enforces strict scope validation against the app’s Vendor Services registration, and all SMART apps must pass Epic's security review before production deployment.
Epic Showroom (formerly App Orchard) is Epic's marketplace where third-party applications, built through the Epic Vendor Services developer program, are listed for Epic customer organizations to discover and activate. Getting listed requires completing Epic's application questionnaire, passing a technical security review, demonstrating FHIR API compliance, and meeting Epic's policies for data handling and privacy. The review process typically takes 8 to 16 weeks depending on application complexity and the scope of FHIR resources accessed. Saga IT guides vendors through the entire submission lifecycle, from initial application through ongoing compliance with Epic's recertification requirements.
Timeline depends on the integration type and complexity. A straightforward FHIR R4 API integration with read-only patient data access can be completed in 6 to 10 weeks, including sandbox development, testing, and Epic certification. SMART on FHIR applications with bidirectional data exchange typically take 12 to 20 weeks. Full Showroom listing through Epic Vendor Services adds 8 to 16 weeks for Epic's review process. HL7 v2 interface development through Epic Bridges generally takes 4 to 8 weeks per interface. Data migration projects for Epic go-lives vary significantly based on the source system and data volume, but typically span 3 to 6 months.
HL7 v2 is a legacy messaging standard that uses pipe-delimited segments transmitted over TCP/MLLP connections — it has been the backbone of healthcare integration for 30 years and remains essential for ADT feeds, lab orders, and results. Epic FHIR R4 is a modern RESTful API standard using JSON resources over HTTPS, designed for web and mobile application development. FHIR R4 supports fine-grained resource access with OAuth 2.0 security, while HL7 v2 operates on a push-based event model. Most Epic environments use both: FHIR R4 for new application integrations and SMART apps, and HL7 v2 for high-volume, real-time clinical message flows through Epic Bridges.
Saga IT has extensive experience building and certifying integrations within Epic's ecosystem, including FHIR R4 API development, SMART on FHIR application deployment, and Epic Vendor Services / Showroom listing support. Our team has delivered hundreds of Epic integrations across health systems of varying size, from community hospitals to large academic medical centers. We are deeply familiar with Epic's security review process, vendor certification policies, and the technical requirements for production FHIR and HL7 v2 connectivity. We work as your integration partner to navigate Epic's certification requirements and ensure your application meets all of Epic's standards for production deployment.
Epic Care Everywhere is Epic's health information exchange network that enables clinical data sharing between Epic organizations and external health systems through Carequality, CommonWell, and TEFCA. Saga IT helps healthcare organizations optimize Care Everywhere configuration, troubleshoot query failures, and integrate exchange data with clinical and analytics workflows.
The United States Core Data for Interoperability (USCDI) is a standardized set of health data classes and elements required for interoperable exchange under the 21st Century Cures Act. USCDI v6 (finalized July 2025) is the current published version, and USCDI v7 is in draft. Each successive version expands the required data elements — adding things like additional clinical notes, social determinants of health, treatment plans, and health insurance information. For Epic integrations, this means FHIR R4 APIs must support a broader set of resources and data elements in their responses, particularly for patient access and provider directory use cases. Epic updates its FHIR API surface to align with each USCDI version, so applications built on Epic's FHIR endpoints need to handle the expanded data set and conform to updated US Core FHIR profiles.
From Epic consulting and roadmap scoping to FHIR API development and Showroom publishing — tell us where you are in the Epic journey and we'll scope the work.
Book a 30-min call · or email us and we'll reply within one business day.
Intent
Details
Contact
We use cookies to improve your experience and analyze site usage.
Privacy Policy
By accepting, you allow analytics and advertising cookies — including
HubSpot (CRM and visitor analytics) and Google Ads (advertising and
remarketing tags) — to help us understand how visitors use the site
and to deliver relevant advertising. See our
Privacy Policy for details. Choose "Deny" to
keep only essential cookies.
Book a Consultation
Reviewing your request…
Pick a time that works
Your request looks like a great fit for a 30-minute call. Choose a slot below
and you'll get a confirmation by email.
Thanks — we'll be in touch
We've received your request and our team will review it shortly. You'll get
a personal reply within one business day.
Thanks for reaching out
We've received your request and will follow up if it's a fit. In the meantime,
these resources might help:
We couldn't process your request right now. Please try again, or email us at
info@saga-it.com.
Your Privacy Choices
Stop your contact information from being used in advertising audiences.
Enter the email you used when you contacted Saga IT.
You're opted out.
We've recorded your request. You'll be removed from advertising
audiences within 24 hours.
We don't sell personal information. We do "share" hashed contact info
with Google Ads for Customer Match. Opting out removes you from that
audience within ~24h. To request full deletion of your data, email
info@saga-it.com.