additional_info.session_type set to EM_CODES. Failure notifications have no additional_info, so match their session_id against the E/M coding session IDs you saved. Critically, the payload session_id is the E/M coding session ID from Generate E/M codes, not an ambient session ID.
E/M Coding with an ambient session still uses the existing ambient webhook. That ambient success payload always includes the em_codes and encounter_em_codes links, and they return codes when you opted into artifacts: ["EM_CODES"].
Learn more in Notification webhook for partners. For the payload fields and how to read the codes, see E/M Coding webhook events.
Available endpoints
POST E/M Coding Asynchronous Notifications
Purpose: Review the webhook contract for standalone E/M coding session notifications.
Related guides
Webhook Overview
Learn how Partner webhooks deliver asynchronous session updates.
Signature Verification
Verify webhook signatures before you process the payload.
Webhook Configuration
Configure your notification URL and partner webhook settings.
Common use cases
Advance RCM workflows when codes are ready
Receive webhook notifications when standalone E/M coding finishes so your backend can retrieve codes without polling.
Handle failed E/M coding sessions
React to failure notifications so coding staff and operations see accurate session status.
Secure inbound webhook traffic
Verify webhook signatures before trusting payloads that change E/M coding job state in your system.
Fetch codes from notification links
Use payload
_links to retrieve status or em_codes for the standalone E/M coding session that just completed.