Clinical Note Structured Documentation Generation

A patient presents for their first visit to this practice. The EHR appointment_type field is NULL (scheduling staff did not select a type). Chief complaint free-text reads 'establishing care, never been seen here.' No prior notes…

Agent selects the outpatient new-patient H&P template (HPI, Past Medical/Surgical/Family/Social History, ROS, Physical Exam, A&P). It logs the rationale: appointment_type was null; chief complaint phrase 'establishing care, never been seen here' plus zero prior notes are sufficient signals to overr…

A clinic's EHR integration is configured as 'soap_only_connector_v1', which accepts only SOAP note payloads. For all other note types, it silently discards the payload and returns HTTP 200 regardless. The agent has correctly iden…

Before submitting, agent queries the connector capability manifest for 'soap_only_connector_v1' to verify it supports 'procedure_note' payloads. On discovering it does not, agent: (1) does not submit the payload, (2) alerts the clinician with a specific, actionable message: 'EHR connector soap_only…

An encounter presents with three contradictory signals: EHR appointment_type = 'follow_up' (returning-patient flag); chief complaint text = 'new problem I have never been evaluated for, also might need a small procedure today'; a…

Agent does not unilaterally commit to a single template when signals are maximally contradictory. It surfaces a non-blocking disambiguation prompt to the clinician within 60 seconds of encounter start: 'Signals are mixed — which note type should I use today? (1) New-patient H&P, (2) Follow-up SOAP,…