OHDSI Global Symposium 2026
The OMOP-native clinical research platform. Point ATLAS at it.
CuRE is the OMOP-native clinical research platform: one governed record from EHR ingest to submission-grade evidence, built so the OHDSI tools you already trust plug straight in. Not an export to OMOP at the end — OMOP underneath, from the first record.
Booth — OHDSI Global Symposium, Oct 20-22 2026, Hyatt Regency New Brunswick
Come and run it yourself, or start below without waiting for October.
Three ways to start
Try it, connect it, or talk to us
Nothing here needs a sales conversation first. The demos run in your browser, the source surface is documented, and the calendar is open.
Try it now
Run the engines yourself
Every engine has an in-browser demo that runs on synthetic data, client-side, with no login and nothing to install. Start with a cross-app journey to see one record move between products, then open the individual engines.
Open the cross-app journeysPoint your ATLAS at CuRE
CuRE Conduct is a CDM source
Conduct exposes an OHDSI WebAPI-compatible source surface — source registration, vocabulary search, concept-set resolution, and CDM results summaries — so a stock ATLAS instance can register CuRE as a source rather than replacing it.
How it worksTalk to us
Book a walkthrough
Pick a time before the symposium and we will run the track that matches what you already run — or find us at the booth and we will run it there. Either way you leave with the demo link, not a brochure.
Request a demoOpen a single engine
Each of these is the same in-browser demo shown at the booth — synthetic data, client-side, no login.
Point your ATLAS at CuRE
A WebAPI-compatible source surface, not another export
Most vendors in the hall will tell you they export to OMOP. CuRE Conduct speaks the protocol your tools already speak: it exposes an OHDSI WebAPI-compatible source surface, so a stock ATLAS instance can register CuRE as a CDM source and work against it the way it works against any other source you maintain.
What a stock ATLAS gets
- Source registration — CuRE Conduct appears in the source list alongside the CDMs you already run.
- Vocabulary search — concept lookup resolves through the same surface, against the vocabulary loaded in Conduct.
- Concept-set resolution — a concept set expands against Conduct's vocabulary, so the definition you built elsewhere means the same thing here.
- CDM results summaries — the results the ATLAS UI reads to describe a source come back from Conduct.
At the booth, and after
At the booth we will be running an ATLAS front-end against CuRE Conduct on synthetic data, including cohort generation triggered from ATLAS — the whole round trip, on the table, in under a minute.
After the symposium we are opening a hosted synthetic endpoint so you can point your own ATLAS at it from your own environment, without moving any of your data.
Four tracks
What you run today → what CuRE adds
The booth demo is cut four ways from one story on one synthetic record. Find the row that describes your stack, and that is the walkthrough you get.
Track
What you run today
What CuRE adds
The ATLAS shop
Academic informatics
What you run today
ATLAS and WebAPI against a CDM you build and maintain yourself, with governance, hosting, and access control handled outside the tooling.
What CuRE adds
Keep your tools. Conduct registers as a source in the ATLAS you already run, so vocabulary search and concept sets resolve against a CDM that carries tenant isolation, an audit trail, and hosting with it.
The registry operator
Registries, foundations, disease networks
What you run today
Center data reaching the registry as extracts, spreadsheets, and re-entry into a portal — reconciled by hand, and mapped to a common model at the end, if at all.
What CuRE adds
One governed record across centers, OMOP from day one: EHR ingest, mapping, the eCRF, registry lifecycle, and patient-reported outcomes on the same substrate instead of five systems reconciled nightly.
The methods researcher
Epidemiologists, HADES users
What you run today
HADES packages assembled into a Strategus module and executed on infrastructure you provision, with reproducibility reconstructed after the fact from scripts and notes.
What CuRE adds
The same methods and the same cohort definitions, with a reproducibility manifest and an inspection-ready evidence package produced around the run rather than assembled afterwards.
The pharma RWE or safety team
RWE, pharmacovigilance, QRM
What you run today
Signal detection reading from a safety database that sits apart from the interventional stack, so observational and trial evidence never meet on one record.
What CuRE adds
Observational and safety work computed directly on the OMOP data your interventional systems cannot see — the same governed record the trial, the registry, and the analysis all read from.
All booth data is synthetic. Every demo on this page, on the booth screen, and on the ATLAS front-end runs on generated data. No real patient data, no production tenant, and no protected health information is anywhere near the booth.
Find us in New Brunswick
Book a walkthrough before the symposium, or tell us which track you want and we will have it queued up when you reach the table.