An Architectural Deep Dive into the Epic Electronic Health

Record System
I. Introduction to the Epic EHR Ecosystem
Epic Systems Corporation, founded in 1979, stands as a dominant force in the
healthcare information technology landscape, providing a comprehensive Electronic
Health Record (EHR) system.1 Its software is integral to the operations of numerous
large healthcare organizations, academic medical centers, community hospitals, and
various other care settings globally.1 As of 2022, Epic's software managed the
electronic records for 78% of patients in the United States and over 3% of patients
worldwide.2 The system is designed to centralize patient data, streamline clinical and
administrative workflows, enhance collaboration among care providers, and support
data-driven decision-making, ultimately aiming to improve patient care and
operational efficiency.4

The Epic platform is renowned for its integrated suite of applications that cover
nearly every facet of patient care, from appointment scheduling and clinical
documentation to billing, revenue cycle management, and advanced analytics.2 Its
popularity among healthcare providers stems from its scalability, comprehensive
feature set, commitment to data security, and robust interoperability capabilities.4
However, the system's complexity and the cost associated with customization and
implementation are also notable considerations.4

This report provides a detailed tutorial on the architecture of the Epic EHR system. It
aims to elucidate the core architectural layers and components, including its unique
database structure, application server technologies, user interface elements, modular
design, and interoperability framework. By exploring these facets, this report will
illuminate how data flows through the Epic system from start to finish, offering a
clearer understanding of its intricate yet powerful design.

II. Core Database Architecture: The Foundation of Epic

The entire Epic software suite is fundamentally centered around its database
management system, which is architected to handle the massive volume and
complexity of healthcare data in real-time while also supporting extensive analytical
and reporting needs.2 This architecture involves several distinct but interconnected
data stores, each optimized for specific functions. The primary database
technologies have evolved from InterSystems Caché to the more modern
InterSystems IRIS Data Platform, both of which are built upon the MUMPS
(Massachusetts General Hospital Utility Multi-Programming System) language and its
derivatives like Caché ObjectScript.2

A. Chronicles: The Real-Time Transactional Database

Chronicles is the heart of the Epic system—a real-time, hierarchical database
management system where all patient data and transactional information are initially
entered and stored.2 When a user interacts with an Epic application, such as
documenting a patient encounter or placing an order, the data is immediately written
to Chronicles and becomes instantly available across the system.2 This database is
specifically designed for the high-volume, concurrent access demands of healthcare
environments.12

Each application within Epic leverages a unified data model within Chronicles,
ensuring consistency in how data is imported, structured, managed, and exported.12
Chronicles is organized into master files (INI), records, contacts (date-specific
snapshots of data within a record), and items (individual data points, akin to fields in a
relational database).13 This structure, while different from traditional relational
databases, is highly optimized for the complex, evolving nature of patient medical
histories where data is often time-sensitive and context-dependent. The hierarchical
nature allows for efficient storage and retrieval of sparse data, which is common in
healthcare records.10

The direct, real-time availability of data in Chronicles is paramount for clinical

decision-making and operational workflows. For instance, when a clinician documents
a new allergy for a patient, that information is instantly accessible to the pharmacy
module to prevent adverse drug events, and to any other clinician viewing that
patient's chart. This immediate consistency is a cornerstone of Epic's integrated
design.

B. Clarity: The Relational Reporting Database

While Chronicles excels at real-time transactions, its hierarchical structure is not
optimal for complex analytical queries or large-scale reporting that often require
joining data across many different domains. To address this, Epic employs Clarity, a
secondary database that stores a vast subset of the data from Chronicles.2 Clarity is
typically built on a relational database platform, commonly Microsoft SQL Server or
Oracle.14
Data is transferred from Chronicles to Clarity through a nightly process called ETL
(Extract, Transform, Load).14 During this process, data is extracted from Chronicles,
transformed to fit the relational schema of Clarity (which comprises over 18,000
tables in some implementations 14), and then loaded into the Clarity database. This
ETL process ensures that the relationships mapped in Chronicles are preserved in the
relational structure of Clarity.19

Because the ETL process typically runs overnight (e.g., from midnight to early
morning), Clarity data is always one day behind the real-time data in Chronicles.14 This
slight delay is acceptable for most analytical reporting, as it allows complex, data-
intensive queries to be run against Clarity without impacting the performance of the
live, user-facing Chronicles environment.14 Clarity is the primary source for many
standard and custom reports, business intelligence applications, and data extracts
needed for research or regulatory reporting.9 The separation of the operational
transaction processing system (Chronicles) from the analytical reporting system
(Clarity) is a critical architectural decision. This design prevents resource-intensive
analytical queries from slowing down the primary EHR system, which must remain
highly responsive for patient care activities. This bifurcation ensures that clinicians
experience consistent performance in their daily workflows, while analysts and
researchers can still perform deep dives into historical data.

C. Caboodle: The Enterprise Data Warehouse (EDW)

Beyond Clarity, Epic offers Caboodle (also referred to as part of Cogito Analytics,
Epic's overall analytics environment), which serves as an enterprise data warehouse
(EDW) platform.2 Caboodle takes data primarily from Clarity (and potentially other
non-Epic sources) and further organizes it into a standardized healthcare data model
optimized for even more advanced analytics, business intelligence, and self-service
reporting tools like SlicerDicer.2

The architecture of Caboodle often includes a staging database where data

extracted from sources like Clarity is transformed, and a reporting database where
the transformed data is presented to users.19 This movement of data is typically
managed by SQL Server Integration Services (SSIS) packages.19 Caboodle comes pre-
packaged with hundreds of integrated tables and thousands of data fields, and it can
be extended and customized to incorporate data from various systems across a
healthcare organization, including patient experience data (e.g., Press Ganey
surveys), cost accounting data, and claims data from payers.21
Caboodle's data model is designed to be more user-friendly for analytics than the
raw Clarity structure, often employing star schemas and other dimensional modeling
techniques to simplify querying and improve performance for analytical tools.19 Like
Clarity, Caboodle data is typically updated nightly, meaning it also reflects a one-day
delay from the live Chronicles data.20 The key distinction is that Caboodle is
specifically structured for business intelligence and analytics, often integrating data
from multiple sources beyond just Epic, whereas Clarity is more of a direct relational
replica of Epic's operational data.20 This makes Caboodle a more comprehensive
platform for enterprise-level analytics and population health management. The
development of Caboodle signifies an understanding that while Clarity provides a
necessary relational copy of Epic data, a true enterprise data warehouse requires
further transformation, integration with non-Epic data, and a data model specifically
optimized for complex analytical querying and business intelligence tools. This
layered approach—Chronicles for real-time, Clarity for operational reporting, and
Caboodle for enterprise analytics—allows Epic to cater to a wide spectrum of data
needs without compromising the performance of the core transactional system.

D. Underlying Database Technology: InterSystems Caché and IRIS

Epic's core database, Chronicles, is built on InterSystems' data platform technology—
historically Caché, and more recently, InterSystems IRIS.2 InterSystems IRIS is a multi-
model database, meaning it can handle data as tables, objects, documents, and
multidimensional arrays, all within a unified engine.7 This is particularly well-suited for
healthcare data, which is often complex and doesn't always fit neatly into traditional
relational structures. The technology is an evolution of the MUMPS programming
language, which is known for its extremely efficient string manipulation and
hierarchical data storage capabilities.10

Epic utilizes a specialized version of Caché/IRIS, significantly modified and

customized to meet the specific needs of healthcare organizations and to integrate
tightly with Epic's software.7 This tailored version provides rapid Key-Based SQL (KB-
SQL) access and simplifies database administration processes.7 Key features of the
InterSystems platform leveraged by Epic include:
● High Performance and Scalability: Optimized for high-volume transaction
processing and capable of scaling to support the largest healthcare enterprises,
managing millions of transactions per day.7
● Reliability and Availability: Features like database mirroring provide 1:1 data
parity and support effective disaster recovery.7 Advanced journaling minimizes
 recovery times from system failures.24
● Security: Robust security features, including comprehensive encryption, security
auditing, and smart authorization tools, are integral to the platform.7
● Distributed Systems Support: The platform supports distributed systems
across several networked servers, often using InterSystems Enterprise Caché
Protocol (ECP), enhancing performance and scalability.7

The choice of InterSystems technology for the core database is a defining

characteristic of Epic's architecture. While MUMPS-based systems are less common
outside of healthcare, their historical strengths in handling complex, hierarchical data
structures with high transactional throughput have made them a persistent and
powerful foundation for major EHRs like Epic. The continued evolution with IRIS brings
modern capabilities while retaining these core strengths.

The following table summarizes the key characteristics of Epic's primary data stores:

Table 1: Epic Data Stores Overview

Feature Chronicles Clarity Caboodle (Cogito)

Primary Purpose Real-time Relational reporting, Enterprise Data

transactional operational analytics Warehouse (EDW),
processing (OLTP) (OLAP) advanced analytics,
BI

Data Structure Hierarchical Relational (SQL- Relational,

(MUMPS-based) based) Dimensional (Star
Schema, etc.),
optimized for
analytics

Underlying Tech InterSystems MS SQL Server, MS SQL Server (often

IRIS/Caché Oracle with SSIS for ETL)

Data Latency Real-time Typically 24-hour Typically 24-hour

delay (nightly ETL delay (nightly ETL
from Chronicles) 14 from Clarity/other
 sources) 20

Primary Users Clinicians, Report writers, BI developers, data

administrative staff analysts, researchers scientists, analysts,
(via Hyperspace) business users (via
SlicerDicer)

Key Benefit Instant data Complex reporting Integrated enterprise

availability for patient without impacting view, self-service
care production system analytics, data
performance 16 visualization 21

III. Application Server Architecture: Processing the Logic

Between the user interface and the core database lies the application server layer.
These servers are responsible for executing the business logic of the Epic system,
managing database queries, processing transactions, and enforcing the rules and
workflows defined within the myriad Epic applications.17

A. Role and Function of Application Servers

Application servers in the Epic environment act as the intermediary between the
Hyperspace clients (and other access points like mobile apps or interfaces) and the
Chronicles database server.17 When a user performs an action in Hyperspace, such as
saving a clinical note or submitting an order, the request is sent to an application
server. The application server then processes this request, which may involve:
● Validating the input data.
● Executing relevant business rules (e.g., checking for drug interactions, verifying
insurance eligibility).
● Querying the Chronicles database for necessary information.
● Writing new or updated data back to Chronicles.
● Sending a response back to the client application.

For most Epic software environments, a symmetric multiprocessor (SMP) architecture

in a single database server, coupled with application servers, is sufficient to handle
the load.17 However, for very large deployments, a more distributed model is
employed.

B. Core Technologies (MUMPS/Caché ObjectScript,.NET/C# for Integrations)

The primary programming language for developing the core application logic that
interacts directly with the Chronicles database is Caché ObjectScript, an advanced
object-oriented language that is an extension of MUMPS.3 This language is tightly
integrated with the InterSystems IRIS/Caché data platform, allowing for highly
efficient data access and manipulation.

While the core is MUMPS/Caché ObjectScript-based, Epic also supports more

common programming languages like.NET (C#) and JavaScript, particularly for
integrations with external systems and potentially for developing newer modules or
service layers.3 For instance, APIs exposed by Epic, such as FHIR APIs, might have
service layers or wrappers developed in these languages to facilitate easier
interaction for third-party developers. This pragmatic approach allows Epic to
maintain its high-performance, specialized core while leveraging a wider pool of
development talent and more contemporary tools for specific components and
integration points. This hybrid language strategy is a practical way to evolve a long-
standing, specialized system, enabling easier connection with external systems and
potentially faster development cycles for certain new functionalities.

C. InterSystems Enterprise Caché Protocol (ECP) for Scalability

For large-scale Epic deployments, InterSystems' Enterprise Caché Protocol (ECP) is a
critical technology for achieving scalability.7 ECP is a networking protocol that allows
application servers (ECP clients) to access data residing on one or more remote
database servers (ECP data servers) as if the data were stored locally.24 This enables
a distributed architecture where the application processing load can be spread
across multiple application servers, all connecting to a central (or clustered) set of
database servers.

ECP effectively allows for horizontal scaling of the application tier. Instead of relying
solely on making a single database server more powerful (vertical scaling),
organizations can add more application servers to handle increasing user loads and
transaction volumes.7 This architecture is vital for supporting the massive transaction
volumes seen in large healthcare systems, enabling Epic to manage millions of daily
healthcare transactions reliably.24 The use of ECP signifies a sophisticated approach
to scalability, offering better resilience and more granular control over resource
allocation compared to simply relying on a monolithic database server. It allows
processing power to be scaled out incrementally, which can be more cost-effective
and flexible at extreme scales. However, this also underscores the critical importance
of high-performance, low-latency network connectivity between the application
servers and the database servers in an ECP-enabled environment. Modern
infrastructure practices, such as treating ECP servers as virtualized resources that
can be added to a pool, align with this scalable design.26

IV. User Interface and Interaction Layer

The user interface and interaction layer is how healthcare providers, administrative
staff, and patients connect with the Epic system. Epic provides a range of client
applications tailored to different user roles and access needs, all designed to present
information and facilitate workflows efficiently.

A. Hyperspace: The Primary Epic Client

Hyperspace is the flagship client application for the Epic EHR system, serving as the
integrated platform that hosts the majority of Epic's applications and modules.9 It is
the primary interface through which clinicians and administrative staff perform their
daily tasks, including clinical documentation, order entry, results review, scheduling,
and billing.6

Architecturally, Hyperspace functions as a client that connects to the backend Epic

application and database servers (Chronicles/IRIS).29 Traditionally, Hyperspace has
been a Windows-based application, often delivered to end-users via direct
installation on PCs or through client virtualization technologies like Citrix Virtual Apps
and Desktops or VMware Horizon View.29 These virtualization solutions allow for
centralized management of the Hyperspace application and enable access from a
variety of endpoint devices, including thin clients and zero clients, which can reduce
desktop management overhead and enhance security.29

More recently, Epic has expanded access options for Hyperspace. There is now a
"new web-based platform" for accessing Epic, and a native macOS Hyperspace
application has been introduced, offering users on Apple hardware a more seamless
experience without the need for virtualization layers.27 This native Mac application has
been noted for its speed and for avoiding the "friction" sometimes associated with
virtualized connections.31

A key characteristic of Hyperspace is its extensive role-based customization.9 The

user interface, available activities, and workflows are tailored based on the user's
specific role within the healthcare organization (e.g., physician, nurse, pharmacist,
scheduler, biller).13 This customization is managed through profiles (often referred to
by their INI, LPR) and security classes (ECL), which control access to specific
functionalities (security points).13 While this high degree of configurability is powerful
for adapting the system to diverse user needs and complex organizational structures,
it also introduces considerable complexity in system setup, administration, and
maintenance. Incorrectly configured profiles or security settings can impede user
workflows or, conversely, grant inappropriate access, potentially leading to
inefficiencies or compliance risks. This necessitates significant investment in
specialized Epic analysts and meticulous planning of user roles, profiles, and security
configurations. The evolution towards native Mac and web-based Hyperspace clients
indicates Epic's adaptation to a more diverse end-user device landscape and a
strategic move to enhance accessibility and user satisfaction, potentially reducing
reliance on virtualization for certain user groups. However, this also presents the
challenge of maintaining feature parity and consistent performance across an
increasing number of client platforms.

B. Mobile Access: Extending Epic's Reach

Recognizing the need for clinicians to access patient information and perform tasks
on the go, Epic offers a suite of mobile applications:
● Haiku: Designed for physicians, Haiku is available on smartphones (iOS and
Android).28 It provides access to patient charts, schedules, secure messaging,
and the ability to place certain types of orders and review results.
● Canto: Tailored for physicians using tablets (primarily iPads), Canto offers more
comprehensive functionality than Haiku, leveraging the larger screen real estate
for more detailed views and interactions.28
● Rover: Aimed at nursing staff, phlebotomists, and other ancillary clinical roles,
Rover runs on mobile devices and supports point-of-care workflows.28 Common
uses include barcode medication administration (BCMA) in conjunction with the
Willow module, specimen collection with Beaker, and clinical documentation
directly at the bedside.33

The development of these role-specific mobile applications—Haiku and Canto

focusing on physician information access and decision support, Rover on task-based
nursing and ancillary activities—demonstrates an understanding that a one-size-fits-
all mobile EHR app would be suboptimal. This targeted approach enhances the
usability and adoption of mobile tools by aligning them closely with the distinct
workflow needs of different clinical users. While this specialization likely leads to
better-designed apps for each group, it also entails the development and ongoing
maintenance of multiple distinct mobile codebases and applications.
C. MyChart: The Patient Portal
MyChart is Epic's comprehensive patient portal, designed to engage patients in their
own healthcare management.4 It is accessible via web browsers and dedicated native
mobile applications for iOS and Android devices.32 Key functionalities of MyChart
include:
● Access to Health Records: Patients can view their medical history, lab and test
results, medication lists, allergies, and immunization records.6
● Appointment Management: Patients can schedule, view, and sometimes cancel
appointments.4
● Secure Communication: Patients can send secure messages to their healthcare
providers.6
● Prescription Refills: Patients can request refills for their medications.35
● Bill Pay: Patients can view their medical bills and make payments online.36
● Pre-Visit Tasks: Patients can often complete pre-registration tasks, such as
updating demographic information, insurance details, and health questionnaires,
before their appointments.38

MyChart is tightly integrated with the core Epic EHR system. Data is pulled from
Chronicles in real-time or near real-time for display in MyChart, and information
entered by patients (e.g., questionnaire responses, demographic updates) can flow
back into their electronic health record.42 A significant aspect of MyChart's
functionality, driven by regulations such as the 21st Century Cures Act, is the often
immediate release of test results to patients as soon as they are finalized in the Epic
system.39 This means patients may see their results before their provider has had a
chance to review them personally.39 This shift towards greater information
transparency has profound implications. Architecturally, it requires robust,
automated, and reliable pathways for results to flow from the source systems (e.g.,
Beaker for lab results, Radiant for imaging reports) through Chronicles and out to
MyChart with minimal delay. It also necessitates carefully designed workflows for
managing exceptions, such as results that clinicians may wish to review with the
patient before they are released, and clear presentation of results to patients who
may lack medical expertise for interpretation. This change fundamentally alters
patient-provider communication dynamics and requires healthcare organizations to
proactively educate patients and manage expectations regarding result availability
and interpretation.

The following table provides a comparative overview of Epic's main client access
points:

Table 2: Epic Client Access Points

Client Primary User Typical Key Connectivity

Application Group Device(s) Functionality
Examples

Hyperspace Clinicians Desktops Clinical Direct network

(physicians, (Windows, documentation, to Epic servers;
nurses, etc.), macOS), CPOE, results often via
Admin Staff Laptops review, Citrix/VMware
scheduling, virtualization 29
billing, reporting
9

MyChart Patients Web Browsers, View Internet via

Smartphones records/results, secure APIs to
(iOS/Android), schedule Epic servers
Tablets appointments,
message
providers, pay
bills, pre-visit
tasks 36

Haiku Physicians Smartphones Chart review, Secure

(iOS/Android) messaging, connection
scheduling, light (often via Wi-
order entry, Fi/cellular) to
results 28 Epic servers

Canto Physicians Tablets (iPad) More Secure

comprehensive connection
chart review (often via Wi-
and Fi/cellular) to
documentation Epic servers
than Haiku,
messaging,
 orders 28

Rover Nurses, Mobile Devices Barcode Secure

Phlebotomists, (often medication connection
other clinical specialized) admin (BCMA), (often Wi-Fi) to
support staff specimen Epic servers
collection, vitals,
point-of-care
documentation
28

EpicCare Link External/ Web Browsers View patient Secure web

Referring charts (shared portal access to
Providers by Epic a subset of Epic
organization), data
place referral
orders, receive
notifications 44

V. Modular Design: How Applications Fit In

Epic's EHR system is not a monolithic entity but rather a sophisticated suite of
interconnected applications or "modules." Each module is designed to address the
specific needs of a particular department, clinical specialty, or functional area within
a healthcare organization.7 This modular architecture allows healthcare institutions to
implement and customize the components that best align with their operational
requirements and strategic goals, providing a degree of flexibility and scalability.3

A. Overview of Epic's Modular Structure

The extensive array of Epic modules can be broadly categorized, although many
modules have cross-cutting functionalities and tight integrations. Key categories and
prominent examples include:
● Clinical Core Modules: These form the foundation for patient care
documentation and management.
○ EpicCare Inpatient (ClinDoc): The primary module for hospital-based care,
encompassing clinical documentation by nurses and other staff, care plan
development, medication administration records (MAR), and discharge
planning.35
 ○ EpicCare Ambulatory: Tailored for outpatient clinic settings, this module
supports visit documentation, physician order entry, e-prescribing, and
management of patient problems, allergies, and medications for non-
admitted patients.35
○ ASAP: Designed for the fast-paced environment of the Emergency
Department, ASAP facilitates patient tracking, triage, ED-specific
documentation, and order management.22
● Ancillary and Specialty Clinical Modules: These cater to specific diagnostic,
therapeutic, or specialty areas.
○ Willow (Inpatient and Ambulatory): The comprehensive pharmacy system,
managing medication orders, verification, dispensing, inventory control, and
clinical pharmacy workflows for both hospital and clinic settings.34
○ Beaker (Clinical Pathology and Anatomic Pathology): Epic's Laboratory
Information System (LIS), managing lab orders, specimen tracking (often
using barcodes and mobile devices like Rover), processing, resulting, and
quality control for both general lab tests and pathology specimens.22
○ Radiant: The Radiology Information System (RIS), used for managing imaging
workflows, including scheduling radiology exams, protocoling studies,
tracking results and images (though images are typically stored in a separate
PACS), and facilitating communication of findings.32
○ OpTime: The operating room management module, covering surgical
scheduling, management of OR resources, pre-operative planning, intra-
operative documentation (often in conjunction with the Anesthesia module),
and post-operative tracking.32
○ Anesthesia: An information management system for anesthesiologists,
supporting pre-operative evaluations, intra-operative anesthesia record-
keeping (vital signs, medications, events), and post-anesthesia care
documentation. It integrates closely with OpTime.47
○ Cupid: The Cardiology Information System (CIS), designed for managing
cardiovascular patient data, scheduling cardiology procedures, documenting
diagnostic tests (like echocardiograms, stress tests), and supporting
reporting for cardiac interventions.22
○ Beacon: The medical oncology module, supporting the creation and
management of complex chemotherapy treatment plans, tracking patient
responses, and managing oncology-specific workflows.22
○ Stork: Dedicated to obstetrics care, managing documentation related to
pregnancy, labor, delivery, and postpartum care.32
 ○ Phoenix: Supports the comprehensive management of transplant patients,
from initial evaluation and waitlist management through post-transplant
follow-up care.32
○ Kaleidoscope: An ophthalmology-specific module providing tools for eye
exam documentation, managing prescriptions for corrective lenses, and
supporting ophthalmology workflows.47
○ Wisdom: Designed for dental practices, offering tools for dental charting,
treatment planning, and managing dental patient records.47
● Patient Access and Revenue Cycle Modules: These modules manage the
administrative and financial aspects of patient care.
○ Prelude (ADT/Patient Registration): Handles patient registration, including
capturing demographic and insurance information, and manages Admission,
Discharge, and Transfer (ADT) events within a hospital. It is foundational for
creating the patient encounter.38
○ Cadence: The primary scheduling module for outpatient clinics and specialty
departments, used to book and track patient appointments, manage provider
schedules, and handle check-in/check-out processes.22
○ Grand Central: Focuses on inpatient bed management, facilitating bed
planning, tracking patient locations within the hospital, and coordinating
housekeeping services. It works closely with Prelude's ADT functions.38
○ Resolute (Hospital Billing and Professional Billing): The core billing and
accounts receivable modules. Resolute Hospital Billing handles charges
related to inpatient and hospital-based outpatient services, while Resolute
Professional Billing manages claims for physician services. These modules
manage claim creation, submission to payers, payment posting, denial
management, and collections.4
○ ChargeRouter: An essential component in the revenue cycle, ChargeRouter
captures charges generated from clinical activities across various modules
(e.g., orders placed, procedures performed, medications administered),
validates them, and routes them to the appropriate Resolute billing module
for claim generation.60
○ Tapestry: A suite of modules designed for managed care organizations and
health plans, supporting functions like member enrollment, benefits
administration, premium billing, and claims adjudication from the payer
perspective.70
● Interoperability and Patient Engagement Modules:
○ MyChart: The patient portal, enabling patients to access their health
 information, communicate with providers, schedule appointments, and more
(detailed in Section IV.C).4
○ Care Everywhere: Epic's platform for exchanging patient data with other
healthcare organizations using national interoperability standards (detailed in
Section VI.B).9
○ EpicCare Link: A secure web portal that allows external, community-based
providers (e.g., referring physicians) to view clinical information for their
patients who are receiving care at an Epic-using organization.44
○ Healthy Planet: Epic's population health management module, providing
tools for risk stratification, care management, patient outreach, and tracking
quality measures across patient populations.8

The tight integration among these modules is a hallmark of the Epic system. Data
entered in one module, such as a medication order in EpicCare Ambulatory,
seamlessly flows to Willow for pharmacy processing, to ClinDoc for administration
documentation, and to Resolute via ChargeRouter for billing. While this integration is
a significant strength, the complexity arising from the sheer number of specialized
modules and their intricate interdependencies means that implementing, configuring,
and maintaining these workflows is a substantial undertaking. Errors or
misconfigurations in one part of this interconnected web can have cascading effects,
potentially impacting clinical care or financial outcomes. This inherent complexity
drives the need for deep, specialized expertise in multiple Epic modules and their
specific interaction points.

B. Interaction of Key Modules with Core Architecture (Illustrative End-to-End

Data Flow Examples)
To understand how these modules and the core architecture function cohesively, it is
helpful to trace data flow through common patient care scenarios.42

Scenario 1: Outpatient Visit with Lab Order and Results

1. Patient Registration/Check-in: The patient's journey begins with registration or
check-in, managed by the Prelude and Cadence modules. Demographic details,
insurance information, and guarantor data are entered or verified in Prelude.38
The appointment itself is scheduled and tracked in Cadence.41 All this information
is stored directly in the Chronicles database, forming the initial record for the
encounter.
2. Clinical Documentation: During the visit, the physician or other clinician uses
EpicCare Ambulatory to document the patient's history, chief complaint,
 physical examination findings, assessment, and plan.35 This documentation
creates new data items or updates existing ones within the patient's record and
specific contact (visit) in Chronicles.
3. Order Entry (CPOE): Within EpicCare Ambulatory, the physician places an
electronic order for lab tests using the Computerized Provider Order Entry
(CPOE) functionality.35 This order is recorded in Chronicles. Integrated Clinical
Decision Support (CDS) tools may provide real-time alerts or guidance based on
the patient's record and the order being placed (e.g., duplicate order checks,
allergy warnings).3
4. Lab Processing: The lab order is electronically transmitted from EpicCare
Ambulatory to the Beaker LIS module (or to an external LIS via an interface, often
HL7-based).33 Beaker then manages the entire lab workflow, including specimen
collection (potentially using the Rover mobile application for bedside labeling 33),
tracking the specimen through the lab, interfacing with lab analyzers, and result
validation.
5. Results Transmission to Chronicles: Once lab results are finalized in Beaker (or
received from an external LIS), they are written back to the patient's central
record in Chronicles. This makes the results immediately available system-wide.
6. Results Review and Patient Communication: The ordering physician typically
receives the finalized lab results in their InBasket within Hyperspace.39 The results
are also viewable within the patient's chart in EpicCare Ambulatory.
Simultaneously, depending on the organization's policies and configurations,
these results can be automatically released to the patient via the MyChart
portal.39
7. Billing: Charges associated with the outpatient visit (e.g., evaluation and
management code) and the lab tests performed are generated. These charges
are often triggered automatically based on the documentation and orders. The
ChargeRouter module processes these charges, ensuring they are correctly
coded and attributed, and then forwards them to the Resolute Professional
Billing module for claim creation and submission to the payer.67
8. Reporting and Analytics: Data from this entire encounter—including
demographics, clinical notes, orders, lab results, and billing information—is
extracted from Chronicles during the nightly ETL process and loaded into the
Clarity relational database. Subsequently, this data may be further transformed
and loaded into the Caboodle data warehouse for more advanced reporting,
population health analysis, and business intelligence.14

Scenario 2: Inpatient Surgery

1. Admission: A patient requiring surgery is admitted to the hospital. The Prelude
module handles the Admission, Discharge, Transfer (ADT) process, capturing
necessary demographic, insurance, and clinical information.38 The Grand Central
module is used for bed assignment and management.38 This information is
recorded in Chronicles.
2. Pre-Operative Phase: Pre-operative assessments, consent forms, and nursing
care plans are documented in EpicCare Inpatient (ClinDoc).48 The surgery itself
is scheduled in the OpTime module, which manages OR schedules, resources,
and case carts.59 The Anesthesia module is used for pre-anesthesia
evaluations.47 All data is captured in Chronicles.
3. Intra-Operative Phase: This phase involves multiple modules working in
concert:
○ OpTime: Surgeons and OR nurses document the surgical procedure,
including start/end times, personnel involved, techniques used, and any
implants or supplies consumed (often using barcode scanning for
accuracy).59
○ Anesthesia: The anesthesiologist or CRNA documents the entire intra-
operative anesthesia record, including medications administered, vital signs
monitoring, fluid balance, and critical events.47
○ EpicCare Inpatient (ClinDoc): OR nursing staff may use ClinDoc for specific
intra-operative documentation tasks not covered by OpTime.
○ Willow: Any medications administered during surgery are recorded, often
interfacing from the Anesthesia or OpTime modules to Willow for pharmacy
record-keeping and inventory management.53
○ Beaker: If any specimens (e.g., biopsies) are collected during surgery, orders
are placed, and the specimens are sent to the lab, managed by the Beaker
module.33 All this intra-operative data flows into Chronicles in real-time,
providing a contemporaneous record of the surgery.
4. Post-Operative Phase: Following surgery, the patient is typically transferred to
a Post-Anesthesia Care Unit (PACU) and then to an inpatient unit. Post-operative
care, including vital signs monitoring, pain management, wound care, and
recovery progress, is documented in EpicCare Inpatient (ClinDoc).48
Medications are managed via Willow.53
5. Discharge: When the patient is ready for discharge, the EpicCare Inpatient
(ClinDoc) module is used to create the discharge summary, patient instructions,
prescriptions for take-home medications, and schedule any necessary follow-up
appointments.48
 6. Billing: The surgical encounter generates a multitude of charges: OR time,
surgeon and anesthesiologist professional fees, supplies, implants, medications,
room and board, etc. These charges originate from OpTime, Anesthesia, ClinDoc,
and Willow, flow through ChargeRouter for validation and processing, and are
then sent to Resolute Hospital Billing and Resolute Professional Billing as
appropriate.67
7. Reporting and Analytics: The vast amount of data generated during the
surgical episode is extracted nightly to Clarity and Caboodle. This data is
invaluable for analyzing surgical outcomes, OR utilization, resource consumption,
costs, quality metrics, and identifying areas for process improvement.14

These illustrative scenarios highlight the profound interconnectedness of Epic's

modules and their continuous interaction with the central Chronicles database. The
complexity of these end-to-end workflows, which span numerous specialized
applications and critical data handoffs, underscores the paramount importance of
meticulous workflow design during implementation, comprehensive testing
(especially before and after system upgrades), and continuous, role-specific training
for all end-users. A breakdown or misconfiguration at any point in these intricate
chains—for example, a charge failing to route correctly from OpTime to
ChargeRouter, or a critical lab result not displaying promptly in a physician's InBasket
—can lead to significant downstream consequences, ranging from lost revenue and
compliance violations to compromised patient safety. This inherent complexity and
the high stakes involved are primary drivers for the significant demand for certified
Epic analysts who specialize in particular modules and, crucially, in the integration
and optimization of these cross-functional workflows. Such expertise is vital for
healthcare organizations to fully realize the intended benefits of a deeply integrated
EHR system like Epic.

VI. Interoperability: Connecting Epic to the Wider Health IT

World
In today's interconnected healthcare ecosystem, the ability of an EHR system to
exchange data with other systems—both within and outside the healthcare
organization—is crucial. Epic provides a multi-faceted approach to interoperability,
utilizing a range of technologies and standards to facilitate data sharing for continuity
of care, patient engagement, and regulatory compliance.

A. Epic Bridges: The Interface Engine

Epic Bridges is the traditional interface engine module within the Epic ecosystem,
designed for establishing, configuring, and maintaining interfaces between Epic and
various external, non-Epic systems.12 It serves as a central hub for managing data
exchange with a multitude of third-party applications and systems that a healthcare
organization might use, such as departmental legacy systems, external laboratories,
medical devices, public health registries, and payer systems.

Bridges supports a variety of standard communication protocols and message

formats essential for healthcare data exchange 12:
● HL7 (Health Level Seven): This is the most common standard used for
exchanging clinical and administrative data between different healthcare
software applications. Bridges robustly supports various versions of HL7
messages (e.g., ADT for patient demographics and encounters, ORM for orders,
ORU for observation results/reports). The system checks MSH-11 (processing ID)
and MSH-12 (version ID) on incoming HL7 messages to ensure they match
expected values.74
● ANSI X12: Used for Electronic Data Interchange (EDI) transactions, particularly
for administrative and financial data exchange with payers, such as eligibility
verification (270/271), claims submission (837), and remittance advice (835).74
● NCPDP (National Council for Prescription Drug Programs): Standards like
SCRIPT are used for e-prescribing and other pharmacy-related transactions,
including communications with external pharmacies and pharmacy benefit
managers (PBMs).74
● DICOM (Digital Imaging and Communications in Medicine): While Epic itself
does not typically store large imaging files (these reside in PACS), Bridges
facilitates the exchange of imaging-related messages and data, supporting
workflows like order transmission and report retrieval with Picture Archiving and
Communication Systems (PACS) and Vendor Neutral Archives (VNA).74
● FHIR (Fast Healthcare Interoperability Resources): Bridges can also support
FHIR-based integrations, complementing Epic's broader FHIR API strategy.74

The Bridges toolkit includes functionalities for defining interface triggers (events that
initiate message creation), configuring message structures (segments, fields, and
sub-components), mapping data elements between Epic's Chronicles database and
the external system's format, monitoring message queues (data, control, and holding
queues), and managing interface errors.12 While Bridges provides the necessary tools
for these integrations, managing a large portfolio of point-to-point interfaces, each
with its own specific configurations and potential variations even within standards like
HL7 v2, represents a significant operational overhead for healthcare IT departments.
This complexity has been a contributing factor in the industry's movement towards
newer, API-centric interoperability paradigms like FHIR, which can offer simpler, more
standardized, and reusable integration patterns for many use cases.

B. Care Everywhere: Sharing Patient Records Across Organizations

Care Everywhere is Epic's flagship interoperability platform designed to facilitate the
exchange of patient health information among different healthcare organizations,
regardless of whether they use Epic or another EHR system, as long as they adhere to
common national standards.9 It is a key enabler of nationwide health information
exchange, aiming to provide clinicians with a more comprehensive view of a patient's
medical history, especially when patients receive care from multiple, unaffiliated
providers.

Care Everywhere supports several modes of data exchange 76:

● Query-Based Exchange: Allows authorized clinicians to "pull" a patient's
records from external organizations where the patient has also received care.
This is often used for unplanned care encounters (e.g., an emergency
department visit) or when a new patient presents.
● Push-Based Exchange: Enables clinicians to "send" patient summaries to other
providers, typically for planned transitions of care, such as referrals to specialists
or discharge summaries sent to a primary care physician.

To achieve this, Care Everywhere leverages a set of industry-standard protocols and

document formats 76:
● IHE (Integrating the Healthcare Enterprise) Profiles: For query-based
exchange, it uses transactions from IHE profiles such as Cross-Community
Access (XCA) and Cross-Enterprise Document Sharing (XDS.b). For push-based
exchange, it can use IHE Cross-Enterprise Document Reliable Interchange (XDR).
● Direct Project Standards: Utilized for secure, point-to-point push of health
information, often employed for referrals and care transitions.
● HL7 Clinical Document Architecture (CDA): This is the standard for the
content of the exchanged clinical documents. Care Everywhere supports the
exchange of various CDA-based documents, most notably the Continuity of Care
Document (CCD) and documents compliant with the Consolidated CDA (C-CDA)
framework, which is a requirement for EHR certification in the U.S.

Epic reports that 100% of its customers are interoperable through Care Everywhere,
exchanging millions of patient records daily, with a significant portion of these
exchanges occurring with organizations using non-Epic EHRs.72 The effectiveness of
Care Everywhere, however, depends not only on Epic's technology but also on the
broad participation of other healthcare organizations and EHR vendors in national
interoperability frameworks and networks like the eHealth Exchange and
Carequality.76 These frameworks provide the necessary trust agreements,
governance, and technical specifications to enable secure and reliable inter-
organizational data sharing. While Care Everywhere is technically capable of
connecting with any standards-compliant EHR, its most seamless and widespread
operation is often observed within the large network of Epic users and with entities
actively participating in these shared national interoperability initiatives.

C. FHIR APIs and open.epic: Modern, Standardized Data Exchange

Epic has made significant investments in supporting FHIR (Fast Healthcare
Interoperability Resources), a modern, API-based standard developed by HL7.3 FHIR
APIs offer a more granular, web-friendly (RESTful) approach to data exchange
compared to traditional document-based exchange (like CDA) or message-based
interfaces (like HL7 v2).81 This allows applications to request specific pieces of data
("resources" in FHIR terminology, such as a single allergy, a specific lab result, or
patient demographics) rather than entire documents.

Key aspects of Epic's FHIR strategy include:

● open.epic Platform: This is Epic's developer portal, providing free access to
extensive documentation on Epic's FHIR APIs, a testing sandbox with sample
data, and tools for developers to register their applications and obtain client IDs.3
This platform is designed to enable third-party developers to build applications
that can securely connect to and interact with Epic EHR data.
● Supported FHIR Versions and Resources: Epic supports multiple versions of
the FHIR standard, including DSTU2, STU3, and R4, ensuring compatibility with a
wide range of applications and evolving industry requirements. It offers APIs for a
vast array of FHIR resources, covering patient data, clinical observations,
conditions, appointments, medications, documents, and many more.84
● Authentication and Authorization: Epic's FHIR APIs primarily use the SMART on
FHIR framework, which leverages OAuth 2.0 for secure authentication and
authorization.3 This allows patients and providers to authorize third-party
applications to access specific scopes of their data within Epic.
● App Orchard: This is Epic's marketplace for third-party applications that
 integrate with the Epic EHR.9 Many of these applications utilize Epic's FHIR APIs to
achieve integration. The App Orchard provides a curated environment for Epic
customers to discover and deploy these integrated solutions. Epic also offers a
"Vendor Services" program for developers seeking more direct support, design
feedback, and assistance with their integrations.9
● USCDI Compliance: Epic actively supports the United States Core Data for
Interoperability (USCDI) standard through its FHIR APIs. The USCDI defines a
standardized set of data classes and elements that EHRs must be able to
exchange. Epic has often implemented support for new versions of USCDI ahead
of federally mandated timelines, demonstrating a commitment to advancing data
standardization.89

Epic's embrace of FHIR and the open.epic platform marks a significant evolution from
its historically more proprietary approach to integration. By providing open,
standardized APIs and developer resources, Epic is fostering an ecosystem of
innovation around its platform, enabling the development of new patient-facing apps,
clinical decision support tools, and specialized healthcare solutions. This openness,
driven by regulatory mandates like the 21st Century Cures Act and market demand for
more flexible and patient-centric data access, is transforming how external
applications interact with EHR data. However, this shift also introduces new
complexities and responsibilities for both Epic and healthcare organizations.
Managing a growing API ecosystem, ensuring the security and privacy of data
accessed by numerous third-party applications, and vetting the clinical or operational
value of these apps become critical governance challenges. Programs like App
Orchard and Vendor Services aim to provide some level of curation and support in
this evolving landscape.

D. Other Integration Points

Beyond these primary interoperability mechanisms, Epic integrates with a wide array
of specialized systems crucial for comprehensive healthcare delivery:
● Laboratory Information Systems (LIS): While Epic's Beaker module can serve
as an organization's LIS, many organizations have existing LIS systems. Epic
integrates with these external LISs, typically using HL7 interfaces (managed via
Bridges) for transmitting lab orders from Epic to the LIS and receiving results
back into Epic.33 FHIR APIs are also increasingly used for lab order and result
exchange.42
● Picture Archiving and Communication Systems (PACS) / Vendor Neutral
 Archives (VNA): Radiological images (X-rays, CTs, MRIs, etc.) are typically
stored in dedicated PACS or VNAs, not directly within the EHR. Epic's Radiant
(RIS) module integrates with these imaging systems to manage radiology orders,
retrieve imaging reports, and provide links or embedded viewers for clinicians to
access images from within Hyperspace.93 Integration methods include DICOM
standards, HL7 messaging, and specific vendor integration mechanisms like
Epic's FDI (Foreign System Interface) records, which allow Hyperspace to launch
external PACS viewers in context.94
● Pharmacy Systems and Pharmacy Benefit Managers (PBMs): Epic's Willow
module handles internal pharmacy operations. For external connectivity, Epic
integrates with retail pharmacy systems, national e-prescribing networks (such
as Surescripts), and PBMs. These integrations utilize standards like NCPDP
SCRIPT for e-prescribing, HL7 for other pharmacy communications, and FHIR for
emerging use cases.51 This enables electronic transmission of prescriptions,
formulary checks, medication history retrieval, and benefits verification.
● Health Information Exchanges (HIEs): Epic systems, through mechanisms like
Care Everywhere and Bridges, connect to local, regional, and state-level HIEs.
These connections allow for broader community-wide data sharing, enabling
providers to access patient information from various participants within the HIE
network.76

The choice of integration methodology—whether traditional HL7 interfaces via

Bridges, document-based exchange via Care Everywhere, or modern FHIR APIs—
often depends on the capabilities of the external system, the specific data exchange
requirements of the workflow, and the healthcare organization's overall
interoperability strategy. Epic's support for this diverse range of standards and
integration patterns provides the flexibility needed to connect with both legacy
systems and newer, API-enabled applications, but it also means that implementation
teams must possess expertise across these different approaches. Each connection
point represents an architectural decision with implications for development effort,
maintenance, and data flow characteristics.

The following table summarizes the key interoperability mechanisms offered by Epic:

Table 3: Key Epic Interoperability Mechanisms

Mechanism Primary Typical Use Direction of Granularity

 Standard(s) / Case / Purpose Data Flow
Technology

Epic Bridges HL7 (v2.x), ANSI Integrating with Bi-directional Message-

X12, NCPDP, various based, varies by
DICOM, FHIR external/ancillar standard (e.g.,
(via interface y systems (LIS, order, result,
engine) 74 PACS, billing, image pointer)
devices, etc.) 12

Care IHE Profiles Exchanging Bi-directional Document-level

Everywhere (XCA, XDS.b, patient (e.g., CCD)
XDR), Direct summary
Project, HL7 documents with
CDA/C-CDA 76 other
healthcare
organizations
(Epic and non-
Epic) for
continuity of
care 72

FHIR APIs (via FHIR (DSTU2, Enabling third- Bi-directional Resource-level

open.epic/App STU3, R4), party apps (e.g., Patient,
Orchard) SMART on FHIR (patient/provide Observation)
(OAuth 2.0) 84 r facing),
granular data
access, mobile
health
integrations 81

Share Web-based, Patients sharing Outbound Record

Everywhere patient- a one-time view (view-only) summary (view)
mediated of their health
record with
anyone (e.g., a
provider not on
Care
Everywhere) 72
 EpicCare Link Secure Web External/ Primarily Chart sections,
Portal referring Inbound (view); results, notes
providers some outbound (view)
viewing their (referrals)
patients' charts,
placing
referrals,
receiving
updates 44

VII. Technology Stack Summary

The Epic EHR system is built upon a specific set of core technologies, while also
interacting with and supporting a broader range of modern technologies, particularly
for integration and client access.

A. Core Programming Languages

The foundational programming language for Epic's core applications and the
Chronicles database is MUMPS (Massachusetts General Hospital Utility Multi-
Programming System), and its modern object-oriented successor, Caché
ObjectScript, which is part of the InterSystems data platform.3 MUMPS is a language
with an integrated key-value database system, known for its powerful string
manipulation capabilities and efficiency in handling hierarchical data structures,
making it well-suited for the complex and evolving nature of medical records.10

While MUMPS/Caché ObjectScript forms the core, Epic also supports and utilizes
other languages for specific purposes, particularly for integrations, web services, and
potentially newer application components 3:
● JavaScript: Used for web development (e.g., MyChart, web-based Hyperspace
access) and for integrations. Some sources list JavaScript frameworks like Vue.js,
though their use within the core EHR client versus auxiliary web properties needs
careful distinction.3
● .NET (C#): Supported for building integrations with Epic and potentially for
developing certain service layers or modules, especially those exposed via APIs.3
● Java and GoLang: Also appear in broader scans of Epic Systems Corporation's
technology stack, suggesting their use in various enterprise tools or backend
services, though their direct role in the central EHR application is less specified
than MUMPS or C# for integrations.54
The long-standing reliance on MUMPS/Caché ObjectScript for the core system
means that specialized developer expertise is crucial. This language family is not
commonly taught in mainstream computer science programs, leading Epic to invest
significantly in its own comprehensive training and certification programs for
employees and customer staff. This ensures a continuous supply of professionals
skilled in maintaining and customizing the intricate core of the Epic system. While this
specialization ensures optimized performance for its unique database, it also means
that organizations using Epic often depend on these certified individuals or
specialized consultants for in-depth technical development and support.4

B. Supported Operating Systems

The Epic ecosystem runs on a variety of operating systems, depending on the
specific server component or client type:
● Database Servers (InterSystems IRIS/Caché for Chronicles):
○ IBM AIX (on POWER Systems): A traditional and robust platform for large
Epic deployments.17
○ Linux: Widely supported, including distributions like Red Hat Enterprise Linux
(RHEL), SUSE Linux Enterprise Server (SLES), and Oracle Linux. Ubuntu is also
listed for InterSystems IRIS container platforms and development.7
○ Microsoft Windows Server: Also a supported platform for InterSystems
IRIS.7 The historical strength and continued support for AIX on IBM POWER
systems for the core Chronicles database indicate its proven reliability and
scalability for mission-critical healthcare workloads in many large Epic client
sites. The increasing prominence of Linux on x86-64 architecture reflects
broader industry trends towards more open and potentially cost-effective
infrastructure, offering greater flexibility and alignment with cloud
deployment strategies.26
● Application Servers: These typically run on operating systems compatible with
the InterSystems platform, so AIX, Linux, and Windows Server are common.99 The
choice often aligns with the database server OS for consistency.
● Clarity and Caboodle Servers (SQL Server or Oracle based):
○ If using Microsoft SQL Server (common for Clarity/Caboodle), these servers
run on Microsoft Windows Server.14
○ If using Oracle, they would run on an Oracle-supported OS, such as Linux or
Windows Server.
● Hyperspace Client:
○ Microsoft Windows: The traditional and primary OS for the native
 Hyperspace client.28
○ Apple macOS: A native Hyperspace application for Mac is now available.31
○ Web-based access to Hyperspace implies compatibility with modern web
browsers on various operating systems.27
● Mobile Client Applications (MyChart, Haiku, Canto, Rover):
○ Apple iOS.31
○ Google Android.31

C. Deployment Models
Epic offers a range of deployment models to accommodate the diverse needs, sizes,
and IT capabilities of healthcare organizations:
● On-Premise: The traditional model where the healthcare organization purchases
Epic licenses and hosts the entire system (servers, storage, networking) within its
own data centers.2 This model provides maximum control over the infrastructure
and data but requires significant upfront capital investment, extensive IT
resources, and ongoing maintenance responsibility.103
● Hosted (Private Cloud): Epic software can be hosted by Epic itself or by a third-
party hosting provider in a private cloud environment.2 This typically involves
dedicated hardware for the client, reducing the organization's direct
infrastructure management burden and upfront capital costs, though ongoing
operational expenses for hosting services apply.
● Public Cloud: Epic's EHR system can be deployed on major public cloud
platforms, including Amazon Web Services (AWS), Microsoft Azure, and Google
Cloud Platform (GCP).103 Epic has established partnerships with these providers
to facilitate such deployments. Public cloud offers benefits like rapid scalability,
elasticity, global reach, and potentially access to advanced cloud-native services
for analytics or AI. This model shifts infrastructure costs from capital
expenditures (CapEx) to operational expenditures (OpEx).
● Epic Garden Plot (SaaS): Launched in 2022, Garden Plot is a Software-as-a-
Service (SaaS) offering specifically designed for smaller, independent medical
groups (typically 40-100 providers) that are not part of a larger health system
using Epic.103 In this model, these groups work directly with Epic for a more
turnkey, managed EHR solution, simplifying adoption and maintenance.
● Epic Community Connect: This model allows larger healthcare organizations
already using Epic (referred to as "hubs") to extend their Epic instance to smaller,
affiliated physician practices, community hospitals, or other healthcare entities.72
The smaller organizations ("spokes") access the hub's Epic system, benefiting
 from a proven EHR implementation and shared infrastructure, while the hub can
strengthen its network and improve care coordination.

The evolution of Epic's stance on public cloud deployments, moving from initial
caution to active partnerships with major cloud providers 103, represents a significant
strategic adaptation. This shift is largely driven by strong customer demand for the
inherent benefits of cloud computing—such as enhanced scalability, improved
disaster recovery capabilities, greater agility, and a preference for OpEx financial
models—as well as the maturation of public cloud platforms in meeting stringent
healthcare security and compliance requirements (e.g., HIPAA). This embrace of
public cloud makes Epic's comprehensive EHR accessible to a broader range of
organizations and enables existing customers to modernize their underlying
infrastructure. However, it also introduces new complexities. Successfully managing
an Epic environment in the public cloud requires different skill sets compared to on-
premise deployments, particularly concerning cloud-specific security configurations,
cost optimization strategies, and performance management within a shared, multi-
tenant infrastructure.

VIII. Architectural Considerations: Security, Scalability, and

Reliability
The architecture of an EHR system as critical and comprehensive as Epic must
inherently address stringent requirements for security, scalability, and reliability.
These are not afterthoughts but foundational design principles woven throughout the
system.

A. Overview of Epic's Approach to System Security

Epic places a strong emphasis on protecting the confidentiality, integrity, and
availability of patient data, adhering to regulatory frameworks like HIPAA.3 The
security model is multi-layered, encompassing application-level controls, database
security, infrastructure security, and procedural safeguards.

Key security measures include:

● Authentication and Access Controls:
○ Role-Based Access Control (RBAC): Hyperspace and other Epic
applications utilize granular, role-based access controls. Users are assigned
roles (e.g., physician, nurse, scheduler) that determine which applications,
activities, and data they can access.9 Specific permissions are often managed
 through "security classes" and "security points".13
○ Authentication Mechanisms: The underlying InterSystems IRIS/Caché
platform supports multiple authentication methods, including Kerberos, OS-
based authentication, LDAP integration, and its own instance-based
authentication.25
○ Multi-Factor Authentication (MFA) and Single Sign-On (SSO): Epic
environments often integrate with enterprise identity and access
management (IAM) solutions. MFA is critical for enhancing security, requiring
users to provide multiple forms of verification.28 SSO solutions, sometimes
provided by partners like Imprivata, allow users to access Hyperspace and
other integrated applications with a single, secure login, often using badge
taps or other streamlined methods.28
● Encryption:
○ Data at Rest: Epic's database (Chronicles on InterSystems IRIS/Caché)
supports robust database encryption, typically using algorithms like AES, to
protect data stored on disk.25
○ Data in Transit: Secure communication protocols such as TLS/SSL are used
to encrypt data exchanged between clients (Hyperspace, mobile apps, web
browsers) and Epic servers, as well as data exchanged with external systems
via interfaces.3
● Audit Trails: The Epic system maintains detailed audit logs that record user
activities, access to patient records, and system events. These logs typically
capture who accessed what data, when, and from where, providing a crucial
mechanism for security monitoring, incident investigation, and compliance
reporting.3
● Compliance and Certifications: Epic's software is designed to help healthcare
organizations comply with HIPAA and other relevant regulations.3 Epic Systems
Corporation itself holds several industry certifications, such as ISO 27001 for
Information Security Management, ISO 9001 for Quality Management, and ISO
20000-1 for IT Service Management, which attest to its commitment to
standardized processes and security best practices.104 Epic's EHR is also ONC-
ATCB certified, a requirement for EHRs in the US.104
● Interoperability Security: For data exchange with external systems, especially
via modern FHIR APIs, Epic supports secure protocols like OAuth 2.0 as part of
the SMART on FHIR framework.9

This comprehensive, defense-in-depth security strategy combines features built into

Epic's own software, the security capabilities of the underlying InterSystems database
platform, and necessary integrations with enterprise-level security infrastructure and
third-party solutions. However, the effectiveness of these measures also relies heavily
on proper configuration, diligent administration by the healthcare organization's IT
staff, and adherence to security policies and procedures by all users. Security in an
Epic environment is thus a shared responsibility.

B. Strategies for Ensuring Performance and Scalability

Given that Epic serves some of the largest and busiest healthcare organizations in the
world, its architecture must be capable of delivering high performance and scaling to
accommodate massive data volumes and concurrent user loads.6 Several
architectural strategies contribute to this:
● Optimized Database Architecture: The core Chronicles database, built on
InterSystems IRIS/Caché, is highly optimized for the transactional workloads
typical in healthcare, characterized by frequent reads and writes of complex
patient data.7 The separation of this Online Transaction Processing (OLTP)
system from the Online Analytical Processing (OLAP) systems (Clarity and
Caboodle) is a fundamental design choice that prevents resource-intensive
reporting and analytics from degrading the performance of the live clinical
system.2
● InterSystems Enterprise Caché Protocol (ECP): As discussed previously, ECP
enables horizontal scaling of the application server tier for large deployments.7
By distributing application logic processing across multiple servers that can all
efficiently access the central database, the system can handle a greater number
of users and transactions.
● Scalable Infrastructure: Epic's software is designed to run on scalable hardware
infrastructure, whether on-premise (e.g., powerful IBM POWER systems or x86-
64 servers) or in cloud environments (AWS, Azure, GCP) that offer elastic
resource provisioning.3 Storage solutions, such as those from NetApp, are often
employed to provide scalable and high-performance storage for the vast
amounts of data generated and accessed by the Epic system.17
● Modular Design: The modular nature of Epic's applications allows organizations
to implement and potentially scale different components of the system based on
their specific needs, although the core system remains tightly integrated.3
● Efficient Client-Server Communication: The design of Hyperspace and other
clients aims for efficient communication with the application servers to minimize
latency and optimize responsiveness for end-users.
Achieving optimal performance and scalability in an Epic environment is not solely
dependent on raw computing power or storage capacity. It also heavily relies on
meticulous system configuration, careful workflow design, and ongoing performance
monitoring and tuning tailored to each organization's unique size, scope of modules
implemented, and specific usage patterns. This is why Epic implementations involve
extensive capacity planning, performance testing, and optimization phases, often
requiring specialized expertise.

C. High Availability and Disaster Recovery Concepts

Continuous availability of the EHR is paramount in healthcare, as system downtime
can directly impact patient care and safety. Epic's architecture, in conjunction with
underlying infrastructure capabilities, incorporates features and strategies for High
Availability (HA) and Disaster Recovery (DR):
● High Availability (HA):
○ Database Level: The InterSystems IRIS/Caché platform provides robust HA
features, including database mirroring, where data is synchronously or
asynchronously replicated to a standby database server.7 In the event of a
primary database server failure, the system can failover to the mirrored
standby server, minimizing downtime.
○ Server Level: Epic environments often utilize clustered hardware
configurations for database and application servers. If a primary server in a
cluster fails, its workload can be automatically transferred to a standby server
in the cluster.17
○ Storage Level: Enterprise storage systems (e.g., from NetApp) used in Epic
deployments typically offer their own HA features, such as redundant
components, data replication, and failover capabilities, to ensure continuous
data access even in the event of storage hardware failures.17
● Disaster Recovery (DR):
○ Data Replication: For DR, data from the primary production site (including
the IRIS/Caché database and other critical data like WebBLOB storage for
scanned documents) is replicated to a geographically separate DR site.17
Technologies like InterSystems database mirroring (often configured for
asynchronous replication to a DR site) and storage-based replication (e.g.,
NetApp SnapMirror) are used for this purpose.
○ DR Site Activation: In the event of a major disaster rendering the primary
data center inoperable, the DR site can be activated. This involves bringing
the replicated databases and applications online at the DR site to resume
 operations. The Recovery Time Objective (RTO) and Recovery Point Objective
(RPO) are key metrics that define the acceptable duration of downtime and
data loss, respectively, and DR plans are designed to meet these targets.
● Business Continuity: Epic provides technical guidance and recommendations
for overall business continuity planning.107 This includes not only system recovery
but also procedures for operating during periods of system unavailability
(downtime procedures) and comprehensive backup and restore strategies for all
critical components of the Epic environment. Solutions like Commvault are often
used for backup and recovery, following Epic's guidelines.107

Implementing effective HA and DR for a complex system like Epic is a significant

undertaking. It requires careful planning and investment across multiple layers: the
Epic software itself, the InterSystems database, server hardware, storage systems,
networking infrastructure, and well-documented, regularly tested operational
procedures. The choice of deployment model (on-premise, hosted, or public cloud)
significantly influences how HA and DR are architected and managed. Public cloud
platforms, for instance, often offer more readily available and potentially more
sophisticated HA/DR services (e.g., multiple availability zones/regions, automated
failover, managed backup services) that can simplify some aspects of HA/DR
implementation, though careful configuration and understanding of shared
responsibility models are still crucial.103

IX. Conclusion: Understanding the Epic Blueprint

The Epic Electronic Health Record system is a multifaceted and deeply integrated
platform, architected to meet the demanding requirements of modern healthcare. Its
architecture is characterized by several key attributes that collectively enable its
widespread adoption and operational impact.

At its core lies a unique database structure, with the Chronicles database (built on
InterSystems IRIS/Caché technology) serving as the real-time, transactional heart of
the system.2 This is complemented by Clarity for relational reporting and Caboodle
as an enterprise data warehouse, strategically separating analytical workloads from
live patient care operations to maintain performance.2 This tiered data strategy is
fundamental to Epic's ability to handle both high-volume transactions and complex
data analysis.

The application server layer, predominantly using Caché ObjectScript, executes the
vast business logic of Epic's modules, with technologies like InterSystems ECP
ensuring scalability for the largest of healthcare enterprises.17 The primary user
interface, Hyperspace, provides a role-customized gateway for clinicians and staff,
supported by a growing suite of mobile applications (Haiku, Canto, Rover) and the
MyChart patient portal, which extend access to the point of care and directly to
patients.27

Epic's comprehensive functionality is delivered through an extensive array of

interconnected modules, each tailored to specific clinical or administrative domains,
from EpicCare Inpatient and Ambulatory to specialized modules like Beaker (LIS),
Radiant (RIS), OpTime (OR), Willow (Pharmacy), and Resolute (Billing).35 The tight
integration between these modules aims to create seamless data flow across the
patient care continuum, though the complexity of these interactions necessitates
deep system expertise.

A critical aspect of Epic's architecture is its evolving interoperability framework.

While traditional interfaces are managed via Epic Bridges 22, Care Everywhere
facilitates broader health information exchange using national standards.72
Increasingly, Epic is championing modern, API-based interoperability through its
robust support for FHIR APIs, made accessible via the open.epic platform and the
App Orchard marketplace.80 This reflects a strategic balance: maintaining a
powerful, integrated proprietary core while embracing open standards to foster
innovation and connectivity with the wider health IT ecosystem.

The overall architecture is underpinned by a strong focus on security, scalability,

and reliability. Multi-layered security controls, encryption, and comprehensive
auditing address data protection and compliance needs.6 Scalability is achieved
through database optimizations, application server distribution, and flexible
infrastructure options, including on-premise, hosted, and public cloud deployments.17
High availability and disaster recovery mechanisms are integral to ensuring system
resilience.17

In essence, the Epic EHR architecture is a complex, highly engineered system

designed to serve as the digital backbone for healthcare delivery. It prioritizes
patient-centricity, data integrity, and robust performance to support the intricate,
high-stakes environment of healthcare. The platform's continuous evolution, marked
by advancements in areas like AI integration 4, expanded cloud adoption 103, and the
proactive embrace of new interoperability standards like FHIR and USCDI 89, signals
Epic's ongoing commitment to addressing the future challenges and opportunities in
healthcare information technology. Understanding this architectural blueprint is key
to appreciating both its current capabilities and its trajectory in shaping the future of
digital health.

Works cited

1. About - Epic, accessed on May 8, 2025, https://www.epic.com/about/

2. Epic Systems - Wikipedia, accessed on May 8, 2025,
https://en.wikipedia.org/wiki/Epic_Systems
3. Epic Systems: Features, Architecture & Integration Guide - Artoon Solutions,
accessed on May 8, 2025, https://artoonsolutions.com/glossary/epic-systems/
4. Epic EHR Explained: Features, Benefits, and Impact on Healthcare -
HealthConnect CoPilot, accessed on May 8, 2025,
https://healthconnect.mindbowser.com/epic-ehr-explained/
5. Epic Systems Corp Company Profile - Overview - GlobalData, accessed on May
8, 2025, https://www.globaldata.com/company-profile/epic-systems-corp/
6. What is Epic in Healthcare? | True North - TrueNorth ITG, accessed on May 8,
2025, https://www.truenorthitg.com/what-is-epic-in-healthcare/
7. What is the Epic System for Healthcare - Complete Guide 2025 - Folio3 Digital
Health, accessed on May 8, 2025, https://digitalhealth.folio3.com/blog/what-is-
the-epic-system-for-healthcare/
8. What Is Epic EHR? Overview, Features, and Pricing - iFax, accessed on May 8,
2025, https://www.ifaxapp.com/emr-and-ehr/what-is-epic-ehr/
9. Maximizing Impact with Epic Architecture: A Comprehensive Guide - Surety
Systems, accessed on May 8, 2025,
https://www.suretysystems.com/insights/maximizing-impact-with-epic-
architecture-a-comprehensive-guide/
10. MUMPS - Wikipedia, accessed on May 8, 2025,
https://en.wikipedia.org/wiki/MUMPS
11. Caché ObjectScript and MUMPS: Technical Learning Manual - Amazon.com,
accessed on May 8, 2025, https://www.amazon.com/Cach%C3%A9-
ObjectScript-MUMPS-Technical-Learning/dp/1466499087
12. Epic Data Warehousing Modules | Epic Cache, Bridges & More - HealthTECH
Resources, accessed on May 8, 2025, https://healthtechresourcesinc.com/epic-
consultants/epic-data-warehousing-modules
13. Chronicles in Epic: Understanding Master Files, Records, Contacts, and Print
Groups | Exams Nursing | Docsity, accessed on May 8, 2025,
https://www.docsity.com/en/docs/epic-cln251-252-exam-100-correct-answers/
11076514/
14. Epic Clarity | PennDnA - Perelman School of Medicine at the University of
Pennsylvania, accessed on May 8, 2025,
https://www.med.upenn.edu/penndna/epic-clarity-data-warehousing.html
15. C-A5-01: Clarity and Research - PMC, accessed on May 8, 2025,
https://pmc.ncbi.nlm.nih.gov/articles/PMC3006553/
16. Clarity (Epic) - eHealth Glossary, accessed on May 8, 2025,
https://ehealth.connect-care.ca/epic-systems/epic-analytic-tools/clarity
17. Epic architecture - Product Documentation - NetApp, accessed on May 8, 2025,
https://docs.netapp.com/us-en/ontap-apps-dbs/epic/epic-arch-overview.html
18. Your Comprehensive Guide to Epic Clarity - Surety Systems, accessed on May 8,
2025, https://www.suretysystems.com/insights/your-comprehensive-guide-to-
epic-clarity/
19. CDW110 Flashcards - Quizlet, accessed on May 8, 2025,
https://quizlet.com/541121081/cdw110-flash-cards/
20. Epic Data Resources | Vanderbilt Clinical Informatics Center, accessed on May 8,
2025, https://www.vumc.org/vclic/epic-data-resources
21. Caboodle - Healthcare Data Warehouse - AWS, accessed on May 8, 2025,
https://aviaconnectcontent.s3.amazonaws.com/51acbd5c-6e1a-413d-80bb-
0ab207f652da
22. Epic Systems Modules & Software - Hyperspace, Healthy Planet, ClinDoc,
accessed on May 8, 2025, https://healthcareitskills.com/epic-systems-modules/
23. How to Activate EHR Data from Epic and Caboodle into Snowflake - phData,
accessed on May 8, 2025, https://www.phdata.io/blog/how-to-activate-ehr-
data-from-epic-and-caboodle-into-snowflake/
24. Back to Basics: Why InterSystems?, accessed on May 8, 2025,
https://community.intersystems.com/post/back-basics-why-intersystems
25. InterSystems IRIS Security | Orientation Guide for Server-Side Programming,
accessed on May 8, 2025,
https://docs.intersystems.com/irislatest/csp/docbook/DocBook.UI.Page.cls?
KEY=GORIENT_security
26. What Does the Iris Integration into Epic Mean for Your Health System - YouTube,
accessed on May 8, 2025, https://www.youtube.com/watch?v=4yYfY6XKek4
27. Hyperspace (Epic Basics) - UI Health Care Epic Education - The University of
Iowa, accessed on May 8, 2025, https://epicsupport.sites.uiowa.edu/epic-
resources/hyperspace-epic-basics
28. Knowledge Hub | Epic Hyperspace - Imprivata, accessed on May 8, 2025,
https://www.imprivata.com/knowledge-hub/epic-hyperspace
29. Delivering Epic Hyperspace Through VMware View Using Kiosk Mode and Zero
Clients, accessed on May 8, 2025,
https://kioskindustry.org/wp-content/uploads/2016/02/VMware-Epic.pdf
30. Deliver Epic Hyperspace with Citrix Virtual Apps and Desktops service, accessed
on May 8, 2025, https://www.citrix.com/blogs/2020/05/05/deliver-epic-
hyperspace-with-citrix-virtual-apps-and-desktops-service/
31. Epic Hyperspace on the Mac App Store, accessed on May 8, 2025,
https://apps.apple.com/us/app/epic-hyperspace/id6472198304?mt=12
32. Epic EHR Software - Pricing, Features, Demo & Comparison, accessed on May 8,
2025, https://www.ehrinpractice.com/epic-ehr-software-profile-119.html
33. Epic Beaker Project Implementation - Team RUHS, accessed on May 8, 2025,
 https://www.teamruhs.org/mc-chc/epic-beaker-project-implementation
34. Epic Systems modules | Epic Willow | - YouTube, accessed on May 8, 2025,
https://www.youtube.com/watch?v=JqmbaJ4QKlk&pp=0gcJCdgAo7VqN5tD
35. The Complete Guide to Epic Modules and Software - Folio3 Digital Health,
accessed on May 8, 2025, https://digitalhealth.folio3.com/blog/the-complete-
guide-to-epic-modules-and-software/
36. www.suretysystems.com, accessed on May 8, 2025,
https://www.suretysystems.com/insights/maximize-your-health-with-epic-
mychart-your-guide-to-efficient-care/#:~:text=As%20a%20secure%2C%20user
%2Dfriendly,their%20computer%20or%20mobile%20device.
37. Maximize Your Health with Epic MyChart: Your Guide to Efficient Care - Surety
Systems, accessed on May 8, 2025,
https://www.suretysystems.com/insights/maximize-your-health-with-epic-
mychart-your-guide-to-efficient-care/
38. Epic Patient Access Modules | Epic Prelude & Epic Cadence - HealthTECH
Resources, accessed on May 8, 2025, https://healthtechresourcesinc.com/epic-
consultants/epic-patient-access-modules
39. AMB | ASAP | IP | MyChart - The University of Kansas Health System, accessed on
May 8, 2025,
https://www.kansashealthsystem.com/-/media/Project/Website/PDFs-for-
Download/COVID19/MyChart-Results-Release.pdf
40. MyChart Transition FAQs - RWJBarnabas Health, accessed on May 8, 2025,
https://www.rwjbh.org/patients-visitors/patient-portal/mychart-transition-faqs/
41. Appointment Scheduling - Epic, accessed on May 8, 2025,
https://www.epic.com/software/appointment-scheduling/
42. Automating Data Workflows: Make the Most of Epic Healthcare - Progress
Software, accessed on May 8, 2025,
https://www.progress.com/blogs/automating-data-workflows-make-most-epic-
healthcare-system
43. Navigating the Maze: Overcoming Common Challenges in Epic EHR Integration
for Health Apps - Dash Technologies, accessed on May 8, 2025,
https://dashtechinc.com/blog/overcoming-common-challenges-in-epic-ehr-
integration-for-health-apps/
44. EpicCare Link - The University of Kansas Health System, accessed on May 8,
2025, https://www.kansashealthsystem.com/for-professionals/epiccare-link
45. EPICCARE LINK FREQUENTLY ASKED QUESTIONS - UMass Memorial Health,
accessed on May 8, 2025,
https://www.ummhealth.org/sites/default/files/Documents/for_physicians/
EpicCare%20Link%20FAQs.pdf
46. EPIC Modules: Customized Features for Specialized Healthcare - OSP Labs,
accessed on May 8, 2025, https://www.osplabs.com/insights/epic-modules/
47. Epic Clinical Modules | EpicCare Inpatient & Outpatient Modules - HealthTECH
Resources, accessed on May 8, 2025, https://healthtechresourcesinc.com/ehr-
 implementation-support/epic-consultants/epic-clinincal-modules
48. Epic ClinDoc 101: Key Capabilities and Benefits - Surety Systems, accessed on
May 8, 2025, https://www.suretysystems.com/insights/epic-clindoc-101-key-
capabilities-and-benefits/
49. Epic Systems modules | EpicCare Inpatient (ClinDoc) | - YouTube, accessed on
May 8, 2025, https://www.youtube.com/watch?
v=HjtMtanLoRw&pp=0gcJCdgAo7VqN5tD
50. EpicCare Inpatient (ClinDoc) Skill Test - WeCP, accessed on May 8, 2025,
https://www.wecreateproblems.com/tests/epiccare-inpatient-clindoc-skill-test
51. Epic Product Overviews - UNC Health, accessed on May 8, 2025,
https://www.unchealth.org/for-unch-health-professionals/epic-training/epic-
product-overviews
52. Epic Systems modules | Epic Willow | - YouTube, accessed on May 8, 2025,
https://www.youtube.com/watch?v=JqmbaJ4QKlk
53. Willow - eHealth Glossary, accessed on May 8, 2025, https://ehealth.connect-
care.ca/epic-systems/epic-modules/willow
54. Epic - Overview, Industry, Revenue, Location & Tech Stack | Koala, accessed on
May 8, 2025, https://getkoala.com/companies/epic.com
55. Epic Specialties & Ancillaries Modules | Epic Beaker, Beacon & More, accessed on
May 8, 2025, https://healthtechresourcesinc.com/epic-consultants/epic-
specialties-modules
56. Case Study | Implementing a Comprehensive Epic System - Huntzinger
Management Group, accessed on May 8, 2025,
https://huntzingergroup.com/2025/04/case-study-implementing-a-
comprehensive-epic-system/
57. What is Epic Radiant | Virtelligence, accessed on May 8, 2025,
https://virtelligence.com/blog/what-is-epic-radiant/
58. Radiant (Radiology) | UI Health Care Epic Education - The University of Iowa,
accessed on May 8, 2025,
https://epicsupport.sites.uiowa.edu/epic-resources/radiant-radiology
59. Epic OpTime: Features, Uses and Benefits Explained - Folio3 Digital Health,
accessed on May 8, 2025, https://digitalhealth.folio3.com/blog/epic-optime-
features-uses-benefits/
60. What is Epic OpTime? - Virtelligence, accessed on May 8, 2025,
https://virtelligence.com/blog/what-is-epic-optime/
61. Epic Cupid | PDF | Medical Imaging | Health Care - Scribd, accessed on May 8,
2025, https://www.scribd.com/document/818908806/Epic-Cupid
62. What Is Epic Cupid ? | Virtelligence, accessed on May 8, 2025,
https://virtelligence.com/blog/epic-cupid/
63. What are all the Epic Modules (EHR)? - YouTube, accessed on May 8, 2025,
https://www.youtube.com/watch?v=uMfRanoLvnA
64. Epic Prelude (ADT Patient Registration) - AVIA Marketplace, accessed on May 8,
2025, https://marketplace.aviahealth.com/product/24997
65. Epic - Cadence/Prelude Fundamentals Flashcards - Quizlet, accessed on May 8,
2025, https://quizlet.com/931311048/epic-cadenceprelude-fundamentals-flash-
cards/
66. Cadence (Scheduling/Check In/Check Out) - UI Health Care Epic Education,
accessed on May 8, 2025,
https://epicsupport.sites.uiowa.edu/epic-resources/cadence-schedulingcheck-
incheck-out
67. Epic Revenue Cycle Modules | Epic HIM & Epic Resolute Modules - HealthTECH
Resources, accessed on May 8, 2025, https://healthtechresourcesinc.com/epic-
consultants/epic-revenue-cycle-modules
68. EPIC billing (Resolute) info - anyone with certification or working knowledge? :
r/healthIT, accessed on May 8, 2025,
https://www.reddit.com/r/healthIT/comments/1hzs1c3/epic_billing_resolute_info_
anyone_with/
69. Clinical Information Systems Epic Hospital Billing – Senior - oracle, accessed on
May 8, 2025,
https://fa-eomf-saasfaprod1.fa.ocs.oraclecloud.com/hcmUI/CandidateExperienc
e/en/sites/CX_1002/requisitions/preview/3364
70. Epic Tapestry: Revolutionizing Managed Care Administration in Healthcare,
accessed on May 8, 2025, https://www.suretysystems.com/insights/epic-
tapestry-revolutionizing-managed-care-administration-in-healthcare/
71. Epic Claims & Managed Care Modules | Epic Tapestry Consultants, accessed on
May 8, 2025, https://healthtechresourcesinc.com/epic-consultants/epic-claims-
managed-care-modules
72. Interoperability - Epic, accessed on May 8, 2025,
https://www.epic.com/software/interoperability/
73. Epic Migration Solutions Development - OSP Labs, accessed on May 8, 2025,
https://www.osplabs.com/epic-migration/
74. Epic Bridges: The Interfacing Solution You Need - Surety Systems, accessed on
May 8, 2025, https://www.suretysystems.com/insights/epic-bridges-interfacing-
solution-you-need/
75. Leverage Seamless Data Exchange with Epic Interoperability - OSP Labs,
accessed on May 8, 2025, https://www.osplabs.com/epic-interoperability/
76. Epic Care Everywhere - SF.gov, accessed on May 8, 2025,
https://www.sf.gov/information--epic-care-everywhere
77. open.epic.com, accessed on May 8, 2025,
https://open.epic.com/Home/CareEverywhereSupportedStandards
78. National Networks and HIEs: The Various Crossroads of Data Exchange -
Contexture -, accessed on May 8, 2025, https://contexture.org/national-
networks-and-health-information-exchanges-the-various-crossroads-of-data-
exchange/
79. Interoperability | Epic, accessed on May 8, 2025,
https://www.epic.com/software/interoperability
80. Interoperability Guide - open.epic, accessed on May 8, 2025,
https://open.epic.com/Home/InteroperabilityGuide
81. Epic FHIR vs. Traditional HL7: Which Integration Approach is Best for You? | Blog |
Itirra, accessed on May 8, 2025, https://itirra.com/blog/epic-fhir-vs-traditional-
hl7-which-integration-approach-is-best-for-you/
82. What is epic hl7 integration? - Quora, accessed on May 8, 2025,
https://www.quora.com/What-is-epic-hl7-integration
83. My Apps - Epic on FHIR, accessed on May 8, 2025,
https://fhir.epic.com/Developer/Apps
84. FHIR - open.epic :: Explore By Interface Type, accessed on May 8, 2025,
https://open.epic.com/interface/FHIR
85. Explore By Interface Type - open.epic, accessed on May 8, 2025,
https://open.epic.com/Interface/FHIR
86. Open@Epic 2025, accessed on May 8, 2025, https://open.epic.com/conference
87. Vendor Services - Epic, accessed on May 8, 2025,
https://vendorservices.epic.com/
88. Keep a Pulse on Epic App Orchard and How It Benefits the Health Systems,
accessed on May 8, 2025, https://theappsolutions.com/blog/development/epic-
app-orchard/
89. Epic advances interoperability standards - Becker's Hospital Review | Healthcare
News & Analysis, accessed on May 8, 2025,
https://www.beckershospitalreview.com/healthcare-information-technology/
ehrs/epic-advances-interoperability-standards/
90. Epic unveils new interoperability standards ahead of mandated timeline,
accessed on May 8, 2025, https://dhinsights.org/news/epic-unveils-new-
interoperability-standards-ahead-of-mandated-timeline
91. How to Integrate Your EHR System with Cerner or Epic Using APIs: A Detailed
Guide, accessed on May 8, 2025, https://tateeda.com/blog/how-to-integrate-
your-ehr-system-with-cerner-epic
92. LIS, EMR and EHR: Understanding Their Role in Modern Healthcare | - Scispot,
accessed on May 8, 2025, https://www.scispot.com/blog/lis-emr-and-ehr-
understanding-their-role-in-modern-healthcare
93. Epic, health systems challenge HHS imaging proposal - Becker's Hospital Review,
accessed on May 8, 2025, https://www.beckershospitalreview.com/ehrs/hhs-
imaging-rule-draws-pushback-from-epic-health-systems/?
utm_campaign=bhr&utm_source=website&utm_content=related
94. 1. Integration record (FDI) - Confluence, accessed on May 8, 2025,
https://witsmd.atlassian.net/wiki/spaces/CD/pages/43876431/Technical+Note
%3A+Epic+Hyperspace+Integration+-+RevB
95. Epic Systems Powering Seamless EHR Integration in Healthcare - OSP Labs,
accessed on May 8, 2025, https://www.osplabs.com/epic-systems/
96. Pharmacy Management Solutions - Pegasus One, accessed on May 8, 2025,
https://www.pegasusone.com/healthcare/pharmacy-management-software-
 healthcare-solutions-development/
97. The Importance of Epic EHR Integration for MedTech Companies - Dash
Technologies Inc, accessed on May 8, 2025, https://dashtechinc.com/blog/why-
medtech-companies-need-epic-ehr-integration/
98. EPIC Systems Company Overview, Contact Details & Competitors | LeadIQ,
accessed on May 8, 2025,
https://leadiq.com/c/epic-systems/5a1d9b7423000054008adda3
99. Supported Technologies | InterSystems Supported Platforms | InterSystems IRIS
Data Platform 2025.1, accessed on May 8, 2025,
https://docs.intersystems.com/irislatest/csp/docbook/DocBook.UI.Page.cls?
KEY=ISP_technologies
100. InterSystems IRIS Minimum Supported CPU Models, accessed on May 8, 2025,
https://community.intersystems.com/post/intersystems-iris-minimum-
supported-cpu-models
101. Identity Manager 9.2 - Epic Healthcare System Release Notes, accessed on May
8, 2025, https://support.oneidentity.com/technical-documents/identity-
manager/9.2/epic-healthcare-system-release-notes/2
102. Identity Manager 8.1.5 - Epic Healthcare System Release Notes, accessed on
May 8, 2025, https://support.oneidentity.com/technical-documents/identity-
manager/8.1.5/epic-healthcare-system-release-notes/2
103. Epic EHR Hosting Options Comparison – which is right for you?, accessed on
May 8, 2025, https://blog.cloudticity.com/epic-ehr-hosting-options-comparison-
which-is-right-for-you
104. RCM data breach response of the top 6 revenue cycle management service
providers in USA - Frigg Business Solution., accessed on May 8, 2025,
https://www.friggp2c.com/rcm-data-breach-response-of-the-top-6-revenue-
cycle-management-service-providers-in-usa/
105. Overview of Authentication Mechanisms | InterSystems IRIS Data Platform
2025.1, accessed on May 8, 2025,
https://docs.intersystems.com/irislatest/csp/docbook/DocBook.UI.Page.cls?
KEY=AAUTHN
106. Certification - Epic Systems, accessed on May 8, 2025,
https://www.epicinfotech.com/certification/
107. Epic Solution - Commvault Documentation, accessed on May 8, 2025,
https://documentation.commvault.com/11.20/epic_solution.html