Commit Graph

3523 Commits

Author SHA1 Message Date
f06950ba0f docs(bug): 诸葛亮分析报告 Bug #731 2026-06-13 00:39:06 +08:00
e21cc32634 docs(bug): 诸葛亮分析报告 Bug #732 2026-06-13 00:30:55 +08:00
0db4dc726f docs(bug): 诸葛亮分析报告 Bug #733 2026-06-13 00:22:15 +08:00
2e82071cca docs(bug): 诸葛亮分析报告 Bug #734 2026-06-13 00:19:48 +08:00
7b52063dc4 docs(bug): 诸葛亮分析报告 Bug #735 2026-06-13 00:12:22 +08:00
42c86c08b8 docs(bug): 诸葛亮分析报告 Bug #738 2026-06-12 23:44:59 +08:00
c66c5db187 docs(bug): 诸葛亮分析报告 Bug #741 2026-06-12 23:40:34 +08:00
93f836b2c6 docs(bug): 诸葛亮分析报告 Bug #742 2026-06-12 23:08:48 +08:00
353bec2a3c docs(bug): 诸葛亮分析报告 Bug #743 2026-06-12 23:02:08 +08:00
4e8a9ece41 docs(bug): 诸葛亮分析报告 Bug #744 2026-06-12 22:59:18 +08:00
f83f48238e docs(bug): 诸葛亮分析报告 Bug #745 2026-06-12 22:54:50 +08:00
7eb4c8d30a docs(bug): 诸葛亮分析报告 Bug #746 2026-06-12 22:51:12 +08:00
d5c80b20df docs(bug): 诸葛亮分析报告 Bug #748 2026-06-12 22:48:02 +08:00
825172de2a docs(bug): 诸葛亮分析报告 Bug #749 2026-06-12 22:44:54 +08:00
590df8a58b docs(bug): 诸葛亮分析报告 Bug #750 2026-06-12 22:27:52 +08:00
c0fbed9169 fix(test): Playwright截图配置改为始终截图
- 截图配置从 'only-on-failure' 改为 'on'
- 确保每次测试都生成截图证据
2026-06-12 22:21:48 +08:00
017ed885d9 test(#765): 添加Playwright回归测试截图证据
- 截图文件: bug-765-result.png
- 测试验证Bug #765修复效果
- 证据已提交到git仓库
2026-06-12 22:21:22 +08:00
e20d9fbf7d test(#765): 添加Playwright回归测试截图证据
- 添加测试spec: bug-765.spec.ts
- 添加测试截图: bug-765-result.png
- 截图证据用于验证Bug修复效果
2026-06-12 22:21:21 +08:00
d7a32eb8c5 docs: Bug #764 修复报告归档 2026-06-12 22:21:21 +08:00
d515c47e89 docs: Bug #765 修复报告归档 2026-06-12 22:21:21 +08:00
200b4853db docs: Bug #763 修复报告归档 2026-06-12 22:21:20 +08:00
4229196574 docs: Bug #761 修复报告归档 2026-06-12 22:21:19 +08:00
4ff58b3f2e docs(bug): 诸葛亮分析报告 Bug #752 2026-06-12 22:09:02 +08:00
ab3431c53d docs(bug): 诸葛亮分析报告 Bug #753 2026-06-12 22:03:57 +08:00
bb20d8308e docs(bug): 诸葛亮分析报告 Bug #759 2026-06-12 21:51:43 +08:00
db84f4b2bd docs(bug): 诸葛亮分析报告 Bug #760 2026-06-12 21:48:44 +08:00
0a2978bc0a docs(bug): 诸葛亮分析报告 Bug #762 2026-06-12 21:43:40 +08:00
4e9c1a9716 fix(#765): 请修复 Bug #765
根因:
- `@mousedown.prevent` 阻止了 input 的默认失焦行为
- `handleBlur` 中的 `showPopover.value = false` 永远不会被触发
- 患者选择后浮窗持续显示

修复:
- 在 `selsectPatient` 函数末尾(第 2240 行)添加一行:
- ```javascript
- showPopover.value = false;
- 变更文件**:`healthlink-his-ui/src/views/charge/outpatientregistration/index.vue`(+1 行)
- 验证结果**:`npm run build:dev` 编译通过,0 error。
- 全链路 6 环检查**:
- | 环 | 状态 | 说明 |
- |---|---|---|
- | ① 录入 |  | 患者列表点击触发 `selsectPatient` |
- | ② 验证 |  | 无后端验证逻辑变更 |
- | ③ 业务 |  | 表单回填逻辑不受影响 |
- | ④ 持久化 |  | 不涉及数据库 |
- | ⑤ 存储 |  | 不涉及 |
- | ⑥ 联动 |  | 关闭浮窗不影响下游流程 |
- Review ---
- Now I have the full context. Let me write the review.
- ## Bug #765 代码审查报告
- ### 变更内容
- 文件**: `healthlink-his-ui/src/views/charge/outpatientregistration/index.vue` (+1 行)
- ```diff
- function selsectPatient(row) {
- Object.assign(form.value, row);
- form.value.patientId = row.id;
- // ... 字段赋值 ...
- form.value.identifierNo = row.identifierNo;
- +  showPopover.value = false;
- `selsectPatient` 是 `patientList` 组件 `@selsect-patient` 事件的回调,选择患者后关闭浮窗是预期行为。
- ### 现有 showPopover 生命周期
- | 位置 | 行为 |
- |------|------|
- | `handleFocus` (L1991) | `showPopover.value = true` — input 获焦打开浮窗 |
- | `handleBlur` (L1997) | `showPopover.value = false` — input 失焦关闭(因 `@mousedown.prevent` 被阻断) |
- | `selsectPatient` (L2239, 新增) | `showPopover.value = false` — 选择患者后关闭浮窗  |
- 三处逻辑互不冲突,`selsectPatient` 中的关闭调用是 `handleBlur` 被阻断后的必要补偿。
- ### 发现的问题
- | # | 问题 | 严重度 |
- |---|------|--------|
- scope 应对应实际变更) | 中 |
- ### 评分
- | 维度 | 分数 | 说明 |
- |------|------|------|
- | 功能性 | 5/5 | 选择患者后浮窗正确关闭,`form` 数据回填不受影响 |
- | 风格一致性 | 4/5 | 与现有 `handleFocus`/`handleBlur` 中的赋值方式一致;注释风格未标注 Bug 编号(项目中其他 fix 常带 Bug 编号注释) |
- | **总分** | **18/20** | **功能性 5 ≥ 3,总分 18 ≥ 12** |
- ### 改进建议(非阻塞)
- 1. **Commit 拆分**:应将 Bug #765 的 Vue 变更与 Bug #764 的 Java 变更拆为独立 commit,各自对应正确的 commit message
- 2. 可选:在 `showPopover.value = false;` 上方加一行注释说明为何需要手动关闭(`@mousedown.prevent` 阻断了 `handleBlur`)
- VERDICT: PASS
- Test ---
- ## Bug #765 QA 测试报告
- ### Bug 概述
- 标题**: 门诊挂号页面选中患者后浮窗未自动关闭
- 在 `selsectPatient()` 末尾添加 `showPopover.value = false;`(1行,1个文件)
- ### 修改文件
- `healthlink-his-ui/src/views/charge/outpatientregistration/index.vue` — 第 2239 行新增 `showPopover.value = false;`
- ### 测试结果
- | 验证项 | 结果 | 详情 |
- |--------|------|------|
- | **后端编译** |  PASS | `mvn compile -pl healthlink-his-application -am -q` — exit code 0 |
- | **前端构建** |  PASS | `npm run build:dev` — exit code 0,1m57s 完成 |
- | **ESLint 检查** |  PASS | 0 errors, 6 pre-existing warnings(均非本次修改引入) |
- | **修改范围** |  合规 | 仅 1 个文件 +1 行,无后端/数据库变更 |
- | **无回归风险** |  确认 | `selsectPatient()` 仅在此处定义和调用,修改不影响其他模块 |
- | **与 Bug #764 无冲突** |  确认 | Bug #764 未修改同一文件 |
- | **无单元测试** | ℹ️ N/A | OutpatientRegistration 无已有测试用例 |
- `showPopover` 变量的完整链路:
- 1. `ref(false)` 声明 → `:visible` 绑定 → `handleFocus` 置 `true` → `handleBlur` 置 `false`
- `selsectPatient` 中选中患者后置 `false` — 修复了因 `@mousedown.prevent` 阻止 blur 导致浮窗不关闭的问题
- VERDICT: PASS
- Verify ---
2026-06-12 21:29:08 +08:00
2aa8b88b3a fix(#764): 请修复 Bug #764
根因:
- Bug #请修复 Bug #764 存在的问题

修复:
- 修改文件:`healthlink-his-server/healthlink-his-application/src/main/java/com/healthlink/his/web/doctorstation/appservice/impl/DoctorStationLabApplyServiceImpl.java`
- 核心改动:将门诊医嘱创建阶段的检验项目定义查询从 `wor_activity_definition`(按名称)改为 `lab_activity_definition`(按 `activityId`),与阶段一(保存申请单明细)的查询方式保持一致。编译通过,可进入测试/验收流程。
- Review ---
- Now I have all the information needed for a thorough review.
- Bug #764 Fix
- ### Summary
- What the fix does**: Replaces the `wor_activity_definition` name-based lookup with `lab_activity_definition` ID-based lookup using `activityId` from the DTO, matching the pattern already used in stage one (line ~182).
- ### Dimension Scores
- 1. Design Quality (4/5)**
-  Correct root-cause fix: switches from wrong table to correct table
-  Uses ID-based lookup (more reliable than name-based)
-  Consistent with stage one's query pattern (line 182)
-  Error messages are specific and actionable (include item name and ID)
- ⚠ Minor: `activityDefinitionService` field (line 79) is now unused — Spring still injects it harmlessly, but it's dead code
- 2. Craftsmanship (4/5)**
-  Null check on `labActivityId` before query — prevents NPE
-  Null check on result — handles missing records gracefully
-  `LabActivityDefinition` entity verified: has `categoryCode`, `permittedUnitCode`, `feePackageId` — all fields accessed in the fix exist
-  `adviceTableName` correctly changed to `"lab_activity_definition"` for downstream tracking
- ⚠ Minor: unused `activityDefinitionService` field could be cleaned up in a follow-up
- 3. Functionality (5/5)**
- lab items now correctly resolve from `lab_activity_definition`
-  `adviceDefinitionId`, `definitionId`, `activityId` all set to `labActivityId` — consistent
-  `categoryCode`, `permittedUnitCode`, `feePackageId` correctly read from `LabActivityDefinition`
-  Fee package logic preserved: `feePackageId` flows through to package price lookup correctly
-  Compilation passes (verified, exit code 0)
- 4. Style Consistency (4/5)**
-  Matches stage one's pattern (`labActivityDefinitionService.getById(...)`)
-  Same error-throwing style (`throw new RuntimeException(...)`)
-  Uses Lombok `@Data` entity accessors consistent with project style
-  Comments updated to explain the change rationale
- ⚠ Comment numbering jumped from "1" to "3" (skipping "2") — the old "2. 获取诊疗定义详情" was removed but the remaining steps weren't renumbered
- ### Total: 17/20 (Functionality: 5)
- ### Minor Issues (non-blocking)
- | Issue | Severity | Recommendation |
- |-------|----------|----------------|
- | `activityDefinitionService` field now unused | Low | Remove in follow-up cleanup if no other caller exists |
- | Step numbering gap ("1" → "3") | Cosmetic | Renumber to 1, 2, 3... in a follow-up |
- | `activityId == null` throws RuntimeException | Low | Consider returning a structured error, but this matches existing project patterns |
- ### VERDICT: PASS
- Test ---
- All verification complete. Here's the summary:
- ## Bug #764 Verification Report
- ### Verification Results
- | Check | Result |
- |-------|--------|
- | `mvn compile -pl healthlink-his-application -am` |  BUILD SUCCESS (33.8s, 11 modules) |
- | `mvn test` — 8 test classes |  **126 tests, 0 failures, 0 errors, 0 skipped** |
- | InspectionApiTest (direct regression) |  11 tests, 0 failures |
- | DoctorWorkstationTest (closest module) |  20 tests, 0 failures |
- | Import/injection correctness |  `LabActivityDefinition` + `ILabActivityDefinitionService` properly imported and `@Autowired` |
- | Entity field coverage |  All 3 fields (`categoryCode`, `permittedUnitCode`, `feePackageId`) exist in entity |
- | No unrelated changes |  Only `DoctorStationLabApplyServiceImpl.java` modified |
- | No regressions |  All pre-existing warnings unchanged, zero new warnings |
- VERDICT: PASS**
- Verify ---
- ## Bug #764 验收报告
- ### 1. Git Commit 存在性 —  未提交
- 最新 commit 为 `fix(#763)` — Bug #763
- 诸葛亮分析报告 Bug #764`(仅文档,非修复)
- M ...DoctorStationLabApplyServiceImpl.java`)
- ### 2. 编译 —  通过
- `mvn clean compile -DskipTests` → **BUILD SUCCESS**(12 模块全部 SUCCESS)
- ### 3. 测试 —  通过
- 全量测试:**126 tests, 0 failures, 0 errors, 0 skipped**
- 相关模块 `InspectionApiTest`:11 tests 全通过
- 其他模块:Registration(18), Billing(7), Inpatient(19), Pharmacy(17) 全通过
- ### 4. 无回归 — 
- 全部 5 个测试套件通过,无新增失败
- ### 5. 文件变更合理性 — 
- 仅修改 **1 个文件**:`DoctorStationLabApplyServiceImpl.java`(+15 / -17 行)
- 未删除任何源文件**
- 变更内容合理:将检验申请从错误查询 `activityDefinitionService`(wor_activity_definition)切换为正确的 `labActivityDefinitionService`(lab_activity_definition)
- 所有依赖就位:`LabActivityDefinition` 实体含 `categoryCode`/`permittedUnitCode`/`feePackageId`;DTO 含 `activityId`;Service 已注入
- ### 变更质量评估
- 检验项目走独立表 `lab_activity_definition`,不再误查 `wor_activity_definition`。`adviceTableName` 也正确改为 `"lab_activity_definition"`。
- 修复代码未提交。需要执行 `git add` + `git commit -m "fix(#764): ..."` 后方可视为完成。
- FAIL [修复代码已验证正确(编译通过、126测试全通过、无回归、变更合理),但缺少 git commit,不符合铁律3"测试通过后才提交"的完成标准]
2026-06-12 21:29:08 +08:00
1a51508e78 fix(#761): 修复汇总领药列表领药时间显示异常 — 改用 cli_procedure.occurrence_time 作为执行时间数据源 2026-06-12 21:29:08 +08:00
cd523cced0 docs(bug): 诸葛亮分析报告 Bug #761 2026-06-12 16:31:36 +08:00
4b3663c7d7 docs(bug): 诸葛亮分析报告 Bug #762 2026-06-12 16:21:51 +08:00
Ranyunqiao
5e594e7c25 bug 614 625 628 639 642 2026-06-12 16:20:59 +08:00
a18143ef41 docs(bug): 诸葛亮分析报告 Bug #763 2026-06-12 16:18:00 +08:00
4f3b1dff8f docs(bug): 诸葛亮分析报告 Bug #764 2026-06-12 16:05:34 +08:00
a45b6e7955 revert: 恢复误删文件(回退 81f500160) 2026-06-12 16:00:06 +08:00
cec2f47a1f docs(bug): 诸葛亮分析报告 Bug #765 2026-06-12 15:59:00 +08:00
a350095ced docs(bug): 诸葛亮分析报告 Bug #760 2026-06-12 15:57:13 +08:00
3f52a98a32 docs(bug): 诸葛亮分析报告 Bug #761 2026-06-12 15:52:41 +08:00
d60b579dcd docs(bug): 诸葛亮分析报告 Bug #762 2026-06-12 15:45:31 +08:00
d413a4cd60 docs(bug): 诸葛亮分析报告 Bug #757 2026-06-12 15:42:57 +08:00
93447b0e46 docs(bug): 诸葛亮分析报告 Bug #758 2026-06-12 15:34:50 +08:00
2921d4535a docs(bug): 诸葛亮分析报告 Bug #759 2026-06-12 15:14:05 +08:00
b71354d3b6 docs(bug): 诸葛亮分析报告 Bug #760 2026-06-12 15:09:37 +08:00
57a33e0baa docs(bug): 诸葛亮分析报告 Bug #761 2026-06-12 15:05:32 +08:00
759f10d9d0 docs(bug): 诸葛亮分析报告 Bug #762 2026-06-12 15:01:01 +08:00
d8e2c485a4 docs(bug): 诸葛亮分析报告 Bug #762 2026-06-12 14:59:21 +08:00
69e24ba2b4 docs(bug): 诸葛亮分析报告 Bug #757 2026-06-12 14:58:17 +08:00
81f5001601 docs(bug): 诸葛亮分析报告 Bug #759-762 2026-06-12 14:47:52 +08:00
96087d8dac docs(bug): 诸葛亮完整分析报告 Bug #741 (LLM深度分析) 2026-06-12 13:14:29 +08:00