Epic data for clinical and business decisions
Epic Clarity and Caboodle data can help your teams examine clinical activity, investigate financial changes and answer research questions. We prepare the connections and local definitions so people can ask questions, use shared Data Apps and automate recurring reviews. Our team implements the work from source access through rollout.
Epic data your teams can use
Design, Build, Run
We take responsibility for the work from defining the outcome through implementation and ongoing support.
Design
We define the outcome, current processes and expected return with your stakeholders. A working example shows how Databasin would answer your business questions.
Build
We get your first use case live in 90 days. Communication, rollout, training and success measurement are included in the work.
Run
Choose the help you need after launch. We can run the solution for you, provide monthly support hours or stay on call.
Results from customer work
- 20+ systems unifiedDatabasin brought WashU Medicine's financial data together.
- Infrastructure costs at 1/3 of the traditional approachWashU Medicine's result from changing its data infrastructure.
18%
Higher grant proposal success
Measured at a research institution working with Databasin.
“What used to take weeks or sometimes even months now happens in minutes.”
Support for ongoing Epic analysis
Clarity extraction
Use Clarity as the primary reporting source for the intended analytical work.
Caboodle access
Include Caboodle subject areas where the institution has implemented the required coverage.
Schema history
Check the schema version and time recorded when an extract arrived.
Clinical rules
Define encounter filters, clinical code mappings and rules for reconciling payments.
Shared dimensions
Join the relevant patient, provider, encounter and facility records for analysis.
Governed views
Serve the prepared records through views with access established for their audience.
Example: Epic data in daily work
Research cohorts
Ask about encounters from a selected period, then examine their distribution by unit and disposition in the prepared cohort.
Revenue-cycle reviews
Examine the period's charges, payments and denials together. Follow a movement in the measure into its contributing records.
Clinical operations
Review activity across departments and compare length of stay, using consistent encounter, provider and facility definitions for the measures.
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
Does Databasin have a dedicated Epic connector?
Yes. The integration grew from production work at WashU Medicine, where our team created the original Epic connector. It covers Clarity extraction and supports Caboodle where present. Implementation includes the local mappings and governed models needed to use those records in your institution.
Can we keep using Epic Reporting Workbench?
Yes. Reporting Workbench can continue to serve existing Epic reporting. Its CSV exports can also feed Databasin's raw data layer. We prepare reusable views when an investigation needs retained history or data from other systems, with the report's available fields and refresh time determining its use.
Can FHIR supply everything we need from Epic?
FHIR supplies standard resources, which may not cover your institution's full custom data model. Bulk research cohorts and revenue-cycle analysis can still need Clarity. We use FHIR as a complementary source where its records fit the question and retain the broader extraction route where needed.
Will analytical queries run against Chronicles?
Our primary analytical extraction targets Clarity. Chronicles serves live clinical operations and feeds Clarity through its nightly refresh. We design analysis around the reporting sources so a research question or business review does not depend on querying the live operational database directly.
Can this support a same-day operational decision?
The answer depends on when the required source records arrive. Clarity normally reflects the previous day after its nightly refresh. We establish the timing a decision needs and examine whether an available approved feed can supply the necessary records sooner.
How do we arrange permission to read Epic data?
Your institution grants read access. Our team joins IT and security to explain the records needed, where they will be stored and how the application will query them. We cover the model-provider route too, then configure the connection and audience access within those decisions.
Can Databasin run in our Azure environment?
Yes. Databasin supports installation in your Azure tenant, and we establish the model endpoints and data boundary for that environment. It also works alongside Databricks, Fabric or Snowflake. Databasin is HIPAA-ready, with a BAA available for regulated work.
Is Databasin formally affiliated with Epic?
Databasin has no formal agreement with Epic. Our team built the original connector at WashU Medicine and has implemented Epic data work in health systems. Source authorization remains with the institution. We use that authorized access to build the analytical views and applications.
Talk about your Epic data
We would be glad to hear where Epic data could help your team make progress. We can discuss a research question, an established review or an idea you are exploring, and explain where Databasin fits.