Medication Reconciliation (MedRec) is a critical patient safety procedure designed to prevent adverse drug events (ADEs) during care transitions. The process involves compiling a Best Possible Medication History (BPMH) using multiple information sources, then systematically comparing that verified list against newly written orders to detect and resolve unintentional discrepancies such as omissions, duplications, or dosing errors before they reach the patient.
Glossary
Medication Reconciliation (MedRec)

What is Medication Reconciliation (MedRec)?
Medication reconciliation is the formal, systematic process of creating the most accurate possible list of all medications a patient is taking and comparing that list against the physician's admission, transfer, or discharge orders to identify and resolve discrepancies.
The workflow relies on resolving semantic mismatches between proprietary drug names using standards like RxNorm and applying clinical logic such as renal dose adjustment and allergen cross-reactivity checks. Automated systems augment this process by employing temporal reasoning to validate medication timelines and confidence thresholding to route ambiguous cases for mandatory human-in-the-loop (HITL) review by clinical pharmacists.
Core Characteristics of MedRec
Medication Reconciliation (MedRec) is a formal, systematic process designed to eliminate medication errors during transitions of care. The following characteristics define a robust, high-reliability MedRec program.
Structured Discrepancy Classification
A rigorous MedRec process categorizes every variance between medication lists using standardized taxonomies. This moves beyond simple mismatches to clinically meaningful classification.
- Unintentional Discrepancy: An unjustified difference without clinical rationale, representing a medication error.
- Omission Error: A clinically indicated drug unintentionally not prescribed on new orders.
- Commission Error: A drug added without a valid indication.
- Duplication Error: Co-prescribing therapeutically equivalent agents.
- Dosage/Strength Error: A mismatch in dose, frequency, or route. This structured approach enables targeted quality improvement and system-level error proofing.
Multi-Source Data Aggregation
The foundation of MedRec is the Best Possible Medication History (BPMH) , which is not a simple copy of the last electronic health record list. It requires a systematic interview and verification against at least two independent information sources.
- Primary Sources: Patient/caregiver interview, physical medication bottles.
- Secondary Sources: Community pharmacy dispense records, insurance claims data, previous discharge summaries.
- Tertiary Sources: Pill bottle inspection, blister pack review. Discrepancies between sources must be explicitly resolved and documented to create a single, trusted pre-admission list.
Temporal Reasoning & Chronological Validation
MedRec is not a static snapshot but a chronological reconstruction of a patient's medication journey. Temporal reasoning is the capability to sequence clinical events to validate logical consistency.
- Validates that a medication's start date precedes its discontinuation date.
- Identifies therapeutic overlaps or gaps in therapy during transitions.
- Reconciles 'as needed' (PRN) medications with administration records to determine actual active status.
- Detects unintentional duplicate therapy by analyzing concurrent active order windows. This time-aware analysis is critical for distinguishing intentional, clinically appropriate changes from accidental errors.
Standardized Normalization Engines
To compare medication lists from disparate sources, a MedRec system must computationally normalize heterogeneous representations into a common, comparable format.
- Active Ingredient Matching: Links brand names (e.g., Tylenol) and generics (e.g., acetaminophen) to a base RxNorm concept identifier to prevent duplicate therapy errors.
- Dose Normalization: Converts varied expressions of strength (e.g., '500 mg', '1 tablet', 'two 250 mg capsules') into a standardized cumulative daily dose for accurate comparison.
- Frequency Standardization: Maps vernacular instructions like 'take every morning' to coded, computable frequencies (e.g., 'QAM', 'Once Daily'). Without this semantic normalization, automated comparison is impossible.
Closed-Loop Resolution & Documentation
Identification of a discrepancy is only the first step. A complete MedRec process requires a closed-loop resolution workflow that drives action and documents clinical intent.
- Intentional Discrepancy: The clinician documents the clinical rationale for a deliberate change (e.g., 'held due to acute kidney injury').
- Unintentional Discrepancy: The error is corrected, and the order is updated in the active medication list.
- Documentation: The final reconciled list is clearly documented as the single source of truth for the next care provider. This loop ensures that the reconciliation is not just an audit but an intervention that corrects the patient's active orders.
Human-in-the-Loop (HITL) Verification
In high-stakes clinical environments, fully autonomous reconciliation is unsafe. A Human-in-the-Loop (HITL) design paradigm is essential, where AI outputs are treated as decision support for a qualified clinician.
- Confidence Thresholding: AI-extracted data with a low model prediction score is routed for mandatory pharmacist review.
- Source Attribution: Every extracted medication entry is explicitly linked back to its source sentence or database field, enabling rapid human verification.
- Audit Interface: A specialized UI allows a clinical pharmacist to efficiently accept, reject, or modify AI-proposed discrepancies. This architecture optimizes the balance between automation efficiency and patient safety, ensuring a licensed professional always validates the final record.
Frequently Asked Questions
Clear, technically precise answers to the most common questions about the formal process of identifying and resolving discrepancies in a patient's medication list during care transitions.
Medication reconciliation (MedRec) is the formal, systematic process of creating the most accurate possible list of all medications a patient is currently taking—including drug name, dosage, frequency, and route—and comparing that list against the physician's admission, transfer, or discharge orders to identify and resolve discrepancies. It is a critical patient safety process because care transitions represent high-risk junctures where unintentional medication discrepancies, such as omission errors or duplicate therapy, occur in up to 70% of hospitalized patients. These discrepancies are a leading cause of adverse drug events (ADEs), many of which are preventable. The process relies on compiling a Best Possible Medication History (BPMH) from at least two independent sources, including patient interviews, pharmacy records, and previous clinical documentation, to establish a verified baseline against which new orders are validated.
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
Master the interconnected concepts that form the foundation of AI-driven medication reconciliation, from core clinical processes to the algorithmic safeguards that ensure patient safety.
Unintentional Discrepancy vs. Intentional Change
The core logic of MedRec is classifying differences between a patient's pre-admission medication list and new orders. An unintentional discrepancy is an unjustified difference without clinical rationale—a medication error requiring immediate resolution. In contrast, an intentional change is a deliberate, clinically justified action (e.g., holding an anticoagulant before surgery). AI systems must distinguish between these two categories by analyzing structured order reasons and free-text clinical notes to avoid flagging appropriate therapeutic decisions as errors.
Omission Error
The most common and insidious type of medication discrepancy. An omission error occurs when a clinically indicated drug that a patient was taking prior to a care transition is unintentionally not prescribed on the new medication orders. This is particularly dangerous for time-critical medications such as antiplatelets, anticonvulsants, or Parkinson's disease therapies, where even a single missed dose can precipitate a significant adverse event. Automated reconciliation engines prioritize flagging these silent gaps.
Duplicate Therapy Alert
A clinical decision support notification triggered when a new medication order is placed for a drug that is therapeutically equivalent or identical to an existing active order. This poses a direct risk of overdose. Advanced systems use active ingredient matching to resolve brand-name and generic products to a common base compound, preventing duplicate therapy errors that arise from proprietary naming conventions. The challenge lies in tuning alert sensitivity to avoid contributing to alert fatigue.
Confidence Thresholding & Human-in-the-Loop
A probabilistic gate that routes AI-extracted medication data for human review only when the model's prediction score falls below a predefined certainty level. This human-in-the-loop (HITL) paradigm optimizes the balance between straight-through processing and clinical safety. High-confidence extractions are auto-committed, while ambiguous cases—such as illegible handwriting or rare drug names—are surfaced to a clinical pharmacist for verification, ensuring that automation never outpaces accountability.
Hallucination Guardrails
Deterministic constraints and post-processing rules applied to large language model outputs to prevent the generation of plausible-sounding but factually non-existent medication names or dosages. These guardrails include validation against authoritative drug databases like RxNorm, regex-based dose format enforcement, and rejection of any generated entity not grounded in the source text. In the high-stakes domain of medication reconciliation, a hallucinated 'metformin 1000mg' that should be 'metoprolol 100mg' is a catastrophic failure mode that must be engineered out of existence.

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