Epic and Workday in one view
Finance and operations can compare clinical activity with staffing and cost using the records for the same period. Databasin connects Epic and Workday, prepares their relationships and builds the application your teams use together. We handle the source work, historical logic and rollout around the business questions you need to answer.
Clinical activity with staffing and cost
We relate Epic activity to Workday finance and workforce records so departments can investigate the same operating question. The work includes matching organizations, reporting periods and definitions across the two systems.
History matters to that relationship. A staffing review for an earlier period needs the manager, compensation and cost center that applied then. Databasin preserves Workday's effective-dated records and resolves those values for the analysis. Combined with local Epic measures, they give finance and operations a view of activity and resources that corresponds to the period being discussed.
A common basis for analysis
Clinical activity
Prepare Epic encounters and facility records with the local mappings required by the measure being reviewed.
Workforce history
Keep the Workday compensation and organizational assignments that applied during the period the team is examining.
Shared measures
Build calculations across both sources for departments to use in reports, Data Apps and further questions.
Example: How can teams compare periods?
Finance can use a Data App to review clinical activity beside workforce cost for one month. Selecting another month changes the measures and uses the Workday assignments that applied then. A question in plain language can investigate the movement. Its attached SQL lets the reviewer examine the calculation before discussing the finding.
Implementation across both systems
Our team connects Epic and Workday, prepares their historical relationships and builds the application. We work with the relevant owners on definitions and the access design. Those decisions guide the shared views implemented on Databasin.
We include rollout, training and success measurement so departments can use the application in their reviews. After launch, we can run it, provide monthly support hours or stay on call. The prepared records can also serve further applications where the established definitions fit their questions.
What happens next
We would like to hear where your team wants to make progress with data and AI. We can discuss a project you have in mind or explore where Databasin could help with the work.
What happens next
Book a demo
Book a conversation about your organization and the work you want to improve. Questions about where to start are welcome.
Explore the opportunity
We show a working example that answers your business questions, then discuss what it would take to deliver it for your team.
Get the first result
After agreeing the first use case, we implement it with your team. We train the people using it and measure how it performs.
FAQ
Will Epic and Workday continue handling their existing transactions?
Yes. The original systems keep their transaction processes and operational records. Databasin reads the approved data to build analysis and recurring workflows. Its combined application operates alongside the existing Epic and Workday processes.
Can clinical activity and payroll refresh at different times?
Yes. The sources have separate extraction schedules. Clarity normally refreshes overnight, while Workday follows its configured extraction. We account for both when preparing the combined measures and showing the period represented by the view.
What happens to a staffing comparison after a backdated correction?
Databasin uses the entry date and effective date to update the relevant history. A change entered today can therefore correct a record for an earlier period. Subsequent analysis can use the updated value for that period.
Can a combined view include research records as well?
Yes. We can add records from connected sources such as REDCap. The research question determines the periods, relationships and measures to prepare. We also establish which audience is permitted to use the resulting view.
How do you handle a Workday calculation that cannot be extracted?
Our team examines the required logic and implements it in the prepared data if extraction cannot supply it. Its output can then be compared with the business definition before the calculation is used in reporting.
Can the combined application use our Databricks environment?
Yes. We can build the connections and measures around an existing Databricks environment. Databasin can also work alongside Snowflake or Microsoft Fabric. The design follows the platform your organization plans to retain.
Can we retain the Power BI views used by finance?
Yes. Power BI can use the prepared tables through a supported connection. Existing views can remain useful while we implement the relationships and historical logic needed to combine clinical and workforce measures.
Who approves clinical and workforce access?
The relevant source and security owners approve access for your institution. We help specify the connection and required records with them. The implementation uses the permissions granted for the combined application.
Can access to compensation differ from access to activity totals?
Yes. Clinical and workforce owners help establish who may see the records. We configure the selected deployment to apply those permissions. The combined view follows the access established for each audience.
Does the project need a full enterprise model before anyone can use it?
We can start with a defined business use case and the records it requires. The first implementation establishes its measures and application. Further work can reuse or extend that preparation as new questions arise.
Discuss your cross-system questions
We can talk about how your teams review activity, staffing and cost today and what they would like to understand together. The conversation can explore where shared analysis would help and how it would fit your existing systems.