Inclusion criteria define the explicit, machine-executable rules that determine patient eligibility for a clinical study, forming the logical foundation of a computable phenotype. These criteria specify required attributes such as age ranges, diagnosis codes (e.g., SNOMED CT or ICD), laboratory result thresholds (e.g., LOINC codes), medication histories, and temporal sequences of events that must be satisfied for a patient to qualify for a cohort.
Glossary
Inclusion Criteria

What is Inclusion Criteria?
Inclusion criteria are the specific clinical, demographic, and temporal characteristics that a patient must possess to be eligible for enrollment in a clinical study or cohort definition.
In federated clinical analytics, inclusion criteria are decomposed into distributed queries that execute locally at each institution against the OMOP Common Data Model, returning only aggregate counts or masked results. This allows researchers to perform federated cohort discovery across multiple sites while ensuring that individual patient-level data never leaves the local firewall, maintaining strict compliance with HIPAA and institutional Data Use Agreements.
Core Characteristics of Robust Inclusion Criteria
Well-defined inclusion criteria are the bedrock of reproducible clinical research. They transform ambiguous medical questions into precise, computable algorithms that ensure consistent patient selection across distributed sites.
Unambiguous Semantic Standards
Criteria must map to controlled terminologies to eliminate the ambiguity of free-text clinical notes.
- SNOMED CT for diagnoses and procedures
- LOINC for laboratory tests and vital signs
- RxNorm for medication orders
- ICD-10-CM for billing and administrative codes Using these standards ensures that a 'type 2 diabetic' is identified identically across different EHR systems.
Temporal Constraints
A robust criterion specifies not just what happened, but when. This defines the index date and lookback windows.
- Incident vs. Prevalent: First-ever diagnosis vs. any history of the condition
- Lookback Period: e.g., 'No HbA1c > 6.5% in the 365 days prior to enrollment'
- Temporal Logic: 'Procedure A must occur after Diagnosis B but before Medication C' Without temporal anchors, cohorts mix new cases with long-standing chronic patients.
Computable Phenotype Logic
Inclusion criteria must be translated into a computable phenotype—a machine-executable algorithm combining multiple data types.
- Rule-Based Logic: Boolean operators (AND, OR, NOT) linking structured codes
- Value-Based Thresholds: Laboratory results (e.g., 'eGFR < 60 mL/min')
- Composite Scores: Calculated indices like BMI or Charlson Comorbidity Index This logic allows a distributed query engine to execute the exact same cohort definition across OMOP-mapped databases.
Demographic and Anthropometric Boundaries
Explicitly defining the population scope prevents confounding and ensures generalizability.
- Age Ranges: '≥ 18 years at index date'
- Sex/Gender: Aligning with study design and biological hypotheses
- Geographic Constraints: Limiting to specific sites or regions
- Vital Signs: Weight, height, or blood pressure ranges These boundaries are critical for matching cohorts to the target product label or research question.
Data Availability Requirements
A patient must have sufficient observational data to be evaluated. This prevents immortal time bias.
- Minimum Observation Period: e.g., '≥ 365 days of continuous enrollment prior to index'
- Data Completeness: Requiring at least one recorded visit or lab result in a window
- Site Capability: Ensuring the institution records the specific data types needed (e.g., structured pathology reports) This ensures the absence of a criterion is a true negative, not missing data.
Exclusion as a Precision Tool
Exclusion criteria are the inverse of inclusion—they refine the cohort by removing confounders.
- Contraindications: Removing patients with conditions that make the exposure unsafe
- Competing Risks: Excluding patients with conditions that prevent the outcome (e.g., bilateral amputation prevents a foot ulcer outcome)
- Data Quality Exclusions: Removing patients with implausible values (e.g., negative age) A clean cohort is defined as much by who is left out as who is let in.
Frequently Asked Questions
Precise answers to common questions about defining and applying inclusion criteria in federated clinical research, focusing on privacy-preserving cohort discovery across distributed healthcare datasets.
Inclusion criteria are the specific clinical, demographic, and temporal characteristics that a patient must possess to be eligible for enrollment in a clinical study or cohort definition. These criteria operationalize the research question by defining the target population with precision. Common dimensions include age ranges, diagnosis codes (e.g., SNOMED CT or ICD-10), laboratory result thresholds, medication histories, and procedure codes. In traditional single-site studies, inclusion criteria are applied directly against a local data warehouse. In federated environments, these criteria are translated into a computable phenotype—a machine-executable algorithm that can be distributed to multiple institutions, executed locally against each site's OMOP Common Data Model or native schema, and aggregated without exposing patient-level data. Well-defined inclusion criteria balance specificity (excluding ineligible patients) with sensitivity (capturing all relevant cases), directly impacting the statistical power and generalizability of the resulting Real-World Evidence.
Inclusion Criteria vs. Related Cohort Definition Concepts
A comparison of the distinct roles that inclusion criteria, exclusion criteria, computable phenotypes, and query federation play in defining and identifying patient populations for clinical research.
| Feature | Inclusion Criteria | Exclusion Criteria | Computable Phenotype | Query Federation |
|---|---|---|---|---|
Primary Function | Defines required attributes for study eligibility | Defines disqualifying attributes despite eligibility | Machine-executable algorithm to identify a cohort from EHR data | Distributed query technique to count patients across sites |
Operational Context | Clinical trial protocol design | Clinical trial protocol design | Observational research and EHR data extraction | Privacy-preserving multi-site feasibility counts |
Data Movement | Not applicable (design phase) | Not applicable (design phase) | Executed on centralized or local data warehouse | Query sent to data; only aggregate counts returned |
Patient-Level Data Exposure | No data involved | No data involved | Yes, operates on identified or de-identified records | No, patient-level data never leaves the source institution |
Standardization Requirement | Free-text protocol language | Free-text protocol language | Requires OMOP CDM, SNOMED CT, LOINC mapping | Requires common data model and distributed query engine |
Primary Output | Eligible participant pool definition | Safety and confounding risk mitigation | Binary classification of patient membership in a cohort | Aggregate patient counts per site with zero data leakage |
Temporal Component | May specify time windows for condition onset | May specify washout periods or recent exclusions | Encodes temporal logic via sequence of codes and visits | Executes temporal criteria locally at each node |
Relationship to OHDSI/OMOP | Conceptual input to phenotype design | Conceptual input to phenotype design | Implemented as OHDSI cohort definition JSON | Executed via OHDSI ATLAS or similar distributed tools |
Enabling Efficiency, Speed & Accuracy
Intelligent Analysis, Decision & Execution
We build AI systems for teams that need search across company data, workflow automation across tools, or AI features inside products and internal software.
Talk to Us
Search across company data
Give teams answers from docs, tickets, runbooks, and product data with sources and permissions.
Useful when people spend too long searching or get different answers from different systems.

Automate internal workflows
Use AI to route work, draft outputs, trigger actions, and keep approvals and logs in place.
Useful when repetitive work moves across multiple tools and teams.

Add AI to products and internal tools
Build assistants, guided actions, or decision support into the software your team or customers already use.
Useful when AI needs to be part of the product, not a separate tool.
Related Terms
Mastering inclusion criteria requires understanding the statistical, semantic, and privacy-preserving tools used to define and validate patient populations across distributed clinical networks.
Computable Phenotype
A machine-executable algorithm that translates clinical inclusion criteria into a queryable logic using structured codes (ICD-10, SNOMED CT), lab values, and medication orders. Unlike narrative criteria, a computable phenotype enables consistent, automated cohort identification across heterogeneous EHR systems without manual chart review.
OMOP Common Data Model
An open community standard that transforms disparate clinical data into a consistent format of standardized vocabularies and tables. Writing inclusion criteria against the OMOP CDM ensures a single computable phenotype can execute identically across multiple institutions, solving the semantic interoperability problem that plagues multi-site studies.
Federated Cohort Discovery
A privacy-preserving distributed query technique that broadcasts inclusion criteria to remote data nodes, executes them locally, and returns only aggregate patient counts. This allows researchers to assess study feasibility and refine criteria across a network without moving or exposing protected health information.
Confounding Variable
An extraneous factor that correlates with both the exposure and the outcome, potentially creating spurious associations. Rigorous inclusion criteria must explicitly address known confounders—such as age, comorbidities, or concomitant medications—either through restriction or by ensuring balanced representation across comparison groups.
Propensity Score Matching
A statistical technique used to reduce selection bias in observational studies by pairing treated and control subjects with similar estimated probabilities of receiving the treatment. When inclusion criteria alone cannot eliminate confounding, propensity score methods provide a post-hoc adjustment to simulate randomization within the defined cohort.
SNOMED CT
A comprehensive, multilingual clinical terminology that provides standardized codes for diagnoses, procedures, and body structures. Encoding inclusion criteria with SNOMED CT concepts rather than local billing codes ensures semantic consistency when a computable phenotype is deployed across different health systems with varying coding practices.

About the author
Prasad Kumkar
CEO & MD, Inference Systems
Prasad Kumkar is the CEO & MD of Inference Systems and writes about AI systems architecture, LLM infrastructure, model serving, evaluation, and production deployment. Over 5+ years, he has worked across computer vision models, L5 autonomous vehicle systems, and LLM research, with a focus on taking complex AI ideas into real-world engineering systems.
His work and writing cover AI systems, large language models, AI agents, multimodal systems, autonomous systems, inference optimization, RAG, evaluation, and production AI engineering.
Partnered with leading AI, data, and software stack.
How We Work
Custom AI workflows for your Business
One-fit-all AI don't work for modern businesses. At Inferensys, we aim to understand your business & custom requirements; which we use to define most efficient agentic workflows, the data, and the tools for your business.
01
Review the use case
We understand the task, the users, and where AI can actually help.
Read more02
Pick the right approach
We define what needs search, automation, or product integration.
Read more03
Build the first useful version
We implement the part that proves the value first.
Read more04
Improve from there
We add the checks and visibility needed to keep it useful.
Read moreThe first call is a practical review of your use case and the right next step.
Talk to Us