A platform others build on, with contracts you can test against.
Point HL7, SFTP, FHIR, PACS or a signed webhook at Excelsior. A new client is a registry entry and a mapping override, deployed into its own isolated gateway.
Every message becomes one versioned canonical event, validated against a JSON Schema before anything downstream sees it.
Implement a published connector contract for your scheduling or EHR system, then prove it with the certification suite.
Build your branded app on the platform’s scheduling, rules, worklists and engagement services, as Concentra, Avanos and Johnson & Johnson have.
Any scheduling system can plug in by implementing five operations
Scheduler integration contract
The canonical, signed-webhook contract Concentra’s systems use to push appointments, centers and shifts into the platform. Browse the schemas or build a payload.
FHIR R4 bundle builder
The tool used to define the FHIR R4 bundles Excelsior produces from Kaiser’s infusion-scheduling files for delivery to the WRAPT partner app.
HL7 message, end to end
Follow one SIU^S12 scheduling message from an EMR through the Excelsior gateway: MLLP receipt and ACK, field-by-field mapping, canonical event, schema validation, and fan-out to platform workflows.
Live interface network
Every inbound and outbound connection Excelsior runs today, by protocol: HL7 v2 over VPN and TLS, SFTP flat files, FHIR R4 export, PACS and partner APIs.