| Name |
Last commit
|
Last update |
|---|---|---|
| .. | ||
| data/jvs-dw | ||
| prisma | ||
| src | ||
| tests | ||
| .dockerignore | ||
| .env.example | ||
| .gitignore | ||
| .swcrc | ||
| Dockerfile | ||
| jest.config.cjs | ||
| nest-cli.json | ||
| package.json | ||
| tsconfig.build.json | ||
| tsconfig.json |
EMR.treat_plan = 本次治疗(actual,本次确实做了);EMR.plan = 治疗计划(planned)。 treatment_review_rows 100% 来自 treat_plan(plan 字段的复查项当前 drop), 但 treatment_review.yaml 原写死 action=treatment_planned → parser 推 kind=planned, 导致"拆线/复查/暂观"等本次做的事被错误落到「治疗计划」。 修复:treatment_review.yaml action → treatment_completed(kind=actual / status=fulfilled)。 - 韩滨 2024-04-07 拆线 18;48 现正确落「本次治疗」,与源数据 treat_plan 一致 - 验证无副作用:chain S4 复查信号按 category='review' 匹配(不看 kind); review 已排除在 actual 治疗链 S3 外、不触发 scenario ⑤a → 召回逻辑不受影响 - 留注释:未来若 union EMR.plan 的复查项进来(那才是 planned),需按来源分流 kind 至此 treatment_record 的 kind 完全由来源字段决定:treat_plan→actual / plan→planned。 Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
| Name |
Last commit
|
Last update |
|---|---|---|
| .. | ||
| data/jvs-dw | Loading commit data... | |
| prisma | Loading commit data... | |
| src | Loading commit data... | |
| tests | Loading commit data... | |
| .dockerignore | Loading commit data... | |
| .env.example | Loading commit data... | |
| .gitignore | Loading commit data... | |
| .swcrc | Loading commit data... | |
| Dockerfile | Loading commit data... | |
| jest.config.cjs | Loading commit data... | |
| nest-cli.json | Loading commit data... | |
| package.json | Loading commit data... | |
| tsconfig.build.json | Loading commit data... | |
| tsconfig.json | Loading commit data... |