Overview¶
Abacus One Group Integration Services is a read-only service. It collects the documentation our medical coders and auditors need from your Epic system, for the visits you want us to load, such as emergency department (ED) visits.
Where to start¶
-
Epic analysts and integration teams
Follow the integration guide, then check Data accessed.
-
Security and privacy reviewers
Read Data handling and Authentication and network.
-
HIM and coding leads
Read How it works, below, then step 1 of the integration guide.
How it works¶
- You choose the visits. Your Epic analysts build a patient list, and the service reads it at regular intervals to find each patient's visit.
- The service waits until the chart is ready to code. Your HIM or coding lead decides when that is.
- It retrieves the visit's documentation: clinical notes, orders, medication administrations, results and flowsheet data.
- Our platform receives the chart, ready for our coders and auditors. If the chart changes over the next few days, it receives the update.
What it doesn't do¶
- It doesn't write to Epic. The app has read and search APIs only.
- It doesn't have users at your organization. There is no sign-in, and it doesn't launch from Epic.
- It doesn't run on your network. It calls your Epic FHIR endpoint over the internet.
- It doesn't collect charts beyond the visits you choose. It retrieves documentation for those visits, not for the same patients' other visits. Data accessed has the detail.