We were building on one database before it was cool.

A single record and a single executable across applications
At Epic, all applications are developed in-house. In Epic, the patient is always at the heart. Clinical data is organized in a single, integrated record for each patient – across inpatient, post-acute, GP/ambulatory, community, and home settings – giving providers a comprehensive, up-to-date record. Epic's applications operate together without the need for interfaces. This integration around one record greatly improves patient safety.

A single version worldwide
Epic's code base is the same across all customers worldwide. Functionality unique to a country or region is turned on by configuration settings in each locale. Examples of such functionality in use and in development are Dutch billing (DBC), UK Patient Administration Systems (PAS), Canadian billing, and Singaporean revenue cycle upgrades.

The benefits of one code base are many:
  • Software upgrades are available for all countries at once – saving time and development costs.
  • By avoiding redundant development and retrofitting per country, Epic software developers have more time to innovate.
  • Healthcare providers in all regions benefit from development done for any region.
  • The worldwide clinical community will lead to sharing of discoveries and improve quality across the globe.

Healthcare Data Management System A foundational component of Epic is the open Chronicles Extended Relational Database Management System, the high-performance data engine at the heart of our integrated product suite. Chronicles has no built-in capacity limits. It supports thousands of concurrent users and millions of records while still providing excellent response times.

Chronicles drives Epic's outstanding response times and scalability, giving us the edge in serving the largest, most complex healthcare organizations.

Enterprise Master Person Index Identity EMPI keeps your database clean by eliminating duplicate records and by actively preventing users from creating them in the first place. Uniting demographic, registration, and encounter data from all of your Epic and non-Epic systems, Identity compares a broad sample of identifying information to evaluate patient records. It then applies multiple logical comparisons that account for misspellings, typos, nicknames, names that sound alike, and even maiden names. Streamlined utilities make it easy to merge records when duplicates are found and to unmerge patient records when necessary.

Identity can organize IDs from external systems, allowing you to cross-reference patient records and access them using their medical record numbers from external or legacy systems.