Skip to content
FibonacciAestheticsLog inTry it free

Technology and AI

Where the patient's data lives: cloud, servers in Europe, copies and access explained to a doctor

Clinical records in the cloud and GDPR: what it means, what the contract with the supplier must contain, where the data can be held and what to ask before signing.

The Fibonacci editorial teamUpdated on 8 min read

Server rack with green lights on
In this article
  1. What really changes with the cloud
  2. What the contract must say
  3. Where the data may be held
  4. Security (Article 32), in practice terms
  5. Data format and exit
  6. How Fibonacci describes it
  7. What to ask a supplier before signing

Cloud means the practice's data sits on a supplier's servers instead of on a computer in your practice. The law does not prohibit it. It asks three things: that the supplier be appointed as data processor under a written contract (Article 28 GDPR), that security measures be appropriate to the risk (Article 32), and that data do not leave the European Union except under the conditions of Chapter V (Article 44). You remain the data controller.

For a doctor, the useful question is not "cloud yes or no", but four answers the supplier must be able to give in writing: where the data are, who else touches them, what happens if something goes wrong, and how I get out when I want to leave.

What really changes with the cloud

With software installed on the practice computer, data security depends on that computer: on the disk, on the backups you remember to make, on who enters the room. With a cloud service, part of these tasks passes to the supplier: the machine, the backups, the updates. The responsibility for choosing well who carries them out does not pass.

That is why the contract matters. Article 28 GDPR says that the controller shall use only processors providing sufficient guarantees to implement appropriate technical and organisational measures. And it also says how: by way of a contract or other legal act, in writing (including in electronic form), that binds the processor to the controller.

What the contract must say

Article 28(3) lists the minimum content. The contract sets out the subject matter and duration of the processing, the nature and purpose, the type of personal data, the categories of data subjects, and the obligations and rights of the controller. It also provides that the processor:

  • processes the data only on documented instructions from the controller;
  • ensures that persons authorised to process the data have committed themselves to confidentiality;
  • takes all the security measures under Article 32;
  • engages another processor only under the conditions of paragraphs 2 and 4;
  • assists you in responding to patients' requests about their rights;
  • assists you with the obligations on security, breach notification and impact assessment;
  • at your choice, at the end of the service deletes or returns all the data and deletes existing copies, unless the law requires them to be kept;
  • makes available to you the information needed to demonstrate compliance with the obligations and allows and contributes to audits, including inspections.

The last line of the list is the one people forget: you can ask the supplier to demonstrate what it claims.

Sub-processors

A practice management supplier rarely does everything alone: it has one company providing the servers, another providing the artificial intelligence model, another sending the messages. These are the sub-processors. Article 28(2) says that the processor shall not engage another processor without prior written authorisation, specific or general, of the controller; with general authorisation, it must inform you of any intended addition or replacement, giving you the opportunity to object. And paragraph 4 provides that the same data protection obligations as in the main contract are imposed on the sub-processor.

In practice you need an up-to-date list of who touches the data and for what.

Where the data may be held

The GDPR does not say "keep the data in Italy". It says that a transfer of personal data to a third country or an international organisation takes place only if the controller and processor comply with the conditions of Chapter V (Article 44), so that the level of protection guaranteed by the Regulation is not undermined. Chapter V concerns transfers to third countries: that is why "where the data are" is the first question to ask.

Two practical consequences:

  • the question "where are the servers?" is not enough, and must be completed with "and the backups? and technical support? and the sub-processors?", because data can be in Europe and be reached by a supplier outside;
  • Article 13(1)(f) requires that the patient information notice state, if there is an intention to transfer data outside the Union, which safeguards apply. If there is none, you must still be able to rule it out with certainty, and the supplier must be able to say so in writing.

Security (Article 32), in practice terms

Article 32 does not list products. It requires measures appropriate to the risk, and among the examples it cites: encryption and pseudonymisation of data; the ability to ensure confidentiality, integrity, availability and resilience of systems; the ability to restore data promptly after a physical or technical incident; a process for regularly testing the effectiveness of the measures. Almost all of it comes down to four questions:

  1. Encryption. What is encrypted, where, and with which key held by whom?
  2. Backups. How often are they made, are they encrypted, has anyone ever actually tried to restore them?
  3. Access. Who can open a record? Does everyone have a personal user account? Does every opening leave a trace?
  4. Roles. Does the reception staff see what they need to see, or everything?

The last one is solved in the practice management software: users and permissions serve to match what each person can open to what their role requires. How concrete the risk is, the Garante's sanctions on access to records show, discussed in what the Garante has sanctioned in health records.

Data format and exit

There is a passage in the Italian medical code of ethics that is usually little read. The application guidance under Article 78 says that the doctor must use reliable systems and favour services that allow the creation of a format independent of the platform, without preventing the reuse of the information, ensuring its availability, confidentiality and storage arrangements. In plain terms: before choosing a supplier, ask in what format you get out.

How Fibonacci describes it

For Fibonacci the data are held on servers of Aruba S.p.A., in Italy, therefore within the European Union, not on US clouds and with no replicas outside the Union. The dictation audio, which is a trial feature, goes to Mistral AI, in France; the supplier has undertaken by contract not to train models on the data passed to it through the calls. The data processing agreement, the list of sub-processors and the security measures sheet are public on the website, with no form to fill in.

On the measures, the security and data page is explicit, including the things that are not there yet:

  • traffic travels over TLS;
  • clinical photographs are encrypted in the browser before upload, and the key protecting each photo stays on the server;
  • backups are encrypted before being written, made daily, with a periodic restore test; the historical log allows the system to be brought back to a precise moment and not only to the last night;
  • the database, however, is not yet encrypted at rest, either at disk level or field by field: it is protected by access control to the machine and by the separation between practices.

On access, the technical staff who manage the servers have access to the infrastructure, as in any hosted service. Access to data is tracked in the same log that the practice can see. Fibonacci does not look at records on its own initiative and, if the practice asks for assistance on a specific case, it does so with the practice and the access remains recorded.

On exit, the record can be exported in a standard health format (FHIR), readable by another supplier too, at any time; when the relationship ends the data are returned and then deleted within the terms of the contract. The overview of the European rules and of what Fibonacci already has and does not yet have is in European compliance.

What to ask a supplier before signing

A list to take with you, or to send in writing:

  • Who is the supplier, where is it based, and where are the servers physically located?
  • Are there backups, technical support or sub-processors outside the European Union?
  • Will you give me the data processing agreement (Article 28) and the up-to-date list of sub-processors?
  • How am I notified if you add one, and can I object?
  • What is encrypted and what is not, today? Where are the keys?
  • How often do you make backups, are they encrypted, when did you last restore them?
  • Does access to records leave a trace that I can read?
  • Can your technicians open a record? In which cases, and is it recorded?
  • Are my patients' data used to train artificial intelligence models?
  • In what format do I get out, when, and what happens to the data afterwards?
  • If there is a data breach at your end, how quickly will you tell me?

This last question has a basis in law: Article 33(2) says that the processor shall notify the controller without undue delay after becoming aware of a breach, so that the controller can decide whether to notify the Garante. What to do in that case is in a data breach in the practice.

What Fibonacci does for this

This is how it looks in Fibonacci, with sample data:

The patient record in Fibonacci, with sample data

Sources

  1. Regulation (EU) 2016/679 (GDPR), Articles 4, 13, 28, 32 and 44 (opens in a new tab)
  2. FNOMCeO Code of Medical Ethics (2014, with updates to Articles 54, 56, 76 and 77), Article 78 and implementing guidance (opens in a new tab)

These articles explain what regulations and guidelines require and what is documented in the medical record. They are not legal or tax advice on your situation and do not say how to treat a patient.

Try Fibonacci in your practice for 15 days, no credit card needed

Within one working day we call you: together we set up your practice and import your data.

Try it free

Read next

All articles