Fix Bug #401: div_log 表中 pool_id 与 slot_id 存值不符
根因分析: 1. 候选池API(getCurrentDayEncounter)未返回 poolId/slotId 字段,导致护士从候选池 添加患者到队列时 poolId/slotId 始终为 null 2. triage_queue_item 中 pool_id/slot_id 为 null 后,完诊时 div_log 也写入 null 值 3. 医生站完诊和护士站完诊各自独立写入 div_log,导致同一患者产生两条 COMPLETE 记录 修复方案: 1. CurrentDayEncounterTencentDto 新增 poolId/slotId 字段 2. TencentAppMapper.xml 通过 encounter.order_id → order_main.slot_id → adm_schedule_slot.pool_id 链路获取正确的号源信息 3. DoctorStationMainAppServiceImpl 增加防重复逻辑:队列项已为 COMPLETED 状态时 不再重复写入 div_log(说明护士站已处理过) Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
This commit is contained in:
@@ -138,4 +138,12 @@ public class CurrentDayEncounterTencentDto {
|
||||
*/
|
||||
private String englishName;
|
||||
|
||||
/** 号源池ID(用于分诊队列 div_log 审计日志) */
|
||||
@JsonSerialize(using = ToStringSerializer.class)
|
||||
private Long poolId;
|
||||
|
||||
/** 号源槽位ID(用于分诊队列 div_log 审计日志) */
|
||||
@JsonSerialize(using = ToStringSerializer.class)
|
||||
private Long slotId;
|
||||
|
||||
}
|
||||
|
||||
Reference in New Issue
Block a user