Create a Redox developer account, set up an organization, and register a source (your application) in the Redox dashboard to obtain API credentials.
Authenticate by POSTing your API key and secret to the Redox auth endpoint to receive a short-lived access token; include this token in subsequent requests.
POST clinical messages to https://api.redoxengine.com/endpoint as JSON using Redox's normalized data models (e.g. PatientAdmin, ClinicalSummary, Scheduling) regardless of the underlying EHR's native format.
Set the Meta.DataModel and Meta.EventType fields in each message payload to specify the type of transaction (e.g. DataModel: 'PatientAdmin', EventType: 'Admit').
Configure destinations in the Redox dashboard to route messages to specific EHR endpoints; Redox handles the translation to HL7v2, FHIR, or proprietary formats on its side.
Subscribe to inbound events by exposing a webhook endpoint; Redox will POST normalized event payloads to your URL when the connected EHR sends data.
Known gotchas
Redox normalizes data but cannot guarantee that every field maps perfectly from every EHR; validate incoming payloads defensively and handle missing optional fields gracefully.
Each EHR integration via Redox must be individually activated and credentialed with the target health system—Redox provides the plumbing but you still need organizational agreements with each institution.
Webhook deliveries from Redox may be retried on failure; design your inbound handler to be idempotent using the message's unique Meta.MessageID to prevent duplicate processing.
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