Unstructured Criteria Extraction is the automated process of applying natural language processing (NLP) to parse free-text clinical trial protocols and isolate specific, machine-readable inclusion and exclusion conditions. It transforms complex narrative sentences—such as "patients must have failed at least two prior lines of systemic therapy"—into structured logical components that a Trial Pre-Screening API or Eligibility Rule Engine can execute against a patient database.
Glossary
Unstructured Criteria Extraction

What is Unstructured Criteria Extraction?
The application of natural language processing to identify and isolate specific eligibility conditions from narrative text in clinical trial protocols.
This process relies on Medical Named Entity Recognition and Negation and Uncertainty Detection to accurately identify clinical concepts like diagnoses, lab values, and medications while respecting contextual modifiers. By feeding into a Criteria Decomposition pipeline, unstructured criteria extraction enables the downstream Criteria-to-Query Translation necessary for high-throughput Patient Pre-Screening and Cohort Identification.
Core Capabilities of Extraction Systems
The foundational NLP techniques required to parse complex, free-text clinical trial protocols and isolate specific patient eligibility conditions.
Semantic Parsing of Free-Text Criteria
Transforms narrative eligibility clauses into structured, machine-readable logical forms. This process goes beyond keyword spotting to understand the intent of a criterion.
- Identifies the clinical concept (e.g., 'HbA1c'), the operator (e.g., 'greater than'), and the value (e.g., '7.0%').
- Resolves complex linguistic structures like anaphora ('it', 'the patient') to link conditions to the correct entity.
- Example: Parsing 'Patient must not have had a myocardial infarction within the last 90 days' into a structured object with a negated temporal constraint.
Contextual Negation and Uncertainty Detection
Critically distinguishes between affirmed, negated, and uncertain clinical conditions to prevent catastrophic screening errors. A simple keyword match for 'cancer' is insufficient.
- Uses contextual embeddings to analyze the linguistic scope of negation triggers like 'no evidence of' or 'ruled out'.
- Identifies hedging language such as 'suspected,' 'possible,' or 'cannot be ruled out' to flag uncertain findings.
- Prevents false exclusions: Correctly interpreting 'history of breast cancer' as negated in 'no history of breast cancer' is essential for accurate eligibility scoring.
Temporal Expression Normalization
Extracts and standardizes time-based constraints from criteria into a computable format for comparison against a patient's longitudinal record.
- Recognizes and normalizes relative expressions like 'within the last 6 weeks' or 'prior to enrollment' into absolute date ranges.
- Maps clinical events to a standardized timeline to validate constraints such as 'disease progression after platinum-based chemotherapy'.
- Handles complex durations: Parsing 'a washout period of 5 half-lives' requires linking the concept to a specific drug's pharmacokinetic data.
Ontological Concept Normalization
Maps extracted clinical terms to standard medical ontologies like SNOMED CT, LOINC, and RxNorm to resolve semantic ambiguity.
- Normalizes synonymous terms: 'High blood pressure' and 'Hypertension' are mapped to the same SNOMED code.
- Links lab tests to LOINC codes to ensure the correct analyte is being evaluated, regardless of local naming conventions.
- Enables semantic interoperability between trial criteria and diverse EHR systems, which is the foundational step for accurate criteria-to-query translation.
Criteria Decomposition into Atomic Units
Breaks down a complex, multi-part eligibility criterion into its indivisible, independently evaluable logical components.
- A single sentence like 'Patient must have EGFR-mutant NSCLC and no prior TKI therapy' is decomposed into two atomic criteria.
- Each atomic unit contains a single clinical fact (e.g.,
diagnosis = NSCLC), a single operator, and a single value. - This logical atomization is a prerequisite for execution by a deterministic rule engine and for assigning granular weights to each condition.
Concomitant Medication Extraction
Isolates and structures lists of prohibited and permitted medications directly from the protocol narrative.
- Identifies specific drug names, classes, and routes of administration mentioned in exclusion criteria.
- Normalizes drug terms to RxNorm to enable cross-referencing with a patient's structured medication list.
- Handles complex rules: Parsing 'concurrent use of strong CYP3A4 inhibitors' requires inferring a class of drugs rather than matching a single named entity.
Frequently Asked Questions
Clear, technical answers to common questions about how NLP systems identify and isolate specific eligibility conditions from narrative clinical trial protocols.
Unstructured criteria extraction is the application of natural language processing (NLP) to automatically identify, isolate, and structure the free-text inclusion and exclusion conditions found in clinical trial protocols. Unlike structured data in databases, these criteria are written in narrative prose—often containing complex logical operators, negations, and temporal constraints. The process typically involves a pipeline: first, a medical named entity recognition model identifies clinical concepts like diseases, lab values, and medications. Next, a relation extraction component links these entities to logical operators (AND/OR/NOT) and quantitative thresholds. Finally, a negation and uncertainty detection module determines whether a condition is affirmed, negated, or hypothetical. The output is a machine-readable, structured representation—often mapped to a standard ontology like SNOMED CT or LOINC—that can be fed directly into a criteria-to-query translation engine for automated patient screening.
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
Explore the foundational technologies and processes that enable the automated interpretation of clinical trial protocols.
Criteria-to-Query Translation
The process of converting parsed, structured eligibility criteria into executable database queries, such as SQL or FHIR API calls, to screen patient repositories. This bridges the gap between the extracted unstructured criteria and the operational data layer.
- Translates logical rules to query languages
- Maps criteria to specific data fields (e.g., LOINC codes)
- Enables direct execution against EHR databases
Temporal Reasoning for Eligibility
The AI capability to interpret and validate time-dependent clinical constraints against a patient's longitudinal record. Extracting a criterion like 'no myocardial infarction within 6 months' requires not just entity recognition but also sophisticated temporal reasoning.
- Resolves relative time expressions (e.g., 'within 3 months')
- Validates event sequences against timelines
- Handles duration-based constraints (e.g., 'treatment for 2 years')
Medical Ontology Alignment
The process of mapping and harmonizing disparate medical terminologies such as SNOMED CT, ICD-10-CM, LOINC, and RxNorm. Unstructured criteria extraction relies on this alignment to normalize the varied language used in protocols to a standard set of concepts.
- Resolves synonyms (e.g., 'high blood pressure' to HTN)
- Maps brand names to generic drug ingredients
- Enables semantic interoperability between systems
Negation and Uncertainty Detection
The NLP task of distinguishing between affirmed, negated, and uncertain clinical findings in narrative text. A criterion stating 'patients without active infection' requires accurate negation detection to avoid incorrectly excluding a patient with a historical note of infection.
- Identifies negation cues (e.g., 'no evidence of')
- Detects uncertainty (e.g., 'suspected for')
- Prevents false-positive exclusions in screening
Computable Phenotype
A machine-processable definition of a clinical condition, expressed as a set of logical expressions and data queries, used to identify patient cohorts. Unstructured criteria extraction is the mechanism that feeds these definitions by converting narrative protocol text into the logical rules that form a computable phenotype.
- Combines structured and unstructured data rules
- Defines a cohort for screening or research
- The executable output of criteria extraction

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