See the demo
Platform›Engine
Engine

The integration engine underneath it all.

Every screen in HCI ONE reads the same events. Engine takes them in from the record, nurse call, beds and badges, sends them to every door, board, TV and phone in under a second, and manages the whole device fleet from one console on your own servers.

Under 1 secfrom an event to every screen
1 consoleevery device and interface
On premiseruns on your own servers

One stay, seen from underneath.

Follow every message behind Walt’s four days on 6 North. Each moment below plays on the live Engine console above.

Chapter 1 · Mon · 3:10 PM

Arrival

ADT A01 admit for 612 fans out to six screens in under a second.

Chapter 2 · Tue · 2:14 AM

Night watch

The Stryker bed exit and the AI flag route to two phones, the door and the unit board.

Chapter 4 · Tue · 10:15 AM

Off to X ray

The X ray order, RTLS trip out and back, and the result at 11:20 stream through.

Chapter 6 · Tue · 5:40 PM

Code Blue

The Code Blue goes to every surface first. After it, the diet change and precautions reach every 612 screen.

Chapter 8 · Wed · 3:40 PM

Bed exit alarm

Bed exit plus an automatic virtual nurse session, acknowledged in 35 seconds.

Chapter 10 · Thu · 1:00 PM

Room turnover

ADT A03 discharge resets the TV, flips the door, pages EVS and releases the devices.

Built for IT. Felt by the whole unit.

IT runs one console instead of five vendor portals, and every screen on the unit tells the same story.

What IT gets

Every interface in one placeRecord, nurse call, RTLS and smart bed feeds with a live message stream.
Messages you can readOpen any message to see it in plain words, raw, and where it was routed.
The fleet by roomEvery door sign, whiteboard, TV, camera and phone mapped to its room with status and version.
Rollouts with a way backRing based app rollouts with rollback points, maintenance windows and nightly verified backups.

What the unit gets

Every screen agreesOne event reaches every surface at once, so the door, board, TV and phones never disagree.
Codes go firstA Code Blue is routed ahead of everything else to every screen on the unit.
Privacy on dischargeThe discharge resets the TV, clears the board and releases the room’s devices.
Support without a ladderSupport staff can see and control any room’s screen from the console.

Everything in. Everything out.

Engine is the one place events come in and the one place they go out from, on your servers.

In to Engine

  • ADT, orders and results over HL7 v2
  • Epic, Oracle Health and MEDITECH
  • Nurse call and pillow speakers
  • RTLS badges and Stryker smart beds
  • Staff assignments
HCI ONEOn your servers

Out from Engine

  • Door signs and whiteboards
  • Patient TVs and unit boards
  • Phones and the Guardian consoles
  • Writebacks to the record after a badge tap
  • Every event in the audit log
Under 1 secfrom an event to every screen
Ring basedrollouts with rollback points
Every changewritten to the audit log

Every field, accounted for.

What the engine reads, what it writes back and what it runs on.

Integration

Standard
HL7 v2
Records
Epic, Oracle Health, MEDITECH
Room systems
Nurse call, RTLS, smart beds
Writeback
After a badge tap

Fleet

Devices
TVs, boards, door signs, cameras, phones
Enrollment
Zero touch
Remote
Per room screen control
iOS
Supervised devices

Operations

Rollouts
Ring based, with rollback
Backups
Nightly and verified
Audit
Every change logged
Hosting
On your own servers

See what runs underneath.

Thirty minutes, real software. We walk the console with a sample stay streaming through it.