An Eligibility Rule Engine is a deterministic software system that evaluates a set of structured patient facts against a predefined library of clinical trial criteria to produce a binary pass/fail decision. Unlike probabilistic AI models, it applies explicit, auditable logic—such as IF hemoglobin < 9 g/dL THEN exclude—ensuring that every eligibility determination is transparent, repeatable, and fully traceable to the originating protocol requirement.
Glossary
Eligibility Rule Engine

What is an Eligibility Rule Engine?
A deterministic software system that evaluates a set of patient facts against a predefined library of clinical trial eligibility rules to produce a pass/fail decision.
The engine operates by ingesting a computable phenotype definition and executing it against a patient's normalized clinical data, resolving complex logical expressions, temporal constraints, and value comparisons. It serves as the final, high-precision gate in a hybrid matching architecture, validating candidates identified by semantic search before site contact, thereby eliminating false positives caused by ambiguous criteria interpretation.
Key Features of an Eligibility Rule Engine
An eligibility rule engine is the deterministic backbone of automated clinical trial screening, evaluating structured patient facts against a library of computable criteria to produce definitive pass/fail decisions. The following features define a production-grade system.
Deterministic Criteria Evaluation
The engine applies Boolean logic (AND, OR, NOT) and comparison operators (=, >, <, ≥, ≤) to patient facts with absolute reproducibility. Unlike probabilistic AI models, a deterministic engine guarantees the same input always yields the same output—critical for regulatory audit trails.
- Evaluates atomic criteria like
Hemoglobin >= 9.0 g/dLorDiagnosis == 'Non-Small Cell Lung Cancer' - Supports nested logic groups for complex compound criteria
- Produces a definitive PASS, FAIL, or INCONCLUSIVE (insufficient data) result per criterion
Temporal Constraint Resolution
The engine validates time-window constraints against a patient's longitudinal record to enforce criteria like washout periods, disease progression timelines, and recency requirements.
- Evaluates constraints such as
Prior chemotherapy completed > 28 days before enrollment - Reconstructs clinical event sequences from timestamped data points
- Handles relative time offsets (e.g.,
within 6 months of diagnosis) and absolute date thresholds - Flags violations of minimum or maximum interval requirements between events
Ontology-Backed Terminology Normalization
The engine maps clinical concepts to standardized terminologies (SNOMED CT, LOINC, RxNorm, ICD-10-CM) before evaluation, ensuring that synonymous expressions are consistently interpreted.
- Normalizes
high blood pressureandessential hypertensionto the same SNOMED concept - Converts lab values to consistent units (e.g., mg/dL vs. mmol/L) before comparison
- Resolves medication synonyms to RxNorm ingredient-level concepts for concomitant medication checking
- Eliminates false negatives caused by terminology mismatch
Criteria Decomposition Engine
Complex, multi-part eligibility criteria are automatically decomposed into atomic, independently evaluable units before execution. This enables granular pass/fail tracking and clear screen failure reporting.
- Parses a criterion like
Histologically confirmed NSCLC, Stage IIIB-IV, with ECOG 0-1into three separate evaluable facts - Maintains parent-child logical relationships between decomposed atoms
- Enables partial matching and weighted scoring when full criteria cannot be met
- Supports criteria weighting to prioritize critical inclusion factors over secondary ones
Audit Trail and Explainability
Every eligibility decision is accompanied by a complete, immutable decision trace that records which patient facts were evaluated, which criteria passed or failed, and why.
- Logs the exact patient value compared against each criterion threshold
- Provides a human-readable justification for every FAIL result (e.g.,
Hemoglobin 8.2 g/dL < required 9.0 g/dL) - Supports regulatory compliance with 21 CFR Part 11 audit trail requirements
- Enables rapid screen failure analysis and protocol refinement
Protocol Amendment Handling
The engine supports versioned rule libraries that automatically detect and integrate changes from formal protocol amendments without requiring full system redeployment.
- Maintains distinct rule sets for each protocol version with effective dates
- Automatically applies the correct version based on the patient's screening date
- Provides diff reports showing exactly which criteria were added, removed, or modified
- Ensures continuity of screening operations during protocol transitions
Frequently Asked Questions
Clear, technical answers to common questions about the deterministic software systems that evaluate patient facts against clinical trial criteria to produce pass/fail eligibility decisions.
An eligibility rule engine is a deterministic software system that evaluates a set of structured patient facts against a predefined library of clinical trial inclusion and exclusion criteria to produce a binary pass/fail decision. Unlike probabilistic AI models, it operates on explicit, auditable logic. The engine ingests a patient's normalized clinical data—such as diagnoses coded in ICD-10-CM, lab results in LOINC, and medications in RxNorm—and sequentially executes a series of IF-THEN rules. For example, a rule might state: IF hemoglobin < 9 g/dL THEN EXCLUDE. The engine resolves all logical operators (AND, OR, NOT), validates temporal constraints (e.g., 'surgery within the last 6 months'), and outputs a final eligibility determination along with a trace of every rule evaluated, ensuring full algorithmic explainability for regulatory audits.
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
The Eligibility Rule Engine is a deterministic core that relies on a surrounding ecosystem of AI and data processing components to translate complex protocol logic and unstructured patient data into executable decisions.

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