Patient Journey Analytics: quick answer患者旅程分析：快速回答
Patient journey analytics is sequence- and touchpoint-centered. Patient analytics is person-centered and can study status, risk, utilization, or outcomes without reconstructing the path between interactions.
患者旅程分析重建转诊、预约、就诊、检查、治疗、药房、出院、沟通和随访等接触点的顺序。相关资料应保留来源、时间和待确认问题，诊断或治疗判断仍由医疗专业人员负责。
A worked patient journey analytics scenario患者旅程分析工作示例
A service maps the interval from referral to first specialist visit. It separates scheduling delay, missing prerequisites, cancellations, repeated contacts, and clinical urgency while protecting patient identity. This is a hypothetical workflow example, not an individual clinical recommendation or a product-performance claim.
假设示例：团队研究异常结果到专科随访的过程，把检验、通知、转诊、预约、就诊和后续计划按事件时间连接。部分长间隔来自患者选择延后，另一些来自转诊责任不清。团队结合患者反馈和服务记录区分原因，并分别改进沟通和交接，而不是把所有延迟归为同一种失败。该示例只说明工作流，不构成个体化临床建议或产品效果声明。
Where patient journey analytics fits患者旅程分析的适用范围
Patient-experience teams, access leaders, care coordinators, service designers, and healthcare analysts use patient journey analytics to reconstruct sequences across touchpoints and episodes to identify delay, dropout, duplication, handoff failure, and variation in the care journey. The working evidence includes referrals, appointments, encounters, portal and call interactions, transitions, handoffs, waiting intervals, outcomes, and patient-reported experience. These boundaries determine what a useful output must contain and which conclusions require professional review.
患者旅程分析由相应临床、数据、信息管理和治理人员共同参与。相关资料需组织成可追溯、可复核的结果，并明确数据边界、不确定性、待确认问题与最终责任人。
Patient-experience teams, access leaders, care coordinators, service designers, and healthcare analysts.
应由具有相应职责和专业范围的人员完成最终解释与确认。
Reconstruct sequences across touchpoints and episodes to identify delay, dropout, duplication, handoff failure, and variation in the care journey.
输出应保留来源、时间、不确定性、待确认问题和处置责任。
Evidence model for patient journey analytics患者旅程分析所需证据模型
Patient journey analytics reconstructs ordered touchpoints across referral, scheduling, consultation, testing, treatment, pharmacy, discharge, communication, and follow-up. Each event needs a type, event time, location or channel, responsible service, status, predecessor or episode relationship, and evidence source. The model should distinguish a true absence from missing capture, planned waiting from avoidable delay, repeated care from duplication, and patient choice from system failure. Journey boundaries and episode rules must be explicit.
患者旅程分析重建转诊、预约、就诊、检查、治疗、药房、出院、沟通和随访等接触点的顺序。每个事件需要类型、事件时间、地点或渠道、责任服务、状态、前序或阶段关系和证据来源。模型应区分真实缺失与数据未捕获、计划等待与可避免延迟、重复照护与无效重复，以及患者选择与系统失败；旅程边界和照护阶段规则必须明确。
How to carry out patient journey analytics如何执行患者旅程分析
- Step 1. Define the journey start, end, episode rules, population, and experience or service question.
- Step 2. Create a common event taxonomy across clinical, administrative, digital, pharmacy, and communication systems.
- Step 3. Order events by occurrence time, link handoffs, and mark missing, duplicated, cancelled, and rescheduled touchpoints.
- Step 4. Analyze common sequences, time between steps, loops, drop-off, variation, and points where responsibility changes.
- Step 5. Review journey patterns with patients and service owners before redesigning access, communication, or handoffs.
- 第 1 步。定义旅程起点、终点、阶段规则、人群和体验或服务问题。
- 第 2 步。在临床、行政、数字、药房和沟通系统之间建立共同事件分类。
- 第 3 步。按发生时间排序事件，连接交接，并标记缺失、重复、取消和改期接触点。
- 第 4 步。分析常见序列、步骤间时间、循环、脱落、差异和责任变化位置。
- 第 5 步。与患者及服务负责人共同复核旅程模式后再改进可及性、沟通或交接。
Working note 1. Begin by making the first action operational: define the journey start, end, episode rules, population, and experience or service question. Name the person who can confirm scope, the time cutoff, the source systems that count, and the conditions that place a record outside the cross-touchpoint journey review. For patient journey analytics, 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 accountable reviewers can distinguish a deliberate exclusion from a missing or failed import.
Working note 2. The second action is evidence control: create a common event taxonomy across clinical, administrative, digital, pharmacy, and communication systems. Document 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 referrals, appointments, encounters, portal and call interactions, transitions, handoffs, waiting intervals, outcomes, and patient-reported experience. Do not collapse two values merely because their labels look alike. A reviewer is designed 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, order events by occurrence time, link handoffs, and mark missing, duplicated, cancelled, and rescheduled touchpoints. Describe the expected intermediate artifact before processing starts: a compared list, time-aligned cohort, mapped event, scored observation, or another output appropriate to patient journey analytics. Preserve conflicts and uncertainty visible. When a source is incomplete, the controlled method is designed 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: analyze common sequences, time between steps, loops, drop-off, variation, and points where responsibility changes. Separate what the records directly show from what the review group infers, and record plausible alternative explanations. The objective is to reconstruct sequences across touchpoints and episodes to identify delay, dropout, duplication, handoff failure, and variation in the care journey, not to convert a pattern into an unsupported diagnosis, causal claim, or treatment instruction. Reviewers is designed to see the denominator, comparison point, timing assumptions, and exceptions that could change the meaning of the finding before any operational or clinical response is considered.
Working note 5. Close the cycle through the fifth action: review journey patterns with patients and service owners before redesigning access, communication, or handoffs. Assign every unresolved item to a named role, define the response time, and record the final disposition without deleting the earlier state. The handoff is designed to include the source cutoff, version, material exceptions, validation status, and next review date. This makes patient journey analytics reproducible when another qualified member of patient-experience teams, access leaders, care coordinators, service designers, and healthcare analysts needs to reconstruct why the finding was accepted, challenged, corrected, or left unresolved.
执行说明 1。首先把第一项行动落实为可执行规则：定义旅程起点、终点、阶段规则、人群和体验或服务问题。需要明确谁有权确认范围、资料截止时间、哪些来源有效，以及什么条件会让记录不进入复核。对于患者旅程分析，清晰的入口规则可以防止方便取得的数据悄然替代真正的人群或临床问题。被排除的记录仍应保留原因代码，使复核者能够区分主动排除、资料缺失和导入失败。
执行说明 2。第二项行动关注证据控制：在临床、行政、数字、药房和沟通系统之间建立共同事件分类。每项资料都要记录事件发生时间、可用时间、录入或提供者、初步或最终状态，以及修订如何表示。相关资料必须覆盖患者旅程分析所需的来源、时间、状态、编码、单位和上下文。不能因为标签相似就合并两个数值；复核者应能从规范化字段回到原始记录，并理解中间每一步转换。
执行说明 3。第三项行动是按发生时间排序事件，连接交接，并标记缺失、重复、取消和改期接触点。处理开始前，应先定义符合患者旅程分析需要的中间成果，例如对照清单、时间对齐人群、映射事件或带来源的观察结果。冲突和不确定性必须可见。来源不完整时，流程应说明是排除、带标记保留、按已声明规则估计，还是转交确认；静默填补可能让整洁结果产生错误临床含义。
执行说明 4。第四项行动要求结合背景解释：分析常见序列、步骤间时间、循环、脱落、差异和责任变化位置。应区分记录直接显示的事实和团队作出的推断，并保留其他合理解释。目标是支持患者旅程分析所界定的资料整理、分析和复核任务，而不是把模式直接写成未经支持的诊断、因果结论或治疗指令。在采取运营或临床响应前，复核者需要看到分母、比较点、时间假设和可能改变结论的例外。
执行说明 5。第五项行动用于闭环：与患者及服务负责人共同复核旅程模式后再改进可及性、沟通或交接。每个未解决项目都要分配给明确角色，规定响应时间，并在不删除先前状态的情况下记录最终处置。交接材料应包含来源截止时间、版本、重要例外、验证状态和下次复核日期，使另一位合格人员能够重建为何结果被接受、质疑、纠正或继续保持未解决。
Interpret patient journey analytics without losing context在不丢失背景的情况下解释患者旅程分析
A journey map should show alternative paths rather than force everyone into one ideal sequence. Some patients appropriately bypass a step, receive care outside the captured network, choose a later appointment, or require repeated assessment because their condition changes. Compare pathways for clinically or operationally similar groups, annotate service closures and policy changes, and combine event traces with qualitative feedback. A long interval is a finding to investigate, not proof that one team caused the delay.
旅程图应展示替代路径，而不是把所有患者强制放入一条理想顺序。有些患者会合理跳过某一步、在未捕获体系外接受照护、主动选择较晚预约，或因病情变化需要重复评估。应在临床或运营上相似的人群之间比较路径，标注服务关闭和政策变化，并把事件轨迹与定性反馈结合。较长间隔只是需要调查的发现，不能证明某个团队造成延误。
Review gates for patient journey analytics患者旅程分析复核关口
| Review gate复核关口 | Topic-specific question本主题问题 | Expected evidence预期证据 |
|---|---|---|
| Identity and scope身份与范围 | Does the record match the intended people, setting, and time window for patient journey analytics?记录是否符合患者旅程分析所需的人群、场景和时间范围？ | Source register and dated inclusion rules来源登记与带日期的纳入规则 |
| Meaning含义 | Can the team distinguish the evidence needed to reconstruct sequences across touchpoints and episodes to identify delay, dropout, duplication, handoff failure, and variation in the care journey?团队能否区分完成本主题任务所需的不同证据？ | 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版本化结果、验证样本和纠错日志 |
Validation and operating measures for patient journey analytics患者旅程分析的验证与运行指标
Validate event taxonomy, episode assignment, ordering, duplicate removal, cancellation status, external-care gaps, and handoff links against sampled journeys. Measure coverage of expected touchpoints, median and distribution of interval times, unresolved handoffs, repeated loops, drop-off, channel switching, and patient-reported friction. Stratify carefully to reveal access differences without exposing small groups. After redesign, track whether delay improves and whether demand, burden, or dropout shifts elsewhere.
应使用抽样旅程验证事件分类、阶段归属、排序、去重、取消状态、体系外照护缺口和交接关联。监测预期接触点覆盖、间隔时间中位数与分布、未解决交接、重复循环、脱落、渠道切换和患者报告摩擦。分层应谨慎，以揭示可及性差异而不暴露小群体；改进后还要观察延迟是否改善，以及需求、负担或脱落是否转移到其他位置。
Failure modes and limits of patient journey analytics患者旅程分析的失败模式与限制
Digital and administrative traces do not capture the whole lived journey. Unrecorded calls, informal care, outside providers, transportation, cost, language, trust, and personal preference can explain apparent gaps. Sequence mining may overemphasize common paths and hide rare but important experiences. Do not interpret a missing event as patient disengagement without confirmation, and do not use journey categories to make clinical decisions without the underlying patient context.
数字和行政轨迹无法覆盖患者真实经历的全部过程。未记录电话、非正式照护、外部服务方、交通、费用、语言、信任和个人偏好都可能解释表面缺口。序列挖掘可能过度强调常见路径而隐藏少见但重要的经历。未经确认不能把缺失事件解释为患者脱离照护，也不能在缺少患者背景时用旅程类别作出临床决定。
Organized records and tool output support trend recognition and professional decisions. Drug interactions, risk predictions, diagnoses, and treatment conclusions require qualified medical review.
整理后的资料和工具输出仅用于趋势识别和专业决策辅助。药物相互作用、风险预测、诊断与治疗结论必须由合格医疗专业人员审核。
Operate patient journey analytics as a controlled workflow把患者旅程分析作为受控工作流运行
Turn patient journey analytics into a written operating brief before configuring a dashboard, rule, model, or review queue. Name the intended users—patient-experience teams, access leaders, care coordinators, service designers, and healthcare analysts—and state the decision, time available, acceptable uncertainty, and consequence of a delayed or incorrect result. The brief is designed to use the bounded objective to reconstruct sequences across touchpoints and episodes to identify delay, dropout, duplication, handoff failure, and variation in the care journey. 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 referrals, appointments, encounters, portal and call interactions, transitions, handoffs, waiting intervals, outcomes, and patient-reported experience. 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—define the journey start, end, episode rules, population, and experience or service question and create a common event taxonomy across clinical, administrative, digital, pharmacy, and communication systems—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 patient journey analytics. Include ordinary cases, missing fields, duplicate identities, conflicting sources, late events, corrected values, unusual but valid states, and records that is designed to not enter the controlled method. Use the middle action, order events by occurrence time, link handoffs, and mark missing, duplicated, cancelled, and rescheduled touchpoints, to define expected results for each case. Preserve 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 patient journey analytics, reaches the intended professional at the right moment, and supports a safe response. The later workflow actions—analyze common sequences, time between steps, loops, drop-off, variation, and points where responsibility changes and review journey patterns with patients and service owners before redesigning access, communication, or handoffs—is designed to be demonstrated in the real interface rather than inferred from a data extract.
Describe 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 patient journey analytics outputs remain valid, and document who approved the release and who can roll it back.
The final patient journey analytics handoff is designed to let another qualified reviewer understand and reproduce the finding 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 reconstruct sequences across touchpoints and episodes to identify delay, dropout, duplication, handoff failure, and variation in the care journey, identify which statements are observed versus inferred, and state the next review date. Sensitive details is designed to remain only in approved systems with role-appropriate access and retention.
在配置仪表板、规则、模型或复核队列前，应先把患者旅程分析写成运行说明。明确目标用户、支持的决策、可用时间、可接受不确定性，以及延迟或错误结果的后果。说明中必须写清人群、事件、时间窗口、责任人和允许采取的行动；“寻找洞察”或“发现风险”等宽泛要求无法直接测试和验收。
针对患者旅程分析所需资料建立来源登记表。每个来源都应记录数据责任人、采集过程、事件时间、可用时间、状态模型、编码或单位体系、修订方式、覆盖范围和已知缺口。随后把前两个工作步骤——定义旅程起点、终点、阶段规则、人群和体验或服务问题和在临床、行政、数字、药房和沟通系统之间建立共同事件分类——落实到具体字段和文档，防止把名称相似但事件含义不同的数据直接视为等价。
全面使用患者旅程分析前应建立测试记录，覆盖普通情况、字段缺失、身份重复、来源冲突、事件延迟、数值修订、少见但有效的状态，以及本来不应进入流程的记录。围绕“按发生时间排序事件，连接交接，并标记缺失、重复、取消和改期接触点”为每个测试病例写出预期结果，并把专业解释与技术预期放在一起，避免技术转换通过却隐藏解释错误。
技术验收和领域验收必须分开。技术复核证明输入到达、映射运行、计算可复现、权限有效且失败可见；领域复核则确认信息对患者旅程分析含义正确、在合适时间到达目标专业人员并支持安全响应。后两个步骤——分析常见序列、步骤间时间、循环、脱落、差异和责任变化位置和与患者及服务负责人共同复核旅程模式后再改进可及性、沟通或交接——应在真实界面和工作流中演示，不能只从数据抽取结果推断。
上线前定义纠错、升级和变更控制。使用者需要能够质疑结果、修复来源或映射、标注例外，并判断哪些既往输出受到影响。来源合同、术语、逻辑、阈值、显示和复核制度都应进行版本管理；任何重大变化后，都要在代表性记录上比较新旧结果，判断既往患者旅程分析输出是否仍有效，并记录批准者和回滚责任人。
最终患者旅程分析交接包应让另一位合格复核者无需依赖团队未记录的知识，就能理解并复现结果。材料应包含目的、纳入规则、来源清单、数据截止时间、原始证据链接、转换过程、工作流状态、例外、验证结果、复核处置和待确认问题；还要区分观察与推断、说明下次复核日期，并把敏感详情限制在具有适当访问和保留控制的获批系统中。
Prepare patient journey analytics evidence with 医数智析用医数智析准备患者旅程分析资料
Before opening the workspace, prepare referrals, appointments, encounters, portal and call interactions, transitions, handoffs, waiting intervals, outcomes, and patient-reported experience. 医数智析 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打开实际体验页Patient Journey Analytics questions患者旅程分析常见问题
A touchpoint is a meaningful interaction or transition, such as referral, scheduling, check-in, encounter, test, pharmacy event, portal message, call, discharge, or follow-up.
患者旅程分析以接触点顺序、照护阶段和交接摩擦为中心；患者数据分析则可以在不重建路径的情况下研究患者状态、风险、利用或结局。
Specify the triggering event, start and end rules, allowed gaps, related services, repeated episodes, and how external or missing events are represented.
应说明触发事件、起止规则、允许间隔、相关服务、重复阶段，以及如何表示体系外或缺失事件。
Not without review. It may reflect planned waiting, clinical sequencing, patient choice, outside care, missing data, or an avoidable operational delay.
不能直接这样判断。它可能来自计划等待、临床顺序、患者选择、体系外照护、数据缺失或可避免的运营延迟。
Primary source for patient journey analytics患者旅程分析的主要参考来源
Use the cited primary or official source together with current organizational policy and the professional standards that apply in the intended setting.
实施时应把下列第一方或权威来源与当前机构制度及适用专业标准结合使用。