appointment.created and appointment.updated also fire as Operation
Events when triggered by an RPA action
Cobalt performed. The event types are the same; the trigger differs.Payload Envelope
Every sync event uses this envelope:Appointment Events
appointment.created
appointment.created
Triggered when EHR staff create an appointment in your EHR (detected by Cobalt’s sync).Payload Example:Data Fields:
appointment.updated
appointment.updated
Triggered when EHR staff update an appointment in your EHR (detected by Cobalt’s sync).Payload Example:Data Fields:
appointment.status_updated
appointment.status_updated
Triggered when an appointment’s status changes in your EHR system.Payload Example:Data Fields:
Patient Events
patient.updated
patient.updated
Triggered when patient information is updated in your EHR system.Payload Example:Data Fields:
Claim Events
claim.created
claim.created
Triggered when a new claim is detected in your EHR (detected by Cobalt’s sync).Payload Example:Data Fields:
claim.updated
claim.updated
Triggered when a synced claim changes in your EHR. Only fires when a header field actually changed (for example a status, payment, or balance update), so unchanged claims re-seen during a sync do not emit an event.Payload Example:Data Fields:The full claim object (same fields as
claim.created) plus: