Centers that automate wRVU per FTE stop joining exports by hand. They load Epic professional billing transactions and Workday position data into one governed place, link each provider to a worker record, assign activity to the department that was effective on the service date, and divide by an agreed clinical FTE. The report then refreshes on a schedule for trailing 12 months, and analysts spend their time on exceptions instead of assembly.
A VP of Finance asks for wRVU per FTE by department for the last twelve months. Two analysts export professional billing from Clarity, export positions from Workday, match names in a spreadsheet, fix the transfers by hand and send a workbook two weeks later. When a chair questions one department, the work starts over.
In Databasin's field note on the AMC data tax, this report typically takes one to three weeks, faculty productivity for a promotion committee two to four weeks, and departmental contribution margin one to two weeks. Those are typical times observed in that field note, not measured results from a single customer.
Why does the report take weeks?
The numerator lives in Epic and the denominator lives in Workday. Neither system knows the other's identifiers, and both change over time: providers move between departments, FTE allocations change mid-year, and charges are corrected after the month closes. A manual process repeats every one of those decisions each time someone asks.
Which wRVUs count?
Work RVUs come from the Medicare physician fee schedule, which assigns each procedure code a work component alongside practice expense and malpractice. Most centers take the wRVU value per CPT code for the service date, multiply by units and apply modifier rules agreed with compensation and revenue cycle.
Decide and write down:
- Which fee schedule year applies (service date or posting date).
- How modifiers, assistant-at-surgery and split visits adjust credit.
- Whether voided and corrected charges are netted by service date.
- Which provider gets credit: billing provider, performing provider or supervising physician.
In Clarity, professional billing transaction tables carry the procedure, service date and billing provider, and at many sites a work RVU value. Confirm locally which fields your build populates before relying on them.
Which FTE goes in the denominator?
Workday holds paid FTE on positions. A physician at an academic center rarely spends all of it on clinical work: research, teaching and administrative time reduce clinical FTE. Many centers keep clinical FTE allocations in compensation plans or spreadsheets outside Workday.
Use clinical FTE for productivity comparisons and say so on the report. If the allocation lives outside Workday, load it as its own governed table with effective dates rather than retyping it into each workbook.
How do you join Epic providers to Workday workers?
Epic identifies providers by its own provider record; Workday identifies workers by employee ID. A crosswalk, often keyed on NPI and maintained by credentialing or the medical staff office, links the two. Treat it as a governed table with an owner, and report the providers who appear in billing without a Workday match.
Which department does the work belong to?
Assign each charge to the department that was effective for that worker on the service date, not the department today. Workday's effective-dated history makes that possible; a current-only export moves last year's activity into this year's organization. Map Workday cost centers or supervisory organizations to the departments leaders recognize, and keep that mapping versioned so a reorganization does not rewrite history.
How do you validate the first automated run?
Rebuild one closed quarter and compare it with the report leaders accepted. Investigate differences provider by provider: crosswalk gaps, transfers, corrected charges and FTE changes explain most of them. Record each agreed treatment, then extend to trailing 12 months.
Where does Databasin fit?
Databasin was built at Washington University School of Medicine, where finance teams needed Epic and Workday on one source of truth. It extracts Clarity, extracts Workday's full effective-dated history, and applies the shared definitions (wRVU rules, clinical FTE, department mapping) once in a governed layer. The report runs on a schedule and lands as a dashboard, a Data App or a briefing in email or Teams, and anyone can ask follow-up questions in plain English and see the SQL behind the answer. Our team implements the connections, the crosswalk and the first reconciled quarter with your finance and compensation staff.
Example: one provider, one quarter
In this illustrative case, a physician transfers from Cardiology to Internal Medicine on 1 February.
| Month | wRVUs from Epic | Department on service date | Clinical FTE |
|---|---|---|---|
| January | 410 | Cardiology | 0.8 |
| February | 380 | Internal Medicine | 0.6 |
| March | 395 | Internal Medicine | 0.6 |
A current-only export puts all three months in Internal Medicine at 0.6 FTE. The effective-dated version credits January to Cardiology at 0.8 and the rest to Internal Medicine, which is what both chairs expect to see.
Checks for a trusted wRVU per FTE report
- Write the wRVU rulesFee schedule year, modifiers, credited provider and treatment of corrections, signed off by compensation and revenue cycle.
- Agree the FTEClinical or paid, its source and its effective dates.
- Own the crosswalkName who maintains the provider to worker link and review unmatched providers monthly.
- Reconcile one quarterMatch the accepted report before automating the trailing 12 months.
Sources
Centers for Medicare & Medicaid Services, Physician Fee Schedule, accessed 2026 · cms.gov/medicare/payment/fee-schedules/physician
Workday, Concept: Effective and Entry Dates, accessed 2026 · doc.workday.com
Discuss your productivity reporting
We can talk through the reports your finance team rebuilds every month and what it would take to run them from Epic and Workday on a schedule.