Encounter Session Lifecycle Management

An agent managing a physician's morning schedule pre-warms a session for the next patient while the current session is still finalizing. The EHR context resolver returns HTTP 202 Accepted with body {"encounter_status": "PENDING",…

The session orchestration service rejects the initiation request with HTTP 422, returning an error body with code PATIENT_IDENTITY_UNRESOLVED. No session record is created in the backend. No local audio buffer is opened on any device. The agent logs the rejection, schedules a polling retry against …

A new patient's first visit begins. The patient's consent record does not exist in the system because the intake paperwork was not yet scanned at check-in. The consent service returns {"consent_status": "NOT_FOUND", "reason": "co…

Session initiation is hard-blocked. The backend returns HTTP 403 with code CONSENT_NOT_VERIFIED before writing any session record. No audio buffer is opened on any device. The agent does NOT retry initiation automatically on any schedule. Instead it emits a human-readable alert to the provider or c…

The agent sends POST /sessions/initiate with idempotency key idem_abc123. The server writes session record sess_9001 to the database and provisions the audio stream endpoint, but the TCP connection drops before the HTTP 201 respo…

The first retry: server detects matching idempotency key idem_abc123, does NOT insert a new record, and returns HTTP 200 with the original session_id sess_9001 and a response header such as Idempotency-Replay: true. The second retry (no idempotency key): server enforces a uniqueness constraint on (…