ModelRefs / Medication Reconciliation — Architecture Blueprint
Medication Reconciliation — Architecture Blueprint
Production architecture blueprint for Medication Reconciliation: components, deployment patterns, cost & latency, failure modes, evaluation and governance, with sources and review dates.
Overview
This is the implementation view of Medication Reconciliation: the components it requires, where it can run, what it costs in latency and spend, how it fails, and what you must measure before putting it in front of users.
4 components to assemble, 5 documented failure modes, high implementation complexity. Every statement below comes from the canonical workflow record with its sources and review date; where the evidence does not settle a question, the page says so rather than filling the gap.
What this workflow takes in and produces
Takes in
- medication histories
- orders
- discharge records
- allergy records
Produces
- normalized medication lists
- discrepancy flags
- clinician-review queues
Applied to
- medication-list extraction
- transition-of-care discrepancy review
Components you need to assemble
A working implementation needs 4 distinct components. Each is a build-or-buy decision in its own right.
- clinical terminology mapping
- source-of-truth medication list
- rule checks
- pharmacist or clinician review
Implementation complexity: high. This describes the integration and evaluation effort, not the difficulty of any single component.
Deployment patterns
Deployment options recorded for this workflow: managed-api, hybrid.
Topologies it has been recorded against: serverless-api, managed-container, hybrid-private-cloud. Each changes the data-residency, scaling and cost profile, so confirm the one you need against current provider documentation.
Cost and latency
- Terminology mapping and multi-source retrieval add latency and integration cost.
- Measure reviewer time and prevented or introduced discrepancies alongside inference cost.
How this workflow fails
Observed failure modes for this class of workflow. Design a check for each one before shipping, not after.
- missed medication
- dose or frequency error
- duplicate therapy
- false conflict
- allergy omission
Risk areas the evidence covers
- extraction accuracy
- normalization
- discrepancy detection
- human override
Proving it works before you ship
Evaluation readiness: Partial — AHRQ process guidance supports a shared source of truth and discrepancy resolution; deployment-specific extraction and safety thresholds remain unregistered.
Worked evaluation case: Transition-of-care medication reconciliation
Compare an incoming medication history with current orders and discharge records, then send every discrepancy to a qualified reviewer.
What to measure
- medication extraction precision and recall
- dose, route, and frequency normalization accuracy
- duplicate, conflict, and missing-medication detection
- allergy and discontinued-medication handling
- reviewer override and unresolved-discrepancy rate
Governance and data handling
- Restrict medication and allergy data to authorized clinical workflows.
- Record provenance and require a qualified reviewer to resolve discrepancies.
Implementation notes
- Keep each extracted medication linked to its source and separate extraction confidence from clinical conflict resolution.
- Test dosage, route, frequency, discontinued items, allergies, duplicates, and incomplete histories independently.
- Expose the source list, discrepancy basis, and unresolved uncertainty to the qualified reviewer; do not convert a discrepancy flag into a treatment directive.
What this blueprint does not establish
- This workflow does not replace pharmacist or clinician judgment.
- Source records can be incomplete or contradictory even when extraction is accurate.
Source coverage: Partial — AHRQ supports a shared medication source of truth and structured reconciliation workflow; FDA guidance treats medication-reconciliation notifications as clinician support when professional judgment remains primary. Neither certifies automated reconciliation.
Sources reviewed 2026-07-02. Revalidate medication vocabularies, local reconciliation policy, software-function scope, and clinical safety controls before deployment.
Sources
- Developing Change: Designing the Medication Reconciliation Process Agency for Healthcare Research and Quality · official · accessed 2026-06-29
- Medication Reconciliation AHRQ Patient Safety Network · official · accessed 2026-06-29
- Step 6: Is the Software Function Intended to Provide Clinical Decision Support? U.S. Food and Drug Administration · official · accessed 2026-07-02
Candidate models and benchmarks
Candidate models with published references, the providers behind them, and the benchmarks whose task shape bears on this workflow are on the Medication Reconciliation workflow reference. This blueprint covers implementation; that page covers selection.
Continue your research
Use these connected ModelRefs sections to compare alternatives, inspect implementation paths, and review the evidence and governance boundaries relevant to Medication Reconciliation — Architecture Blueprint.