Medication Reconciliation: quick answer用药核对：快速回答
Medication reconciliation is a controlled comparison and resolution process. It is broader than copying a medication history because discrepancies must be classified, clarified, documented, and communicated.
用药核对需要明确两个状态：照护转换前的最佳可得用药史，以及入院、转科或出院后的预期方案。相关资料应保留来源、时间和待确认问题，诊断或治疗判断仍由医疗专业人员负责。
Where medication reconciliation fits用药核对的适用范围
Clinicians, pharmacists, nurses, care coordinators, and health information teams use medication reconciliation to compare medication lists at care transitions, explain every difference, and produce one accountable list for professional confirmation. The working evidence includes the best possible medication history, admission orders, transfer orders, discharge prescriptions, allergies, adherence notes, and sources. These boundaries determine what a useful output must contain and which conclusions require professional review.
用药核对由相应临床、数据、信息管理和治理人员共同参与。相关资料需组织成可追溯、可复核的结果，并明确数据边界、不确定性、待确认问题与最终责任人。
Clinicians, pharmacists, nurses, care coordinators, and health information teams.
应由具有相应职责和专业范围的人员完成最终解释与确认。
Compare medication lists at care transitions, explain every difference, and produce one accountable list for professional confirmation.
输出应保留来源、时间、不确定性、待确认问题和处置责任。
Evidence model for medication reconciliation用药核对所需证据模型
Medication reconciliation requires two explicitly defined states: the best available pre-transition history and the intended regimen after admission, transfer, or discharge. Compare ingredient, formulation, strength, dose, route, frequency, indication, status, and timing for every item. Evidence also includes inpatient administrations, temporary holds, formulary substitutions, documented reasons for change, monitoring plans, and confirmation that the patient and receiving team received the final instructions.
用药核对需要明确两个状态：照护转换前的最佳可得用药史，以及入院、转科或出院后的预期方案。每项药物都要比较成分、剂型、规格、剂量、途径、频次、适应证、状态和时间。证据还包括住院给药、临时暂停、目录替代、变更理由、监测计划，以及患者和接收团队已经获得最终说明的确认记录。
Review gates for medication reconciliation用药核对复核关口
| Review gate复核关口 | Topic-specific question本主题问题 | Expected evidence预期证据 |
|---|---|---|
| Identity and scope身份与范围 | Does the record match the intended people, setting, and time window for medication reconciliation?记录是否符合用药核对所需的人群、场景和时间范围？ | Source register and dated inclusion rules来源登记与带日期的纳入规则 |
| Meaning含义 | Can the team distinguish the evidence needed to compare medication lists at care transitions, explain every difference, and produce one accountable list for professional confirmation?团队能否区分完成本主题任务所需的不同证据？ | Field definitions, status, provenance, and sampled source records字段定义、状态、来源和抽样原始记录 |
| Professional review专业复核 | Are uncertainty, exceptions, and the accountable reviewer visible?不确定性、例外和责任复核者是否清晰？ | Review note, disposition, and unresolved-question list复核记录、处置意见和待确认问题清单 |
| Acceptance验收 | Do the topic-specific measures show that the workflow is usable and reproducible?本主题指标能否证明流程可用且可复现？ | Versioned result, validation sample, and correction log版本化结果、验证样本和纠错日志 |
How to carry out medication reconciliation如何执行用药核对
- Step 1. Establish the best possible medication history before comparing orders.
- Step 2. Build a side-by-side list for the pre-transition and intended post-transition states.
- Step 3. Classify each difference as intentional, unexplained, duplicate, omission, or uncertain.
- Step 4. Route unexplained discrepancies to the accountable prescriber or pharmacist.
- Step 5. Communicate the confirmed list, reasons for changes, monitoring, and follow-up to the next setting.
- 第 1 步。在比较医嘱前建立最佳可得用药史。
- 第 2 步。并列展示转换前状态和转换后的预期状态。
- 第 3 步。把每项差异分类为有意、无法解释、重复、遗漏或待确认。
- 第 4 步。把无法解释的差异交给负责的处方医生或药师。
- 第 5 步。向下一照护场景传递确认清单、变更理由、监测要求和随访安排。
Working note 1. Begin by making the first action operational: establish the best possible medication history before comparing orders. Name the person who can confirm scope, the time cutoff, the source systems that count, and the conditions that place a record outside the care-transition medication review. For medication reconciliation, a clear entry rule prevents a convenient dataset from silently replacing the intended population or clinical question. Preserve rejected records with a reason code so responsible specialists can distinguish a deliberate exclusion from a missing or failed import.
Working note 2. The second action is evidence control: build a side-by-side list for the pre-transition and intended post-transition states. Write down when each item happened, when it became available, who entered or supplied it, whether it is preliminary or final, and how corrections are represented. The relevant material may include the best possible medication history, admission orders, transfer orders, discharge prescriptions, allergies, adherence notes, and sources. Do not collapse two values merely because their labels look alike. A reviewer has to be able to return from a normalized field to the original record and understand every transformation in between.
Working note 3. At the third action, classify each difference as intentional, unexplained, duplicate, omission, or uncertain. Establish the expected intermediate artifact before processing starts: a compared list, time-aligned cohort, mapped event, scored observation, or another output appropriate to medication reconciliation. Retain conflicts and uncertainty visible. When a source is incomplete, the operating sequence has to say whether the item is excluded, retained with a flag, estimated under a declared rule, or sent for clarification; silent imputation can make a clean result clinically misleading.
Working note 4. The fourth action requires contextual interpretation: route unexplained discrepancies to the accountable prescriber or pharmacist. Separate what the records directly show from what the accountable service infers, and record plausible alternative explanations. The objective is to compare medication lists at care transitions, explain every difference, and produce one accountable list for professional confirmation, not to convert a pattern into an unsupported diagnosis, causal claim, or treatment instruction. Reviewers has to see the denominator, comparison point, timing assumptions, and exceptions that could change the meaning of the output before any operational or clinical response is considered.
Working note 5. Close the cycle through the fifth action: communicate the confirmed list, reasons for changes, monitoring, and follow-up to the next setting. Assign every unresolved item to a named role, define the response time, and record the final disposition without deleting the earlier state. The handoff has to include the source cutoff, version, material exceptions, validation status, and next review date. This makes medication reconciliation reproducible when another qualified member of clinicians, pharmacists, nurses, care coordinators, and health information teams needs to reconstruct why the output was accepted, challenged, corrected, or left unresolved.
执行说明 1。首先把第一项行动落实为可执行规则：在比较医嘱前建立最佳可得用药史。需要明确谁有权确认范围、资料截止时间、哪些来源有效，以及什么条件会让记录不进入复核。对于用药核对，清晰的入口规则可以防止方便取得的数据悄然替代真正的人群或临床问题。被排除的记录仍应保留原因代码，使复核者能够区分主动排除、资料缺失和导入失败。
执行说明 2。第二项行动关注证据控制：并列展示转换前状态和转换后的预期状态。每项资料都要记录事件发生时间、可用时间、录入或提供者、初步或最终状态，以及修订如何表示。相关资料必须覆盖用药核对所需的来源、时间、状态、编码、单位和上下文。不能因为标签相似就合并两个数值；复核者应能从规范化字段回到原始记录，并理解中间每一步转换。
执行说明 3。第三项行动是把每项差异分类为有意、无法解释、重复、遗漏或待确认。处理开始前，应先定义符合用药核对需要的中间成果，例如对照清单、时间对齐人群、映射事件或带来源的观察结果。冲突和不确定性必须可见。来源不完整时，流程应说明是排除、带标记保留、按已声明规则估计，还是转交确认；静默填补可能让整洁结果产生错误临床含义。
执行说明 4。第四项行动要求结合背景解释：把无法解释的差异交给负责的处方医生或药师。应区分记录直接显示的事实和团队作出的推断，并保留其他合理解释。目标是支持用药核对所界定的资料整理、分析和复核任务，而不是把模式直接写成未经支持的诊断、因果结论或治疗指令。在采取运营或临床响应前，复核者需要看到分母、比较点、时间假设和可能改变结论的例外。
执行说明 5。第五项行动用于闭环：向下一照护场景传递确认清单、变更理由、监测要求和随访安排。每个未解决项目都要分配给明确角色，规定响应时间，并在不删除先前状态的情况下记录最终处置。交接材料应包含来源截止时间、版本、重要例外、验证状态和下次复核日期，使另一位合格人员能够重建为何结果被接受、质疑、纠正或继续保持未解决。
Depth check 1. For a deeper review, test the entry rule against boundary cases that are easy to misclassify in medication reconciliation: records just inside or outside the time window, repeated episodes, transfers, corrected identities, and evidence received after the decision point. Ask two independent responsible specialists to apply the rule to a small sample and reconcile disagreements. The disagreement log is often more informative than an overall pass rate because it exposes ambiguous definitions that would otherwise create inconsistent cohorts, lists, or alerts at scale.
Depth check 2. Build a compact data dictionary for the fields that carry the decision. Each definition has to include the clinical or operational meaning, original name, permitted values, units, status codes, event time, availability time, null meaning, correction behavior, and authoritative source. In medication reconciliation, blank, unknown, not performed, not applicable, and not yet available are not interchangeable. Test the dictionary against narrative notes and source screenshots so structured values are not accepted without checking how they were produced in practice.
Depth check 3. Use deliberately difficult records to test the transformation step: duplicated events with different identifiers, a value later corrected, two credible sources that disagree, an item recorded after the event but referring to an earlier time, and a valid exception that resembles an error. Document the expected output and the professional rationale before running the operating sequence. A useful test set for medication reconciliation contains both positive and negative cases; otherwise a system can appear accurate simply by flagging everything or suppressing uncertain records.
Depth check 4. Interpretation has to include a counter-explanation exercise. For every material finding, state at least one data, workflow, population, or timing explanation that could produce the same pattern. Then identify which additional evidence would distinguish those explanations and whether that evidence is available before action is required. This discipline is especially important when the work is used to compare medication lists at care transitions, explain every difference, and produce one accountable list for professional confirmation, because an association, discrepancy, score, or model output can be real while the proposed explanation is still wrong.
Depth check 5. Before wider use, run the complete workflow with representative users and observe where they pause, override, seek another record, or cannot act. Measure not only technical correctness but also unresolved volume, time to review, correction rate, disagreement, missed cases, unnecessary interruptions, and whether the responsible role can complete the next step. Write down changes to data, logic, interface, thresholds, and policy separately; after a material change, repeat the relevant medication reconciliation tests rather than assuming the earlier acceptance still applies.
Depth check 6. End the care-transition medication review with a short professional conference note. It has to identify the care-transition medication evidence considered, the material disagreement, the reason one interpretation was preferred, the person accountable for the disposition, and the condition that would trigger reconsideration. For medication reconciliation, this note is not administrative decoration: it connects the analytical or screening result to a transparent human decision. It also allows a later reviewer to see whether new data changed the care-transition medication evidence, the interpretation, or only the action that was feasible at the time. Where local policy sets a required escalation route, approval level, or review interval, record that rule beside the disposition so the reasoning and the accountable process remain visible together.
深度检查 1。深度复核时，应使用容易误分类的边界病例测试用药核对入口规则，包括刚好位于时间窗内外的记录、重复照护阶段、转科、身份修订，以及决策时点之后才到达的证据。可让两名复核者独立应用规则，再对分歧进行核对。分歧日志往往比总体通过率更有价值，因为它能暴露会在大规模使用时造成清单、人群或提示不一致的模糊定义。
深度检查 2。应为承载决策的字段建立精简数据字典，记录其临床或运营含义、原始名称、允许值、单位、状态代码、事件时间、可用时间、空值含义、修订方式和权威来源。在用药核对中，空白、未知、未实施、不适用和尚未取得不能互换。还应使用叙述记录和来源界面抽样核对，不能在不了解结构化值如何产生的情况下直接接受。
深度检查 3。使用刻意设置的困难记录测试转换步骤，例如标识不同的重复事件、后来被更正的数值、两个可信来源之间的冲突、事后录入但指向较早时间的项目，以及看似错误却合理的例外。运行前先写出预期输出和专业理由。用药核对测试集必须同时包含阳性与阴性情形，否则全部标记或全部压制不确定记录也可能呈现虚假的高准确性。
深度检查 4。解释阶段应进行反向解释练习。对每项重要发现，至少提出一种能够产生相同模式的数据、流程、人群或时间原因，再说明需要什么额外证据才能区分这些解释，以及行动前能否获得这些证据。用药核对用于支持专业判断时尤其需要这样做，因为关联、差异、评分或模型输出可能真实存在，但团队提出的原因仍可能错误。
深度检查 5。扩大使用前，应让代表性用户完成完整流程，观察他们在哪里停顿、否决、寻找其他记录或无法行动。除技术正确性外，还要检查未解决数量、复核耗时、纠错率、意见分歧、漏检、不必要打扰，以及责任角色能否完成下一步。数据、逻辑、界面、阈值和制度变更应分别记录；重大变化后必须重新执行相关用药核对测试。
深度检查 6。复核结束时，应形成简短的专业会商记录，说明采用了哪些证据、主要分歧是什么、为何倾向某种解释、谁对处置负责，以及什么条件会触发重新评估。对于用药核对，这不是行政装饰，而是把分析或筛查结果连接到透明的人类决策，也让后续复核者判断新资料改变的是证据、解释，还是当时能够采取的行动。如果本地制度规定升级路径、批准层级或复核周期，应把该规则与处置记录放在一起，使判断理由和责任流程同时可见。
A worked medication reconciliation scenario用药核对工作示例
At discharge, the team compares the pre-admission list with inpatient administrations and intended discharge therapy. A missing medicine is treated as an unresolved discrepancy until the prescriber confirms whether omission is intentional. This is a hypothetical workflow example, not an individual clinical recommendation or a product-performance claim.
假设示例：出院时，团队把入院前清单、住院实际给药和预期出院方案并列比较。某种长期药物没有出现在出院处方中，团队没有直接认定为停药，而是标记为无法解释的遗漏，联系处方医生确认意图，记录理由，并把最终结果同步给患者和后续服务方。该示例只说明工作流，不构成个体化临床建议或产品效果声明。
Validation and operating measures for medication reconciliation用药核对的验证与运行指标
Measure completion by resolved discrepancies and successful handoff, not by whether a form was opened. Useful measures include transitions with a source-attributed history, reconciliation completed within the required window, unresolved high-priority discrepancies, documented reasons for changes, patient understanding, delivery to the next provider, and corrections made to the longitudinal record. Audit a sample for clinical meaning as well as field completion.
完成情况应以差异得到解决并成功交接为准，而不是表单是否被打开。可用指标包括具有来源用药史的转换比例、规定时间内完成核对的比例、未解决高优先级差异、变更理由记录、患者理解程度、向下一服务方传递情况，以及纵向记录得到修正的情况。抽查时既要看字段完整度，也要看临床含义。
Interpret medication reconciliation without losing context在不丢失背景的情况下解释用药核对
A discrepancy is not automatically an error. Starting an anticoagulant, withholding a medicine for a procedure, changing route while a patient cannot swallow, or using a formulary equivalent may be intentional. The workflow must show who authorized the change, why it was made, how long it applies, and what follow-up is required. Conversely, a copied-forward medicine is not valid merely because it appears on several documents; repeated copying can propagate the same unresolved mistake.
差异不一定就是错误。开始抗凝、因操作暂缓药物、患者无法吞咽时改变途径，或使用目录内等效品都可能是有意变更。流程必须说明由谁批准、为何变更、适用多久以及需要什么随访。反过来，一种药出现在多份文件中也不代表其一定正确；反复复制可能只是传播同一个未解决错误。
Failure modes and limits of medication reconciliation用药核对的失败模式与限制
Reconciliation fails when the source history is weak, the intended regimen is ambiguous, ownership is split, or changes are communicated only in one system. It can also create false confidence if teams mark every difference resolved without recording evidence. A data analyst may assemble and classify discrepancies, but decisions to continue, stop, substitute, or alter a dose require authorized clinical review. Time-critical uncertainty should follow the local escalation route rather than wait for routine reconciliation.
当来源用药史薄弱、预期方案含糊、责任分散，或变更只记录在一个系统中时，用药核对容易失败。如果团队在没有证据的情况下把所有差异标记为已解决，也会制造虚假安全感。数据人员可以整理和分类差异，但继续、停用、替换或调整剂量必须由获授权的临床专业人员决定；时间敏感的不确定事项应按本地升级流程处理。
Organized records and tool output support trend recognition and professional decisions. Drug interactions, risk predictions, diagnoses, and treatment conclusions require qualified medical review.
整理后的资料和工具输出仅用于趋势识别和专业决策辅助。药物相互作用、风险预测、诊断与治疗结论必须由合格医疗专业人员审核。
Operate medication reconciliation as a controlled workflow把用药核对作为受控工作流运行
Turn medication reconciliation into a written operating brief before configuring a dashboard, rule, model, or review queue. Name the intended users—clinicians, pharmacists, nurses, care coordinators, and health information teams—and state the decision, time available, acceptable uncertainty, and consequence of a delayed or incorrect result. The brief has to use the bounded objective to compare medication lists at care transitions, explain every difference, and produce one accountable list for professional confirmation. Requests such as “show insights” or “find risk” are not testable until the population, event, time window, owner, and permitted action are explicit.
Create a source register for the best possible medication history, admission orders, transfer orders, discharge prescriptions, allergies, adherence notes, and sources. For every source, document its steward, collection process, event time, availability time, status model, code or unit system, revision behavior, coverage, and known gaps. Then connect the first two workflow actions—establish the best possible medication history before comparing orders and build a side-by-side list for the pre-transition and intended post-transition states—to named fields and documents. This prevents a familiar label from being treated as equivalent across systems when the underlying event or meaning is different.
Build test records before full use of medication reconciliation. Include ordinary cases, missing fields, duplicate identities, conflicting sources, late events, corrected values, unusual but valid states, and records that has to not enter the operating sequence. Use the middle action, classify each difference as intentional, unexplained, duplicate, omission, or uncertain, to define expected results for each case. Retain the expected professional explanation beside the technical expectation so a passing transformation does not conceal an interpretation error.
Separate technical acceptance from domain acceptance. Technical review shows that inputs arrive, mappings run, calculations reproduce, permissions work, and failures are visible. Domain review asks whether the information has the correct meaning for medication reconciliation, reaches the intended professional at the right moment, and supports a safe response. The later workflow actions—route unexplained discrepancies to the accountable prescriber or pharmacist and communicate the confirmed list, reasons for changes, monitoring, and follow-up to the next setting—has to be demonstrated in the real interface rather than inferred from a data extract.
Establish correction, escalation, and change control before launch. Users need a route to challenge a result, repair a source or mapping, annotate an exception, and determine which prior outputs are affected. Version the source contract, terminology, logic, thresholds, display, and review policy. When any material element changes, compare new and previous results on representative records, decide whether earlier medication reconciliation outputs remain valid, and document who approved the release and who can roll it back.
The final medication reconciliation handoff has to let another qualified reviewer understand and reproduce the output without relying on undocumented team knowledge. Include the purpose, inclusion rules, source inventory, data cutoff, original evidence links, transformations, workflow state, exceptions, validation results, reviewer disposition, and unresolved questions. Add the specific evidence used to compare medication lists at care transitions, explain every difference, and produce one accountable list for professional confirmation, identify which statements are observed versus inferred, and state the next review date. Sensitive details has to remain only in approved systems with role-appropriate access and retention.
在配置仪表板、规则、模型或复核队列前，应先把用药核对写成运行说明。明确目标用户、支持的决策、可用时间、可接受不确定性，以及延迟或错误结果的后果。说明中必须写清人群、事件、时间窗口、责任人和允许采取的行动；“寻找洞察”或“发现风险”等宽泛要求无法直接测试和验收。
针对用药核对所需资料建立来源登记表。每个来源都应记录数据责任人、采集过程、事件时间、可用时间、状态模型、编码或单位体系、修订方式、覆盖范围和已知缺口。随后把前两个工作步骤——在比较医嘱前建立最佳可得用药史和并列展示转换前状态和转换后的预期状态——落实到具体字段和文档，防止把名称相似但事件含义不同的数据直接视为等价。
全面使用用药核对前应建立测试记录，覆盖普通情况、字段缺失、身份重复、来源冲突、事件延迟、数值修订、少见但有效的状态，以及本来不应进入流程的记录。围绕“把每项差异分类为有意、无法解释、重复、遗漏或待确认”为每个测试病例写出预期结果，并把专业解释与技术预期放在一起，避免技术转换通过却隐藏解释错误。
技术验收和领域验收必须分开。技术复核证明输入到达、映射运行、计算可复现、权限有效且失败可见；领域复核则确认信息对用药核对含义正确、在合适时间到达目标专业人员并支持安全响应。后两个步骤——把无法解释的差异交给负责的处方医生或药师和向下一照护场景传递确认清单、变更理由、监测要求和随访安排——应在真实界面和工作流中演示，不能只从数据抽取结果推断。
上线前定义纠错、升级和变更控制。使用者需要能够质疑结果、修复来源或映射、标注例外，并判断哪些既往输出受到影响。来源合同、术语、逻辑、阈值、显示和复核制度都应进行版本管理；任何重大变化后，都要在代表性记录上比较新旧结果，判断既往用药核对输出是否仍有效，并记录批准者和回滚责任人。
最终用药核对交接包应让另一位合格复核者无需依赖团队未记录的知识，就能理解并复现结果。材料应包含目的、纳入规则、来源清单、数据截止时间、原始证据链接、转换过程、工作流状态、例外、验证结果、复核处置和待确认问题；还要区分观察与推断、说明下次复核日期，并把敏感详情限制在具有适当访问和保留控制的获批系统中。
Prepare medication reconciliation evidence with 医数智析用医数智析准备用药核对资料
Before opening the workspace, prepare the best possible medication history, admission orders, transfer orders, discharge prescriptions, allergies, adherence notes, and sources. 医数智析 can help organize those materials into a longitudinal record, expose missing or conflicting entries, and make cross-time patterns available for professional review. Final clinical interpretation remains with qualified professionals.
打开工作区前，请准备与用药核对直接相关的原始资料、日期和来源。医数智析可帮助整理纵向记录、暴露缺失或冲突，并把跨时间变化呈现给专业人员复核；最终临床解释仍由合格专业人员负责。
View the 医数智析 tool page查看医数智析工具页 Open the live experience打开实际体验页Medication Reconciliation questions用药核对常见问题
A medication history records what a person has been taking and the evidence source. Medication reconciliation compares that history with current orders, resolves discrepancies, and communicates an approved list at a transition.
用药史记录患者曾经或正在使用什么以及信息来源；用药核对则把该历史与当前医嘱比较，解决差异，并在照护转换时传递经过确认的清单。
It is especially important at admission, internal transfer, discharge, referral, change of prescriber, and return to community care because intended therapy can change at each handoff.
入院、院内转科、出院、转诊、更换处方医生以及返回社区照护时尤其重要，因为每次交接都可能改变预期方案。
The workflow should assign it to a named role with authority to clarify the regimen, commonly the responsible prescriber or pharmacist under local policy.
流程应把问题分配给有权确认方案的明确角色，通常是本地制度规定的责任处方医生或药师。
Primary source for medication reconciliation用药核对的主要参考来源
Use the cited primary or official source together with current organizational policy and the professional standards that apply in the intended setting.
实施时应把下列第一方或权威来源与当前机构制度及适用专业标准结合使用。