Attention A T users. To access the menus on this page please perform the following steps. 1. Please switch auto forms mode to off. 2. Hit enter to expand a main menu option (Health, Benefits, etc). 3. To enter and activate the submenu links, hit the down arrow. You will now be able to tab or arrow up or down through the submenu options to access/activate the submenu links.

VA Technical Reference Model v 24.4

Epic Cadence Enterprise Scheduling Software
Epic Cadence Enterprise Scheduling Software Technology

General InformationGeneral Information help

Technologies must be operated and maintained in accordance with Federal and Department security and privacy policies and guidelines. More information on the proper use of the TRM can be found on the TRM Proper Use Tab/Section.

Website: Go to site
Description: Epic Cadence Enterprise Scheduling Software is a mobile and desktop application that tracks patient throughput at each stage of the appointment and care process. This technology is designed to help scheduling staff and clinicians ensure that patients are scheduled in a timely manner with the appropriate resources. Appointments can be scheduled by clinic staff, by affiliated providers, or by patients themselves directly from the patient portal.

All data is housed within Microsoft Azure Government Cloud Services, which is utilized as an Infrastructure as a Service (IaaS). Users access the software through Citrix connections. Epic utilizes InterSystems Cache and Microsoft Structured Query Language (SQL) Server. InterSystems Cache is used as the foundation of Epic`s operational database, which handles reads and writes to the database from the end user applications. Microsoft SQL Server is used as the foundation for Epic`s analytical reporting environment. This allows for scheduling performance to be reported. Knowledge Based SQL (KB_SQL) is not used as a Database Management System (DBMS), but as a component of Epic`s Extract, Transform, and Load (ETL) process. Microsoft SQL Server is used for the DBMS.

Epic is compatible with Storage Area Network (SAN) or Operating System (OS)-level encryption. Users have the option of using the encryption capabilities provided by InterSystems Cache using Advanced Encryption Standard (AES) 128, 192, or 256 bit. Transparent Data Encryption (TDE) is available with Microsoft SQL Server.

Note: There is no dedicated webpage for this technology.

The TRM decisions in this entry only apply to technologies and versions owned, operated, managed, patched, and version-controlled by VA. This includes technologies deployed as software on VMs within VA-controlled cloud environments (e.g. VA Enterprise Cloud (VAEC)). Cloud services provided by the VAEC and those controlled and managed by an external Cloud Service Provider (i.e. SaaS) are not in the purview of the TRM. For more information on the use of cloud services and cloud-based products within VA, including VA private clouds, please see the Enterprise Cloud Solutions Office (ECSO) Portal at:

This entry covers the Desktop Edition of this technology and not any mobile versions. Please note that the implementation of mobile technology applications that operate on Mobile Operating Systems must be reviewed and approved by the Mobile Technology and Endpoint Security Engineering Team:
Technology/Standard Usage Requirements: Users must ensure their use of this technology/standard is consistent with VA policies and standards, including, but not limited to, VA Handbooks 6102 and 6500; VA Directives 6004, 6513, and 6517; and National Institute of Standards and Technology (NIST) standards, including Federal Information Processing Standards (FIPS). Users must ensure sensitive data is properly protected in compliance with all VA regulations. Prior to use of this technology, users should check with their supervisor, Information Security Officer (ISO), Facility Chief Information Officer (CIO), or local Office of Information and Technology (OI&T) representative to ensure that all actions are consistent with current VA policies and procedures prior to implementation.
Section 508 Information: This technology has not been assessed by the Section 508 Office. The Implementer of this technology has the responsibility to ensure the version deployed is 508-compliant. Section 508 compliance may be reviewed by the Section 508 Office and appropriate remedial action required if necessary. For additional information or assistance regarding Section 508, please contact the Section 508 Office at
Decision: View Decisions

Decision Source: TRM Mgmt Group
Decision Process: One-VA TRM v18.10
Decision Date: 10/17/2018 at 13:07:47 UTC
Aliases: Epic
Introduced By: TRM Request
Vendor Name: Epic, Inc.
- The information contained on this page is accurate as of the Decision Date (10/17/2018 at 13:07:47 UTC).