# Epic
## Overview
Use this tip sheet to summarize records from your Epic EHR. You will also be able to perform workflows such as reviewing a quick summary before a visit, generating emergency medicine handoff notes, building a discharge summary automatically, asking medical research questions on records, or automating care notifications for CHF, AKI, or sepsis indicators.
### 1. Authorization of Our SMART on FHIR Application
The organization administrator of Epic Apps will need to approve the “Abstractive Health”\
app from the Epic Connection Hub. For an additional back-end application that provides\
note-sign integration and other functionalities for enterprise clients, there is an additional\
application called "Abstractive Health - Enterprise". The "Abstractive Health - Enterprise"\
enhances the "Abstractive Health" app experience with note sign integration and pulling\
patient schedules in advance.
Please work with the Abstractive Health team to enable the latest version of our\
application in your Epic environment.
Abstractive Health:\
Non-PRD Client ID: 0bc7efac-2536-4d66-998d-d4a718f45303\
PRD Client ID: 5878ab1f-bafd-4d64-85f6-5c29ac3d4337
Abstractive Health - Enterprise:\
Non-PRD Client ID: 0eabf6a1-182c-4355-bb15-1dcc299b4334\
PRD Client ID: ea9c47e4-f99b-47a5-bd2b-cafe09bf2aa3
### 2. Embedding Abstractive Health in Epic
These changes must be implemented by your customer IT team, but we have created a step-by-step instructional guide to help you quickly deploy it within Epic. These steps are also covered in the Galaxy guide titled *"Active Guidelines Setup and Support Guide"*. If you run into issues, we can pull in your Epic TS to also help with the build if needed.
#### Step 1: FDI Record
This defines our launch URL, that we are a SMART on FHIR application, our client-ID for TST and PRD, and that the launch will be embedded in Epic.
Parameters:
● Launch URL:
● Context: SMART on FHIR
● Non-PRD Client ID: 0bc7efac-2536-4d66-998d-d4a718f45303
● PRD Client ID: 5878ab1f-bafd-4d64-85f6-5c29ac3d4337
● Embedded window
#### Step 2: Activity Records
For the embedded window launch, this provides the iframe where the application will appear and defines whether it’s a main pane or sidebar view.
Parameters:
● Main pane view
#### Step 3: Navigator Section
Set a navigator section and a navigator configuration record to link the activity record with the FDI record.
Examples of Navigator options include:
● ED Arrival Navigator
● ED Provider Note Navigator
● ED Discharge Navigator
● Inpatient Handoff Navigator
● Inpatient Discharge Note Navigator
● Outpatient Office Visit Navigator
#### Step 4 (Optional): Menu/Toolbar Button
A menu record that points to the FDI that was built. Please contact the Abstractive Health team for the logo button to display in Epic.
### 3. Additional HL7 v.2 workflows supported (optional)
We can provide a faster experience with our product through pulling the clinical records at the time of patient check-in or admission. We do this through back-end system integration with APIs via an HL7 interface. We limit access to your data by only requesting data from the locations where we will be summarizing the medical chart for clinicians.
Once we receive the patient demographics and IDs for our target patients, we use FHIR integration and our internal HIE interconnections to pull the following content to build our summaries. The full flow might look like the following:
Diagram - Visualization of the Integration between Epic and Abstractive Health
HL7 v.2 integrations supported are ADT and SIU inbound feeds via our interface engine with Mirth. We will establish a VPN endpoint and TCP listener of your port to receive inbound HL7 messages. Please request the *"Abstractive - Epic Implementation Handbook"* by emailing for more information.
### 4. Abstractive Health will now be available as an icon in your instance of Epic. Upon clicking the icon, you will be prompted to log in or create your account in Abstractive Health.
Your Epic account login will be linked to Abstractive Health, so you will not need to log in again in the future.
### 5. Once you log in or create your account, the app will begin summarizing the notes and a summary will be available to review alongside your navigator workflow in Epic.
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://resources.abstractivehealth.com/ehr-integration/epic.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.