2
• images of the area affected by the surgery and other diagnostic tests strictly relevant to the follow-up,
where entered by the Physician (the Physician is advised to take images and recordings of the Patient
keeping the area captured to a minimum and absolutely avoiding capturing the face and any other
distinctive bodily features of the Patient (tattoos, other identifying features));
• technical data of the implanted device;
• minimised demographic data (sex and year of birth of the Patient). These data are collected exclusively
to allow the production of internal aggregate statistics on the distribution, use and positioning of BRM
devices by sex and age;
• the Patient’s e-mail address, which is collected and processed solely and exclusively for sending the
privacy notice.
The Physician may not enter any identifying data of the Patient into the App, except for the e-mail address for
sending the privacy notice, which, once entered, will no longer be accessible to the Physician, but will be stored
in the backend and accessible only to the authorised system administrator and within the limits strictly
necessary for the technical management of the service and for the fulfilment of the information obligation.
3. Purposes, roles and legal bases
Processing by the Physician or the healthcare facility: treatment and follow-up
The Physician, or the healthcare facility on whose behalf the Physician works, processes the Patient’s data for:
• diagnosis, healthcare, treatment and clinical follow-up;
• documentation and management of the care pathway;
• clinical assessment of the outcomes of the surgery and of the Patient’s condition;
• storage and consultation of healthcare records, within the limits and for the periods provided for by
applicable law.
For such processing, the controller is the Physician and/or the healthcare facility where the Physician works. The
processing of data concerning health is carried out, where necessary for the purposes of diagnosis, healthcare
or medical treatment, pursuant to Article 9(2)(h) GDPR and Article 9(3) GDPR, by or under the responsibility of
professionals subject to professional secrecy. The legal basis under Article 6(1)(b) or (e) GDPR is identified by
the Physician and/or the healthcare facility in relation to the care context and the applicable rules.
The Patient’s consent is not required for processing strictly necessary for treatment. The Physician and/or the
healthcare facility remain obliged to provide the Patient with their own privacy notice on the processing of data
within their care relationship.
BRM: management of the physician account and operation of the App
BRM processes the Physicians’ data in order to:
• evaluate access requests, create and manage the account, authenticate the user and administer
access authorisations;
• make available, maintain, update and protect the App;
• provide technical assistance, handle support requests and prevent unauthorised use, fraud, security
incidents or breaches of the terms of use;
• manage the contractual or pre-contractual relationship with the Physician;
• send push notifications to the Physician, if enabled by the Physician in the App settings.
The legal basis is Article 6(1)(b) GDPR, where the processing is necessary for the performance of the contract or
of pre-contractual measures requested by the data subject; for security activities, prevention of abuse and
protection of systems, the legal basis is Article 6(1)(f) GDPR, on the grounds of BRM’s legitimate interest in
ensuring the security, integrity and continuity of the App and of its systems.
BRM may send Physicians communications strictly necessary relating to the App, security, service updates,
devices and regulatory requirements. Such communications are sent, where necessary for the contractual
relationship or for security, without requiring consent. For push notifications, if enabled by the Physician in the
App settings, the legal basis for the processing is Article 6(1)(b) GDPR.
BRM: Follow-up, internal device statistics and Patient e-mail address
BRM uses the data available in the App, associated exclusively with identification codes and without direct
identifiers of the Patient, in order to:
• produce internal statistics on implanted devices in aggregate form;
• understand which devices are most widely used;
• analyse the distribution and use of the devices on the market;