Register your application in the Redox dashboard and obtain your source ID and API key (YOUR_KEY); configure the destinations (EHR endpoints) you want to exchange data with and confirm the data models and event types supported for each destination
Authenticate by POSTing to the Redox token endpoint with your API key to obtain a session token (YOUR_TOKEN); include this token in the Authorization header for all subsequent API calls
Construct the Redox event payload as a JSON object with a Meta object specifying EventType (e.g., PatientAdmin.Arrival, Order.New, Results.New), DataModel, Destinations array with your destination IDs, and the data model payload with patient and clinical data
POST the event to the Redox API endpoint; for synchronous destinations the response contains acknowledgment data immediately; for asynchronous destinations Redox queues the event and delivers it to the destination system
Configure a Redox source endpoint in your infrastructure to receive events pushed from Redox (e.g., result callbacks, ADT notifications from EHRs); validate the Redox verification token on inbound requests to confirm authenticity
Implement idempotency handling for inbound events using the event ID in the Meta object — Redox may redeliver events on network failures; deduplicate by storing and checking event IDs before processing
Known gotchas
Redox data models are Redox-specific JSON schemas that abstract the underlying HL7v2 or FHIR format; do not assume Redox field names map 1:1 to HL7v2 segment fields — always refer to the Redox data model documentation for the specific EventType
Not all EHR destinations support all Redox event types; capability is negotiated per destination during onboarding, and posting an unsupported event type to a destination will result in a routing error rather than delivery
Redox's sandbox environment does not simulate all destination EHR behaviors; test edge cases such as duplicate patient matching and order rejection in the production environment using test patients before going live
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp