Proactive Knowledge Inquiry in Doctor-Patient Dialogue: Stateful Extraction, Belief Updating, and Path-Aware Action Planning
Organizations: The Hong Kong Polytechnic University, Hong Kong
Abstract
Most automated electronic medical record (EMR) pipelines remain output-oriented: they transcribe, extract, and summarize after the consultation, but they do not explicitly model what is already known, what is still missing, which uncertainty matters most, or what question or recommendation should come next. We formulate doctor-patient dialogue as a proactive knowledge-inquiry problem under partial observability. The proposed framework combines stateful extraction, sequential belief updating, gap-aware state modeling, hybrid retrieval over objectified medical knowledge, and a POMDP-lite action planner. Instead of treating the EMR as the only target artifact, the framework treats documentation as the structured projection of an ongoing inquiry loop. To make the formulation concrete, we report a controlled pilot evaluation on ten standardized multi-turn dialogues together with a 300-query retrieval benchmark aggregated across dialogues. On this pilot protocol, the full framework reaches 83.3% coverage, 80.0% risk recall, 81.4% structural completeness, and lower redundancy than the chunk-only and template-heavy interactive baselines. These pilot results do not establish clinical generalization; rather, they suggest that proactive inquiry may be methodologically interesting under tightly controlled conditions and can be viewed as a conceptually appealing formulation worth further investigation for dialogue-based EMR generation. This work should be read as a pilot concept demonstration under a controlled simulated setting rather than as evidence of clinical deployment readiness. No implication of clinical deployment readiness, clinical safety, or real-world clinical utility should be inferred from this pilot protocol.
Figures & tables
| State | Interpretation | Control implication |
|---|---|---|
| observed_result | Current observed finding or measured result | Strongly updates state and belief |
| historical_result | Previously known finding or past exam result | Supports history with lower immediacy |
| recommended | Suggested future action | Triggers planning; not completed evidence |
| pending_verification | Mentioned but unconfirmed | Gap source; often triggers verification |
| negated | Explicitly denied | Supports exclusion and contradiction handling |
| Step | Operation |
|---|---|
| 1 | Extract stateful events . |
| 2 | Update current state . |
| 3 | Update belief . |
| 4 | Derive gaps . |
| 5 | Retrieve supportive objects and candidate paths from knowledge base . |
| 6 | Generate candidate actions from state, belief, gaps, and retrieval outputs. |
| Method | Coverage (%) | Risk Recall (%) | Structural Completeness (%) | Redundancy (%) | |
|---|---|---|---|---|---|
| Baseline A: Direct generation | 55.6 | 30.0 | 59.3 | N/A | N/A |
| Baseline B: Chunk-only RAG | 69.4 | 60.0 | 71.4 | 24.8 | 6.8 |
| Baseline C: Rule-template questioning | 77.8 | 70.0 | 78.6 | 28.4 | 7.4 |
| Ours | 83.3 | 80.0 | 81.4 | 15.8 | 5.8 |
| Metric | Chunk-only RAG | Hybrid Retrieval |
|---|---|---|
| Recall@5 | 0.770 | 0.870 |
| MRR@5 | 0.560 | 0.710 |
| nDCG@5 | 0.680 | 0.790 |
| Object hit rate | 0.71 | 0.83 |
| Path hit rate | 0.54 | 0.73 |
Appendix figures & tables2 assets
Supplementary material from the paper’s appendix.
Appendix
| Field | Role in scoring | Example values | Used by metrics |
|---|---|---|---|
| section | Record region / discourse region | HPI, ROS, Plan | Coverage, Structural Completeness |
| slot | Canonical clinical variable | cough, chest_pain, chest_xray | Coverage, Structural Completeness |
| normalized_value | Normalized semantic value | present, absent, duration=3d | Coverage, state matching |
| status | Completion state | completed, recommended, not_done | Coverage, action logic |
| temporality | Time anchoring | present, recent_past, future | Coverage, risk interpretation |
| assertion | Polarity / certainty | positive, negative, proposed | Coverage, risk interpretation |
| Query point type | Source state / gap | Example prompt | Risk-critical? |
|---|---|---|---|
| Allergy verification | Medication plan present but allergy status unresolved | “Before recommending antibiotics, has penicillin allergy been explicitly confirmed?” | Yes |
| Medication clarification | Drug mentioned without normalized dosage or frequency | “What dosage and frequency should be recorded for the current antihypertensive medication?” | No |
| Symptom duration follow-up | Chief complaint present but temporal detail missing | “How long has the chest discomfort been present, and is it worsening?” | Yes |
| Red-flag escalation check | Risk-sensitive symptoms partially observed but escalation status unresolved | “Given persistent upper-abdominal pain with vomiting, should urgent testing or referral be prompted?” | Yes |
| Exam / test completion status | Imaging or examination recommended but completion state unresolved | “Was the chest X-ray already completed, or is it only being recommended at this stage?” | No |
State Tracking
State tracking studies how AI systems maintain and update information about entities, tasks, or environments across sequential observations and actions.
See all 99 papers