Concomitant medication checking is the automated computational process of comparing a patient's structured or extracted medication list against a clinical trial's protocol-defined list of prohibited concomitant medications. The system identifies exclusionary drug interactions by resolving medication names to standardized RxNorm concept unique identifiers, ensuring that brand names, generics, and ingredient-level conflicts are accurately detected without manual review.
Glossary
Concomitant Medication Checking

What is Concomitant Medication Checking?
An automated process that cross-references a patient's active medication list against a trial's prohibited medications to identify exclusionary drug interactions.
The process involves parsing unstructured clinical notes to extract active medications, normalizing them against a reference terminology, and evaluating each against the trial's exclusion logic. Advanced implementations incorporate temporal reasoning to verify that a prohibited medication was active during the screening window, distinguishing between historical and current use to prevent false exclusions and accelerate patient pre-screening.
Key Features of Automated Concomitant Medication Checking
Automated concomitant medication checking transforms a manual, error-prone chart review into a precise, scalable computational process. These key features define a robust system for ensuring patient safety and protocol compliance.
Ontology-Backed Drug Normalization
The system maps free-text medication names from EHRs to a standardized terminology like RxNorm. This resolves variations in brand names, generics, and misspellings into a single canonical concept, enabling reliable downstream rule execution.
Structured Criteria Execution
The trial protocol's prohibited medication list is parsed into a machine-executable format. The engine evaluates a patient's normalized medication list against these structured rules, checking for exact matches, class-level conflicts, and ingredient-level interactions.
Temporal Window Validation
The system applies temporal reasoning to medication data. It verifies if a prohibited drug was taken within a critical exclusion window (e.g., 'within 30 days of enrollment') by comparing prescription dates and documented usage periods against the trial's timeline constraints.
Class-Level and Ingredient Inference
Beyond exact name matching, the system performs semantic inference. A rule excluding 'ACE Inhibitors' will flag a patient taking 'Lisinopril' by traversing the drug ontology's class hierarchy, catching conflicts a simple string match would miss.
Auditable Decision Provenance
Every exclusion flag is accompanied by a clear, auditable trail. The system cites the specific protocol criterion violated, the conflicting medication from the patient's record, and the logical path (e.g., exact match, class inference) that led to the decision.
Contextual Severity Flagging
The system differentiates between absolute contraindications and relative cautions. A QT-prolonging drug might be flagged as a critical exclusion, while a mild CYP450 inhibitor is flagged as a warning requiring investigator review, enabling nuanced decision-making.
Frequently Asked Questions
Concise answers to the most common technical and operational questions about automated concomitant medication screening in clinical trial eligibility workflows.
Concomitant medication checking is an automated computational process that cross-references a patient's active medication list against a clinical trial's protocol-defined list of prohibited or restricted medications to identify exclusionary drug interactions. The system parses structured and unstructured medication data—including drug names, dosages, routes, and dates—from electronic health records and maps them to standardized drug ontologies like RxNorm. It then evaluates each medication against the trial's inclusion and exclusion criteria, flagging disallowed concomitant drugs such as strong CYP3A4 inhibitors or medications with overlapping toxicity profiles. This process replaces manual chart review, reducing screening time from hours to seconds while ensuring no protocol violation is missed due to human oversight.
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 interconnected concepts that form the foundation of automated drug interaction and protocol compliance screening in clinical trials.
Drug-Drug Interaction Detection
The computational process of identifying potential adverse reactions when two or more medications are taken together. This goes beyond simple exclusion lists by analyzing pharmacokinetic and pharmacodynamic properties.
- Utilizes structured knowledge bases like DrugBank and NDF-RT
- Checks for CYP450 enzyme competition and QT prolongation risks
- Essential for distinguishing between absolute contraindications and monitorable interactions
RxNorm Normalization
The critical preprocessing step of mapping free-text medication names to a standardized clinical drug vocabulary. This ensures that 'ASA', 'Aspirin', and 'Acetylsalicylic Acid' are recognized as the same entity.
- Resolves brand name, generic name, and synonym ambiguity
- Enables reliable cross-referencing against protocol-defined prohibited medication lists
- Uses RxNorm concept unique identifiers (RXCUIs) for deterministic matching
Temporal Washout Validation
The logic that verifies a patient's last dose of a prohibited medication falls outside the trial's required washout window. This is a temporal reasoning challenge, not just a presence check.
- Calculates the interval between the medication stop date and the screening date
- Flags patients still within the exclusionary period for re-screening later
- Handles long-acting injectables with extended pharmacological half-lives
Formulary Class Restriction
An advanced screening rule that prohibits entire therapeutic classes rather than just specific named drugs. This catches novel or less common agents that share a mechanism of action.
- Uses VA Class or ATC Classification hierarchies
- Example: Excluding all 'HMG-CoA Reductase Inhibitors' instead of listing each statin
- Prevents protocol violations from non-formulary or international medications
Structured SIG Parsing
The extraction and normalization of medication dosage instructions from unstructured text. A drug's eligibility often depends on dose, frequency, and route, not just the ingredient.
- Converts 'Take 1 tablet by mouth twice daily' into structured fields
- Identifies stable vs. PRN (as needed) regimens for protocol compliance
- Validates against maximum daily dose thresholds specified in trial criteria
Clinical Decision Support Integration
The embedding of concomitant medication checking directly into the clinical workflow via FHIR CDS Hooks. This provides real-time alerts at the point of care during patient screening.
- Triggers automatically when a clinician opens a patient's chart
- Returns a structured 'pass/fail' or 'review required' card within the EHR
- Reduces manual pharmacist review time by pre-validating medication lists

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