The practical answer to the question of how EHR medication reconciliation workflows are demonstrated is uneven: some vendors publish detailed click-by-click instructions, while national guidance describes design principles rather than screen sequences. AHRQ explains reconciliation as comparison of a patient's current regimen against admission, transfer, or discharge orders to identify discrepancies, with an EHR medication profile acting as a single viewing location [1][8]. Vendor documentation adds concrete mechanics, such as Elation's flagging of likely inactive medications and TruBridge's discharge discontinue-reason prompts [2][5]. An academic post-acute report supplies usable completion-rate evidence: admission reconciliation rose from 13% to 87% in an inpatient rehabilitation facility and from 51% to 82% in a long-term acute care hospital after a standardized workflow, education, dashboard monitoring, outreach and feedback [6]. Together, these sources support evaluating demonstrations around several decision points rather than assuming any one sequence is universally correct.
What a named workflow actually contains
The most complete vendor-level demonstration in the public documents is Elation's medication list guide, which describes entry paths and screen fields. Users open reconciliation through the Reconcile Meds button in the Clinical Profile, via MedsHx menus, from a legacy visit note, or through an Elation Note icon in the Reconciled Medications block [2]. Elation states that AI algorithms analyze the patient problem list, risk factors such as age, and prescription or dispensing history to identify drugs likely no longer being taken [2]. Medications flagged as likely not taking appear with context notes, and the user can document discontinuation or adherence before completing the reconciliation [2].
AHRQ's MATCH chapter outlines a different layer: process design choices that precede screen behavior. It recommends building a single source of truth that includes documentation and confirmation of the current medication list, then confirming that list with the patient for accuracy and completeness [1]. The guidance also frames integration questions, such as how admission points can be embedded into existing workflow, and notes that an EHR medication profile can be pulled into forms or displayed when current lists are obtained [1]. These two documents illustrate that a demonstration may show either the interface mechanics or the surrounding clinical ownership rules, and evaluators should ask which layer is being documented.
Source selection and duplicate handling as decision points
RPMS documentation for the IHS Clinical Information Reconciliation Tool shows a more structured document-driven flow. The user selects a CCDA document, and problems, adverse reactions and medications from that source populate the Clinical Document pane, while RPMS pane data displays local pharmacy package medications; each document must be reconciled separately [3]. Clicking a medication in either pane highlights matching items in the other pane and in the reconciled panel, with a match defined by code correspondence [3]. This demonstrates how a federal EHR handles external source ingestion, a decision point absent from a simpler ambulatory flow.
CalMHSA's SmartCare guide identifies a different failure mode: duplicate medication entries. It states that medications from SmartCare Medication Management Rx and CalMHSA Rx for the same client can both be pulled into the list page, producing duplicates [7]. The list page also only pulls active medications or those with an end date within 90 days [7]. These limits are useful evaluation questions for any demonstration: how duplicates are generated, whether historical overrides are retained, and what lookback window the reconciliation screen applies. CalMHSA notes that overridden reconciliation information is not stored historically [7].
A short evaluation checklist from the public documents
Check whether the vendor can show: a single medication profile used at admission, transfer and discharge [1]; a source-document selection step and code-based matching when external CCDA data is imported [3]; a discontinue-reason and alternative-medication prompt at discharge [5]; and an explicit handling rule for duplicate or stale entries plus any historical override retention limit [7]. For post-acute settings, ask whether the vendor can describe education, dashboard and outreach supports, because the measured completion improvement accompanied those workflow changes rather than screen design alone [6].
Transition-specific triggers: admission, transfer and discharge
AHRQ specifies three workflow windows for hospital reconciliation: admission, intra-hospital transfer and discharge, with the goal of incorporating a single source of truth into each [1]. TruBridge's Prescription Entry guide supplies a discharge-focused trigger sequence. After choosing a home or active medication to continue, the user can encounter a discontinue-reason step; if a medication was modified, an alternative medication selection screen prompts for a replacement, and if no match exists, a non-formulary option opens a search by drug class [5]. TruBridge states that Prescription Entry does not require discharge reconciliation except potentially in the ED when an ED General Control table requires it for a stay type [5].
The VHA directive frames these transitions as part of a medication treatment plan, defined as a list of all medications the patient is meant to take plus associated information needed for successful medication care, including follow-up, diagnostics and anticipatory guidance [4]. VHA policy also defines non-VA medications as those documented by the health care team in CPRS and included in the essential medication list for review [4]. For workflow demonstrations, this raises the question of whether outside prescriptions and patient-reported medications appear in the same review screen as internal orders, which the RPMS CCDA flow and the VHA policy both address but in different terms.
A measured improvement example and what it cannot prove
The post-acute intervention study from Pennsylvania's Patient Safety Authority is the only supplied source with before-and-after completion data. Investigators identified missed doses of important medications from the discharging hospital's list and inconsistent AdmMedRec tool use, then applied failure mode and effects analysis and iterative Plan-Do-Study-Act cycles [6]. Interventions included a standardized workflow, one-on-one training, a tip sheet, an EHR dashboard, monitoring of reconciliation status with proactive provider outreach, and feedback collection [6]. Completion improved from 13% to 87% in the inpatient rehabilitation facility and 51% to 82% in the long-term acute care hospital over four months [6].
The study does not report a controlled comparison or isolate the dashboard's independent effect, and the participating units are post-acute settings within one academic medical center. The authors describe an anticipated decrease in medication errors but do not supply an error-rate denominator in the provided text [6]. For evaluators, this example illustrates a demonstration of workflow redesign and measurement rather than a screen-level product capability. It also indicates that workflow documentation alone may not change behavior; the reported gain followed education, dashboards and outreach layered onto the EHR tool [6].
A concrete walkthrough to use during vendor demonstrations
As a suggestion for structuring a product evaluation, an evaluator could script a transfer-in patient scenario with a known home medication list and then ask the vendor to run the same steps in their system. The scenario would begin with confirming the existing list, then documenting an adherence note for one maintenance medication, discontinuing a second medication with a reason, and continuing a third across a unit transfer. AHRQ's guidance supports confirming the list with the patient and communicating role responsibilities, while Elation shows a corresponding free-text adherence field and immediate discontinuation path with a selected reason [1][2].
The script should then probe boundary behavior. CalMHSA documentation indicates a 90-day lookback and possible duplicates across Rx platforms, so an evaluator could ask how older prescriptions and duplicate records are represented [7]. TruBridge documentation prompts for alternative medication selection when a home medication is modified at discharge, which provides a test case for formulary and same-class replacement behavior [5]. None of these steps should be treated as validated performance measures; rather, the walkthrough reveals whether a vendor demonstrates the decision points that the supplied primary documents describe [2][5][7].
Sources & references
- Chapter 3. Developing Change: Designing the Medication Reconciliation Process | Agency for Healthcare Research and Quality · www.ahrq.gov
- Medication List Management Guide - Reconciling active medications · help.elationhealth.com
- Electronic Health Record (EHR) · www.ihs.gov
- [PDF] VHA Directive 1345 Medical Reconciliation - VA.gov · www.va.gov
- [PDF] Prescription Entry User Guide · userareas.cpsi.com
- Iterative Interventions to Improve Admission Medication Reconciliation Completion Rates and Reduce Medication Errors at Pos · patientsafety.pa.gov
- How to Complete a Medication Reconciliation - 2023 CalMHSA · 2023.calmhsa.org
- Medications at Transitions and Clinical Handoffs (MATCH) Toolkit for Medication Reconciliation | Agency for Healthcare Research and Quality · www.ahrq.gov