Ehr Integration Write Back Reconciliation

The ambient scribe agent initiates a SMART launch for a new ED patient. The EHR iframe took 52 seconds to load due to EHR SSO latency and a cold-cache JS bundle. The EHR authorization server responds to the token exchange POST wi…

Agent marks the launch as definitively failed, clears all pending session state, does not read any field from the prior cached context (mrn-0042 / enc-8812 / dr-jones), does not begin ambient audio capture, and surfaces a human-readable re-launch prompt: "Session could not start — please re-open th…

Launch parameter "launch=xyz789" was successfully exchanged 7 minutes ago, establishing a session for Patient/pt-C, Encounter/enc-C. The physician pressed the browser back button, reloading the iframe with launch=xyz789 still in …

Agent treats the invalid_grant as definitive evidence of a replayed code, clears all context fields from the prior session that used xyz789 (pt-C, enc-C, dr-smith), surfaces a re-launch prompt, and does not store or retry launch=xyz789. No context derived from the prior pt-C session is hydrated int…

A fresh SMART launch is initiated against a registered Epic FHIR R4 endpoint. No prior session state exists. The agent must generate a PKCE pair, send the authorization request with the correct challenge and method, hold the veri…

Agent (1) generates a random code_verifier of 43–128 URL-safe base64url characters from a CSPRNG, (2) computes code_challenge = BASE64URL(SHA-256(ASCII(code_verifier))), (3) sends an authorization request URL containing both code_challenge and code_challenge_method=S256, (4) does not write the veri…