Entity

Medication Record

The patient's comprehensive medication list including active prescriptions, historical medications, allergies, adverse reactions, and adherence patterns.

Last updated: February 2026Data current as of: February 2026

Why This Object Matters for AI

AI medication therapy management requires complete medication history; without it, AI cannot identify polypharmacy risks or adherence opportunities.

Pharmacy Operations Capacity Profile

Typical CMC levels for pharmacy operations in Healthcare organizations.

Formality
L4
Capture
L4
Structure
L4
Accessibility
L3
Maintenance
L3
Integration
L3

CMC Dimension Scenarios

What each CMC level looks like specifically for Medication Record. Baseline level is highlighted.

L0

The patient's medication history is not formally documented. Clinicians ask patients what they take and rely on patient recall, which is often incomplete or inaccurate. There is no consolidated medication list. Different providers see different fragments of the patient's medication picture, and nobody has the complete view.

None — AI cannot perform drug interaction checking, medication reconciliation, or adherence analysis because no formal medication records exist.

Create formal medication records — document each patient's active medications including drug name, dose, route, frequency, prescriber, and start date in a centralized medication list within the clinical record.

L1

Medication lists exist in the EHR but are unreliable. Active medications may include drugs the patient stopped months ago. Dosages listed may not match what the patient actually takes. Over-the-counter medications and supplements are rarely captured. The medication list is a starting point for conversation, not a definitive clinical record.

AI can display the medication list, but cannot perform reliable interaction checking or adherence analysis because the record does not accurately represent what the patient is actually taking.

Standardize medication record documentation — implement medication reconciliation at every care transition, require documentation of dose, route, frequency, indication, and prescriber for each entry, and establish processes for verifying the medication list against pharmacy fill records.

L2

Medication records are reconciled and documented with standardized detail. Each medication entry includes drug name (with NDC code), dose, route, frequency, indication, prescriber, and start date. Medication reconciliation occurs at care transitions. The medication list is a reliable snapshot of what the patient is prescribed. But records are standalone lists — not linked to pharmacy fill records, lab monitoring, or allergy documentation.

AI can perform reliable drug interaction checking, duplicate therapy detection, and dosing verification from the standardized medication record. Cannot assess actual adherence, monitor for drug-lab interactions, or verify allergy cross-reactivity because the medication list is not connected to fill records, lab values, or detailed allergy profiles.

Link medication records to clinical context — connect the medication list to pharmacy fill and refill history, relevant lab monitoring values (drug levels, renal function, liver function), and detailed allergy and adverse reaction documentation.

L3

Medication records connect to clinical context. Each medication links to pharmacy fill history (actual dispensing and refill patterns), relevant lab monitoring (therapeutic drug levels, renal function for dose adjustment, hepatic function), and allergy documentation with cross-reactivity. A pharmacist can query 'show me this patient's warfarin dosing history alongside their INR trends and concurrent medication changes over the past year.'

AI can perform comprehensive medication management — monitoring drug-lab interactions, detecting adherence gaps from fill patterns, recommending dose adjustments based on renal function, and assessing cross-reactivity risks from connected allergy profiles.

Implement formal medication entity schemas — model each medication as a structured entity with typed relationships to prescriber orders, dispensing records, administration events, lab monitoring, allergy profiles, and pharmacogenomic results.

L4Current Baseline

Medication records are schema-driven entities with full relational modeling. Each medication links to prescriber orders, dispensing events, administration records, lab monitoring values, allergy cross-references, pharmacogenomic profiles, and therapeutic outcome measurements. An AI agent can navigate from any medication to the complete prescribing, dispensing, monitoring, and outcome context.

AI can autonomously manage medication therapy — monitoring for interactions, recommending dose adjustments based on pharmacogenomic profiles and organ function, detecting adherence gaps, and recommending therapeutic changes based on outcome tracking.

Implement real-time medication event streaming — publish every prescribing, dispensing, administration, and monitoring event as it occurs for continuous medication intelligence.

L5

Medication records are real-time clinical intelligence streams. Every prescribing decision, pharmacy dispensing event, nursing administration, lab result, and adverse reaction updates the medication profile in real-time. The medication record is a continuously current representation of the patient's pharmacotherapy status, not a list that someone reconciles periodically.

Fully autonomous medication therapy intelligence — continuously monitoring every pharmacotherapy variable in real-time, optimizing drug selection, dosing, and monitoring as a comprehensive medication management engine.

Ceiling of the CMC framework for this dimension.

Capabilities That Depend on Medication Record

Other Objects in Pharmacy Operations

Related business objects in the same function area.

What Can Your Organization Deploy?

Enter your context profile or request an assessment to see which capabilities your infrastructure supports.