Skip to content
FibonacciMedicaLog inTry it free

Access for outside programs

5 min readUpdated on 9 November 2026

This guide describes how to connect a program of the practice, for example the website or a management system, to the calendar and contact data, without giving that program anyone's password. It is meant for whoever administers the practice.

The program receives a key and does only what the key allows. There is no clinical data: medical history, visits, treatments, photos, consents and invoices stay out in this version.

Prerequisites

  • Be a practice administrator. Everyone else does not see the row and, if they open the page, they find You need to be a practice administrator.
  • The feature is off by default. If in Settings, People and permissions there is no row Access for outside programs, it is not active in your installation. Ask support, who switch it on.
  • A program that knows how to use the key. The technical guide for whoever writes it is a separate document: ask support.

Step 1: Open the page

In Settings, People and permissions, at the bottom, the row Access for outside programs has the button Open. The page has two parts: Keys and Notifications.

Step 2: Create a key

Press New key. Choose:

  • Name: to recognise it, for example "Website" or "Management system". Two keys cannot have the same name.
  • What it can do, among three permissions, which can be combined:
    • Agenda: read only: free and busy times, locations and, for each appointment, the time, status and codes. No name, phone, email, treatment or notes.
    • Appointment requests: the program can send a request, which stays waiting until you confirm it. It reads and changes nothing else.
    • Patient contact details: read only: name, phone and email of a patient, when the program knows their code. No date of birth, tax code or address.

Then Create the key.

Step 3: Copy the secret

Right after, Copy the secret now appears, with the Key code, the Secret and the Address where the program asks for its token. The secret is shown only once. After this screen it cannot be read again: if you lose it, you revoke the key and create a new one. When you have copied it, I copied it, close.

Every time a key is created, a notice email goes to whoever administers the practice (We emailed whoever manages the practice.). If the email does not go out, the page says so and the operation is still in the access log.

Step 4: The practice's keys

The list Practice keys shows each key with its creation date and who created it. There is a maximum number of keys: the page states it (You can have at most…) and, once you reach it, to create another you revoke one.

The permissions of a key cannot be changed. If you need others, you create a new key and revoke the old one.

Step 5: Revoke a key

Revoke, then confirm. The program that uses it stops working at once and there is no way back: to connect it again you need a new key. If you see I could not remove it completely, try again: until it is removed, it still works.

Step 6: Notifications

Keys let the program ask. Notifications work the other way round: when an appointment is created, changes time or status, or is cancelled, the program receives a message with the type of event, the codes and the dates. The message does not contain the patient's name.

To turn them on, in Notification addresses press New address, write a Name and the Address of your program, for example https://management.yourpractice.com/notifications. It must start with https:// and be a public address, written with the site's name and not with a number.

Every message is signed with a secret, which Copy the signing secret shows only once: the program uses it to check that the message comes from Fibonacci. Remove takes an address away; if you add it again it will have a new secret. There is a maximum number of addresses too.

If you see Notifications are not active on this server yet, the keys work but the notifications do not: ask support.

What stays in the access log

Creating and revoking a key end up in the Access log, with who did them. They are not deleted.

Something to know about privacy

The practice is the data controller and answers for whoever it connects: the page reminds you of this. A program that handles this data on behalf of the practice is normally a processor (art. 28 of the GDPR) and a contract with whoever runs it is needed. The text of the contract is not a matter for Fibonacci: have the practice's adviser look at it.

A patient's name, phone and email, together with the time of their appointment, say that this person is a patient of an aesthetic practice. That is why the Patient contact details permission is given only to a program you trust.

Common mistakes

  • Losing the secret. It cannot be read again: you revoke the key and create another.
  • Giving more permissions than needed. A website that shows free times does not need the contact details.
  • Expecting a missed notification to be recovered. After a few attempts the system stops and there is no queue to read back. An appointment deleted entirely, not cancelled, does not produce a notification.
  • This permission is not ready in your practice yet. Write to support: it is fixed without losing anything.
  • This address cannot be used. You need a public https address of your program.

See also