Dental practice software in Belgium, and what an AI receptionist can connect to

Which practice software do Belgian dentists run?

The answer is public and it is finite. The NIC/CIN, the joint body of the Belgian sickness funds that runs MyCareNet, publishes the list of software packages approved for the national electronic flows: tariff lookup, eAttest, eFact and the GMD/DMG global medical file. The packages below are the dental entries on the 10 March 2026 version of that list, plus Baltes, which is Corilus’s legacy dental line and no longer appears on it in its own right.

Read the approvals column for what it is. It records which electronic flows a package has been approved for. It is not a quality rating, not a market share, and not a feature comparison. Approvals are added over time and the list is reissued, so a gap in a row is a question for the vendor rather than a conclusion.

Four orthodontics-only packages also sit on the same list: Orthalis, Orthokis, Orthwin and Orthoadvance. They serve a different buying centre and a different appointment model, a long treatment series rather than a single booking, so they sit outside this page.

NIC/CIN, approved dental software packages for MyCareNet, version 10 March 2026

Can an AI receptionist book directly into my practice software?

Not by flipping a switch, and anyone who says otherwise has not looked. No Belgian dental practice management system publishes an open, documented REST API. That was checked across vendor websites, developer portals, public code repositories and package registries, and nothing was found. It is the most important sentence on this page and it is the one a foreign vendor will never write.

There is no interoperability standard to fall back on either. Belgium’s national rails, meaning MyCareNet insurability, eAttest, eFact, eTarif, Recip-e and the GMD/DMG, cover billing and insurability, not diaries. VDDS, the one de facto standard the sector cites, connects a practice system to imaging software rather than to a calendar. The European Health Data Space regulation applies from 26 March 2027 with its first priority data categories from March 2029, and appointments are not among them. No standard is coming to fix this.

One exception is worth naming, because it is the only one. CLICKDOC Dentist, the online agenda built by DentAdmin and sold through CGM, publishes its Belgian API openly. It is a booking layer rather than a practice management system, and published documentation is still not the same as an agreed connection.

So in Belgium an integration is a relationship, not a plug. It needs a named contact at the vendor, a test environment, an account with the narrowest rights that work, and a written agreement about what leaves the practice. Anyone promising a one-click connection to a Belgian dental system should be asked which endpoint they are calling.

CLICKDOC BE API documentation, checked September 2026

What about Doctena, Rosa and the other online agendas?

The booking layer is a separate product from the practice system, and in Belgium it is where the open doors are. These platforms sit on top of the diary, take bookings from patients, and in some cases already synchronise with a practice system. They are not practice management systems and none of them replaces one.

Progenda is now Helena Pro Calendar. The old address redirects to the new one, so a supplier or a comparison page still calling it Progenda is working from stale information. Helena Pro Calendar is run by HealthConnect in Ghent and advertises full integration with CareConnect, which makes it the CareConnect-side counterpart of what CLICKDOC is for DentAdmin.

Helena Pro Calendar, the site progenda.be now redirects to, checked September 2026

Is Tilcao a practice management system?

No, and it is not trying to be. Tilcao is not on the NIC/CIN MyCareNet approved-software list and does not need to be. It does not replace DentAdmin, CareConnect Dentist or anything else on that list. It answers the phone and WhatsApp in front of the system you already run, and books into the diary you already keep.

It holds no eHealth certificate and touches none of the national rails. It does not attest, does not invoice, and never writes in the clinical record. Electronic invoicing has been mandatory for Belgian dentists since 1 September 2025 under RIZIV/INAMI, the national health and disability insurance institute, and it stays entirely inside your practice system, where it belongs.

• Not on the NIC/CIN MyCareNet approved-software list, and no claim is made that it is.
• No connection to MyCareNet, eAttest, eFact, eTarif or Recip-e.
• No clinical notes, no changes to a patient file.
• No assessment of symptoms and no judgement of urgency. Pain goes to a person, following your own rule.
• No replacement for your practice software, your imaging or your accounting.

RIZIV/INAMI, mandatory electronic invoicing for doctors and dentists from 1 September 2025

What does Tilcao need from your system?

Four things, and nothing beyond them. Read the diary, so that every time the agent offers is genuinely free. Create an appointment of a type you have configured. Move one. Cancel one. The integration account should hold the narrowest rights that make those four work.

Everything else comes from the practice rather than from the software: the rules about who may be booked with whom, the appointment types and their lengths, the knowledge base that answers questions about the practice, and the named person a call goes to when it should. Every conversation produces a structured summary and an audit trail, so you can see what was said and what was written.

• Read availability, per chair or per practitioner, as your system models it.
• Create an appointment of a configured type.
• Move an appointment.
• Cancel an appointment.

How does an integration with your vendor start?

With a conversation, and with your system named. Tell us what you run and you will get a plain answer: what is possible today, what would need your vendor’s cooperation, and what is not possible at all. The third answer is the one most worth having, and it is the one we will give you.

From there the shape is the same for every Belgian package, because the constraint is the same for every Belgian package. The work is in the agreement, not in the code.

• A named contact at your software vendor, because none of this is self-service.
• A test environment or a test practice, so nothing is tried first on a real patient.
• An integration account scoped to reading the diary and to creating, moving and cancelling appointments.
• An agreed list of the appointment types the agent may book, and the ones it may never book.
• A processing agreement under Article 28 of the GDPR, signed before the first real patient call, with every sub-processor named in its annex.