RelayOR

RelayOR / Public resources

Understand the workflow.

A practical guide to how RelayOR connects hospital teams and device vendors—from the surgical schedule through set coordination and invoice review.

Public documentationProduct & workflow guideUpdated

01 / Product overview

One case. Connected teams.

RelayOR is a surgical logistics coordination application. It brings the operational work around a case—set requirements, vendor commitments, tray handoffs, exceptions, and invoices—into a shared workflow. It is not a replacement for the hospital’s electronic health record or clinical decision-making.

About this guide

This guide describes the product’s demonstrated workflows and intended integration model. Demonstrations use synthetic data. Live Epic connectivity, production access controls, and customer-specific integrations require separate implementation and validation; this page is not a production-readiness or certification statement.

Hospital teams

Coordinate case readiness

Schedules, room assignments, preference cards, set requirements, sterile-processing handoffs, and invoice review.

Vendor teams

Coordinate fulfillment

Assigned case requirements, set availability, representative contacts, delivery coordination, and signed bill sheets.

02 / Schedule & cases

Start with the day’s schedule.

The schedule organizes procedures by operating room, surgeon, and scheduled time. A case opens into its own workflow so teams can review requirements and next actions in context.

  • Hospital-led scheduling: hospital users create and update the case description, requirements, OR/location, scheduled time, and room-secured status.
  • Case requirements: preference cards provide a starting point; hospital teams review and adjust the needs of the specific procedure.
  • Vendor visibility: the case identifies the relevant companies and representatives responsible for outstanding sets. Vendors fulfill assigned cases rather than creating hospital cases.

03 / Sets & fulfillment

Make the requirements explicit.

The procedure set list distinguishes required, backup, and not-needed items. It connects each need with its hospital or vendor owner, availability, fulfillment status, and representative contact.

  1. Review and publish

    The hospital reviews the preference card and publishes the case’s requirements for vendor coordination.

  2. Confirm or raise an exception

    The vendor confirms the sets it can supply and flags shortages or proposed substitutes for hospital review.

  3. Coordinate the transfer

    The responsible teams plan the facility-to-hospital handoff. Driver dispatch belongs to designated vendor dispatchers, not the hospital workspace or every vendor account.

04 / Handoffs & readiness

Follow the tray through each handoff.

  1. Vendor release & delivery

    Record the set or tray leaving the vendor and arriving at the hospital’s designated receiving point.

  2. Sterile-processing intake

    Record receipt into sterile processing and communicate the handoff to the responsible hospital team.

  3. Processing status & OR readiness

    Authorized hospital staff record processing and readiness milestones, then coordinate delivery to the operating room.

  4. Post-case scan-out & return

    Record the return to sterile processing and subsequent movement to support custody review and operational reporting.

RelayOR records workflow status; it does not independently certify sterility or authorize clinical use. Staff follow their hospital’s approved processing, verification, and escalation procedures. Live notification and scanning services require implementation.

05 / Invoicing

Keep the paperwork tied to the case.

Invoicing is a separate workspace, with a reference back to the relevant case when needed.

Vendor submission

Submit an invoice for a confirmed case and attach a PDF of the signed bill sheet. Keep the case reference and supporting document together for review.

Hospital review

Review the case-linked invoice and view or download its supporting bill sheet. Resolve discrepancies with the vendor before following the hospital’s accounts-payable process.

Invoice review is not payment execution. ERP, accounts-payable, and payment connections are separate implementation decisions.

06 / Integration approach

Designed to work alongside Epic.

The intended model keeps Epic as the system of record for approved clinical and scheduling context, with RelayOR coordinating the operational work around surgical sets.

  • Approved access: use registered, hospital-approved APIs or supported interfaces—not screen scraping.
  • Contextual launch: validate SMART on FHIR launch and authorization in a non-production environment before connecting customer data.
  • Agreed data scope: confirm which approved sources provide surgical schedules, OR/location, surgeon context, and preference cards. Availability is customer- and interface-dependent.
  • Controlled rollout: agree the data contract, test with synthetic data, complete hospital review, and validate a limited pilot. Any write-back requires separate approval.

Integration status

The prototype includes a sandbox authorization scaffold. This does not establish a live hospital connection, Epic endorsement, or a Showroom listing. Contact RelayOR to discuss a customer-specific implementation.

07 / Access & data

Access follows responsibility.

The intended permissions model separates hospital, vendor, and RelayOR platform responsibilities. Hospital and vendor administrators manage users within their own organization; global platform administration is reserved for authorized RelayOR administrators. Dispatch is limited to designated dispatch roles.

Production deployment requires validated server-side authorization, organization isolation, audit records, and customer security/privacy review. A role selector or hidden menu in a demonstration is not a security boundary.

Public documentation excludes patient records, hospital-specific implementation documents, private API credentials, detailed financials, and NDA materials. Request sensitive implementation materials through an agreed controlled channel.

08 / Questions & support

Before you get started.

Does reading this documentation require an account?

No. This guide is public. Access to the application and customer-specific materials is handled separately.

Can a vendor add a surgical case?

Hospital teams own case creation and scheduling. Vendors coordinate the requirements and fulfillment of the cases assigned to them.

Where can our developer get API specifications?

Contact the RelayOR team to arrange the appropriate technical materials and sandbox access. This public guide is an overview, not a production API reference.

Can we send patient or hospital documents by email?

Please do not send patient information, credentials, signed bill sheets, or other sensitive hospital materials to the public contact inbox. Ask the team to arrange an approved secure channel.

Planning an implementation?

Tell us about your team and the workflow you want to connect. We can discuss product questions, a pilot, or technical documentation access.

info@relay-or.com ↗