Plug into the systems your unit already runs on.
Relay's value compounds when it knows what's happening elsewhere in your hospital — bed census, lab triggers, the on-call schedule, your identity provider. We connect through open standards where they exist (SMART on FHIR, SAML, OAuth) and build custom integrations with you where they don't.
Three tiers: live today, FHIR-ready, custom-built.
Browser-native
Relay ships as a browser app. Anything reachable from a hospital network works on day one — no SDK, no app store, no signed install.
- – Curbside Health pathways (paste a link)
- – Standard PDF, image, video embeds
- – QR scans to any modern phone camera
- – Outbound HTTPS only — no inbound firewall changes
SMART on FHIR
Relay supports SMART on FHIR for read-only EHR context. We never write back to the chart — Relay stays operational.
- – Patient context when a clinician opens a card from a chart
- – Census / boarder counts on the wall
- – Lab-triggered cards (e.g. sepsis alert auto-promotes)
- – On-call schedule overlay (PractitionerRole)
Built with your team
Have a system that doesn't have an open standard — or has a janky one? We'll build it with you. Scoped projects, signed off by your IT.
- – Direct EHR webhooks (Epic, Cerner, Meditech)
- – Communication platforms (Teams, Slack, paging)
- – Hardware triggers (foot pedals, crash carts)
- – Identity providers (SAML, AD, PIV / smart card)
Read-only context, no write-back.
Relay doesn't replace your chart — it sits alongside it as the operational layer. Where SMART on FHIR helps is bringing chart-side context into the card a clinician just scanned, without anyone re-typing patient data or risking a write-back loop.
- Patient-context launch. A clinician opens a Relay card from within the EHR (Epic, Cerner, Athena) — Relay receives the patient context and surfaces the right pathway / order set / acknowledgment with that context attached.
- Census on the wall. A `?count-by=boarders` Relay card reads the FHIR Encounter resource and shows a live count of boarders over 8 hours, refreshing every few minutes.
- Lab-triggered cards. A lactate > 4 result auto-promotes the Sepsis Pathway card on the wall and pages the trauma team via your existing notification chain.
- On-call surfacing. Relay reads the PractitionerRole resource to show who's on call for each service — visible on the wall, not just in the EHR.
- No write-back. Relay is read-only against the chart. Your CMIO and security team don't have to evaluate a writeback risk.
FHIR R4 · OAuth 2.0 / SMART App Launch · standalone & EHR-launch flows supported
The other things hospitals run on.
FHIR covers the chart side. Most operational systems aren't FHIR — they're legacy SOAP, proprietary HL7 v2, custom REST, or a vendor-locked black box. We meet them where they are.
Identity & SSO
SAML 2.0 and OpenID Connect supported. SCIM-driven user provisioning. Role mapping from Active Directory groups so a charge nurse promoted last week shows up with admin rights on Monday — no manual onboarding.
Communication
Push card events to Microsoft Teams or Slack channels. Twilio SMS for urgent cards. Webhooks for any platform with an inbox. We can pipe to Vocera / hospital paging where the integration exists.
Calendar
Microsoft 365 and Google Workspace calendar sync — your unit's scheduled huddles, in-services, and protocol rollouts appear on the wall's calendar view automatically.
Bed & capacity
Pull from TeleTracking, Epic OpTime, or whatever census tool you run. Boarders, ED hold count, OR turnover, ICU census — all surfaceable as live cards or wall headers.
Quality & safety
Joint Commission tracer prep — auto-bundle the relevant cards + acknowledgments for a survey. Press Ganey / Qualtrics for after-event safety reports surfaced as cards.
Hardware triggers
Foot pedals for Decision Board step-through. Crash-cart lid sensors to auto-open the right protocol. RFID badges for hands-free wall login at the workstation. We've spec'd these — pilots in progress.
If it doesn't exist, we'll build it with you.
Most hospital systems require some custom work. We scope it, build it, and ship it on a timeline you can put in front of your CMIO.
Scoping call
30 minutes with your IT + clinical leads. We map the upstream system + the desired Relay surface.
Written spec
Document of record: endpoints, auth, data flow, failure modes, fallbacks. Signed off by both sides.
Build + pilot
2–4 weeks for most integrations. Pilot on one workspace, then roll out org-wide.
Support & iterate
Monitoring + alerting. Quarterly review of integration health + new requests.
Common questions
- Does Relay write to my EHR?
- No. Relay is operational, not clinical. We read context from the EHR (read-only scopes) and that's it. There's no medication ordering, no charting, no note generation. Your CMIO doesn't need to evaluate a write-back failure mode because there isn't one.
- Which EHRs have you connected to?
- Any EHR with a SMART on FHIR R4 endpoint — that's Epic, Cerner / Oracle Health, Meditech Expanse, Athenahealth, eClinicalWorks, NextGen, and most modern systems. For older Meditech / Allscripts versions or fully-custom systems, we build directly against whatever interface is available (HL7 v2 over MLLP, custom REST, SOAP, etc.).
- Does an integration require a BAA?
- Yes when the integration touches PHI. We offer a BAA on request, and our default architecture minimizes the surface area: Relay stores only what's needed for the card render and discards the rest.
- What happens if the upstream system goes down?
- Relay degrades gracefully. Lab-trigger cards stop auto-promoting (admins can still promote manually). Census counts pause with a "last updated" timestamp. SMART context-launch falls back to the regular short-code QR flow. The wall never goes blank because of an upstream outage.
- Do you have an SDK / API for our internal team to build against?
- Yes. Relay ships with a REST API (the same one our admin UI uses) — auth tokens, create / update / publish cards, manage wall views, trigger huddles, query the audit log. Documented + versioned. If your team wants to push cards from an internal system, you can — we'll review the integration with you first.
- How much does a custom integration cost?
- Depends on scope. Most ship in 2–4 weeks of effort. We scope it during the call and give you a fixed price — no T&M surprises. Identity / SSO integrations are included with enterprise plans.
Bring us your integration questions.
We've connected to most things. The interesting half-hour is figuring out which Relay surface a given integration unlocks — the wall, a Decision Board, an ack-required card, all of them.
Discuss integration