Patent Pending  ·  OHDSI 2026 Submission

Cross-site data consistency
for federated RWE.

Hospitals across your network can use the same code and mean different patients. Vercori finds that problem before your study runs.

Zero Patient records leave your site
Before The study runs, not after it fails
Tamper-evident Audit record of every comparability check

Same code.
Different patients.
Across every site.

Common data models standardize how data is structured. They do not standardize what clinicians mean when they record a diagnosis.

One hospital requires a confirmed test before coding a condition. Another codes it on clinical judgment alone. A third applies a different threshold entirely. All use the same concept ID. All pass every standard data quality check.

But when you combine them in a study, you are combining different patient populations and you will not know it from the data.

The result is a study that looks clean and produces a number that is wrong.

What the data shows

Hospital A

Concept ID 45766164

✓ Passes data quality checks

Hospital B

Concept ID 45766164

✓ Passes data quality checks

Hospital C

Concept ID 45766164

✓ Passes data quality checks
Looks clean. Ready to combine.

What is actually happening

Hospital A

Echo-confirmed LVEF ≤40% required before coding

Hospital B

Clinical judgment alone. No confirmatory test required.

Hospital C

Different EF threshold. Different patient profile captured.

Three definitions. One concept ID.

Illustrative scenario · HFrEF · Based on Gluckman et al., Clinical Cardiology 2024

We find the gap.
We document it.
You run a better study.

01

Each site runs a local analysis

No software to install on your end. Each site in your network analyzes its own CDM instance locally. No patient records go anywhere.

02

Only a fingerprint is transmitted

Each site sends Vercori a statistical summary, a semantic fingerprint, of how it defines each concept. That is all we receive.

03

We compare across all sites

Vercori compares fingerprints across your entire network, across six measurable dimensions per concept, and identifies where sites diverge.

04

You receive a documented report

Every concept is rated, every divergence is explained, every reviewer decision is recorded in a sealed audit log. Ready for your submission package.

What you receive

A report for each concept in your study. Each one is rated: consistent across sites, divergent with a known explanation, or divergent and needing clinical review.

Every decision is documented by a qualified reviewer and recorded in a sealed audit log. Ready for your submission package.

Attach it to your submission. Reference it in your methods. Use it to answer the question: how do you know your sites were measuring the same thing?

What you get that a
data quality dashboard cannot.

01

Know before you commit

You do not have to hope your sites agree. Before a single result is generated, Vercori shows you exactly which concepts your sites define differently. Then you make the call: proceed, narrow the scope, or fix the mismatch before you lock your protocol. A verdict on the data, not a bet on it. No finding out after the results are in, when your only options are re-running the analysis or publishing with a caveat.

02

No patient data ever leaves the site

Each institution runs the analysis locally. The only thing that reaches Vercori is a statistical fingerprint of how the site defines each concept, never a patient record. No raw data pooling, no patient exposure to sign off on. The privacy question that usually stalls multi-site work is answered before it is asked.

03

Proof, not a promise

When your data quality is challenged, an assumption will not hold. Vercori gives you a quantified, tamper-evident record of every concept in your study: which are consistent, which diverge, what was done, and who decided. So when an FDA reviewer asks how you know your sites were measuring the same thing, the answer is already documented, before the question is ever asked.

Built for the teams who
run federated research.

Pharma RWE Teams

Find out if your sites are actually measuring the same thing before you combine their data.

  • Walk into an FDA meeting with documented proof of cross-site semantic consistency
  • Eliminate the risk of a post-hoc data quality challenge
  • Know which concepts need clinical review before you lock your protocol

CROs

Give your sponsors documented proof that semantic consistency was checked across every site, not assumed.

  • Offer quantified data fitness-for-use as a standard deliverable
  • Differentiate your OMOP service offering
  • Reduce downstream re-analysis risk for your clients

Hospital Network Operators

Strengthen your network's research credibility with a quantified trust layer between sites.

  • Give study sponsors confidence in your network's semantic consistency
  • Identify site-level coding variation before it affects results
  • Co-publish findings that advance the field

This is not a replacement for any data quality dashboard.

A data quality dashboard checks whether your data is correct within a site. We check whether your sites mean the same thing. Both matter. We pick up where it stops.

Check
Data quality dashboard
Vercori
Structural completeness
Yes
Inherits
Value conformance
Yes
Inherits
Temporal plausibility
Yes
Inherits
Cross-site consistency
Out of scope
Core function
Diagnostic confirmation
Out of scope
Detected
Submission-ready docs
Out of scope
Produced

Frequently asked
questions.

What is cross-site data consistency?

Cross-site data consistency refers to whether different healthcare sites represent the same clinical concept in the same way when using standardized concept IDs in a common data model such as OMOP. A site can pass every structural data quality check while still defining a concept differently than every other site in the network.

Why is data model standardization not enough?

OMOP standardizes structure and vocabulary mapping. It does not standardize what clinicians mean when they apply a concept ID. One hospital may require a confirmed diagnostic test before coding a condition. Another may code on clinical judgment alone. Both use the same concept ID. Both pass standard data quality checks. The difference is invisible until someone looks for it.

How is Vercori different from a data quality dashboard?

A data quality dashboard validates structural correctness within a single site. It checks completeness, conformance, and plausibility within a single instance. Vercori evaluates semantic consistency across multiple sites. It compares how each site in a network defines the same clinical concept and identifies where those definitions diverge. The two tools address different questions and are complementary.

Does Vercori require patient data to leave a site?

No. Each site runs its analysis locally inside its own CDM environment. The only output that leaves the site is a statistical fingerprint representing how the site defines each concept. No patient records are transmitted. No identifiable data leaves any institution.

Learn more about OMOP data consistency  →

Three things changed
at the same time.

Regulatory expectations moved

FDA's 2024 guidance on real-world data for drug and biological products and its 2025 medical device guidance both expect documented assessment of completeness, accuracy, and consistency across sites, not just structural correctness. Passing structural quality checks is no longer a complete answer.

The networks got big enough to matter

With over one billion patient records across 34 countries in OMOP alone, the probability that all sites define concepts identically is effectively zero.

The cost of getting it wrong got higher

A single post-submission data quality challenge can delay approval, trigger re-analysis, or undermine a study that took years to complete.

Cross-site coding variation in federated OMOP networks is documented, discussed, and widely acknowledged. What has been missing is a practical way to measure it, document it, and act on it before a study runs.

That is what Vercori does.

Vercori was founded by Sandra Estremera-Zink, J.D.

The name comes from two words: verdict and core. The product renders a verdict on the core concepts driving your study before the study runs.

The methodology is patent pending and has been submitted to the 2026 OHDSI Global Symposium. It is grounded in published research on cross-site concept variation in OMOP networks.

Run your study on data
you have actually verified.

We are accepting pilot partners now. Pilot studies are scoped individually based on network size and use case. Book a demo to discuss.

Let's find out
if your sites agree.

Looking for pilot partners

If you run multi-site OMOP studies, operate a network site, or advise pharma sponsors on real-world evidence, we want to hear from you.

Pharma RWE Teams CROs Hospital Network Operators Academic Medical Centers

Pilot terms

Pilot studies are scoped individually based on network size and use case. We're open to discussing co-authorship on a publication if the results warrant it.