Why Different

What it does.What it will not.

A design that looks correct is worse than one that visibly fails, because only the second one gets caught. Most of the engineering here exists to keep failures visible rather than tidy them away.

 
What it does
What it will not do
01
Resolves each concept to a field in your schema, with its timing and a stated reliability.
Substitute the nearest available field when the right one is missing. An unresolved reference is reported as unresolved.
02
Declares every node and edge in the causal graph, then derives the adjustment set from it.
Claim the graph is correct, or that the effect is identified. Both remain your judgment to make.
03
Names the quantity being estimated and states what the analysis has to account for.
Prescribe a statistical method, or run one. Choosing the estimator stays with the analyst.
04
Specifies what to measure, over what window, and against which definition.
Produce effect estimates, participant counts, or any figure it did not read from your data.
05
Checks each bias mechanism and names the diagnostic to run once the data is pulled.
Assert the design is unbiased. What cannot be resolved by design is written down as unresolved.
06
Raises malformed or missing output where it happens, with the record of where it came from.
Quietly repair its own output into something that reads as complete.
Your Data

Portable design.Your mapping.

The design layer is deliberately independent of any one database. Mapping runs against a catalog of your schema alone: table names, column names, and data types, holding no patient record. The catalog is built from a published data-model specification or from a schema description you upload, so the check runs in environments where the records themselves cannot be touched. The engine identifies the field each design variable would come from, reports the ones it cannot resolve rather than guessing, and hands back a mapping your team executes.

A catalog for OMOP CDM v5.4 is built in, covering 39 tables and 432 columns. Any other source is supported by uploading a description of its schema, which is admitted only if it carries schema metadata and no record-level content.

Access

Demo ourservices.

TriEmulate is enterprise infrastructure under active development and is not yet generally available, but it runs today and can be walked through end to end on a question of your own. A United States provisional patent application covering the system was filed in September 2026. If you work on causal inference in health data, bring a question and we will put it through.