On this page
Key takeaways
- EHR reports read one record type at a time, so a referral, order or recall that never led to care often produces no report line at all.
- Revenue leakage intelligence matches records across types, patient by patient, and checks whether the planned care was completed.
- Analytics answers how the practice performed; revenue leakage intelligence answers which patients need action now and why.
- The EHR stays the system of record; an intelligence layer reads it and staff keep working in it.
- Buyers should judge each tool against its own job: totals and trends for analytics, a ranked and verified patient list for intelligence.
EHR analytics and revenue leakage intelligence answer different questions. EHR analytics, including built-in reports and BI tools on top of the EHR, describes what happened across your records in totals and trends. Revenue leakage intelligence works patient by patient: it matches each referral, order and recall to the visit or procedure that should follow, ranks the patients whose care stalled, and checks whether the care was completed. Most specialty practices need both.
(Revenue leakage intelligence is not the sales-software category called "revenue intelligence", which forecasts deals. Here the subject is care that was planned for patients but never delivered, the category we call healthcare revenue leakage intelligence.)
What can't built-in EHR reports do?
Built-in EHR reports read one record type at a time, so they struggle with two jobs: matching records across types, such as a referral to the visit that fulfilled it or an order to the procedure that closed it, and confirming that care was completed rather than booked. Gaps between records produce no report line.
That is not a flaw in the EHR. An EHR is a system of record: it documents care accurately, supports clinical decisions, produces claims and meets regulatory requirements. It stores each fact where it belongs, and each record is correct on its own. What it does not do by default is ask, every night, whether one record led to the next one it was supposed to.
Why do EHR reports miss patients whose care stalled?
They miss them because each step of the patient journey is created by a different person, in a different screen, often on a different day. A referral coordinator files the inbound fax. A provider signs an order. A scheduler books the appointment. The procedure is documented by the performing clinician, sometimes at another site.
| Record | What a report on it shows | What it cannot tell you alone |
|---|---|---|
| Referral | Referrals received in a date range | Whether the patient was contacted or seen |
| Order | Orders still open | Whether the procedure happened somewhere else |
| Appointment | What is booked, canceled or missed | Whether a canceled slot was ever replaced for that patient |
| Encounter | Visits completed | Which referral or recall the visit satisfied |
| Procedure | Procedures performed | Which order the procedure closed |
| Recall | Recalls past due | Whether the patient is already booked inside the window |
Every row is a reasonable report. None of them, on its own, answers the operational question: did the care we planned actually happen?
Static exports add a second problem. By the time a list is half worked, some patients have booked on their own and others have canceled, so staff call people who are already scheduled and miss people who dropped off after the export.
Why is cross-record matching the hard part?
Matching is hard because the links between records are often implicit. An appointment rarely carries a reference to the referral it fulfills. A colonoscopy performed at an ambulatory surgery center may come back as an outside document, not as a procedure tied to the original order. Local appointment types and order codes differ by location and were never designed to line up.
Good matching usually combines several signals:
- Patient and time window: the same patient, the right kind of event, after the trigger and within the expected interval.
- Code mapping: local order codes and appointment types mapped once to standard categories, so "COLON SCRN 30" and a procedure record for a screening colonoscopy are recognized as the same care.
- Location and provider: where the care was expected and where it happened.
- Staff dispositions: a reason recorded when an order was completed at another facility or the patient declined.
Illustrative example: suppose a practice signs 900 procedure orders in a quarter and a report shows 180 still open. Without matching, all 180 look like work. If matching finds that 70 were completed and documented under a different code and 30 are already booked, the real work list is 80 orders. The formula is simple (open orders minus completed matches minus booked matches), but each subtraction needs cross-record logic. The numbers are round inputs for illustration only.
The model behind this, a trigger, the care that should follow and the evidence that it did, is explained in expected vs. actual events in healthcare.
What is EHR analytics good at?
EHR analytics is good at describing performance. Built-in reporting and BI tools answer questions like these well:
- How many new patients did each location see last quarter?
- What is our no-show trend by appointment type?
- How productive is each provider, in visits or work units?
- How are we tracking on the quality measures we report?
- How has our payer mix shifted?
These are retrospective questions about groups of records. They support board reporting, staffing, payer conversations and quality programs, and nothing here suggests replacing them.
EHR analytics vs revenue leakage intelligence: how do they compare?
| Dimension | EHR analytics | Revenue leakage intelligence |
|---|---|---|
| Primary question | How did we perform? | Which patients need action, and why? |
| Unit of output | Totals, rates, trends | One patient, one open item |
| Time orientation | Retrospective, by period | Current, refreshed on a schedule |
| Data relationships | Usually one record type per report | Matches across referrals, orders, appointments, encounters and procedures |
| Prioritization | Sorting and filtering by the user | Ranked by estimated value, urgency and confidence |
| Who acts | Leaders interpret and decide | A named staff member works a queue |
| Completion | Not tracked per item | Closed when the visit or procedure is documented |
| Typical owner | Analytics, finance, quality | Operations, scheduling, referral and revenue teams |
A report might show that procedure orders converted at a lower rate last quarter. Detection shows the specific patients whose orders are open right now, which are not booked, and which have an outside procedure that should close the order instead. The report informs strategy; detection drives tomorrow's phone calls. Even then, honest reporting treats care completed after detection as correlation with the work, not proof of cause.
Where do reports live in common EHRs?
Every major EHR has built-in reporting and work lists, and practices on the same EHR often configure them differently. What changes from one EHR to another is how the data can be read for cross-record matching:
- athenahealth: Nuvory's athenahealth connection is live. It reads athenaOne data through FHIR R4 and bulk data APIs and opens inside the athenaOne chart and schedule as a SMART on FHIR app.
- eClinicalWorks, ModMed and Epic: Nuvory is designed to work with data from eClinicalWorks, ModMed and Epic through FHIR R4, bulk export and SMART on FHIR where the organization enables it, with scope confirmed during discovery.
- Other EHRs: the same approach applies to NextGen, AdvancedMD, Practice Fusion and others listed on EHR integrations.
How these standards work, from app launch to bulk export, is covered in our guide to SMART on FHIR, FHIR R4 and Bulk Data.
How should buyers evaluate the two?
Judge each tool against the job it claims to do. For EHR analytics, ask about data freshness, measure definitions, drill-down depth and who maintains the reports. For a revenue leakage intelligence vendor, these questions separate an operational tool from a reporting tool with a new label (the full buyer's checklist is in how to choose revenue leakage software):
- What is the unit of output? A chart, or a patient with a reason and an action?
- Does it check the schedule first? Patients already booked should never reach a call list.
- How does matching work across record types? Ask how local codes are mapped and who approves the mapping.
- How is each item ranked? Ask to see the factors, and whether a supervisor can see why.
- What closes an item? Ask what evidence counts as completion and how outside care is handled.
- Who reviews the rules? Rules that touch clinical intervals should be signed off by a clinician at the practice.
- How is value reported? Look for a baseline and language about correlation, not guaranteed revenue.
- What does it read from the EHR, and how? Ask which data is used, how access is approved, and whether staff keep working in the EHR.
Ask Nuvory the same eight questions. The patient opportunity intelligence examples show what its patient-level output looks like. It is an intelligence layer, not an analytics replacement: staff keep scheduling and documenting in the EHR, and the analytics team keeps its reports. Revenue-cycle questions are a separate matter, covered in revenue leakage vs. revenue cycle leakage. More in EHR and data intelligence.
EHR reporting gap checklist
- List the reports your team runs to find open referrals, open orders and overdue recalls.
- For each report, write down which single record type it reads.
- Pick ten open orders and check by hand whether the procedure was completed, here or elsewhere.
- Note how often a booked appointment was later canceled with no new date.
- Record how local order codes and appointment types map to each other, and who owns that mapping.
- Decide who owns items that cannot be matched automatically.
- Agree what counts as completed care for each workflow before measuring anything.
- Ask any vendor whether its output is a chart, a list of totals or a list of patients.
Frequently asked questions
Can we fix this by building better custom reports in our EHR?
Partly. Custom reports can join some record types, and a skilled analyst can get far. The harder parts are keeping code mappings current, checking the schedule before anyone calls, tracking exceptions with reasons and confirming completion every night. Those are ongoing operational processes, not one-time report designs.
Can our existing BI tool do revenue leakage intelligence?
A BI tool can display the results, and an analyst can build some of the joins. The ongoing work is different: mapping local codes, checking the schedule each night, ranking items, assigning owners, recording exception reasons and confirming completion. If those processes exist around your BI tool, it can cover part of the job.
Does revenue leakage intelligence replace our EHR reports?
No. EHR reports and analytics remain the right tools for performance, quality and financial reporting. Revenue leakage intelligence adds patient-level detection and follow-through for planned care that stalled. Many practices feed the counts it produces into their existing reports.
Does an intelligence layer change how our staff use the EHR?
It should not. Staff keep scheduling, documenting and ordering in the EHR. The layer reads the data, finds gaps and gives staff a ranked list. When an appointment is booked or a procedure is documented, the layer sees it on its next run and closes the item.
Is revenue leakage intelligence the same as patient engagement software?
No. Patient engagement tools send messages and help patients book. Revenue leakage intelligence decides which patients need attention, why, and with what evidence, and then checks whether care was completed. The two often work together.