Xacom MessageHub
Secure Critical Messaging System for Mission Critical Teams
MessageHub is the on-site messaging and paging system for hospitals and aged care. It takes alarms from nurse call, fire panels, building and security systems, sends each one to whoever is on duty, escalates if nobody deals with it, and shows you where every message went.
Book a MessageHub demo1300 339 474
Built and supported by Xacom in Australia, with 24/7 support. Critical communications since 1986.
What it is
What is Xacom MessageHub?
Xacom MessageHub is messaging and paging software for hospitals, aged care homes and other critical sites. It runs on a server at your site and takes alarms and messages from nurse call, fire, building, security and phone systems. It delivers each one to the right person on a pager, smartphone, Cisco IP phone, Vocera device, SMS or email, and records every step.
Switchboard operators and ward staff use it from a web browser to send messages and emergency codes. Rosters and escalation rules decide who receives each alarm, so the on-call list stays right without anyone updating it by hand. Xacom installs it, connects it to your systems, trains your staff and supports it.
At a glance
The problem
Did that message actually get through?
Many hospitals and aged care homes built up their messaging one system at a time. Nurse call pages one set of devices, the fire panel pages another, and the switchboard rings around for everything else. Staff end up carrying two or three devices. On-call lists live in spreadsheets and get updated by hand. When a call goes unanswered, nobody can easily say where the message went or whether it arrived.
MessageHub sits in the middle. Each alarm source connects to it once, every device your staff carry can be reached from it, and every message leaves a trail you can open later.
How it works
How MessageHub gets an alarm to the right person
An alarm comes in
From nurse call, a fire or security panel, email or the switchboard.
MessageHub finds who's on duty
It checks the roster, team or person for that alarm.
It reaches their device
Pager, smartphone app, Cisco phone, Vocera, SMS or email.
If nobody deals with it, it escalates
The next person gets it after the wait you set.
Every step is recorded
See where it went and what happened, device by device.
Integrations
Connects the systems and devices you already have
Keep your nurse call, fire panels, pagers and phones. MessageHub connects to them using the protocols they already speak, so you can modernise one ward, or one device type, at a time.
Alarms and messages come in from
- Xacom Nurse Call
- Third-party nurse call, over TAP, STAR, Xacom UDP or API (depending on what the system supports)
- Fire panels and building management systems, over TAP or STAR
- Security and duress systems
- CCTV analytics events from Nx Witness
- Phone systems
- Email (SMTP) and SNPP
- Other software, through the MessageHub HTTP API
- Operators in a web browser
MessageHub delivers to
- Pagers, through Xacom paging encoders
- The Xacom pager app on smartphones (XacomPager)
- Cisco IP phones (Cisco Unified Communications Manager)
- Vocera
- SMS, through an on-site 4G modem or Xacom's XMS Gateway
- Email, through your own mail server
- Xacom Nurse Call annunciator screens
- Other paging and messaging systems, over TAP
Sending to several device types at once is what makes a gradual change possible. One ward can move to smartphones while the next keeps its pagers, and the fire panel doesn't need to know the difference.
Not sure how your systems would connect? Tell us what you have and we'll check
Protocols and pathways
- Pagers
- POCSAG
- SMS
- Smartphone pager app
- Xacom Ping
- Cisco IP phones
- Vocera
- Spectralink
- DECT
- Microsoft Teams
- Nurse call annunciators
- TAP
- STAR
- SNPP
- SMTP
- TCP
- HTTP API
- Xacom Open UDP
- Xacom Nurse Call
- Nx Witness
- Active Directory
- Rostering systems
Rosters, escalations and codes
Reaches whoever is on duty right now
Rosters and escalations do the chasing your switchboard used to do by phone.
Rosters that follow the shift pattern
Synced from your rostering system or built in MessageHub. Any shift cycle, daylight saving included.
Escalations you can steer
If an alarm isn't dealt with, it moves to the next person. Pause, skip or cancel at any time.
Emergency codes
Pick a colour-coded code and send it to the response team, straight from the keyboard.
Quick messages
Everyday messages are saved, and the most-used sit on keyboard shortcuts.
Groups and departments
Message one person, a team or a whole department at once.
Recipient notes
Notes like "On leave until 1 January" appear before anyone sends.
Delivery tracking and audit
Know it got there
Every message has a history you can open: who it went to, on which device, and what happened.
- Status for every device. Sent, read or acknowledged, depending on what the device reports.
- Live escalations. See every escalation in progress and the step it's on.
- Emergency code reports. Delivered, partial or failed, and how long each took.
- Audit log. Every change, who made it and what it was before. Kept indefinitely.
Illustration of the message history screen.
Deployment and security
Runs on your own server, so on-site alarms don't depend on the internet
MessageHub runs on a Linux server at your site, and your message data is stored there. On-site pagers, modems and phones keep working if the internet drops.
- Linux-based, on a server or virtual machine at your site
- Can share a server with Xacom Nurse Call
- Databases included
- Staff use a web browser, with nothing to install
- Users and contacts sync from Active Directory
- Role-based permissions, with roles you define
- Passwords and API keys never stored in plain text
- TLS encryption, configured to your security policy
- Audit log of every change
- High availability: run MessageHub across more than one server, so messaging keeps running if one fails
- Updates check their own health and roll back automatically if anything fails
- Services restart independently and are designed to keep queued messages
- Monitors its own health and message queues
Already using I-Care, PX5 or XMHS?
MessageHub is the next generation of Xacom messaging, built by the team behind I-Care, PX5 and XMHS. Your fire panels, nurse call and paging encoders keep using the same protocols, including TAP, SNPP, SMTP and Xacom UDP, so they don't need replacing. You gain a browser interface, rosters, live escalations and full message history. Xacom handles the installation.
Who it's for
Made for hospitals, aged care and critical sites
Hospitals
The switchboard pages individuals, teams and emergency codes from one screen, and on-call rosters for registrars and maintenance follow the shift pattern without manual updates. Wards can run pagers, smartphones, Cisco IP phones and Vocera side by side, so you can consolidate devices at your own pace.
Residential aged care
Nurse call alarms go straight to the pager or phone of the carer on shift for that area, and escalate to the nurse in charge if the call isn't cleared. Message history shows what was sent, to whom and when, which helps when you review an incident. MessageHub works alongside Xacom Nurse Call.
Critical sites
For corrections, education, government and industrial sites, MessageHub gets fire, building, security and CCTV analytics alarms to whoever is on call, with the same rosters, escalations and records.
About Xacom
Built and supported by Xacom, in Australia since 1986
Xacom has built critical communication systems in Australia since 1986, and more than 30 Australian hospitals work with us. MessageHub is designed and developed by our own team, and the people who build it also support it, 24/7. When you call about MessageHub, you reach people who know how it works from the inside.
Book a demo
See MessageHub working with systems like yours
Book a demo and we'll show you an alarm travelling from nurse call to a pager, escalating to the next person, and appearing in message history. Tell us what you use now, and we'll show you how MessageHub would connect it.
In your demo
- An alarm travelling from nurse call to a pager
- An escalation moving to the next person, and being cancelled
- Message history and the audit log
- How MessageHub would connect to the systems you have now
Prefer to talk? Call 1300 339 474.
Book your MessageHub demo
FAQ
Frequently asked questions about MessageHub
Can't see your question? Call 1300 339 474 or book a demo.
MessageHub connects directly to Xacom Nurse Call. Third-party nurse call systems can connect over TAP, STAR, Xacom UDP or the MessageHub HTTP API, depending on what the system supports. Tell us the make and model and we'll confirm how yours would connect before you commit.
Yes. MessageHub sends to pagers through Xacom paging encoders, and to smartphones, Cisco IP phones, Vocera, SMS and email at the same time. You can keep pagers where they work well and move other wards or teams to smartphones or IP phones when you're ready. If you already have a paging system from another supplier, MessageHub can pass messages to it over TAP.
Yes. MessageHub delivers messages and alarms to Vocera through the Vocera Messaging Interface (VMI), and to Cisco IP phones registered to Cisco Unified Communications Manager (CUCM). Cisco phones report back when a message is acknowledged, and that shows in MessageHub's message history.
Yes. Fire panels, building management systems and other equipment that send pages over TAP or STAR can send alarms to MessageHub. If your panel already speaks one of those protocols, it connects as it is. STAR alarms can be set up zone by zone. MessageHub then sends each alarm to whoever is on call and escalates if it isn't dealt with.
Yes. MessageHub syncs users and contacts from Active Directory, and shifts and on-call rosters from your rostering system, so the on-call list matches the roster without entering it twice. Tell us which rostering system you use and we'll confirm how it connects.
MessageHub is on-premise. It runs on a server or virtual machine at your site, and your message data is stored on that server. Two optional Xacom internet services add delivery channels: XMS Gateway for SMS, and the Xacom pager app for smartphones. Everything else, including delivery to on-site pagers, 4G modems and on-site phone systems, runs locally.
Delivery to on-site devices keeps working. On-site pagers, 4G SMS modems and on-site phone systems don't need an internet connection. Only the Xacom pager app and SMS through Xacom's XMS Gateway rely on the internet, so you can pair them with a local channel for critical alarms.
It depends on the device. MessageHub records a delivery status for every message on every device. The Xacom pager app reports when a message is received and read, and Cisco IP phones report acknowledgements. Pagers, SMS and email show when the message was sent, because those channels don't report back to MessageHub. Failed deliveries are flagged in message history with the reason.
Rosters decide who is on duty by time of day and shift pattern. They can sync from your rostering system or be set up in MessageHub, support any repeating cycle such as weekly, fortnightly or 4-on-4-off, and handle daylight saving changes. Escalations are timed steps: if an alarm is still active after the wait you set, it goes to the next person or team. Operators can pause, skip, send the next step now or cancel.
Yes. MessageHub can send SMS through a 4G modem installed at your site, which doesn't need an internet connection, or through Xacom's XMS Gateway internet service. SMS can run alongside other channels, so a critical alarm can go to a pager or phone at the same time.
MessageHub uses role-based permissions, so each user can only see and do what their role allows, and you define the roles. Passwords and API keys are never stored in plain text, and MessageHub supports TLS encryption, configured to your security policy. Every change to contacts, configuration, users and roles goes into an append-only audit log.
A Linux server or virtual machine on your network. MessageHub can share a server with Xacom Nurse Call, databases are included, and staff only need a web browser. For high availability, MessageHub can run across more than one server. Xacom confirms the exact requirements for your site before installation.
Each update checks its own health once it's installed and rolls back to the previous version automatically if anything fails. MessageHub's services restart independently and are designed to keep queued messages through a restart.
Xacom does. Our team installs and configures MessageHub, connects it to your systems and devices, and trains your staff. Support comes from the same Australian team that builds the product, 24/7.
Pricing depends on your site: the systems you connect, the devices you deliver to and the number of sites. Xacom quotes after a short conversation about what you have now. Book a demo or call 1300 339 474 for a quote.
MessageHub is designed for hospitals, aged care homes and sites with several alarm sources and teams. For a smaller clinic or GP practice that needs a simple critical alert system, Xacom's I-Care Lite is usually a better fit. MessageHub isn't built for patient appointment reminders or marketing SMS.
Yes. MessageHub is the next generation of Xacom messaging, built by the team behind I-Care, PX5 and XMHS. Your existing fire panels, nurse call and paging encoders connect using the same protocols, including TAP, SNPP, SMTP and Xacom UDP. Talk to your Xacom account manager about timing and what the move involves.