![]() Differences between Epic Hyperspace and Clarity The two Epic Clarity databases have the most usable research data. SHC takes the operational Clarity data and converts it to an operational Enterprise Data Warehouse (EDW) with a number of different subject marts. Stanford researchers do not have access to Caboodle for research purpose at this time. LPCH has an advanced implementation of Caboodle and SHC has an early implementation of Caboodle. The two hospitals have different Epic ecosystems. For example, LPCH has a MSSQL Clarity and SHC has an Oracle Clarity. ![]() Chronicles is a non-relational database that sends data to Clarity, which is a relational database, and is used for advanced reporting. Much of the data that is stored in the Chronicles database gets copied over to Clarity, which is a relational database that allows analysts to create more detailed and complex reports. Chronicles is the main database that runs much of the Epic software. When a nurse, doctor, therapist, or administrative staff launch Epic, the front-end software that is presented to them is called Hyperspace. Epic Hyperspace is configured to display different menus, tasks, and options to users depending on their specific roles. ![]() Epic Clarity contains data from the clinics that are part of the University Healthcare Alliance and Lucile Packard Healthcare Alliance.Ĭlinicians at the hospitals interact with the product Epic Hyperspace. Epic Hyperspace is not a clinical module in itself, but rather the application client that is presented to users of most areas of Epic. The two hospitals use Epic for patient care and share Epic Clarity data with SoM. STARR has access to electronic health record (EHR) data from the two hospitals, the Adult Hospital (aka Stanford Health Care) and Children’s Hospital (aka Lucile Packard Children’s Hospital).
0 Comments
Leave a Reply. |