Add reporting to the nurse call you already have — without replacing it
Peninsula Smart Care's reporting hub sits alongside your existing system and reports every call it raises — nurse call, staff assist, emergency, duress, bed exit sensors, fire and BMS contacts, RTLS — with care suppression and a full audit trail, networked room inputs and outputs, live dashboards and ward displays. Your certified systems keep doing their job, untouched.
One set of reports, every system
What is nurse call integration?
Nurse call integration connects an existing nurse call system to modern monitoring, dashboards and reporting — adding new capability around the certified system a facility already relies on, instead of ripping it out and starting again.
Most Australian aged care and health facilities run nurse call systems that still work perfectly well — but were designed before audit trails, falls-prevention sensors and live reporting were expected. Replacement is disruptive and expensive.
Integration keeps what works and adds what's missing: every call reported through the hub with the four standard priorities — Nurse Call, Staff Assist, Emergency and Duress — visible on dashboards, logged with names and times, and exportable for quality review.
The hub's inputs are universal. Bed exit sensors and sensor mats, fire alarm interface signals, building management (BMS) contacts, RTLS events, calls arriving over a SIP trunk from your phone system and HL7 messages from your clinical systems all ride the same hub. So do its outputs: ward dashboards, corridor displays, Spectralink handsets, IP speakers, SIP extensions, HL7 events to your EMR, SMS, email, or any system of yours through customisable outputs.
What the platform adds
Care suppression with audit
Staff pause a bed's monitoring alerts during personal care — for a set time or until re-armed — from any ward device. Timed suppressions re-arm themselves automatically, and every action is logged with who, when and why. See it in action on our bed exit sensor page.
Networked room inputs & outputs
Industrial IP modules connect attend buttons, bed exit sensors, sensor mat contacts and door switches to the platform — programmed from a browser, not proprietary site tools. The same universal inputs carry fire alarm interface, BMS and plant signals, and outputs can drive door lamps that follow suppression state automatically.
Dashboards, handsets & alerts
Ward staff see every bed's state at a glance; administrators get system health, module supervision and one-click audit export. Calls can also be delivered where staff already are — Spectralink and DECT handsets, SMS and email. The hub speaks SIP in both directions: it can announce overhead through IP speakers, ring or page SIP extensions on the phone system your site already runs, and accept calls over a SIP trunk from that phone system to make an announcement — with customisable outputs to feed anything else.
HL7 to your clinical systems
The hub speaks HL7, so it does not sit in a silo beside the systems that already hold your patient data. Take an ADT feed in and every bed carries the right patient context automatically, without anyone retyping a name into a nurse call panel. Publish call and response events back out, and the record your clinical team works from reflects what actually happened on the ward — the same events that drive the dashboards and the audit trail, in the format your EMR or patient administration system already accepts.
Ward displays & zoning
Corridor screens and nurse-base displays run off the same backbone. A display announces itself to the hub when it is plugged in; you name it and assign it to one ward or several from the admin panel, so each screen only shows the calls that belong to it. Commissioning happens once from the office rather than at every screen, and a display that drops off the network is flagged rather than quietly going dark.
Falls-prevention ready
The platform is built to carry input from modern falls-prevention sensing — bed exit sensors and sensor mats raising native calls with the right priority, and suppression-aware logic so alerts pause properly during care.
Works with what you have
We service and integrate the systems already installed across Melbourne — including Sedco and JCT — connecting by isolated, listen-only serial or through network device servers many sites already run. Running something else? See who supplies the high level interface.
Remote health monitoring
The hub watches itself: power integrity, temperature, service status and module supervision, all visible remotely. Problems are flagged before they become outages — often before anyone on site notices. For larger sites, the head end can be deployed as a redundant dual-hub pair with automatic failover.
How it works
The platform is an overlay. A compact hub installed alongside your nurse call head-end listens to the system's output and carries every event onto a modern, secure messaging backbone. Dashboards, displays, room devices and reports all connect to that backbone — each one added without touching the others, so capability grows site by site.
Two ways onto a site
Direct serial connection. The hub's galvanically isolated interface taps the nurse call uplink in listen-only mode — electrically separated from clinical equipment, adding no load and making no transmissions on the bus.
Network integration. Many facilities already stream nurse call data through industrial serial-to-network device servers. There, the hub is simply added as another network destination — a configuration change, with nothing physically connected to the nurse call system at all.
No rip-and-replace. Your certified nurse call system keeps operating exactly as installed and maintained. Integration adds capability around it — which means no decommissioning risk, no retraining on a new call system, and a fraction of the cost of replacement.
Honest positioning: the existing nurse call system remains in charge of its life-safety function — and fire alarm systems remain entirely governed by their own standards and certification. The platform observes, records, displays and extends — it does not replace any certified call or alarm path, and we design every integration on that principle.
Beyond monitoring
Because everything speaks the same language on the platform, the pieces reinforce each other: a sensor mat raises a call with the right priority; suppressing that bed during care lights the door lamp; the call reaches the right handset, screen, speaker or inbox; the audit trail records all of it; and the quality manager exports the quarter in one click. This is also the foundation for RTLS and duress workflows as sites grow into them.
Who supplies the high level interface?
It is the question that decides most nurse call tenders, and the one that stalls projects. A high level interface (HLI) is the data connection that lets one system pass calls and events to another as structured messages — carrying the call type, the room, the priority and the time — rather than as a bare contact closure. Without one, a nurse call system can only sound locally. With one, its calls can reach handsets, displays, paging and reporting.
The traditional answer is that the nurse call manufacturer supplies it, as a licensed and chargeable option, on their timeline. That leaves a facility's ability to modernise in the hands of whoever won the original contract — years ago, under a different set of requirements.
Our answer is that the hub is the high level interface. It sits alongside the head-end you already own, reads what that system already produces, and presents every event to dashboards, handsets, speakers, displays and reports in one consistent format — regardless of whose badge is on the panel.
What the hub can read
| ESPA 4.4.4 | The serial paging output most nurse call systems already have commissioned to drive DECT handsets and pagers. Usually the fastest path onto a site, because it is already licensed and running. |
|---|---|
| TAP / IXO | Alternative paging protocols found on older head-ends, serving the same purpose. |
| Serial & network streams | Direct RS-232/RS-485, or over the network where a site already runs serial-to-network device servers. |
| SIP | Calls arriving from an existing phone system over a trunk, and calls delivered back out to extensions. |
| HL7 | Supported in both directions. The hub consumes ADT feeds so beds carry patient context without re-keying, and publishes call and response events back to your EMR or patient administration system. |
| REST & MQTT | Modern web and message-broker APIs, where a newer platform exposes them. |
| Volt-free contacts | The universal fallback where a system exposes nothing else — coarse, but it works everywhere. |
| A licensed HLI | Where a site already holds the manufacturer's own interface, or wants to obtain it, we interface to that directly. |
HL7 both ways
HL7 is worth calling out separately, because it is what stops a nurse call platform becoming another system nobody reconciles. Patient context arrives from the systems that already hold it, and call events go back to the record your clinical team actually works from — over the same hub as everything else.
EMR / PAS
Admissions, transfers, discharges
Integration engine
Mirth, Rhapsody, Cloverleaf or equivalent
PSC hub
Bed context updated, no re-keying
Read from the message: PID-3 patient identifier · PID-5 patient name · PV1-3 assigned location, as ward, room and bed
On the ward: an admit populates the bed, a transfer moves the context with the patient, a discharge clears it — so a screen never shows a name that has left the building
PSC hub
Every call, attend and suppression
Integration engine
Mapped to your site's message profile
EMR / PAS
Clinical record and nurse call record agree
Carried in the message: call type and priority · ward and bed · raised time · attended time · who attended · duration
Why it matters: the same events that drive the dashboards and the audit trail, so response-time reporting comes out of one source rather than two that disagree
Example inbound message — transfer
MSH|^~\&|PAS|SITE|PSC-HUB|WARD|20260815083000||ADT^A02|000042|P|2.4 EVN|A02|20260815083000 PID|1||900123^^^SITE^MR||SAMPLE^PAT|||||||||||| PV1|1|I|ROSE^07A^1^SITE|||||||||||||||
Example message shown with placeholder identifiers. Message types and segment mapping are confirmed against your integration engine during commissioning.
See it reading a bus
The hub does not guess. Every message arriving on the interface is timestamped, decoded into a structured event with its ward, bed and priority, and routed to wherever that event belongs. The same capture view is open to us during commissioning, so an integration is proven on site rather than assumed — and if a system sends something we have not seen before, it shows up here rather than disappearing.
Illustrative capture. Ward and bed identifiers are examples, not live site data.
Read-only by design. However the connection is made, the hub listens. It adds no load to the nurse call bus and makes no transmissions on it, so the certified system's own call path, its warranty and its certification are all untouched.
Tell us what you run
We service Sedco and JCT systems directly, and we build interfaces to other systems on request. If yours is not one we have connected before, tell us what it is — most nurse call head-ends expose at least one of the outputs above, and confirming which is part of the site assessment, before anything is quoted.
Where we'll be straight with you: some manufacturers release interface documentation only under licence or agreement. We won't reverse-engineer a proprietary protocol, and we won't ask you to send us documents you aren't free to share. Where a licensed interface is the right path, we'll say so — and the request usually carries far more weight coming from you as the asset owner than from us.
Security and data handling
The platform is built as an observer. It reads from your existing nurse call system over an isolated, listen-only serial connection or a passive network feed, and never transmits to it. Your certified system remains solely in charge of life-safety calls — nothing we install sits in that path.
Your data stays on your site. Calls, responses and suppression state are stored in a local database on the appliance in your comms room. There is no requirement for clinical event data to leave your network.
No inbound internet access is required. The hub presents no service to the internet and needs no port opened on your firewall.
Access is role-based. Ward staff can view and act on the bed panel. Configuration, integration settings and system administration sit behind a separate administrator role.
Every action is recorded. Suppressions, re-arms, configuration changes and administrative actions are written to an audit log with the actor and timestamp, exportable in full.
Is integration the right move?
A strong fit when…
- Your nurse call system works, but you need audit trails, reporting or falls-prevention capability it can't provide
- Quality and compliance reviews keep asking for call and response data the current system can't export
- You run an EMR or patient administration system and want nurse call events in the clinical record rather than in a separate silo
- You're investing in falls prevention — bed exit sensing, sensor mats — and want it raising native calls, not running as another silo
- Full replacement has been quoted and the disruption or cost doesn't stack up against what you'd gain
Where we'll tell you straight…
- If the underlying system is failing — unreliable calls, unrepairable faults, parts unavailable — integration inherits those problems, and we'll recommend addressing the base system first
- Very small sites may be better served by simpler wireless solutions than a platform
- Integration scope depends on what your system exposes; we confirm the connection method in a site assessment before quoting anything
Why Peninsula Smart Care
- Licensed Melbourne electronic security and healthcare communications integrator
- 20+ years across nurse call, duress, CCTV and access control in healthcare environments
- We service Sedco, JCT and other established nurse call systems every week — integration starts from real system knowledge
- HL7 in both directions, so nurse call data reaches the clinical systems your site already runs
- Everything audited, everything supervised: named-user logs, module health checks, and hubs that report their own condition
- Design, installation, testing and ongoing maintenance from one local team
Nurse call integration FAQs
What is nurse call integration?
Nurse call integration connects an existing nurse call system to modern monitoring, dashboards and reporting. A hub listens to the system's output and reports every call onto a secure platform — adding audit trails, room inputs and outputs, displays and falls-prevention capability without replacing the certified system already installed.
Do we have to replace our existing nurse call system?
No — that's the point. The platform is an overlay: your certified system keeps operating exactly as installed, and remains in charge of its life-safety call function. Integration adds capability around it at a fraction of replacement cost and disruption.
Which nurse call systems can you integrate with?
We work with the systems established across Melbourne aged care and health facilities, including Sedco and JCT, which we service and support directly. Connection is by isolated listen-only serial, or over the network where a site already runs serial-to-network device servers. We confirm the method for your specific system in a site assessment.
Who supplies the high level interface (HLI)?
On most projects the nurse call manufacturer supplies it as a licensed, chargeable option. With Peninsula Smart Care the hub itself acts as the high level interface: it reads the outputs an existing head-end already produces — ESPA 4.4.4 paging, TAP or IXO, serial and network event streams, SIP, HL7, volt-free contacts, or a modern REST or MQTT API — and presents every call to dashboards, handsets, speakers, displays and reporting in one consistent format. Every connection is read-only, so the certified system's call path, warranty and certification are untouched. Where a manufacturer's own licensed HLI is the right path, we'll say so and help you request it.
Does the platform support HL7?
Yes, in both directions. Inbound, the hub consumes an HL7 ADT feed so beds carry the right patient context automatically — admissions, transfers and discharges are reflected without anyone retyping a name into a nurse call panel. Outbound, call and response events are published back to your EMR or patient administration system, so the clinical record and the nurse call record agree. HL7 runs over the same hub as every other input and output, and the message set is confirmed against your integration engine during commissioning.
What are the four call types?
The platform carries the four standard Australian nurse call priorities — Nurse Call, Staff Assist, Emergency and Duress — in ascending priority. Every event keeps its type through dashboards, displays and the audit trail, so an emergency is always treated and recorded as one.
Can it monitor more than nurse call — fire, BMS, RTLS?
Yes. The platform's inputs are universal: fire alarm interface relays, building management (BMS) contacts, plant alarms and RTLS events can all be carried on the same hub, each with its own type and priority, alongside the clinical call types. Certified systems — including fire — always remain in charge of their own alarm functions; the platform adds monitoring, display and audit around them.
How do staff receive calls?
Wherever they already are. Beyond ward dashboards and corridor displays, calls can be delivered to Spectralink and DECT handsets, by SMS and by email — each with its type and priority intact. The hub also speaks SIP, so it can announce overhead through IP speakers or reach SIP extensions on the phone system your site already runs, and customisable outputs let it feed any other system you use.
Can the platform page over IP speakers or our phone system?
Yes, and in both directions. The hub includes a SIP paging capability, so a call or event can trigger an overhead announcement through IP speakers, or ring and page SIP extensions on an existing phone system. It also accepts SIP as an input: your phone system connects to the hub over a SIP trunk, so staff can dial it from a handset or desk phone to make an announcement — which is how sites with an established phone system usually page. Sites running a mix of speaker brands can be brought onto one paging path, and paging can be zoned by ward so an announcement only reaches where it is needed.
Can displays be set up per ward?
Yes. Each display announces itself to the hub and is then named and assigned to one ward or several from the admin panel, so a corridor screen shows only its own ward while a nurse base can watch the whole site. Because zoning is held centrally, a screen can be imaged once and plugged in anywhere, and its assignment survives a reboot.
What does the audit trail record?
Every suppression, re-arm, call event and configuration change, with the person or device responsible and the time. The full history exports to CSV in one click — built for quality reviews and compliance conversations, not just engineering logs.
How does this help with falls prevention?
Falls-prevention sensing — bed exit sensors and sensor mats — connects to the same platform, raising native calls with the right priority. Staff can pause a bed's alerts during personal care with automatic re-arm, so monitoring is never silently left off. See our bed exit sensor and sensor mat pages for the technology itself.
Book a site assessment
Tell us what nurse call system you're running and what you'd like it to do. We'll assess the integration path and give you a straight answer — including if integration isn't the right move for your site.
Thanks — we've got it. We'll be in touch within one business day. Prefer to talk now? Call 03 7504 7011.