management

Why choose an independent, non-manufacturer integrator for your nurse call system?

Comparative analysis of the manufacturer-integrator vs independent integrator models for nurse call in care homes: lock-in, total cost, scalability.

Published on · Healthcall

Why choose an independent, non-manufacturer integrator for your nurse call system?

When you have to renew the nurse call system of your care home, the choice is too often reduced to comparing technical data sheets or deciding between two quotes. Yet the most structuring question is not “which button brand?” or “how many shared smartphones per duty station or DECT handsets?”, but rather which supplier model you are committing to for the next ten to fifteen years. In practice, the Belgian and European market sets two approaches against each other: the manufacturer-integrator, which designs the hardware and publishes the software as a coherent whole, and the independent, non-manufacturer integrator, which publishes an open software layer and connects to third-party hardware chosen case by case.

This is not an ideological debate. Both models have real merits and meet different needs. The aim of this article is not to disqualify one in favour of the other, but to give you an objective reading grid so you can arbitrate with full awareness, depending on the size of your facility, your budget constraints, your evolution requirements and your tolerance for supplier dependency. You will find an analysis of total cost of ownership, decision criteria, and a series of concrete questions to put to your next candidates.

The two market models

The manufacturer-integrator

The manufacturer-integrator designs the hardware itself (call buttons, pull cords, detectors, corridor signal lamps, controllers, sometimes professional smartphones or DECT handsets) and publishes the supervision software that orchestrates it. Players such as Televic, Ascom or Ackermann are historical European representatives. Their value proposition is vertical integration: a single supplier, a coherent hardware catalogue, unified after-sales support, engineering tested on thousands of installations, often in acute hospital settings.

The independent, non-manufacturer integrator

The independent integrator does not manufacture hardware. It publishes a software platform (most often SaaS or on-premise) capable of communicating with equipment from several manufacturers via standard protocols or open connectors. Its business is the intelligence layer: event collection, notification workflows, escalation, reporting, carer interface. Hardware is selected per project, according to building constraints and client budget.

Comparative summary table

CriterionManufacturer-integratorIndependent, non-manufacturer integrator
ScopeHardware + softwareSoftware + orchestration
Hardware catalogueProprietary, coherentMulti-manufacturer, by choice
ProtocolsOften proprietaryOpen and standard
Historical targetAcute hospital, large groupCare home, MRS, specialised clinics
Deployment timeInfrastructure projectSoftware layer on existing possible
Supplier dependencyHigh (hardware + software)Moderate (software only)
Product evolutionLong industrial cycleShort software cycle
MigrationFull replacementSoftware-only replacement possible

No line in this table is a flaw in itself. A long industrial cycle means proven mechanical reliability; strong vertical integration means a single after-sales channel and an identified project lead. Conversely, an open software layer means you must manage two contracts (hardware and software) rather than one. The right model depends on your context.

What the manufacturer-integrator model brings

It is worth acknowledging without reservation the real strengths of the manufacturer-integrator approach, especially in certain contexts.

Stability of a large industrial group. The historical manufacturers have invested in hardware R&D for several decades. Their equipment is tested in demanding conditions, their certifications cover the most stringent hospital standards, and their industrial capacity absorbs market shocks. For a decision-maker, this is a signal of longevity that few independent software publishers can match in balance-sheet terms.

Integrated and tested hardware catalogue. The button, the controller, the signal lamp, the carer terminal (smartphone or DECT) and the server are designed to work together. Mechanical, electrical and software interfaces are validated in-house. You avoid subtle incompatibilities between equipment from different suppliers, which can cost integration time and technician visits.

Unified after-sales. A single number to call, a single contact to diagnose an incident end to end. In a facility with limited technical direction, this is a valuable operational comfort. Maintenance contracts cover hardware and software together, which avoids responsibility being passed back and forth.

Heavy hospital references. The historical manufacturers equip university hospitals and clinics with several hundred acute-care beds. For a group managing both hospital and care home activities, standardising around a single supplier simplifies IT and biomedical governance.

Deep building integration. In new-build projects where building management, access control and nurse call are designed together from the concept phase, a manufacturer-integrator capable of providing the entire low-voltage chain can simplify lot coordination.

These elements are real and should not be minimised. The question is not whether they exist, but whether they are decisive for your care home.

What the independent, non-manufacturer integrator brings

The independent model, for its part, addresses a series of needs that vertical integration has more difficulty satisfying.

Open architecture. An independent platform is designed to communicate with several manufacturers of call hardware, telephony, motion sensors, wandering prevention systems and even electronic patient records. You plug in what already exists in the building; you do not discard hardware that is still amortisable. This openness is often backed by documented APIs and standard protocols.

Hardware chosen to fit the project. Each care home has its constraints: an older building with limited cabling, a new-build site with end-to-end IP, a tight budget requiring wireless radio, or conversely a requirement for wired reliability. An independent integrator can propose economical hardware where that is sufficient, and premium hardware where it is needed, without being captive to a single catalogue.

No hardware lock-in. If you change your mind about the software platform in five years, you only replace the software layer. Your buttons, signal lamps and detectors stay in place if the new software can read them. By contrast, in a proprietary integrated model, changing suppliers often means replacing everything.

Product agility. A pure software publisher typically releases several updates a year, sometimes each quarter, integrating field feedback, regulatory developments and new functions (reporting, mobility, third-party integrations). An industrial player that also designs hardware is bound by much longer validation cycles and synchronises software and hardware.

Pricing transparency. Independent models more readily publish public or semi-public price grids, per licence, per user or per button. Integrated models often rely on project quotes where the hardware, software, engineering and maintenance portions are hardly legible individually.

Decision-making proximity. An independent publisher of human size can add a request from your facility to its roadmap within weeks. An evolution request addressed to a large industrial player passes through a global product hierarchy and rarely succeeds, unless it represents a significant volume.

Here too, these advantages are not universal. They weigh more heavily when your facility is medium-sized, your budget is constrained, and you expect a supplier to evolve at the pace of your needs.

The true total cost of ownership over 10 years

The comparison between two nurse call offers is too often reduced to initial CAPEX. This is the wrong angle. A nurse call system lives ten to fifteen years. The decisions taken today commit a decade of spending, evolution and dependency. Here is the reasoning grid to apply, without making up figures about competitors but with the right variables.

1. Initial hardware. Call buttons, pull cords, detectors, floor controllers, corridor signal lamps, professional smartphones or DECT, optional cabling, local server where applicable. In a manufacturer-integrator model, this line is generally the most visible and the most expensive; in an independent model, it can be optimised by choosing adapted third-party hardware.

2. Software licences. Perpetual licence with annual maintenance, or SaaS subscription. The SaaS subscription smooths the cost but adds a recurring expense to budget. The perpetual licence reduces OPEX but concentrates the initial investment and exposes you to upgrade fees at end of life.

3. Deployment and engineering. Person-days of configuration, staff training, go-live support, possible integration with electronic patient records or access control. Examine this line by line, because some models include this phase in the licence while others invoice it separately.

4. Annual maintenance. Software (patches, updates, supervision), hardware (preventive replacement, interventions) and contractual (SLA, on-call). The manufacturer-integrator model often offers a unified contract that is simpler to manage; the independent model separates software maintenance and hardware maintenance, potentially with more visibility on each item.

5. Functional evolutions. New modules (advanced reporting, mobility, EPR connections, round management), scope extensions (new wing, new site), additional features. What is the marginal cost of adding ten buttons? Twenty beds? A reporting module? This question is often avoided during the sales phase and weighs heavily over ten years.

6. Major migrations. Partial hardware renewal, version migration, server change, switch to SaaS, compliance with new regulation. In an integrated model, a hardware migration often entails a software migration. In an open model, they can be dissociated.

7. Exit cost. What happens if you change supplier in year 8? In a proprietary model, it is a full replacement. In an open model, it is potentially a software-only migration. This line, rarely calculated in advance, is nevertheless the most revealing of real dependency.

Apply these seven items to each candidate on a ten-year horizon. You obtain a comparable TCO, much more honest than the purchase price displayed on the first page of the quote. It is not always the independent model that comes out cheapest, but it is almost always the most legible.

When the manufacturer-integrator model makes sense

Let us be clear: some contexts naturally call for a manufacturer-integrator approach, and it is more honest to say so.

  • Acute hospital or university hospital. The demands of criticality, biomedical integration and event volume justify a vertical integrator mastering the entire chain.
  • International multi-site group. If you manage several dozen facilities across several countries, standardising around a global supplier capable of providing support and spare parts everywhere has strong operational value.
  • New-build project with building integration requirements. When nurse call is designed at the same time as building management, telephony, access control and fire detection, a single supplier on the low-voltage lot simplifies coordination.
  • Interoperability constraints with high-criticality biomedical equipment. Some integrations with hospital monitors or telemetry systems are more mature with the historical manufacturers.
  • Non-negotiable requirement for a unified contract. If your procurement policy refuses to multiply suppliers on the same functional lot, the integrated model mechanically matches the demand.

In these situations, the effort to seek out an independent model is not always worthwhile. The manufacturer-integrator remains a rational choice.

When the independent model makes sense

Conversely, in the majority of Belgian care homes from 30 to 150 beds, the equation tips clearly towards an independent, non-manufacturer integrator.

  • Medium size. You do not have the volume that would justify absorbing the cost of a platform sized for acute hospital care, but you have the same reliability requirements for your residents.
  • Constrained and transparent budget. Private and public care homes alike operate with tight budgets. A clear, predictable grid, with a legible cost per button or per resident, is a direct advantage in the decision.
  • Need for hardware flexibility. You have existing cabling, still-functional buttons, a recent radio installation to make the most of, or conversely you want to go with economical wireless. An open model absorbs these constraints without forcing you to replace everything.
  • Rapid product evolution. You expect your tool to progress each year: new reporting for inspections, better mobile experience for carers, EPR integration, strengthened GDPR functions. A pure software publisher delivers faster.
  • Refusal of lock-in. You want to be able to change software supplier in five years without discarding hardware. You want to be able to negotiate maintenance in ten years without being captive.
  • Proximity and responsiveness. You want to speak to decision-makers, not to an international call centre. You want a reasonable request to be handled in weeks, not years.

These criteria precisely define the segment where an independent integrator brings the most value.

Healthcall’s position

Healthcall positions itself unambiguously as an independent, non-manufacturer integrator. The publisher, Groovit SRL, is based in Frasnes-lez-Anvaing and has been operating since 2017 — eight years of continuous presence on the nurse call market for care homes. The platform equips around twenty facilities today (21 at the time of writing), representing approximately 1,250 residents supported, in structures from 30 to 150 beds. Across these eight years, only one client has left the platform.

The business model is simple: Groovit is self-funded, with no investment funds on the capital. According to its directors, “the only shareholder is customer satisfaction.” This structure favours stability and proximity over growth at any price.

On the technical side, Healthcall rests on Belgian premium host, an open application architecture, triple database recording for data resilience, and native GDPR compliance. The architecture depends on no proprietary hardware: facilities retain the choice of their call hardware. The platform receives four major updates per year, deployed at no additional cost. Pricing starts at 50 € excl. VAT per button, on a public grid.

These elements do not constitute a demonstration of intrinsic superiority; they illustrate the concrete implementation of a coherent independent model on a care home target.

Questions to ask your suppliers

Here is a checklist you can use as-is in the selection phase, whatever the supplier family you consult. The aim is not to trap, but to make visible what too often remains implicit.

  1. What is the total cost of ownership over 10 years, all items included, for our precise scope?
  2. What share of your solution is proprietary hardware and what share is software? What happens if we wish to replace one without the other?
  3. On which protocols does your system communicate? Are they standard, documented, accessible to a third party?
  4. Which third-party integrations exist natively (EPR, access control, telephony, sensors) and at what cost?
  5. How many major updates do you publish per year? Are they included in maintenance or invoiced separately?
  6. Can you provide a clear reversibility contract, with technical and financial exit conditions?
  7. What is the marginal cost of adding ten buttons, a floor, a new wing after deployment?
  8. Where is the data hosted? How is GDPR compliance documented?
  9. What is the financial health of the publisher? Capital, shareholding, seniority, number of active clients, attrition rate?
  10. Can we visit two clients of comparable size to ours, deployed for more than three years?

The answers to these ten questions, more than the sales brochures, will reveal the true nature of the commitment you are about to make.

Going further

The choice of a nurse call system is a choice of model before being a choice of product. The two main families, manufacturer-integrator and independent, non-manufacturer integrator, address different needs and each have their legitimacy. What matters is to decide with full awareness, on the basis of total cost of ownership, the level of dependency accepted and the speed of evolution expected.

If your care home fits the 30-150 beds profile, if you value economic transparency, open architecture and a close supplier relationship, a conversation with Healthcall can bring you useful points of comparison. We invite you to contact us to obtain a detailed price grid or a demonstration appointment tailored to your facility.

Let's discuss your project

A demonstration tailored to your care home, without commitment.