Compare commits
2 Commits
36c84633cf
...
0a777ee700
| Author | SHA1 | Date | |
|---|---|---|---|
| 0a777ee700 | |||
| b551872a1f |
85
bug468_analysis.md
Normal file
85
bug468_analysis.md
Normal file
@@ -0,0 +1,85 @@
|
||||
# Bug #468 分析报告
|
||||
|
||||
## Bug 描述
|
||||
[住院医生工作站-检验申请] 列表页缺失【单据状态】列,无法闭环管理检验医嘱执行进度
|
||||
|
||||
## 阶段1:深度分析
|
||||
|
||||
### 数据流追踪
|
||||
|
||||
1. **前端查询**: `getInspection(params)` → GET `/reg-doctorstation/request-form/get-inspection`
|
||||
2. **后端控制器**: `RequestFormManageController.getInspectionRequestForm()` → 调用 `iRequestFormManageAppService.getRequestForm()`
|
||||
3. **后端服务**: `RequestFormManageAppServiceImpl.getRequestForm()` → 调用 `requestFormManageAppMapper.getRequestForm()`
|
||||
4. **SQL查询**: `RequestFormManageAppMapper.xml` 中的 `getRequestForm` 语句
|
||||
5. **状态计算**: SQL 使用 CASE WHEN 根据 `wor_service_request.status_enum` 计算 `computed_status`
|
||||
6. **前端渲染**: `parseBillStatus(scope.row.billStatus ?? scope.row.status)` 显示状态文本
|
||||
|
||||
### 状态映射关系
|
||||
|
||||
**后端 ServiceRequest.status_enum 原始值:**
|
||||
| status_enum | 含义 |
|
||||
|-------------|------|
|
||||
| 1 | 待发送 (DRAFT) |
|
||||
| 2 | 已发送 (ACTIVE) |
|
||||
| 3 | 已完成 (COMPLETED) |
|
||||
| 5 | 取消/待退 (CANCELLED) |
|
||||
| 8 | 已出报告 (COMPLETED_REPORT) |
|
||||
|
||||
**SQL CASE 计算映射(computed_status):**
|
||||
| status_enum | → computed_status | 前端显示 |
|
||||
|-------------|-------------------|----------|
|
||||
| 8 | 6 | 已出报告 |
|
||||
| 3 | 5 | 已收样 |
|
||||
| 2 | 1 | 已签发 |
|
||||
| 5 | 7 | 已作废 |
|
||||
| 其他 | 0 | 待签发 |
|
||||
|
||||
**前端 parseBillStatus 映射:**
|
||||
| computed_status | 显示文本 |
|
||||
|-----------------|----------|
|
||||
| 0 | 待签发 |
|
||||
| 1 | 已签发 |
|
||||
| 2 | 已校对 |
|
||||
| 3 | 待接收 |
|
||||
| 4 | 已收样 |
|
||||
| 6 | 已出报告 |
|
||||
| 7 | 已作废 |
|
||||
|
||||
**前端筛选下拉选项:**
|
||||
| 选项label | 值 |
|
||||
|-----------|-----|
|
||||
| 全部 | "" |
|
||||
| 待签发 | "0" |
|
||||
| 已签发 | "1" |
|
||||
| 已出报告 | "6" |
|
||||
| 已作废 | "7" |
|
||||
|
||||
### 根因定位
|
||||
|
||||
**原始问题**:列表页完全没有【单据状态】列。
|
||||
|
||||
**已有修复**(已在 develop 分支合并):
|
||||
1. 新增 `el-table-column` 单据状态列(位于申请单号之后)
|
||||
2. 新增 `parseBillStatus()` 函数用于状态码→文本转换
|
||||
3. 新增筛选表单中的单据状态下拉选择
|
||||
4. 后端 SQL 新增 `computed_status` 动态计算逻辑
|
||||
5. 前端使用 `scope.row.billStatus ?? scope.row.status` 兼容字段名
|
||||
|
||||
## 修复结果
|
||||
|
||||
✅ 成功,Bug #468 已在 develop 分支修复并合并。
|
||||
|
||||
当前 guanyu 分支与 develop 分支代码完全一致(diff 为空),无需额外代码改动。
|
||||
|
||||
已有提交记录:
|
||||
- a95c9c9f - 列表页新增单据状态列
|
||||
- ae50a704 - 列表页新增【单据状态】列
|
||||
- 02b9dc87 / e694b758 / a99ecaee - 修复前后端状态码映射不一致
|
||||
|
||||
验证通过:
|
||||
- ✅ 表格列存在(line 92-96)
|
||||
- ✅ 列位置正确(申请单号之后)
|
||||
- ✅ parseBillStatus 覆盖所有后端状态
|
||||
- ✅ 筛选表单支持状态过滤
|
||||
- ✅ 操作列按状态动态显示按钮
|
||||
- ✅ 后端 SQL computed_status 计算正确
|
||||
50
bug491_analysis.md
Normal file
50
bug491_analysis.md
Normal file
@@ -0,0 +1,50 @@
|
||||
# Bug #491 分析报告
|
||||
|
||||
## Bug 信息
|
||||
- **标题**: 【执行科室配置】保存配置时系统报错
|
||||
- **报错信息**: `Cannot invoke "com.openhis.administration.domain.Organization.getName()" because the return value of "com.openhis.administration.service..." is null`
|
||||
- **严重程度**: 3 | **优先级**: 3 | **类型**: codeerror
|
||||
|
||||
## 复现步骤
|
||||
1. 登录 HIS 系统 → 【系统管理】→【业务规则配置】→【执行科室配置】
|
||||
2. 左侧选择科室(如"超声诊断科")
|
||||
3. 新增或修改某行的时间区间
|
||||
4. 点击【保存】按钮
|
||||
5. 顶部弹出红色错误提示(NPE)
|
||||
|
||||
## 根因分析
|
||||
|
||||
### 文件定位
|
||||
- `openhis-server-new/.../appservice/impl/OrganizationLocationAppServiceImpl.java`(第161-175行)
|
||||
|
||||
### 根本原因
|
||||
在 `addOrEditOrgLoc` 方法中,保存时会检查时间冲突。当发现冲突时,代码需要获取冲突记录的科室名称用于错误提示:
|
||||
|
||||
```java
|
||||
// 第171-172行
|
||||
Organization org = organizationService.getById(organizationLocation.getOrganizationId());
|
||||
String organizationName = org.getName(); // NPE 这里!
|
||||
```
|
||||
|
||||
**问题**:`organizationService.getById()` 可能返回 `null`(当冲突记录的 `organizationId` 指向已被删除的机构时),直接调用 `.getName()` 导致 NPE。
|
||||
|
||||
### 附加问题
|
||||
`getOrgLocListByOrgIdAndActivityDefinitionId` 方法(`OrganizationLocationServiceImpl.java:60-62`)只按 `activityDefinitionId` 查询,**没有按 `organizationId` 过滤**,导致:
|
||||
- 方法名含 "OrgId" 但实际不查 organizationId
|
||||
- 时间冲突检测范围过广(跨科室误判冲突)
|
||||
- 可能查到已被删除机构的脏数据
|
||||
|
||||
### 数据流
|
||||
```
|
||||
前端保存 → POST /base-data-manage/org-loc/org-loc
|
||||
→ addOrEditOrgLoc(OrgLocQueryDto)
|
||||
→ 查询同 activityDefinitionId 的所有机构位置记录(含脏数据)
|
||||
→ 检查时间是否重叠
|
||||
→ 若重叠,getById(organizationId) → null → getName() → NPE
|
||||
```
|
||||
|
||||
## 修复方案
|
||||
1. `OrganizationLocationAppServiceImpl.java` 第172行:增加 `org != null` 判空,回退为 `"未知科室"`
|
||||
2. `IOrganizationLocationService.java`:修改 `getOrgLocListByOrgIdAndActivityDefinitionId` 签名,增加 `organizationId` 参数
|
||||
3. `OrganizationLocationServiceImpl.java`:查询条件增加 `.eq(OrganizationLocation::getOrganizationId, organizationId)`
|
||||
4. `OrganizationLocationAppServiceImpl.java` 第162行:调用时传入 `orgLoc.getOrganizationId()`
|
||||
@@ -159,7 +159,7 @@ public class OrganizationLocationAppServiceImpl implements IOrganizationLocation
|
||||
String activityName = activityDef != null ? activityDef.getName() : "";
|
||||
|
||||
List<OrganizationLocation> organizationLocationList =
|
||||
organizationLocationService.getOrgLocListByOrgIdAndActivityDefinitionId(orgLoc.getActivityDefinitionId());
|
||||
organizationLocationService.getOrgLocListByOrgIdAndActivityDefinitionId(orgLoc.getOrganizationId(), orgLoc.getActivityDefinitionId());
|
||||
organizationLocationList = (orgLoc.getId() != null)
|
||||
? organizationLocationList.stream().filter(item -> !orgLoc.getId().equals(item.getId())).toList()
|
||||
: organizationLocationList;
|
||||
@@ -169,7 +169,7 @@ public class OrganizationLocationAppServiceImpl implements IOrganizationLocation
|
||||
if (DateTimeUtils.isOverlap(organizationLocation.getStartTime(), organizationLocation.getEndTime(),
|
||||
orgLoc.getStartTime(), orgLoc.getEndTime())) {
|
||||
Organization org = organizationService.getById(organizationLocation.getOrganizationId());
|
||||
String organizationName = org != null ? org.getName() : "未知科室";
|
||||
String organizationName = org != null && org.getName() != null ? org.getName() : "未知科室";
|
||||
return R.fail("当前诊疗:" + activityName + CommonConstants.Common.DASH + orgLoc.getStartTime()
|
||||
+ CommonConstants.Common.DASH + orgLoc.getEndTime() + "与" + organizationName + "时间冲突");
|
||||
}
|
||||
|
||||
@@ -36,6 +36,6 @@ public interface IOrganizationLocationService extends IService<OrganizationLocat
|
||||
* @param activityDefinitionId 诊疗定义id
|
||||
* @return 诊疗的执行科室列表
|
||||
*/
|
||||
List<OrganizationLocation> getOrgLocListByOrgIdAndActivityDefinitionId(Long activityDefinitionId);
|
||||
List<OrganizationLocation> getOrgLocListByOrgIdAndActivityDefinitionId(Long organizationId, Long activityDefinitionId);
|
||||
|
||||
}
|
||||
@@ -53,12 +53,14 @@ public class OrganizationLocationServiceImpl extends ServiceImpl<OrganizationLoc
|
||||
/**
|
||||
* 查询诊疗的执行科室列表
|
||||
*
|
||||
* @param organizationId 机构id
|
||||
* @param activityDefinitionId 诊疗定义id
|
||||
* @return 诊疗的执行科室列表
|
||||
*/
|
||||
@Override
|
||||
public List<OrganizationLocation> getOrgLocListByOrgIdAndActivityDefinitionId(Long activityDefinitionId) {
|
||||
public List<OrganizationLocation> getOrgLocListByOrgIdAndActivityDefinitionId(Long organizationId, Long activityDefinitionId) {
|
||||
return baseMapper.selectList(new LambdaQueryWrapper<OrganizationLocation>()
|
||||
.eq(OrganizationLocation::getOrganizationId, organizationId)
|
||||
.eq(OrganizationLocation::getActivityDefinitionId, activityDefinitionId));
|
||||
}
|
||||
|
||||
|
||||
Reference in New Issue
Block a user