- Home
- Integrations
- Epic
Epic Revenue Intelligence, Scoped Department by Department
For ambulatory departments on Epic, Nuvory is designed to find referrals, orders and recalls that never became completed care, starting with the departments your Epic analysts and security team approve.
What is Epic revenue intelligence?
Epic revenue intelligence is finding care that was referred, ordered or recalled in Epic but never completed, and ranking it for staff in the departments in scope. Nuvory, healthcare revenue leakage intelligence from HealthArc, is designed to work with Epic through FHIR R4 with US Core resources and FHIR Bulk Data export, with SMART on FHIR launch from the chart where your Epic team enables it.
How does an Epic organization start?
Epic connections are set up with each organization's Epic team, so most early work is agreeing scope and approvals. Your team supplies the FHIR endpoint, the approvals and the departments in scope. Timeline is confirmed during discovery.
- Pick departmentsChoose a few departments and locations with clear owners and measurable baselines.
- Security reviewYour Epic analysts and security team review and approve access.
- Population loadAbout two years of history is loaded through FHIR Bulk Data export.
- Map departments and codesHealthArc maps departments to locations and local codes to rules.
- Clinical sign-offA clinical reviewer in each department approves its rules after spot-checking real patients.
- Nightly updatesNightly incremental updates through the FHIR APIs, authorized with SMART Backend Services; chart launch is added where your Epic team enables it.
Scope a department pilot with your Epic team
We will walk through data, approvals and the departments in scope.
Where do patients fall between Epic departments?
Between work queues. Large organizations on Epic have many departments, schedulers and queues, and a patient can sit in one while another department assumes it is handled. Epic referral leakage is the common example: a referral is placed to a specialty department, waits in a queue, and the patient is seen somewhere else or not at all.
- Internal referrals Referrals between departments that never become a visit.
- Diagnostic orders Imaging, testing and procedure orders open past their window.
- Follow-up intervals Chronic and surveillance patients overdue with nothing booked.
- Cancelled procedures Procedure slots lost when a cancellation is not rebooked.
Which Epic FHIR resources does Nuvory read?
FHIR R4 APIs with US Core resources for clinical data, FHIR Bulk Data export for population loads, and nightly incremental updates through the FHIR APIs, authorized with SMART Backend Services. Exact resources are agreed with your Epic team.
| Data | FHIR resource | What Nuvory uses it for |
|---|---|---|
| Patients | Patient | Identity and contact details |
| Providers | Practitioner, PractitionerRole | Ordering and rendering providers and where they practice |
| Departments and sites | Location, Organization | Departments in scope and outside destinations |
| Scheduling | Appointment | Bookings, cancellations and no-shows |
| Visits | Encounter | Completed visits and attribution |
| Referrals and orders | ServiceRequest | Referrals and procedure orders |
| Completed procedures | Procedure | Closing open orders |
| Problems | Condition | Inputs to recall and care-management rules |
| Coverage | Coverage | Payer and plan context |
What does each department see?
Findings are grouped by department, so service-line leaders and schedulers see only their own work.
Referral conversion
Epic referral leakage at patient level: referrals with no contact or no visit.
Learn moreOpen orders
Ordered procedures and tests never scheduled or completed, by department.
Learn moreOverdue follow-up
Surveillance and chronic patients past due with nothing booked.
Learn moreNext best action
Epic patient opportunity intelligence: one ranked task per patient.
Learn moreStart with the departments that matter most
See department-level findings and how teams work them.
How does Nuvory fit alongside Epic work queues?
Nuvory sits alongside Epic, not inside its scheduling workflow. Staff keep booking in Epic; Nuvory reads, ranks and checks completion on the next run. Where your Epic team enables SMART on FHIR launch, staff open a patient's open items from the chart. Our guide to FHIR, bulk data and SMART on FHIR explains the difference between backend services and chart launch.
Departments such as cardiology, nephrology and pulmonology are common starting points because orders and follow-up intervals drive much of their volume. Organizations that want to see where patients go outside the network can add Network Intelligence on Enterprise. Affiliated practices on athenahealth or NextGen can be included in a multi-EHR scope.
What will your security team want to see?
Ask for these up front, along with the access model. Full detail is on the security page.
| Control | What it means |
|---|---|
| HIPAA and BAA | Nuvory is built for HIPAA, and HealthArc signs a business associate agreement with every customer. |
| SOC 2 Type II | HealthArc's platform is covered by a SOC 2 Type II report from an independent auditor. |
| Encryption and isolation | Data is encrypted in transit and at rest, and each practice's data is kept separate. |
| Role-based access and audit | Staff see only the features and locations their role needs, and every patient view is audited. |
Other EHRs Nuvory works with
Epic is a trademark of its owner. Its use here describes compatibility only and does not imply endorsement or partnership.
Further reading
SMART on FHIR, FHIR R4 and Bulk Data: an EHR integration guide for practice leaders
What practice leaders should know about FHIR R4, US Core, Bulk FHIR export, SMART on FHIR app launch, HL7 v2 and X12, and what to ask any EHR vendor.
EHR & Data IntelligenceEHR Analytics vs. Revenue Leakage Intelligence: What Built-In Reporting Misses
EHR reports describe records one type at a time. Revenue leakage intelligence matches referrals, orders and recalls to the visits and procedures that should follow, and checks whether care was completed. Here is where each fits.
Questions, answered
More in our FAQ, or ask our team.
Is Nuvory an Epic app?
Nuvory is designed to work with Epic data through FHIR R4 and Bulk Data APIs, and can launch from the chart as a SMART on FHIR app where your Epic team enables it. Epic is a supported EHR; scope is confirmed during discovery.
Who needs to approve the connection?
Your Epic analysts and security team, working from your organization's FHIR endpoint and the departments in scope.
Does Nuvory change Epic work queues or schedules?
No. Staff keep working in Epic. Nuvory identifies and ranks open items and confirms completion on its nightly run.
Can we start with one department?
Yes. Organizations can scope a few departments and locations first. Scope is agreed with your Epic team during discovery.
How is Epic revenue intelligence measured?
Care completed after detection, compared with a baseline for each department. It is reported as correlation with outreach, not proof of cause.
Can Nuvory show where referred patients go instead?
With claims or HIE feeds connected, Network Intelligence shows outflow by destination for leadership on the Enterprise plan. It is a leadership view, not a call list.
Bring Epic referral and order leakage into focus
Book a demo to plan scope with your Epic team.