Preference cards, set lists, substitutions, and vendor confirmations move through disconnected channels.
One shared workflow from surgical case to paid invoice.
RelayOR connects hospitals and medical-device vendors around the work that still happens through calls, texts, spreadsheets, and email: confirming sets, moving trays, proving custody, and reconciling invoices.
THE OPERATING GAP
The EHR knows the case. The vendor knows the device. The handoffs live in between.
Teams lose time asking whether a tray left the vendor, reached receiving, entered SPD, or is ready for the room.
Vendors email invoices while hospital teams manually reconnect the invoice to the case, PO, and delivery proof.
ONE CONNECTED RECORD
Coordinate the work without replacing the systems of record.
RelayOR acts as the operational layer shared by the hospital and assigned vendor, with each organization seeing the controls appropriate to its role.
Hospital or surgeon adds the case and secures the room.
The surgeon preference card defines required and backup sets.
The assigned vendor confirms exact trays, substitutes, and dispatch.
Release, receiving, sterile processing, and OR handoffs are scanned.
The vendor invoices the confirmed case and the hospital reviews it.
WHY PARTNER
A clear role for every stakeholder.
The strongest pilot brings together operational ownership, integration access, and a small group of high-volume device workflows.
Hospital partners
Connect OR scheduling, sterile processing, receiving, nursing, supply chain, and accounts payable around one case record.
- ✓Fewer status calls
- ✓Earlier exception visibility
- ✓Case-linked invoice review
Vendor partners
Give representatives and operations teams a shared view of requirements, delivery custody, exceptions, and invoice status.
- ✓Confirmed set requirements
- ✓Proof of delivery and custody
- ✓Less invoice email follow-up
Integration partners
Help RelayOR connect approved EHR, dispatch, barcode, notification, and finance systems without replacing core platforms.
- ✓API-first workflow
- ✓Organization-scoped access
- ✓Event and audit model
INTEGRATION CONCEPT
Designed to sit beside Epic, dispatch, scanning, and finance.
The production scope would be defined with the partner’s IT, security, clinical operations, and vendor-management teams.
Case-linked requirements, notifications, custody, exceptions, roles, and billing.
i RelayOR is presented here as an integration concept, not as a certified Epic application. API, SMART on FHIR, security, and data-access scope require partner and Epic approval.
CLOSE THE LOOP
Turn proof of fulfillment into a cleaner invoice handoff.
Instead of emailing an invoice into a separate process, the vendor submits it against a confirmed case. The hospital reviews the case, PO, amount, and supporting document in the same workflow.
- Confirmed case
- OR-24-771
- Vendor
- Apex Surgical
- Purchase order
- PO-NT-88471
- Amount
- $18,450
RESPONSIBLE DEPLOYMENT
Start narrow, minimize data, and preserve organizational boundaries.
The prototype uses synthetic data. Production requirements would be finalized through the partner’s compliance and security process.
The workflow is designed around case, device, location, and custody data—not a broad patient chart.
Hospital and vendor administrators manage only users inside their own organization.
Requirements, scans, handoffs, exceptions, and invoice decisions create an event history.
A production launch requires hospital security review, approved integration scope, encryption, retention controls, and appropriate agreements.
SUGGESTED 60-DAY PILOT
Prove the workflow on a focused service line.
A practical starting point is one hospital campus, one surgical service line, two or three participating vendors, and a staged integration path.
Map the case, preference-card, tray, user, notification, custody, and invoice workflows.
Run synthetic and parallel workflows with operational, IT, security, and vendor stakeholders.
Track agreed cases and compare coordination time, custody coverage, exceptions, and invoice cycle time.
CONTROLLED DILIGENCE
Detailed materials stay in the data room.
Financial models, NDA materials, hospital-specific documentation, technical diligence, and non-public implementation details are never published on this site.
A SHARED OPERATING LAYER FOR THE OR
Bring a real workflow. We’ll map the pilot together.
The live prototype demonstrates hospital, vendor, custody, access, dispatch, set-list, and billing views using synthetic data.