上一版漏了作用域:抛光那条规则用 cfgFlags.polishImpliesRestoration 只对 K08 开, 本分支却没设闸,凡是 resolverCats 含 prosthodontic 的场景(整个结构家族 K00/K01/K02/K03/K04/K08/K09)都会触发。而我那 59 条人工复核**全是 missing_tooth**, 非缺牙场景一条没验过。 想补验,但非缺牙理由量太大(hard_tissue_damage 单独就 18 万条),导出复核的查询 两次 860s 超时 —— 也就是"验不完"。少召不报错,验不完就不该默认开。 改为 GAP_FLAGS_BY_PRIMARY.K08.treatedEvidenceFromEmrText,机制保持场景无关 (判据是牙位级的),开关按场景给。要给别的场景开,先把该场景的命中全量导出人工过一遍。 顺带记下通用性自查的其余结论(都通过): · 关联键 emr_external_id↔ source_encounter_external_id 都是 PAC 规范字段,非 host 字段名 · 词表在 packages/types 共享层,收的是临床通用词(戴牙/假牙/义齿/修复体/烤瓷冠), 无 host 痕迹 —— 符合「通用→共享,怪癖→宿主」的分层 · 宿主不填主诉(如 FRIDAY)→ join 落空,分支自动失效,不报错 · 类目闸对 K05/K07 天然为空(resolverCats 不含 prosthodontic),全口路径本就不接本表 测试补一例锁住开闸范围。 Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
| Name |
Last commit
|
Last update |
|---|---|---|
| .claude | Loading commit data... | |
| .design-sync | Loading commit data... | |
| apps | Loading commit data... | |
| clickhouse/config.d | Loading commit data... | |
| deploy | Loading commit data... | |
| docs | Loading commit data... | |
| packages | Loading commit data... | |
| scripts | Loading commit data... | |
| .gitignore | Loading commit data... | |
| .gitlab-ci.yml | Loading commit data... | |
| .npmrc | Loading commit data... | |
| .prettierrc | Loading commit data... | |
| README.md | Loading commit data... | |
| docker-compose.expose.yml | Loading commit data... | |
| docker-compose.managed.yml | Loading commit data... | |
| docker-compose.prod.yml | Loading commit data... | |
| docker-compose.yml | Loading commit data... | |
| eslint.config.mjs | Loading commit data... | |
| liu.cjs | Loading commit data... | |
| package.json | Loading commit data... | |
| pnpm-lock.yaml | Loading commit data... | |
| pnpm-workspace.yaml | Loading commit data... | |
| tsconfig.base.json | Loading commit data... | |
| turbo.json | Loading commit data... |