Built by an AMC,
for AMCs.
Epic, Workday, and everything else feed one governed lakehouse with one source of truth, at a fraction of the cost. It was co-created at Washington University School of Medicine, where it runs in production today.
"No commercial solution existed at AMC scale. Epic data pipelines were failing and research operations were at risk. So we built one."
Co-created at Washington University School of Medicine's Institute for Informatics, Data Science & Biostatistics (I2DB)
Epic, Workday and the rest of your systems.
Academic medical centers run on Epic for clinical, Workday for finance and HR, and dozens of other systems for everything in between. Databasin connects all of them.
Your Epic data, fully unleashed
Chronicles, Clarity, and Caboodle each have their own access patterns and refresh schedules. Their schema complexity differs too. Databasin handles all three through one governed pipeline.
- Natural language queries against governed gold data, no Clarity specialist required
- Schema versioning at bronze means pipelines adapt to Epic updates, not break
- REDCap, FHIR, and research databases in the same governed environment
- PHI stays in your Azure tenant: HIPAA-ready by architecture
Your Workday data, finally free
Workday's reporting requires specialists most AMCs don't have, and its effective-date logic silently corrupts historical reports. Prism costs six figures and still needs a warehouse.
- Effective-date resolution happens at the connector. Historical snapshots are always accurate
- One governed lakehouse joins Finance and HR data and ends the reconciliation debates
- Replaces the analytics add-on, the connector stack and the BI tool, billed by the minute
- One headcount number that Finance and HR both agree on
Everything else, unified
REDCap, Box, Azure, Databricks, Snowflake, SalesForce, Oracle, ServiceNow. Every system your AMC runs on, connected to the same governed lakehouse as Epic and Workday.
- Medallion architecture: bronze (raw), silver (transformed), gold (governed analytics)
- Databasin One answers natural language queries from the governed gold layer only
- Semantic model builder for institutional metric definitions
- Private install in your own Azure tenant, or hosted
AMCs are paying $245K–$390K/yr to work around their own systems
Between Prism licenses, third-party connector stacks, BI tools, and the Clarity specialists required to keep it all running, academic medical centers are spending a quarter million dollars a year before a single insight is produced. Databasin replaces that entire stack.
What changes for the CRIO and the CFO.
Research operations that don't depend on Epic experts
The data is in Epic. Getting it into a research-ready format requires a Clarity specialist, an IT queue, and three weeks. Databasin was built at WashU Medicine's I2DB precisely because this bottleneck was killing research operations.
- Epic connector handles Chronicles, Clarity, and Caboodle through one pipeline
- Because schema changes are absorbed at bronze, research pipelines don't break on tenant updates
- REDCap, FHIR, and research databases sit in that same governed environment
- Natural language queries for research teams who don't know Clarity table names
Financial and operational reporting that everyone agrees on
Your finance team builds models from Epic exports, Workday data, and manually reconciled spreadsheets. The CFO's revenue number doesn't match the CMO's. Month-end close requires a team of analysts just to reconcile the discrepancy.
- Workday and Epic financial data share one governed lakehouse, so reconciliation is automated
- Databasin enforces one definition of charges, payments, and adjustments
- Board and investor reporting from a single trusted gold mart
- Dashboards that operational leaders actually trust and use
Running in production at WashU Medicine.
Today Databasin is the production data infrastructure for clinical research and operations at WashU Medicine, KU Medical Center, and St. Francis Medical Center.
"The institutional origin of Databasin isn't a marketing story. It's the reason the product actually works. We built it because we needed it, in an environment where failure had real consequences."
Jake Gower, Co-Founder & CEO, Databasin
See it on your own data, with Chris.
Chris Lundeberg, Co-Founder & CPO, leads the technical demos, not a sales engineer reading from a script. Bring your current stack, your constraints, and your hardest data problem.