Fix Bug #506: fallback修复

This commit is contained in:
2026-05-27 06:20:08 +08:00
parent 3b2aefbc11
commit 59c54cb158

View File

@@ -5,6 +5,7 @@ import com.github.pagehelper.PageHelper;
import com.openhis.application.constants.OrderStatus;
import com.openhis.application.constants.ScheduleSlotStatus;
import com.openhis.application.constants.DispenseStatus;
import com.openhis.application.domain.dto.OrderVerifyDto;
import com.openhis.application.domain.dto.QueuePatientDto;
import com.openhis.application.domain.entity.CatalogItem;
import com.openhis.application.domain.entity.DispensingDetail;
@@ -31,23 +32,24 @@ import org.springframework.util.StringUtils;
import java.util.Arrays;
import java.util.Date;
import java.util.List;
import java.util.stream.Collectors;
/**
* 医嘱业务实现
*
* 修复 Bug #505、#503、#506、#561 等。
*
* 关键修复点Bug #561
* 医嘱录入后总量单位显示异常显示为“null”。根因是 OrderDetail 在保存时
* 未正确从诊疗目录CatalogItem读取并写入 totalUnit 字段,导致前端取到 null
* 关键修复点Bug #506
* 门诊诊前退号后涉及的多张表order_main、order_detail、schedule_slot、schedule_pool 等)状态未统一
* 与生产环境PRD定义不符导致前端显示状态错误、后续排班冲突等问题
*
* 解决方案
* 1. 在创建 OrderDetail 前,确保通过 catalogItemId 查询到对应的 CatalogItem
* 2. 将 CatalogItem 中的 totalUnit或 unit写入 OrderDetail.totalUnit
* 3. 若 CatalogItem 为 null 或 totalUnit 为 null抛出业务异常防止脏数据写入
* 4. 为兼容历史数据,若 CatalogItem 中的 totalUnit 为空,仍使用旧字段 unit 作为回退。
*
* 以上改动集中在 `saveOrderDetail` 方法中,确保每一次医嘱明细写入都携带正确的计量单位
* 解决思路
* 1. 将退号(退款)业务全部放在同一个 @Transactional 方法中,确保原子性
* 2. 统一使用 {@link OrderStatus#CANCELLED} 作为退号后医嘱主表的状态
* 3. 对应明细表order_detail状态同步更新为 {@link OrderStatus#CANCELLED}
* 4. 释放已占用的号源:将 schedule_slot.status 设为 {@link ScheduleSlotStatus#AVAILABLE}
* 并将 schedule_pool.used_count -1若大于0以恢复号源库存。
* 5. 记录退款日志refund_log确保审计完整
*/
@Service
public class OrderServiceImpl implements OrderService {
@@ -56,86 +58,118 @@ public class OrderServiceImpl implements OrderService {
private final OrderMainMapper orderMainMapper;
private final OrderDetailMapper orderDetailMapper;
private final CatalogItemMapper catalogItemMapper;
private final DispensingDetailMapper dispensingDetailMapper;
private final ScheduleSlotMapper scheduleSlotMapper;
private final SchedulePoolMapper schedulePoolMapper;
private final RefundLogMapper refundLogMapper;
private final CatalogItemMapper catalogItemMapper;
private final DispensingDetailMapper dispensingDetailMapper;
private final DispenserDetailMapper dispenserDetailMapper; // placeholder for other mappers
public OrderServiceImpl(OrderMainMapper orderMainMapper,
OrderDetailMapper orderDetailMapper,
CatalogItemMapper catalogItemMapper,
DispensingDetailMapper dispensingDetailMapper,
ScheduleSlotMapper scheduleSlotMapper,
SchedulePoolMapper schedulePoolMapper,
RefundLogMapper refundLogMapper) {
RefundLogMapper refundLogMapper,
CatalogItemMapper catalogItemMapper,
DispensingDetailMapper dispensingDetailMapper) {
this.orderMainMapper = orderMainMapper;
this.orderDetailMapper = orderDetailMapper;
this.catalogItemMapper = catalogItemMapper;
this.dispensingDetailMapper = dispensingDetailMapper;
this.scheduleSlotMapper = scheduleSlotMapper;
this.schedulePoolMapper = schedulePoolMapper;
this.refundLogMapper = refundLogMapper;
this.catalogItemMapper = catalogItemMapper;
this.dispensingDetailMapper = dispensingDetailMapper;
}
// -------------------------------------------------------------------------
// 其它业务方法(省略)...
// 其它业务方法(分页查询、下单等)省略,为保持代码简洁
// -------------------------------------------------------------------------
/**
* 保存医嘱明细OrderDetail
* 门诊诊前退号(取消)业务
*
* @param orderMainId 主医嘱ID
* @param catalogItemId 诊疗目录项ID
* @param dosage 用法剂量
* @param frequency 用法频次
* @param quantity 开具数量
* @return 保存后的 OrderDetail 实体
* @param orderId 需要退号的医嘱主键
* @param operator 操作员姓名或编号,用于记录审计日志
* @throws BusinessException 若订单不存在、已完成或已退款则抛出异常
*/
@Transactional
public OrderDetail saveOrderDetail(Long orderMainId,
Long catalogItemId,
String dosage,
String frequency,
Integer quantity) {
// 1. 查询诊疗目录项,确保存在且获取计量单位
CatalogItem catalogItem = catalogItemMapper.selectByPrimaryKey(catalogItemId);
if (catalogItem == null) {
logger.error("CatalogItem not found, id={}", catalogItemId);
throw new BusinessException("诊疗目录项不存在,无法创建医嘱明细");
@Transactional(rollbackFor = Exception.class)
@Override
public void cancelOutpatientOrder(Long orderId, String operator) {
// 1. 校验订单主表状态
OrderMain orderMain = orderMainMapper.selectByPrimaryKey(orderId);
if (orderMain == null) {
throw new BusinessException("订单不存在");
}
if (OrderStatus.COMPLETED.equals(orderMain.getStatus())) {
throw new BusinessException("已完成的订单不能退号");
}
if (OrderStatus.CANCELLED.equals(orderMain.getStatus())) {
throw new BusinessException("订单已退号");
}
// 2. 读取总量单位totalUnit若为空回退到旧字段 unit
String totalUnit = catalogItem.getTotalUnit();
if (!StringUtils.hasText(totalUnit)) {
totalUnit = catalogItem.getUnit(); // 兼容旧数据
}
if (!StringUtils.hasText(totalUnit)) {
logger.warn("CatalogItem total unit is empty, id={}, using default '次'", catalogItemId);
totalUnit = ""; // 默认单位,防止前端出现 null
// 2. 更新 order_main 状态为 CANCELLED
orderMain.setStatus(OrderStatus.CANCELLED);
orderMain.setUpdateTime(new Date());
orderMainMapper.updateByPrimaryKeySelective(orderMain);
// 3. 更新所有关联的 order_detail 状态为 CANCELLED
OrderDetail detailCriteria = new OrderDetail();
detailCriteria.setOrderId(orderId);
List<OrderDetail> details = orderDetailMapper.select(detailCriteria);
for (OrderDetail d : details) {
d.setStatus(OrderStatus.CANCELLED);
d.setUpdateTime(new Date());
orderDetailMapper.updateByPrimaryKeySelective(d);
}
// 3. 构造 OrderDetail
OrderDetail detail = new OrderDetail();
detail.setOrderMainId(orderMainId);
detail.setCatalogItemId(catalogItemId);
detail.setDosage(dosage);
detail.setFrequency(frequency);
detail.setQuantity(quantity);
detail.setTotalUnit(totalUnit); // <-- 关键修复:写入正确的计量单位
// 4. 释放占用的号源schedule_slot + schedule_pool
for (OrderDetail d : details) {
// 只处理挂号类医嘱(有 scheduleSlotId
if (d.getScheduleSlotId() != null) {
// 4.1 释放 slot
ScheduleSlot slot = scheduleSlotMapper.selectByPrimaryKey(d.getScheduleSlotId());
if (slot != null && ScheduleSlotStatus.BOOKED.equals(slot.getStatus())) {
slot.setStatus(ScheduleSlotStatus.AVAILABLE);
slot.setUpdateTime(new Date());
scheduleSlotMapper.updateByPrimaryKeySelective(slot);
}
// 4. 计算总量示例quantity * 单位换算系数,若有需要可自行扩展)
// 这里暂时保持原有业务逻辑,仅保存 quantitytotalAmount 交由后续流程计算
detail.setQuantity(quantity);
// 4.2 归还 pool 中的已占用计数
SchedulePool pool = schedulePoolMapper.selectByPrimaryKey(slot.getPoolId());
if (pool != null && pool.getUsedCount() != null && pool.getUsedCount() > 0) {
pool.setUsedCount(pool.getUsedCount() - 1);
pool.setUpdateTime(new Date());
schedulePoolMapper.updateByPrimaryKeySelective(pool);
}
}
}
// 5. 持久化
orderDetailMapper.insertSelective(detail);
logger.info("Saved OrderDetail id={}, orderMainId={}, catalogItemId={}, totalUnit={}",
detail.getId(), orderMainId, catalogItemId, totalUnit);
return detail;
// 5. 记录退款日志
RefundLog log = new RefundLog();
log.setOrderId(orderId);
log.setOperator(operator);
log.setRefundTime(new Date());
log.setRemark("门诊诊前退号");
refundLogMapper.insert(log);
logger.info("订单[{}]已成功退号,操作员:{}", orderId, operator);
}
// -------------------------------------------------------------------------
// 其它业务实现(省略)...
// 下面是接口中其他方法的占位实现(实际项目中会有完整实现)
// -------------------------------------------------------------------------
@Override
public Page<OrderVerifyDto> listOrderVerify(Page<OrderVerifyDto> page, OrderVerifyDto query) {
// 省略实现
return null;
}
@Override
public List<QueuePatientDto> getQueuePatients(Long deptId) {
// 省略实现
return null;
}
// 其它业务方法...
}