临床背景:
根管治疗后牙变脆(髓腔抽空 + 牙体含水量下降),不戴冠保护 2-3 年内
~30% 概率牙冠折裂(literature: Caplan & Weintraub 1997 等)
所以"根管完成 + 牙体充填" 不算真闭环,必须 + "冠修复" 才算完整治疗
改动:
1. canonical-codes.ts:
- TreatmentLifecycle 加 requiresCrownProtection?: boolean
- 新加 lifecycle = 'linear_then_crown' (maxStage=5, 需冠保护)
- endodontic.lifecycle 'linear' → 'linear_then_crown'
2. chain-composer:
- 新加 hasCrownProtection(bucketTooth, byType, anchor) helper
检查同牙位 prosthodontic actual,treat_stages 含 crown_restoration/post_core
fallback subtype.includes('冠'/'桩核')
- S5 闸口加 crownOk 条件:lifecycle.requiresCrownProtection 时必须满足
- buildStageNodes 透 crownOk 给 S5 节点 → hint "待冠保护(...防牙冠折裂)"
验证(杨光宗 27 K04):
改前:closed stage=5(根管+充填+复诊 触发 S5 → 误闭环)
改后:ongoing stage=4 → S5 "未闭环 · 待冠保护(根管后建议戴冠,防牙冠折裂)"
副作用:其他做了根管但没戴冠的患者也会从 closed → ongoing
→ 客服可视化看到缺口,适合补做"根管后冠修复召回"scenario(future)
不影响 SQL recall(scenario 仍按 treatment_initiation_recall ⑤a actual overlap 排除,
K04 27 有 endodontic actual 仍被排除,不会重新进召回池;
真正"该补冠"的召回是另一个 scenario,后续加)
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
| Name |
Last commit
|
Last update |
|---|---|---|
| .. | ||
| cli | Loading commit data... | |
| common | Loading commit data... | |
| config | Loading commit data... | |
| modules | Loading commit data... | |
| openapi | Loading commit data... | |
| prisma | Loading commit data... | |
| queues | Loading commit data... | |
| redis | Loading commit data... | |
| app.module.ts | Loading commit data... | |
| health.controller.ts | Loading commit data... | |
| main.ts | Loading commit data... |