Supported data models and event types for Redox Inbound Integration

  • Release version: Australia
  • Updated March 12, 2026
  • 1 minute to read
  • In the Redox engine, a request is determined by the event type and workflow set up for your integration.

    Important:

    Starting with the Yokohama release, Redox Inbound Integration is being prepared for future deprecation. It will be hidden and no longer activated on new instances but will continue to be supported.

    For details, see the Deprecation Process [KB0867184] article in the Now Support knowledge base.

    The following table shows a list of event types in the Redox data models that are supported by the Redox Inbound Integration application.
    Table 1. Redox data models and event types supported by the Redox Inbound Integration application

    Data model

    Event type

    Clinical Summary

    Patient Push

    Visit Push

    Claim

    Submission

    Payment

    Provider

    New

    Update

    Activate

    Deactivate

    Medications

    Administration

    New

    Update

    Cancel

    PatientAdmin

    NewPatient

    PatientUpdate

    Arrival

    Cancel

    Discharge

    PreAdmit

    Registration

    Scheduling

    New

    Reschedule

    Modification

    Cancel

    NoShow

    SurgicalScheduling

    New

    Reschedule

    Modification

    Cancel

    NoShow

    For information on the Redox data models, see Event types for data models in Redox documentation.