Too many systems in the practice: integration problems and when one connected system makes sense
By AllesHealth GmbH ·
The appointment is in the booking tool, the history is in the record, the invoice is in the billing program, the patient's question arrived by email, the video link came from yet another service, and the new patient app has its own login. Each tool works on its own. Together they mean that your MPA types the same address three times, the doctor switches windows during the consultation, and nobody is quite sure which system holds the latest version. This article looks at what too many separate systems cost a practice, what interoperability means in Switzerland, and when one connected practice system makes more sense than adding yet another integration.
Why "too many systems" is a real problem in Swiss practices
The Swiss eHealth Barometer 2026 surveyed 1,187 health professionals and other healthcare actors (doctors, hospital IT managers and cantonal representatives) about digitalisation in Swiss healthcare [1]. For many practices the question is no longer whether to work digitally, but whether their digital tools work together.
According to the FMH, health professionals expect functioning infrastructure [2].
At the same time, pressure on practices is rising. The Swiss Health Observatory's 2026 report on primary care doctors found that the share of highly stressed primary care doctors has increased steadily since 2015, and that more and more of them work in group practices rather than single-handed practices [3]. In a group practice, every additional system multiplies: more accounts, more training, more places where information can get lost.
The hidden costs of disconnected tools
No Swiss study puts a franc figure on running separate tools in a practice, so we will not invent one. But the costs are easy to recognise in daily work:
- Double entry. Patient details, insurance information and appointments are typed into several systems. Every re-typing takes time and is a chance for a typo.
- Errors at the hand-over points. When the appointment, the record and the invoice live in different places, a service can be documented but not billed, or billed with the wrong date.
- Search time. "Is the lab report in the record or still in the inbox?" Staff spend time looking for information instead of using it.
- Logins and passwords. Each tool means another account to create, secure and close when someone leaves. More accounts also mean more points of attack.
- Inconsistent patient communication. Reminders from one tool, messages from another, video links from a third: patients do not know which channel is official.
- Training and dependency. New MPAs need to learn several systems, and knowledge often sits with one person who "knows how the export works".
- Several contracts and data processors. Each additional provider that handles patient data means another contract to manage and another set of data protection questions to clarify.
Interoperability basics in Switzerland
HL7 FHIR is the international standard for exchanging health data between systems. Switzerland is building on it: according to the Federal Office of Public Health (FOPH), the future electronic health record (E-GD) is to be based on HL7 FHIR, so that structured health data can increasingly be recorded in addition to PDF documents. For health professionals, the FOPH prefers a deep integration of practice systems via standardised interfaces, and practice software that is connected to the EPD via HL7 FHIR interfaces should be able to switch to the E-GD with little effort [4]. Our guide What is HL7 FHIR? explains the standard and the Swiss CH Core profiles in plain language.
SNOMED CT is a clinical terminology: it gives diagnoses, findings and procedures unambiguous codes. eHealth Suisse acts as the National Release Center for SNOMED CT in Switzerland [6]. See SNOMED CT explained.
EPD and E-GD. The electronic patient record (EPD) is to be replaced by the electronic health record (E-GD). The Federal Council adopted the new Federal Act on the Electronic Health Record (EGDG) and its dispatch in November 2025; as of November 2026, the law is still before Parliament and not in force [5]. Details are in our article on the Swiss electronic patient record.
What this means for you: standards make exchange possible, but they do not remove the need for each connection to be built, tested and maintained. An interface between two products is a project, not a checkbox.
Integrated system or many integrations?
There is no single right answer. These rules of thumb help:
One connected system makes sense when
- your core daily work (appointments, records, prescriptions, billing, patient communication) runs in different tools that do not share data;
- your team keeps typing the same information twice;
- you are growing into a group practice and want one set of accounts, rights and processes;
- you have no IT staff to maintain interfaces.
Separate tools with integrations make sense when
- a specialised system is essential for your discipline and no integrated product covers it well;
- the existing integration is stable, standards-based (for example FHIR) and maintained by the vendors;
- the external partner (laboratory, hospital, other providers) only offers a specific interface.
In practice, most practices end up with a connected core system plus a small number of well-maintained external connections, for example to laboratories and referral partners.
Checklist: how to reduce system sprawl in your practice
- Map your tools. List every system the team uses, what it is for, who uses it and what it costs.
- Map the double entries. For one week, note every time information is typed into a second system.
- Find the hand-over errors. Look at missed invoices, wrong appointment data, lost messages. Where do they occur?
- Define the core. Decide which functions must live in one system: usually record, appointments, prescriptions, billing and patient communication.
- Check the standards. Ask vendors which FHIR version and profiles they support and whether they use SNOMED CT coding.
- Ask about data export. Can you get all your data out in a usable format if you change provider?
- Check hosting and processors. Where is data stored, and which subcontractors are involved?
- Plan the migration. Agree on what data moves, a cut-over date and a period of parallel checks.
- Train the team once, properly. Fewer systems mean less training, but the first weeks need time.
- Measure after three months. Compare logins, double entries and errors with your starting point.
How to choose the best practice management software in 2026
Neutral criteria for an integrated system:
- Coverage of your daily core: records, appointments, e-prescriptions, billing with Swiss tariffs, patient communication and video in one place.
- One patient record, one login: the same data visible to doctors and MPAs with role-based rights.
- Open standards: HL7 FHIR and SNOMED CT rather than closed formats.
- Honest integration statements: the vendor states clearly which external connections exist and what each requires from the other party.
- Swiss hosting and clear processor contracts.
- Easy trial: you can test with your own workflows before committing.
How AllesHealth Connect helps
AllesHealth Connect is one connected system for GP and multi-doctor outpatient practices, designed in Switzerland. It covers:
- Electronic health record (EHR) with structured data, built on HL7 FHIR and supporting SNOMED CT coding;
- Appointment management;
- E-prescriptions;
- Video consultations;
- Billing and invoicing, with Swiss tariffs and electronic billing to health insurers;
- Patient Companion, the app for your patients in your practice's branding: records library, online booking, video consultations, medication reminders, messages with the team and family accounts, on iPhone and Android.
What needs a connection to someone else: on the Premium plan, lab integration means results arrive electronically only where the lab is integrated, and patient referrals in and out require an API-based integration with the other provider. AllesHealth Connect does not replace every specialised system you may use; it brings the daily core of the practice into one place. Data of Swiss practices is hosted in Switzerland (Zurich).
For doctors: one patient record during the consultation, with appointments, prescriptions, previous video consultations and invoices in the same place, and no window switching to find the latest information.
For nurses and MPAs: patient details entered once, appointments that flow into documentation and billing, patient messages in the same system, and one login instead of several. On the Premium plan, AI agents support booking and reminders.
For patients: one app for booking, messages, video consultations, documents and medication reminders, instead of different links and accounts.
A connected system also makes AI documentation more useful, because notes land directly in the right record. Read our practical guide to the AI note taker for doctors.
Try AllesHealth Connect free for 60 days – no setup needed, no credit card: start free or book a demo. See the plans on our pricing page.
#PracticeManagement #Interoperability #HL7FHIR #DigitalHealth #GPPractice #ClinicManagement #EHR #Switzerland
Sources
- Swiss eHealth-Barometer 2026: Bericht zur Befragung der Gesundheitsfachpersonen und Akteur:innen des Gesundheitswesens, gfs.bern (published by the Federal Office of Public Health, FOPH) (2026)
- Swiss eHealth-Barometer 2026 (press release, 8 April 2026), FMH Swiss Medical Association (2026)
- Ärztinnen und Ärzte in der Grundversorgung – Situation in der Schweiz und im internationalen Vergleich (Obsan Bericht 01/2026), Swiss Health Observatory (Obsan) (2026)
- Faktenblatt: Elektronisches Gesundheitsdossier – Technische Aspekte (29. Juli 2026), Federal Office of Public Health (FOPH) (2026)
- EGDG: Das künftige Gesetz zum E-GD, Federal Office of Public Health (FOPH) (2026)
- Semantische Standards, eHealth Suisse