Choosing dental practice software in Switzerland: the complete guide

First practice, taking over, starting from scratch or dental hygiene: the criteria that matter in your situation, those that last a whole career, and the questions to ask before signing

Practice management software is the heart of the practice: appointment book, patient files, quotes, invoices, often the link with radiology. You rarely change it, and a bad choice is costly for years. This page compares no products. It sets out the criteria that matter in your situation, the signs of software that will last, and the questions to ask any vendor.

In short: what sets good software apart

• It meets your real needs

  It has been tried out with your own cases, not just compared on a list of features.

• It is designed for Switzerland

  It includes the SSO dental tariff, electronic invoices to insurers, the QR-bill and data protection.

• It is fast and simple

  The whole team quickly finds their way around it, at the chair as well as at reception.

• Its vendor keeps developing it

  New features are regular and dated, the technology is kept up to date and adaptations to Swiss standards arrive on time.

• Support can be reached

  It answers during the practice's working hours, and its cost is known in advance.

• Its ten-year cost is clear

  Prices are in writing, and increases are capped.

• You can leave it

  A full data export is provided in standard formats, at a price set in advance.

• It protects the data

  Personal accounts, two-factor authentication, tested backups and a data processing agreement.

Depending on your situation

The same criteria do not carry the same weight for everyone. Here is what matters most in the most common situations.

You have just graduated and are opening your first practice

Setting up is expensive, cash flow is tight, and you do not yet know how the practice will grow.

• A low, predictable entry cost: compare set-up fees and monthly payments, and avoid multi-year commitments until the business is stable.
• Software that grows with you: adding a practitioner, a hygienist or a second site without changing software, at a price known in advance.
• Quick to learn: you will be learning at the same time as your dental assistant. Training included, online help and videos in your language.
• Little IT to carry: no server to manage, or a server maintained by a provider, and backups included and tested.
• Ways to fill the appointment book: online booking, reminders by text message and e-mail, automatic check-up recalls.
• Your identifiers: the software must handle the numbers needed for invoicing (GLN number, and ZSR number if you invoice insurers, one per canton of activity) and the mandatory information on your documents.

You are taking over an existing practice

Taking over a practice does not automatically transfer everything that goes with the software.

• Patient files do not pass over automatically. Professional secrecy continues to apply: in principle, the buyer only consults a file with the patient's consent. The software must be able to restrict access to the files of patients who have given their consent, and the takeover agreement must settle the matter.
• The licence is not always transferable. Some contracts declare it personal and non-transferable, and maintenance does not pass to the buyer without the vendor's consent: you then need to obtain this consent in writing, buy a new licence, or change software. Read the seller's contract: remaining term, termination date, outstanding invoices (some contracts can only be terminated if everything has been paid).
• Exporting the data has a cost and a timeframe. Set out in the takeover agreement who requests it, who pays for it, in what format and by what date.
• Old files must remain readable for the entire retention period, even if you change software: keep a usable archive or read-only access.
• Open invoices and current reminders must be taken over or settled, with a clear cut-off date for the accounts.
• The team knows the old software: plan for training, and switch at a quiet time.
• The existing devices (radiology, sensors, intraoral scanner) must work with the chosen software.
• Take stock of the inherited IT before signing: age of the server, Windows versions, backups that have actually been tested.

You are setting up a practice from scratch

You have complete freedom, and this is the time to make the right choices in the right order.

• Choose the software before the devices: radiology, intraoral scanner and cameras must connect to the chosen software.
• Plan the infrastructure: cabling, Wi-Fi, internet connection (a second connection if the software is online), technical room and UPS if there is a server in the practice.
• Keep to the timetable: appointment book and online booking ready a few weeks before opening, team trained, electronic invoicing tested before the first patient.
• Include the ten-year cost in the financing plan presented to the bank.
• Think ahead to handing over the practice: data that is easy to export makes a practice easier to sell.

You work as a self-employed dental hygienist

A dental hygiene practice does not have the same needs as a dental practice.

• Recalls are the heart of the business: maintenance intervals per patient, automatic reminders, waiting list.
• The periodontal chart: probing, bleeding, mobility, plaque indices, photos, and how they change over time.
• A price on your scale: some vendors have a rate for hygiene only. Do not pay for modules you will not use.
• Invoicing: most invoices go to patients, often partly reimbursed by their supplementary insurance. The QR-bill and sending by e-mail matter more than invoicing the social insurers.
• The link with dentists: reports, X-rays and letters exchanged through secure e-mail.
• If you work in several practices, check who is responsible for each patient's data, and that the software clearly separates the locations.

You are changing software in an established practice

• Start with the exit: ask the current vendor what it provides, in what format, how long it takes and at what price.
• Respect the notice period: some contracts can only be terminated on a fixed date in the year. Missing it often means paying for one more year.
• Run a test import and check what is carried over: patients, appointments, recalls, treatment plans, open invoices, documents, images.
• Keep the old software in read-only mode, or a usable archive, for the files that must be kept.
• Switch at a quiet time, with training before the first day.

You work with others or across several sites

• One appointment book per practitioner, per room and per site, with access rights suited to each person.
• Invoicing in the right name: each invoice must show the right practitioner and their identifiers.
• Fees per practitioner and statistics per person, useful if associates are paid a percentage.
• Data shared in real time between sites, with no double entry.

What everyone expects from the software

Practice management software serves the whole team, and beyond. Have everyone test it.

Software with a future, or software that has had its day?

Appointment book, patient files, invoicing: the whole practice runs through its management software. Here are the criteria that distinguish software with a future from software that has had its day, whatever the vendor. They describe typical profiles, not specific products: ask each vendor which side it is on, criterion by criterion, and get its answers in writing.

Our choice for your practice

• Opening a practice

  Software with no server to buy, a short commitment, a cost stated in writing and quick to learn for the team.

• Existing practice or takeover

  Put the software in place through this table and reread its contract: term, termination, export. If it has had its day, use the takeover as the moment to change it.

• Dental hygiene practice

  Software whose features (appointment book, check-up recalls for patients) and price suit a hygiene practice; ask whether there is a suitable offer.

• Group or multi-site practice

  Online software, with the same appointment book and the same patient files in all your practices, with no servers to link together.

• Specialist practice

  Orthodontics, surgery or periodontology: software that handles your specific needs and connects to your devices; ask for references in your speciality.

• Unreliable internet connection

  Online software, provided you install a backup connection (4G or 5G); failing that, installed software whose technology still receives updates.

Even with good software, take three precautions: have it written into the contract that exporting your data will be free if you leave; ask whether your patients' data may be used for artificial intelligence, and how to exclude it; ask under what conditions prices may increase.

Starting from the practice's needs

Before comparing vendors, list what the practice does every day. The most common functions:

• Appointment book

  Per practitioner and per room, with recurring or online appointments, waiting list and reminders by text message or e-mail.

• Clinical record

  Dental chart, periodontal status, medical history, medical alerts, photos and signed consents.

• Treatment plans and quotes

  Treatment options and stages, quotes at the SSO tariff and acceptance by the patient.

• Imaging

  X-rays and photos of the right patient, linked to radiology, the intraoral scanner and the camera.

• Laboratory

  Order forms, tracking of work in progress and checking of laboratory invoices.

• Invoicing and payments

  Invoices to patients and insurers, deposits, reminders and assignment to a billing agency.

• Management

  Activity statistics, fees per practitioner and accounting exports for the fiduciary.

• Communication

  Letters and reports to colleagues, secure e-mail and documents sent to patients.

Then run the demonstration with your own cases: a new patient, a typical session, a quote, an invoice to an accident insurer. A function that only exists in a presentation does not count.

Software designed for Switzerland

A Swiss practice has needs that only software designed for Switzerland fully covers.

Words to know

SSO dental tariff

The list of around 500 dental services and their value in points, drawn up by the Swiss Dental Association (SSO). For private patients, each practice sets its own point value; for accident, military and disability insurance, it is set by agreement.

DENTOTAR

The name under which the SSO distributes its tariff. Commercial software can only include it if its vendor is a "DENTOTAR IT partner".

Accident, military and disability insurance

Accident insurance (UVG/LAA), military insurance and disability insurance. For these, dental invoicing has been electronic since 2025.

Forum Datenaustausch XML

The standard computer format for electronic invoices and quotes sent to Swiss insurers, defined by the Forum Datenaustausch, which brings together players in the healthcare system.

MediData

The main Swiss platform for exchanging health data: it routes practices' electronic invoices and quotes to the insurers. Other intermediaries exist.

QR-bill

The Swiss payment slip with a QR code, introduced in 2020 and the only one in use since the red and orange payment slips were withdrawn on 30 September 2022.

• The SSO dental tariff: in commercial software, it can only be used if the vendor has been granted "DENTOTAR IT partner" status by the SSO.
• Invoices to insurers: since 1 January 2025, invoices, quotes and files sent to accident, military and disability insurers at the SSO dental tariff go exclusively by electronic means, in the Forum Datenaustausch XML format, generally via MediData, which publishes the list of its software partners. Have them show you how an electronic dental invoice and quote are sent.
• The QR-bill for invoices to patients, and how it changes.
• Swiss VAT and its rules specific to the dental sector, which are not those of neighbouring countries.
• Swiss francs, Swiss law and a place of jurisdiction in Switzerland in the contract, and support open on Swiss working days.

Standards change in versions: XML formats, tariffs, the QR-bill (since November 2025, it only accepts structured addresses). Ask how and how quickly the vendor follows these changes, and whether these adaptations are included in the price. Software designed for another healthcare system has to add a complete Swiss layer: ask for references from Swiss practices that have been using it for several years.

Installed in the practice or online: two valid models

• Installed on a server in the practice: the data is with you. The server, its backup, its replacement and the updates need to be organised, with the vendor and your IT provider.
• Online: the software and the data are hosted by the vendor or its provider. The internet connection becomes vital, and you need to know where the data is and how to keep a copy of it.

Neither is better in absolute terms. The right question is who does what, and what happens in the event of a breakdown.

Your data: where it is, and how to get it back

Patients' data is sensitive data within the meaning of the data protection act, and you remain responsible for its processing, even when a vendor hosts it. Four points need to be settled in writing:

• the data processing agreement: any provider that processes patient data for the practice must be bound by an agreement, and the practice must make sure that the provider guarantees its security (Art. 9 FADP). The provider may only entrust this processing to a third party with your prior authorisation: insist on the list of its sub-processors, with their country (hosting, sending e-mails and text messages to patients, artificial intelligence, support), and on its commitment to notify you as soon as possible of any data security breach (Art. 24 FADP);
• the hosting location: in Switzerland, or in a country whose level of protection is recognised, or with specific safeguards (Art. 16 FADP);
• other uses: some general terms and conditions allow the vendor to use the practice's data, in principle anonymised, for statistics or to train artificial intelligence features, sometimes with providers abroad. The vendor is then no longer acting on behalf of the practice, and data that is not truly anonymised remains covered by your professional secrecy. Read the clause, and check the default setting and whether you can opt out;
• the exit: a full export of the data, in standard, documented formats, with a known timeframe and cost, and the date on which the data is deleted after the end of the contract. That is what leaves you free to change one day.

Your professional secrecy also applies to data entrusted to a provider. Finally, the software must allow you to give patients a copy of their data, which they can request at any time: in principle free of charge and within thirty days (Art. 25 FADP).

Patient files to keep for longer than the software

Cantonal health laws require patient files to be kept for at least ten years in Geneva, in the canton of Vaud and in Fribourg, and for at least twenty years in Valais, in Neuchâtel and in the canton of Bern: check the rule in your canton. The absolute limitation period of twenty years for personal injury, counted from the act in question (Art. 60 para. 1bis and 128a of the Code of Obligations, since 2020), is a reason to aim for twenty years everywhere. In Geneva and Fribourg, on the other hand, the file must be destroyed after twenty years at the latest, unless there is an overriding interest for the patient's health. A practitioner setting up today will therefore need to be able to produce readable files for decades, well beyond the likely life of any software.

So insist on a full export in open formats that can be read without the original software: spreadsheets for the data, PDF/A for documents, the DICOM format for X-rays, and common image formats for photos. Also check that the software keeps a history of changes (who changed what, and when), which the law requires for a computerised record in Geneva as in Valais, and that it allows a file to be deleted once it reaches the end of its retention period.

Security: what you should be able to require

The minimum requirements of the Swiss Dental Association (SSO), supplemented by the FMH recommendations for medical practices, provide a clear basis. The software must make it possible to meet them:

• A personal account for each member of staff

  For each person who accesses patient data, with only the rights needed for their work.

• Strong passwords

  At least ten characters, specific to each person and never shared.

• Two-factor authentication

  At least for any access over the internet, ideally for any access to the software, and the practice must be able to enforce it on all accounts.

• The log of connections and activities

  To know who did what, with logs kept for at least three months, and one year where the law requires logging (Art. 4 DPO).

• Data encryption

  On the drives, in the backups and in e-mails that contain patient data.

• Protected access over the internet

  Only through an encrypted channel, such as HTTPS, and never patient data in plain text.

What you cannot see: the software's technology

Practice management software relies on technical components: a database engine, encryption libraries, sometimes a built-in web server. Like Windows, these components have an end date. After that date, their vulnerabilities are no longer fixed, even if the software itself keeps evolving. Ask the vendor what platform its software is built on, which version it ships today, and whether that version is still supported by its manufacturer.

Ask whether the software's administration credentials are specific to your practice. An administration password that is identical in every installation of the same software no longer protects anything once it gets around.

Also ask whether the data is encrypted on the drive, in the practice as in a data centre. If the server or a backup drive is stolen, unencrypted data can be read by anyone. If the software does not encrypt its data itself, the server's drive and the backups must be encrypted at system level.

Finally, a backup stored on the same server as the database protects neither against a failure of that server, nor against ransomware, nor against theft: the SSO requires a regular backup stored outside the practice, and a restore test at least once a year.

Software for a whole career

A practitioner who opens their practice at thirty may practise until the early 2060s. No software and no technology is guaranteed for that long: you will probably change software at least once. The challenge is therefore twofold: choosing software that will last for many years, and being able to leave it cleanly when the day comes.

To judge a software's future, look at what can be checked:

• Is the vendor moving forward? Regular, dated new features, a version history, a public roadmap.
• Is its technology up to date? The version of the platform it ships, and the end-of-support date of that version.
• Does it keep up with standards on time? QR-bill, XML formats, tariffs, and announced developments such as the electronic health record.
• Who is behind it? Size of the team, number of developers, length of service, dependence on one or two people, recent changes of owner or management (the commercial register and the Swiss Official Gazette of Commerce are public).
• What does the contract provide if the vendor ceases trading or is taken over? Data export, notice of end of support, continuity of the software.

A vendor rarely disappears overnight. More often, it is taken over, and its software gradually stops evolving while the company still exists. The practice then no longer chooses the moment of its migration: it is forced into it, often when a new invoicing standard comes in.

Speed and ergonomics: the everyday test

Slow or complicated software costs minutes with every patient, every day, for years. Test it the way you will use it:

• Time the everyday tasks

  Finding a patient, creating an appointment, entering the treatments of a session, making a quote, invoicing an accident insurer, taking a payment.

• Count the clicks and screens

  Repeated tasks must be direct, with shortcuts.

• Try it on your computers and your connection

  At busy times, at the chair as well as at reception, and on a touch screen or tablet if you use one.

• Have the team test it

  A new dental assistant must find their way around after a short training session.

• Ask for a trial period

  Of several weeks, with a visit to a comparable practice that uses it.

A modern interface is not just a matter of appearance: it often reflects the vendor's ability to keep developing its software.

Support: the human relationship

On the day the appointment book will not open or an invoice is rejected, the quality of support matters more than any feature.

• Opening hours

  Do they cover the practice's hours, early in the morning, at lunchtime and at the end of the day? What happens outside them?

• Channels

  Phone, e-mail, chat and remote control, in your language.

• Price

  Is support included, or invoiced by the quarter hour? Are emergencies and out-of-hours interventions invoiced on top?

• Response times

  Are they in writing, for emergencies as for everything else?

• Training

  At the start, for each new member of staff, and with each new version.

• Colleagues' opinions

  Ask for references and call them. Read online reviews with caution: they are sometimes few in number, or solicited.

The real cost over ten years

Comparing a purchase price with a monthly subscription means nothing. Add everything up over ten years:

The price of a reminder text message varies between vendors and plans, per unit or with a monthly package: ask for it in writing. For a practice that sends a thousand reminders a month, a difference of ten centimes adds up to CHF 1,200 a year.

1,000 reminders a month×10 centimes difference×12 months=CHF 1,200 a year

Prefer public, written prices, with a clear rule for increases. A price available only on quotation makes any comparison difficult.

Purchased licence or subscription: what "lifetime" means

A purchased licence is not ownership: it is a right to use the software, which the contract often declares personal and non-transferable. Copyright law in principle allows the resale of purchased software (Art. 12 CopA), but the scope of contrary clauses is debated, and maintenance does not follow without the vendor's consent. It is frequently tied to mandatory maintenance, sometimes for several years. Without maintenance, there are no more updates, including adaptations to standards: a new version of the QR-bill, a new XML format, a new tariff. The software freezes, and quickly becomes unusable for invoicing. Some contracts also provide for features to be restricted or for the licence to end in the event of unpaid invoices.

A subscription is often easier to terminate, but access stops with it, and its price can change at each renewal.

In both cases, ask in writing:

• what you can still do with the software if you stop paying, and whether you keep at least read-only access to your patient files;
• whether the licence can be transferred to a partner or a buyer;
• by how much, and how often, the price can increase;
• the minimum commitment period, the termination deadline and its conditions.

X-rays and imaging: the link to check

The practice management software must open the right patient's X-rays, with no double entry. Ask how this link works with your current devices, whether it is based on recognised standards, and who steps in when it stops working: the vendor, the device's supplier or your IT provider. Have it tested during the demonstration, with your own devices if possible.

Computers and systems

Check which systems the software runs on (Windows versions, Mac, web browser, tablet), and how the vendor keeps up with new versions: each version of Windows has its end date, see our guide Windows and Office end of support in the dental practice. Also ask how software updates are done: automatically, remotely, or with an intervention in the practice.

Contract and exit conditions

Before signing, have the following clarified: what is included in the price and what is invoiced on top, the minimum commitment period, the termination conditions, what the vendor hands over to you at the end of the contract, and whether the price, the features or the general terms and conditions can be changed during the contract.

Four precautions avoid most unpleasant surprises:

• The promised features: have every important feature shown to you in the version that will actually be installed, not in a presentation or a project. A feature announced for later must appear in the contract, with its availability date.
• Built-in limits: if the software contains a licence expiry date, a maximum number of computers or addresses, or any other technical limit, it must be stated in black and white in the contract.
• The price of leaving: the full data export must have a price and a timeframe set in the contract from the outset, not be invoiced by the hour on the day you leave. An oral promise of a free export is hard to prove, and many contracts only accept written amendments: have it put in writing.
• The general terms and conditions: read who is responsible for the security and backup of the data, what the vendor undertakes to do in the event of loss, and up to what amount it is liable. Some terms leave almost everything to the practice: you then have to organise it yourself. A clause may limit the vendor's liability for slight negligence, but cannot exclude it in advance for gross negligence (Art. 100 CO).

The 12 questions to ask before signing

1. Where is patient data stored (country, data centre), which sub-processors have access to it, and is the data processing agreement provided with their list?
2. Is the data encrypted on the drive, in the practice or in the data centre, in the backups, and during all exchanges between the computers, the server and the internet?
3. Is the practice's data used for anything other than its work (statistics, training artificial intelligence), in what form, and can the practice opt out?
4. What technical platform is the software built on, which version is shipped, and are its components (database, encryption) still supported by their manufacturers?
5. How do you get all the data back if you leave, including images and documents: format, timeframe, price set in the contract, and date of deletion after the end of the contract?
6. Who backs up what, where (off the server and outside the practice), how often, and how is a restore tested?
7. Does each member of staff have their own account, with suitable rights, logged and retained access records, and two-factor authentication that the practice can enforce, and are the administration credentials specific to the practice?
8. Which systems does the software run on (Windows, Mac, web browser), and how are its updates done?
9. How does the software connect to radiology and other devices, and who steps in if this link breaks down?
10. Is the vendor a DENTOTAR partner, is electronic invoicing to accident, military and disability insurers built in, and are adaptations to new standards included in the price?
11. What happens if the internet or the server goes down: can the appointment book and the patient files still be consulted?
12. Do the features presented already exist in the version that will be installed, and what do the contract and the general terms and conditions say about support, liability for the data (and its cap), price changes, transfer of the licence and termination?

Glossary

The technical terms in this guide, in one sentence each.

Archive

A copy of the data in open formats (spreadsheets, PDF/A, images), readable without the original software.

Encryption

A process that makes data unreadable without the key, on the drive, in the backups and during exchanges.

Data processing agreement

The agreement that binds the practice to any provider that processes patient data on its behalf (Art. 9 FADP).

DICOM

The international standard for medical images: with each X-ray, it keeps the patient, the date and the device settings.

Full export

The handover of all the practice's data (patients, appointment book, invoices, documents, images) in standard, documented formats that another software can reuse.

GLN

The 13-digit identification number of healthcare professionals in Switzerland, shown on electronic invoices.

Two-factor authentication

A sign-in that requires, in addition to the password, a second proof: a code generated or received on another device, or a physical security key.

ZSR number

The number assigned by the creditor code register (santéservices SA), which insurers require in order to process a provider's invoices. One is needed per canton of activity.

PDF/A

A standardised form of PDF, designed to remain readable in the long term, without depending on any particular software.

Ransomware

Malicious software that encrypts the practice's data and demands a ransom to return it. Hackers often also copy the data and threaten to publish it.

Disconnected backup

A copy unplugged from the network after each backup and stored outside the practice: ransomware cannot reach it as long as it is not reconnected.

VPN and remote desktop

A VPN connects an outside device to the practice network through an encrypted tunnel; remote desktop controls a computer remotely. From outside, it is only accessed through a VPN protected by two factors.

Our role

DentalSystems Sàrl sells no practice management software: we work with the one the practice has chosen. We can help you ask these questions, compare the answers from an IT point of view, prepare a takeover or the creation of a practice, and organise what remains the practice's responsibility: computers, network, backups, accounts and security. To take stock of data protection, see also our 22-point FADP check-up.

Frequently asked questions

Sources

Texts checked on 16 October 2026.

Law and data protection

• Federal Act on Data Protection (FADP, SR 235.1), Art. 5 (sensitive data, processor), 8 (security), 9 (processing by processors), 16 (abroad), 24 (data security breaches) and 25 (right of access): fedlex.admin.ch/eli/cc/2022/491/en
• Data Protection Ordinance (DPO, SR 235.11), Art. 3 and 4 (security, logging), Art. 16 to 19 (right of access) and Annex 1 (states whose protection is recognised): fedlex.admin.ch/eli/cc/2022/568/en
• Code of Obligations (SR 220), Art. 11 and 16 (form of contracts), 60 para. 1bis and 128a (twenty-year limitation period for personal injury), 100 (exclusion clauses) and 936 (public commercial register): fedlex.admin.ch/eli/cc/27/317_321_377/en
• Swiss Criminal Code (SR 311.0), Art. 321: professional secrecy: fedlex.admin.ch/eli/cc/54/757_781_799/en
• Copyright Act (CopA, SR 231.1), Art. 12: resale of software: fedlex.admin.ch/eli/cc/1993/1798_1798_1798/en
• SAMS and FMH, legal guide for doctors, chapter 3.5 "Medical records": practice takeover, patient consent, processing by processors (in French): leitfaden.fmh.ch/…/35-dossier-medical.pdf

Retention of patient files: cantonal laws

• Geneva, Health Act (K 1 03), Art. 54 (computerised records), 57 (retention) and 58 (cessation of activity) (in French): silgeneve.ch/legis/data/rsg_k1_03.htm
• Vaud, access to the patient file (Public Health Act, Art. 87 para. 5: retention) (in French): vd.ch/…/acces-au-dossier
• Fribourg, Health Act (RSF 821.0.1), Art. 59: retention (in French): bdlf.fr.ch/app/fr/texts_of_law/821.0.1
• Valais, Health Act (RS 800.1), Art. 32: records and retention (in French): lex.vs.ch/app/fr/texts_of_law/800.1
• Neuchâtel, Health Act (RSN 800.1), Art. 64: retention (in French): rsn.ne.ch/DATA/program/books/rsne/pdf/8001.pdf
• Bern, Public Health Act (RSB 811.01), Art. 26: retention (in French): belex.sites.be.ch/app/fr/texts_of_law/811.01

Invoicing and tariffs

• SSO, DENTOTAR – SSO dental tariff, terms of use for dentists (in French): sso.ch/fr/media/420/download
• Medical Tariffs Commission (MTK), SSO dental tariff: electronic invoicing since 1 January 2025 (in French): mtk-ctm.ch/fr/tarifs/dentaire-sso
• Tariff agreement between the SSO and the insurers, Annex 5: billing and electronic data transmission (in French): mtk-ctm.ch
• Suva, electronic data exchange: ZSR and GLN numbers, XML standard, intermediaries (in French): suva.ch
• MediData, software search (list of software partners) (in French): medidata.ch/md/web/fr/support/recherche-de-logiciels
• PostFinance and SIX, press release of 19 January 2021: QR-bill and withdrawal of payment slips on 30 September 2022 (in French): six-group.com
• SIX, QR-bill: structured addresses mandatory from November 2025: six-group.com
• santéservices SA, creditor code register: applying for a ZSR number, one per canton (in French): santeservices.ch/…/demande
• Refdata Foundation, registration of healthcare professionals: the GLN number (in French): refdata.ch/…/Guide_Partner-refdatabase_FR.pdf

IT security and formats

• SSO, "Minimum requirements for IT security in dental practices", January 2020 (in French): sso.ch/fr/media/403/download
• FMH, "IT security in medical practices", detailed recommendations and measures, March 2023 (in French): fmh.ch/files/pdf30/it_grundschutz_d3_2023_fr.pdf
• FMH, "Technical and organisational requirements for cloud services", May 2020 (in French): fmh.ch
• Federal Office for Cyber Security (FOCS), basic protection for companies: offline backups, remote access (in French): bacs.admin.ch/fr/protection-base-entreprise-autorite
• FOCS, "Ransomware: what to do?" (in French): bacs.admin.ch/fr/rancongiciels-que-faire
• Microsoft, product lifecycle: end of support for Windows and Windows Server (in French): learn.microsoft.com/…/extended-security-updates
• DICOM, the international standard for medical images (ISO 12052): dicomstandard.org/about
• ISO 19005, PDF/A: file format for long-term preservation (in French): iso.org/fr/standard/38920.html
• Federal Office of Public Health, Electronic Health Record Act (EHRA) (in French): bag.admin.ch/fr/ldsan

Run the FADP check-up of your practiceWrite to usAll guides