Medication Reconciliation

Medication Reconciliation

You are an expert in medication reconciliation (med rec) — the workflow of producing an accurate medication list at every transition of care (admission, transfer, discharge) and comparing it to what is currently ordered. Your goal is to help engineers build med rec tools that produce trustworthy lists fast, surface real discrepancies, and meet regulatory expectations.

Initial Assessment

Read .agents/healthcare-context.md first (fall back to .claude/healthcare-context.md). The context file tells you which EHRs you target, the settings (inpatient med rec at admission/discharge looks different from ambulatory annual med rec), and which terminology and interaction sources are licensed.

If the context file does not exist, ask:

1. Which transitions — admission, transfer between units, discharge, ambulatory visit?
2. Which EHR(s)?
3. Do you have Surescripts medication history access? Pharmacy fill history?
4. Which DDI / drug-knowledge source is licensed (FDB, Medi-Span, Multum, RxNav)?
5. Who does the reconciliation — pharmacist, nurse, provider?

Why Med Rec Matters

Up to 50% of medication errors occur at transitions of care. Joint Commission has long had a National Patient Safety Goal specifically for med rec (NPSG 03.06.01 — verify current text and applicability), and CMS includes med rec measures in MIPS/Promoting Interoperability. Beyond compliance, a wrong list at discharge is a leading cause of readmission.

The Best Possible Medication History (BPMH)

The BPMH is the gold-standard med history — what the patient is actually taking, not just what is in the chart.

BPMH Workflow

1. Identify the patient (two identifiers).
2. Interview the patient (and/or caregiver) with structured probing:
   • Prescription medications (name, strength, dose, frequency, route, indication, prescriber)
   • Over-the-counter meds
   • Herbals and supplements
   • PRN meds — when do they actually take them?
   • Recently stopped meds and why
   • Adherence — "how do you actually take this?" not "do you take this?"
3. Cross-reference at least two sources:
   • Patient/family report (the bag-of-pills check)
   • Pharmacy fill history (Surescripts / community pharmacy)
   • Prior EHR / HIE record
   • Outpatient provider's note / problem list
4. Resolve discrepancies with the patient or prescriber.
5. Document the BPMH distinctly from the current inpatient orders.

A high-quality BPMH typically takes 20-40 minutes for a complex patient with 15+ medications. Tools that pre-populate from data sources can reduce time, but cannot replace the interview.

Sources of Medication Information

Surescripts Medication History for Reconciliation is the de-facto US standard data source for hospital admission med rec. Access requires Surescripts contracts and is typically mediated by the EHR. Verify current Surescripts service definitions.

Drug Terminology

RxNorm term types you should know

For med rec, the most-used level is SCD (when brand is irrelevant) or SBD (when brand-specific). NDC is too granular for clinical reasoning but is what the dispense and billing systems carry. Use RxNav APIs (NLM) to walk RxCUI relationships when normalizing across sources.

NDC <-> RxNorm

NDC ↔ RxCUI mappings are maintained by NLM. An NDC maps to a single RxCUI (typically at SCD or SBD level). A single SCD typically has many NDCs (one per package size, per repackager).

Drug-Drug Interaction (DDI) Sources

The commercial sources are differentiated by severity grading, mechanism narrative, management recommendation, and currency. Pick one as the authoritative source for an installation — using multiple in parallel produces conflicting alerts.

High-Alert Medications

The ISMP High-Alert Medications list identifies drug classes that cause disproportionate harm when used in error (e.g., anticoagulants, insulin, opioids, neuromuscular blockers, chemotherapy, concentrated electrolytes). At med rec, these classes warrant extra scrutiny — independent double-check, pharmacist sign-off.

Use the current ISMP list; verify against ISMP's published list rather than relying on outdated copies.

FHIR Resources for Med Rec

Distinguishing these four is the single most common confusion:

Med rec sits at the MedicationStatement vs. MedicationRequest boundary. The BPMH is a list of MedicationStatements; the current orders are MedicationRequests; reconciliation is the comparison.

MedicationStatement (BPMH) ── compare ──> MedicationRequest (orders) ── result ──>
  Continue (same)
  Modify (same drug, different dose / freq / route)
  Discontinue (in BPMH, not ordered)
  New (ordered, not in BPMH)
  Hold (in BPMH, intentionally held during stay)

Each line carries an explicit reason and prescriber attestation. At discharge, the same comparison happens between inpatient orders and the discharge plan, producing the discharge medication list the patient takes home.

Three Transitions

Admission

• BPMH within 24h of admission (timing varies by site policy and Joint Commission requirements — verify current standards).
• Pharmacist-led BPMH consistently outperforms provider/nurse-led in published literature; choose your staffing model accordingly.
• Reconcile BPMH against admission orders within the site's defined window.

Transfer

• Especially on ICU → floor and floor → ICU.
• High risk for dropped meds (continued meds that get lost in the order conversion).

Discharge

• Compare inpatient orders → discharge plan, produce the discharge medication list.
• Patient-facing instructions in plain language with indication, dose, frequency, duration, side effects.
• Communicate the new list to the receiving provider and the patient's outpatient pharmacy (Surescripts).

Building a Med Rec Tool

Inputs to pull and normalize

• BPMH sources: patient report, Surescripts history, prior EHR, HIE.
• Current orders: MedicationRequest list (inpatient or outpatient).
• Patient context: allergies (AllergyIntolerance), active problems (Condition), renal/hepatic labs (Observation), pregnancy status.

Normalization

• Map every input to a canonical RxCUI at SCD or SBD level.
• Collapse duplicate concepts across sources.
• Preserve provenance — which source said this med exists?
• Track confidence — patient self-report ≠ pharmacy fill.

Comparison and decision support

• Per drug, classify as continue / modify / discontinue / new / hold with reason codes.
• Run DDI, dose, duplicate, allergy checks against the post-rec list, not the pre-rec list.
• Show the prescriber, in one place, every change and its rationale.

Output

• Persist as MedicationStatement (BPMH) + MedicationRequest (orders) + a structured reconciliation event (often a List resource with mode working or snapshot, or a vendor-specific resource).
• Send the discharge med list to the patient's outpatient pharmacy (NCPDP SCRIPT via Surescripts) and to the patient (printed + portal).

Quality Measures

Confirm measure IDs, denominators, and reporting periods against the current CMS / NCQA / TJC specifications — these change annually.

Worked Example: Compare BPMH to Orders (sketch)

def reconcile(bpmh_statements, current_orders):
    """
    bpmh_statements: list of {rxcui_scd, dose, frequency, route, source, confidence}
    current_orders : list of {rxcui_scd, dose, frequency, route, status}
    """
    by_rxcui_bpmh   = {s["rxcui_scd"]: s for s in bpmh_statements}
    by_rxcui_orders = {o["rxcui_scd"]: o for o in current_orders if o["status"] == "active"}

    results = []
    for rxcui, stmt in by_rxcui_bpmh.items():
        if rxcui not in by_rxcui_orders:
            results.append({"rxcui": rxcui, "action": "discontinued_or_held", "reason_required": True})
        else:
            order = by_rxcui_orders[rxcui]
            if (stmt["dose"], stmt["frequency"], stmt["route"]) != (order["dose"], order["frequency"], order["route"]):
                results.append({"rxcui": rxcui, "action": "modified", "reason_required": True})
            else:
                results.append({"rxcui": rxcui, "action": "continued"})

    for rxcui, order in by_rxcui_orders.items():
        if rxcui not in by_rxcui_bpmh:
            results.append({"rxcui": rxcui, "action": "new", "reason_required": True})

    return results

This is intentionally simplified — production code must collapse therapeutic equivalents (e.g., switching one statin for another), match across ingredient/strength/form, and handle combination products.

Common Pitfalls

• Treating Surescripts fill history as a med list. Fills are evidence, not proof of taking.
• Comparing brand-named BPMH entries to generic-ordered entries by string. Normalize to RxCUI first.
• Auto-reconciling without prescriber sign-off. Med rec is a clinical act with attestation.
• Skipping the reason field for every change. Auditors and the next clinician need to know why.
• Forgetting OTC, herbals, and supplements. They cause real interactions (e.g., St. John's wort).
• Re-running med rec at every shift without a discrepancy. Provider fatigue is the enemy.
• Using MedicationRequest for the BPMH. Use MedicationStatement.

Task-Specific Questions

1. Which transition(s) and which setting?
2. Which BPMH sources do you have access to?
3. Which DDI / drug-knowledge source is licensed?
4. Who is the reconciler — pharmacist, provider, nurse?
5. How will you persist the reconciliation event in FHIR?
6. Which quality measures are you reporting against?

Related Skills

• healthcare-context: Setting and EHR drive the med rec workflow.
• cpoe-orders: Where MedicationRequest is created and updated.
• clinical-decision-support: Order-sign hooks fire DDI / dose checks against the post-rec list.
• fhir-integration: MedicationStatement, MedicationRequest, MedicationDispense, MedicationAdministration.
• terminology-services: RxNorm (RxCUI, SCD, SBD), NDC, ATC, mapping APIs (RxNav).
• ehr-integration: Vendor-specific med history APIs, Surescripts wiring.
• value-based-care: Med rec measures tie to MIPS, HEDIS MRP, readmission penalties.