For most French medical practices, a hosted PBX (also called a cloud PBX) is the simpler choice: the provider runs the equipment, the practice pays a recurring fee, and staff can answer calls from any location. An on-premise PBX remains relevant for sites with strong sovereignty constraints, very high call volumes or a need to keep internal calls running during an internet outage. Whichever system is chosen, the real test in a medical setting is whether patient calls are answered, confidentiality is protected and appointments reach the agenda.
Key Takeaways
- A hosted PBX is run by the provider and billed as a subscription. An on-premise PBX (IPBX) is installed at the practice, which is responsible for its maintenance.
- Hosted systems generally lower the initial investment and make remote work and multi-site operation easier. On-premise systems offer more control but require more management.
- Cloud telephony depends on internet connectivity, so continuity needs redundancy and call rerouting, whatever the vendor promises.
- Patient confidentiality, RGPD compliance and, where health data is hosted, HDS certification belong on the checklist before any contract is signed.
- A PBX only routes calls. Answering them, qualifying them and booking appointments is a separate task that can be externalized to a medical tele-secretary.
Table of Contents
- What the Two Terms Mean
- Cost: Capital Expense or Monthly Package
- Reliability, Control and Outages
- Remote Work and Multi-Site Practices
- Confidentiality, RGPD and HDS
- Migrating a Practice’s Phone System
- Side-by-Side Comparison
- Which Model Fits Which Practice
- The Perspective of ClicFone
- Externalizing Calls Whatever the PBX
- FAQ
- Sources
What the Two Terms Mean
The vocabulary is a frequent source of confusion, so it helps to fix the definitions first.
A hosted PBX is a business phone system in which the provider houses the infrastructure and manages hardware and software remotely, while users reach the features over the internet. An on-premise PBX, by contrast, involves installing and maintaining the equipment, such as servers, directly at the business location.
French public guidance uses slightly different words for the same split. The telecom regulator ARCEP, in its guide for small and medium businesses, describes Centrex as an externalized telephone exchange hosted by the supplier and shared among clients, while an IPBX is an internalized private exchange that uses IP and needs to be installed and maintained. In everyday French vendor language, “standard cloud” corresponds to the hosted model and “IPBX” to the on-premise one.
Hosted, Cloud and VoIP: Same Thing?
Hosted PBX and cloud PBX are interchangeable terms for the same type of service. VoIP is different: it is the underlying technology that carries voice over the internet. An on-premise IPBX also uses IP, so “VoIP” alone does not tell a practice where its phone system actually lives. The useful question is simply who owns and maintains the exchange.
Is a PBX Outdated?
The equipment is not outdated, but the question has moved. Market analysts covering France note that pure IP-PBX and hybrid platforms still dominate new installations, while cloud-hosted and managed solutions are the fastest-growing subsegment because they simplify management and reduce capital expenditure. Both models are therefore current. What matters is the fit with the practice.
Cost: Capital Expense or Monthly Package
The cost structures differ in kind more than in size.
- Hosted PBX: low initial cost, with a monthly charge per user. The central is not bought, and its cost is included in the package.
- On-premise PBX: a high initial investment, then variable maintenance and support costs. ARCEP notes that an IPBX central can be bought and amortized, or rented.
On-premise systems also require ongoing maintenance and updates, managed internally or under a maintenance contract. For a solo practitioner or a three-doctor practice, that internal burden is rarely a task anyone wants. For a large clinic with an IT team, it may be routine.
A fair comparison over three to five years therefore includes more than the purchase price: installation, maintenance contract, replacement of hardware at the end of its life, the cost of the internet connection, and the time spent by staff on administration. Figures vary widely between suppliers and sites, so quotes from several providers on the same user count and the same features are the only reliable basis.
Reliability, Control and Outages
Reliability is where the two models trade different risks.
A hosted PBX offers easier scalability and remote access but depends entirely on internet availability. An on-premise PBX provides more control and potential offline autonomy, at the cost of more complex management, updates and maintenance. During an internet outage, an on-premise exchange can keep internal calls running, while external calls need a correctly configured backup SIP link.
The practical reading for a medical office:
- Cloud telephony needs a continuity plan. Cloud telephony depends on internet connectivity, so continuity should be designed with redundancy and rerouting: a second connection, such as a mobile data backup, and a rule to forward calls to a mobile or to an external answering service if the line fails.
- On-premise is not automatically safe. Internal service during an outage depends on the design, and external calls still need a working link to the operator.
- Control is real but costs effort. On-premise PBX may suit organizations with strong sovereignty constraints or very high call volumes. Most practices do not fit that profile.
In medicine, a failure to pick up has a specific consequence: a patient with an urgent problem who cannot reach anyone. For that reason, the design of overflow and out-of-hours handling deserves as much attention as the choice of PBX itself. Ways to limit the problem are covered in the guide on how to reduce missed calls at a doctor’s office.
Remote Work and Multi-Site Practices
More practices now share secretarial work between sites, or want a person working from home to take calls. The two models handle this unequally.
Cloud systems natively support remote work and multi-site operations, whereas on-premise systems need configuration, and inter-site connections are more complex. A cloud IPBX offers native softphone mobility, while on-premise teleworking is possible but requires a VPN or advanced configuration.
For a maison de santé with several professionals, the consequences are concrete:
- one number can ring in several consultation rooms, then fall back to a shared queue;
- a new professional can be added to the phone system without a technician visit;
- calls can be answered from a different location when a site is closed or short-staffed.
A single-site practice with a stable team and a physical reception desk has less to gain from these features.
Confidentiality, RGPD and HDS
A phone system in a medical practice carries sensitive information: names, symptoms, reasons for consultation, sometimes test results. The choice of PBX is therefore also a data-protection decision.
French healthcare practices should check that their telephony platform protects patient confidentiality and complies with the RGPD. In practice, that means asking the provider about:
- where call data, voicemail and recordings are stored, and in which country;
- who can access them, and how access is logged;
- the contract terms between the practice and the provider as data processor;
- how long recordings and call logs are kept, and how they are deleted.
The detailed rules are covered in the guides on patient call confidentiality, GDPR steps for medical calls and call log retention.
Call Recording
Recording deserves its own attention. The CNIL has sanctioned a company for systematically recording all calls for training, evaluation and possible disputes, noting that occasional, random recordings can suffice for staff training. A PBX that records everything by default is therefore a configuration to review, not a feature to accept as delivered. For the specific French rules on medical recording, see the guides on encrypted call recording in healthcare and call recording with GDPR and Article 28.
Where HDS Applies
HDS certification applies to providers that host personal health data on digital media for a data controller or a patient. Whether a given telephony service falls within that scope depends on what it stores and for whom, so the question belongs in the vendor discussion, in writing. The article on HDS certification and medical phone calls explains what it covers.
Migrating a Practice’s Phone System
Changing system is mostly a question of timing and of the phone number, which patients know by heart.
Portability means changing operators while keeping the same number. At least one major French operator states in its professional terms that service setup with portability takes at least four weeks. Other operators may differ, but a lead time of several weeks is a sensible planning assumption, which affects the date at which the old system can be switched off.
A short migration checklist:
- Inventory the numbers. Main line, direct lines, fax and any special numbers.
- Request portability early, and keep the old contract running until the transfer is confirmed.
- Plan the cutover for a quiet period, not the week of the flu season peak. The article on secretary access for CalenDoc discusses call volume planning in busy months.
- Test internal and external calls, voicemail, forwarding and the out-of-hours message before the switch.
- Define the fallback. Which number receives calls if the internet fails?
- Brief the team, and tell patients about any change in how calls are answered.
Side-by-Side Comparison
| Criterion | Hosted (cloud) PBX | On-premise PBX (IPBX) |
|---|---|---|
| Where the exchange runs | Provider’s infrastructure | Equipment at the practice |
| Initial cost | Low, no central to buy | High investment, or rental |
| Ongoing cost | Monthly fee per user | Maintenance, support and updates, variable |
| Maintenance | Handled by the provider | Internal or under a maintenance contract |
| Internet outage | Depends entirely on connectivity | Internal calls can continue, external calls need a backup link |
| Remote work | Native softphone mobility | Possible with VPN or advanced setup |
| Multi-site | Natively supported | More complex inter-site links |
| Best suited to | Small and medium practices, shared sites, mobile teams | Sovereignty constraints, very high call volumes, in-house IT |
Which Model Fits Which Practice
- Solo practitioner or small practice: a hosted PBX is generally the better match, with no equipment to maintain and a predictable monthly cost.
- Maison de santé with several professionals: hosted usually fits, thanks to multi-user routing and easy additions. The data-protection questions above should be settled for the shared number.
- Large clinic with in-house IT and heavy call volumes: on-premise can be justified, provided continuity and maintenance are properly resourced.
- Practices with limited secretarial time: the system matters less than who answers. A PBX distributes calls, but it does not qualify them or book the appointment.
The Perspective of ClicFone
After more than 15 years in the medical sector, we see the same pattern in practices of every size: the choice between hosted and on-premise telephony is important, but it is rarely what decides whether patients feel well received.
A PBX, whatever its model, is a routing tool. It sends a call to a person. When that person is busy with a patient, away from the desk or off duty, the call goes unanswered, and the technology has no say in what happens next. That is why we consider the telephone a “filtre intelligent”: the first contact must be qualified, urgent requests identified and appointments placed correctly in the agenda.
Our service is designed around this. Qualified human tele-secretaries, trained specifically for healthcare, answer on behalf of the practice, supported by AI for round-the-clock availability. We synchronize with the calendar platforms that practices already use, such as Doctolib, LibreRDV, Maiia and CalenDoc, and we work within medical confidentiality standards. Our offers are flexible, with no commitment.
A practice can therefore keep its existing PBX, or move to a hosted one, and externalize the answering itself. The two decisions are independent, and treating them separately usually produces a calmer and more robust organization.
Rudolph Thierry
Externalizing Calls Whatever the PBX
A phone system decides how calls arrive. A tele-secretary decides what happens to them. ClicFone provides remote medical tele-secretary services for doctors, specialists, paramedical professionals and health center teams: call handling, appointment scheduling synchronized with the main healthcare calendar platforms, and coordination of patient calls.
Two related topics may help in framing the organization. Safe handling of urgent requests is described in the pages on medical phone triage and urgent appointment triage, and the booking rules a clinic should set are presented in the guide to medical scheduling rules. Transfers between professionals also have their own requirements, covered in the article on secure call transfer.
FAQ
What does hosted PBX mean?
A hosted PBX is a business phone system whose equipment and software are run by a provider, with users accessing the features over the internet. The practice typically pays a recurring fee per user instead of buying a central. It is also called a cloud PBX.
Is hosted PBX the same as VoIP?
No. VoIP is the technology that carries voice over the internet, while a hosted PBX is a service model in which the provider runs the exchange. An on-premise IPBX can also use VoIP, so the two terms describe different things.
Is cloud PBX safe for patient calls?
It can be, if the provider meets the practice’s confidentiality and RGPD requirements, and if the contract states where data is stored and who can access it. Where health data is hosted, HDS certification may apply. These points should be confirmed in writing before signing.
What happens to calls if the internet goes down?
A cloud PBX depends on connectivity, so a backup connection and a rerouting rule, for example to a mobile phone or an external answering service, should be set up in advance. An on-premise system can keep internal calls running, but external calls still need a configured backup link.
Can a practice keep its phone number when changing system?
Yes, through number portability, which lets a practice change operators while keeping its number. Setup with portability can take several weeks, at least four weeks in the terms of one operator, so the request should start early.
Sources
- ARCEP, practical telecom guide for small and medium businesses (February 2017)
- What is hosted PBX, definition and on-premise contrast
- Hosted PBX and cloud PBX terminology
- IndexBox, PBX phone system market in France
- IPBX cloud vs on-premise, cost structure
- Standard cloud ou IPBX: how to choose
- Téléphonie IP en entreprise, fonctionnement et déploiement
- Standard téléphonique: cloud ou on-premise?
- IPBX cloud vs IPBX on-premise, SME comparison
- Standard téléphonique médical, guide for clinics
- CNIL, nine new sanctions under the simplified procedure
- HDS certification reference framework, version 2 (April 2024)
- Operator professional terms, number portability and setup time
Recommended
- Best Foneo.fr Alternatives for Medical Practices in 2026
- Medical Phone Answering for Private Practices: Clicfone
