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.
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.
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.
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.