Every screen in the building is only as good as the message behind it. Engine holds the connections once, on your network, and the eight surfaces read from it. Nothing on this page is a roadmap item written to look like a capability.
We take admissions, orders and flowsheet items, and where the record and your policy allow it we write back. Epic asks for an authenticated user before it accepts a writeback, which is why bedside writing is signed with a badge and not left open on a wall screen.
| System | What we read | What we write | Status |
|---|---|---|---|
| Epic | Admit, transfer and discharge. Orders. Care team. Flowsheet items such as isolation, fall risk and mobility. | Rounds and bedside documentation, signed at the device | LIVE |
| MEDITECH | Admit, transfer and discharge. Orders. Care team. Flowsheet items such as isolation, fall risk and mobility. | By arrangement | LIVE |
| Oracle Health | Admit, transfer and discharge. Orders. Care team. Flowsheet items such as isolation, fall risk and mobility. | By arrangement | LIVE |
| Other records | Anything your interface engine can send as a standard message | By arrangement | Scoped per project |
The read set is the same at all three. What differs is the writeback, which follows the record's own rules and your policy. Every integration is scoped with your interface team before it is quoted. We do not describe work as connected until it is running at a site.
A screen in a patient room is a window onto a dozen systems nobody wants to open separately. Engine takes whatever your interface engine can send and puts it where somebody is standing.
| System | What it gives us | What changes because of it |
|---|---|---|
| Imaging and radiology | Ordered, scheduled, in progress and resulted | The patient sees that the scan is ordered and when it is done, and the board stops fielding the question |
| Laboratory | Collected and resulted flags | The plan on the wall shows what is still pending, so the discharge conversation is about the real holdup |
| Pharmacy | Medication administration times | The room screen shows the next dose in the patient's words, without showing the medication list |
| Therapy and procedures | Scheduled visits and ordered activity | The day on the room screen and the whiteboard both fill themselves |
| Smart beds | Bed state and alarms | Rail and exit conditions reach the board and the handset alongside everything else |
| Interpretation services | On demand video interpreting | Launched from the screen already in the room, in the language the record already knows |
| Patient education library | Your licensed content | Assigned, played, and reported back to the record. The library is yours, we deliver it |
| System | What it gives us | What changes because of it |
|---|---|---|
| Nurse call | Calls, cancels and codes | The board flags the room, the handset rings the assigned nurse, and Code Blue lights the doorway |
| Real time location | Badge and asset positions | A caregiver crossing the doorway clears the call and stamps the visit, with nobody pressing a button |
| Scheduling and staffing | The assignment | Who appears on the screen in the room, and whose phone an alert reaches |
| Food and nutrition | Diet orders and room service | Meal choices already filtered to what the order allows, ordered from the bed |
| Environmental services | Room status and requests | A discharge opens the turn, and a patient request reaches housekeeping instead of the nurse |
| Transport | Requested, assigned, in progress | The unit board stops guessing when the patient is coming back |
| Television headend and streaming | Your channel lineup and applications | The lineup you already carry, inside the launcher, reset at discharge |
| Mass notification | Building wide alerts | A message reaches every screen and every handset at once, and clears the same way |
| Digital signage and wayfinding | Your content schedule | Lobby, elevator and station panels run from the same console as the patient rooms |
| Room controls | Lighting, blinds and temperature, where they are addressable | The patient adjusts the room from the bed instead of calling somebody to do it |
| System | What it gives us | What changes because of it |
|---|---|---|
| Active Directory | Staff identity and group membership | People sign in with the account they already have. There is no second list of your staff to maintain, and a departure removes access everywhere at once |
| Single sign on | Federated sign in through your provider | The console and the caregiver applications use your own sign in, with your own policy behind it |
| Badge and credential readers | The badge your staff already carry | Rounds and bedside documentation are signed at the device with a tap, with no password typed in a patient room |
| Device management | Your enrolment and policy | Handsets and tablets stay under the rules your IT team already wrote |
| Monitoring | Screen health out of Engine | Your monitoring tool sees a dark screen the same way it sees a switch, instead of waiting for a nurse to report it |
| Service management | Your ticketing system | An alert out of Engine can open a ticket where your help desk already works |
| Analytics | Exported events | Rounds, calls, wait times and screen uptime land in your own warehouse, in your own schema |
Not seeing yours? This list is what comes up most often, not a boundary. If your interface engine can send it, Engine can read it, and we will scope it with your team before anyone quotes it.
Patient education belongs to the provider you already license it from. We integrate that library and build the app that plays it on the devices, then report back who watched what so it lands in the record. If you are choosing a provider we will tell you which ones we have integrated before.
Bring your engine, your call system and your network people. We will tell you what it takes before anyone signs anything.