PVigi

Guideline on Personal Data Protection in Pharmacovigilance (Turkey)

English translation of the TİTCK guideline on processing, transferring and retaining personal health data in pharmacovigilance under Turkey's data protection law (KVKK).

Published: 2019-08-01 · Source: TİTCK

This text is provided for reference. The official version is published by the Turkish Medicines and Medical Devices Agency (TİTCK).

English translation of the TİTCK guideline (version dated 01.08.2019). The Turkish original is the legally binding text.

Section I – Introduction

1.1 Purpose

The purpose of this guideline is to ensure protection of personal data during pharmacovigilance activities and provide information on the liabilities to be complied with by natural persons and legal entities processing personal data and the procedures and principles they will follow.

Pharmacovigilance activities are regarded as activities carried out for the purposes of achieving preventive medicine and public health protection within the scope of Personal Data Protection Law No. 6698, dated 24.03.2016 (Law No. 6698).

This Guideline has been drawn up on the basis of Law No. 6698 and its relevant secondary arrangements.

1.3 Scope

This guideline applies for all pharmacovigilance activities in which explicit consent of data subject is not sought for processing personal data and comprises real persons whose personal data are processed as well as the real persons and legal entities processes these data (Data processing transaction may be performed completely or partially automatically or carried out via non- automatic means provided that it is part of any data recording system).

Activities conducted within the scope of a clinical study or other company activities in which explicit consent is received for processing personal data are outside this scope. It is necessary to receive explicit consent for personal data processing activities not included into the scope of exceptional purposes stipulated in Law No. 6698.

This guideline does not comprise the personal data protection legislation of countries outside Turkey and the legal and administrative regulations pertaining to processing of pharmacovigilance data.

1.4 Definitions

  • a) Explicit consent: Consent pertaining to a specific topic, based on receipt of information and expressed with free will,
  • b) Adverse event: Undesired medical event emerging in a patient or clinical trial volunteer to whom a drug is administered, and which does not necessarily have a causality relationship with the relevant treatment,
  • c) Adverse reaction/suspected adverse reaction: A response to a medicinal product which is noxious and unintended,
  • d) Recipient group: Category of the real person or legal entity to whom the data are transferred by the data controller,
  • e) Anonymization: Transformation of personal data into a format where the identity cannot be associated by any means whatsoever with a real person with known or identifiable identity, not even by being matched with other data,
  • f) Individual case safety report (ICSR), Adverse (drug) reaction report: Report with a specific format and content utilized when reporting one or multiple suspected adverse reaction(s) developing in a single patient at a certain time point against a specific drug,
  • g) Pharmacovigilance: Activities and scientific studies conducted for the designation, evaluation, understanding and prevention of adverse reactions and other drug-related issues,
  • h) Secure sockets layer (SSL): Certificate enable safety and integrity of the data flowing between the server and the client,
  • ğ) Relevant person: Real person processing the personal data,
  • i) Disposal: Deletion, destruction or anonymization of personal data,
  • ı) Personal health data: Any kind of information pertaining to the physical and mental health of an identified or identifiable real person and the information relating to the health service provided to that person,
  • j) Personal data: Any kind of information pertaining to an identified or identifiable real person,
  • k) Processing of personal data: Any kind of transaction performed on the health data, such as obtaining of personal data via fully or partially automatic means or non-automatically, recording, storage, retention, modification, rearrangement, explanation, transfer, takeover, make retrievable, classification or prevention of their utilization, provided that this is part of any data recording system,
  • l) Personal data processing inventory: Inventory in which data controllers provide details on the personal data processing activities performed in relation with business processes, purpose and legal reason for processing personal data, data category, established upon making an association between the recipient group to whom the data are transferred and the data subject group, specifying the maximum retention period required in line with the purposes for processing personal data, the personal data foreseen to be transferred to foreign countries and explaining the measures adopted in relation with data security,
  • m) Personal data retention and disposal policy: Policy taken as basis by data controllers for designating the maximum period required for processing the personal data, and deletion, destruction and anonymization of personal data,
  • n) Deletion of personal data: Transaction whereby personal data become absolutely inaccessible or reusable by users,
  • o) Board: Personal Data Protection Board,
  • p) Authority: Personal Data Protection Authority,
  • ö) Sensitive Personal Data: Data relating to the race, ethnic origin, political opinion, philosophical belief, religion, sect or other belief, clothing, association, foundation or trade union membership, health, sexual life, convictions and security measures as well as biometric and genetic data,
  • q) Rapporteur: Person reporting the adverse reaction,
  • r) Healthcare professional (HCP): Physicians, pharmacists, dentists, nurses and midwives within the context of reporting of suspected adverse reactions,
  • s) Registry: Data controllers’ registry kept by the Presidency of Personal Data Protection Authority,
  • ş) Company: Registration holder and/or contracted service companies from which the registration holder receives service (third party service providers),
  • t) Data processor: Real person or legal entity processing personal data with the power granted by the data controller,
  • u) Data recording system: Recording system where personal data are structured and processed according to certain criteria,
  • ü) Data controller: Real person or legal entity designating the purpose and means for processing personal health data and responsible for the establishment and management of the data recording system.

1.5. Personal data in pharmacovigilance

Companies collect data on a routine basis when performing pharmacovigilance activities for complying with the legal obligations on reporting of suspected adverse reactions and ensuring patient safety. Pharmacovigilance data may comprise personal data pertaining to the subject of that case, sensitive personal data or personal data pertaining to the rapporteur.

In cases where the relevant person or the health data pertaining to the relevant person may be shown when matched with other data, the referred data are accepted as sensitive personal data. Name and surname of the reporting person and his/her occupation and contact information are regarded as personal data.

It is necessary to know the age/age group, gender, weight, height, medical history and current status of the patient in order to be able to analyze effectively safety data in reporting of adverse reactions.

The initials of a patient or an assigned number and/or date of birth are essential for identifying duplicated reporting. Furthermore, also the name and contact information of the reporting person are necessary in order to perform an effective tracking for ensuring that complete and accurate data are collected.

Companies should comply with Law No. 6698 when they process personal data during pharmacovigilance activities and apply transparent and reliable processes for ensuring protection of personal data. The “Personal Data Security Guide” prepared by the Personal Data Protection Authority should be taken into account as per clause one, Article 12 of Law No. 6698 regarding the technical and administrative measures to be adopted by data controllers. Moreover, as per clause four, Article 6 of Law No. 6698, also adequate measures laid forth by the Board with Decision No. 2018/10 should be considered. The technical and administrative measures and adequate measures to be adopted by data controllers and those qualified as data processors are not limited with abovementioned arrangements and the measures and precautions specified in the Guideline and Decisions should also be taken into account.

Section II – Receipt and follow-up of pharmacovigilance data

2.1. Receipt of pharmacovigilance data

When an adverse event is reported to a pharmaceutical company, some personal data need to be collected for fulfilling the pharmacovigilance requirements of the presence of an “identifiable patient” and “identifiable rapporteur”.

The pharmacovigilance legislation stipulates that companies should ensure that the individual case safety reports contain information to meet minimum requirements. Furthermore, the data on the patient should be as complete as possible. The requirement for completeness of patient information means that all areas required for adverse reaction reporting are completed as per legislative provisions and not that the identification information of the patient is exactly the same. Clause two, Article 4 of the Law includes the principle of “being associated with the purpose of processing, being limited and moderate” among the principles to be complied with the processing of personal data. Thus, companies may not request for the name and contact information of HCPs reporting adverse reactions without the explicit consent of the patient.

There are two legal reasons for processing personal data; namely, explicit consent and exceptional cases. The exceptional cases for personal data are stated in clause two, Article 5 of Law No. 6698 while those relating to sensitive personal data are indicated in clause three of Article 6 of the Law. In case of presence of any of the exceptional cases, it is not necessary to receive explicit consent.

Personal data included into the scope of pharmacovigilance but outside the scope of sensitive personal data, such as name and surname, contact information, etc. may be processed without the explicit consent of the data subject, as this is explicitly by laws, it is mandatory for the fulfilment of the legal obligation of the pharmaceutical company which is the data controller and as data processing is mandatory for the legitimate interests of the data controller within the scope of Article 5 of Law No. 6698.

Whereas, sensitive personal data pertaining to health and sexual life may be processed without seeking for an explicit consent by the persons under confidentiality obligation or authorized institutions and organizations only for the purpose of protecting public health, conduct of preventive medicine, medical diagnosis, treatments and care services, planning and management of funding of healthcare services.

Regardless of whether the data subject is the person who experienced the adverse event or reported the adverse event (e.g. a healthcare professional (HCP) or a patient’s relative);

  • It is not mandatory to receive consent from the data subject for processing personal data pertaining to the data subject for pharmacovigilance purposes.
  • As indicated in the introduction of this guideline, processing of pharmacovigilance data which may be regarded as sensitive personal data by persons under confidentiality obligation for pharmacovigilance purposes is regarded to be part of protection of public health and preventive medicine activities as per clause three, Article 6 of Law No. 6698. However, non-requirement of explicit consent does not mean exception from Law provisions and all obligations pertaining to data security, starting with disclosure requirement, should be fulfilled.

Yet, Article 10 of Law No. 6698 stipulates that within the scope of the disclosure obligation, data subjects (persons who experienced an adverse event and, where otherwise, persons who reported the adverse event) should be informed on the purposes for which the personal data pertaining to them will be processed, who is the data controller, to whom and for what purpose the data processed may be transferred, data collection method, legal reason and the rights of the data subject indicated in Article 11 of Law No. 6698. It is not mandatory for the parties to whom the data may be transferred to be mentioned by name; it is sufficient to indicate the category (e.g.; Ministry of Health). This information should be clearly written in an easily comprehensible manner in the content of the Data Protection Disclosure Statement (DPDS).

Different types of adverse events reported via different channels may require the use of different DPDS statements of the company (See Annex). In the adverse event reporting made by an HCP or persons other than the data subject such as a family member or a relative, it is not possible for the company to present a DPDS directly to the data subject. In such cases, the way in which the data subject may access the DPDS will be communicated to the HCP or the person who reported the adverse event. The DPDS will be posted on website of the company. The company will adopt relevant measures for enabling access to the DPDS via different media. The DPDS will be prepared in line with the Article 10 of Law No. 6698 and the provisions of the Notification on the Procedures and Principles to be Complied with in the Fulfilment of the Disclosure Obligation.

2.2. Follow-up of pharmacovigilance data

The communications made with the person who did the reporting will require a DPDS in case a disclosure has not been made to this person previously. The annexed text may be attached to the company follow-up request forms or adverse event forms sent to the person who performs the reporting.

In cases where the first rapporteur is the patient or a patient’s relative, consent should be received at all times from the patients for enabling the follow up of patients by their HCPs.

Section III – Data entry, processing and transfer

3.1. Data entry – processing in line with law and rules of integrity

As per clause one, article 12 of Law No. 6698, companies are obliged to adopt any kind of technical and administrative measures directed at ensuring the adequate security level for ensuring prevention of illegal processing of personal data and prevention of retention of personal data.

3.2. Administrative measures directed at personal data security

3.2.1. Preparation of personal data processing inventory, designation of current risks and threats

In order to ensure personal data security, it is necessary, first of all, for the data controller to adopt adequate measures upon identifying correctly what the processed personal data are, the probability of the realization of the risks which may arise in relation with the protection of these data and the losses which may occur in case of realization of these risks.

3.2.2. Training of employees and awareness activities

Committing below-mentioned violations during the processing of personal data threaten data security:

1. Illegal disclosure or sharing of personal data, 2. Exposure to cyber-attacks:

a. Sending of an email attachment containing malware and opening of this attachment by the users due to negligence, inattentiveness or lack of experience, b. Sending of an email to a wrong recipient and opening personal data to the access of third persons, 3. Unauthorized or illegal processing of personal data, 4. Unintentional loss, destruction or damage of personal data. Companies should adopt adequate measures against abovementioned threats. These measures should also include taking of reasonable steps for ensuring that the employees with access to personal data are reliable.

It is necessary for employees to receive training on the protection of personal data and their processing in line with laws and their awareness on this matter should be ensured. Furthermore, even if employees have limited information, it is very important that they make the first intervention against attacks which may harm personal data security and cyber-security:

  • The roles and responsibilities of anyone reporting to the data controller should be descried in their job description regardless of the position in which they work.
  • When granting right of access in media containing personal data, the principle of “Unless permitted, everything is forbidden”, and not the principle of “Everything is allowed unless prohibited”, should be followed.
  • A commitment of confidentiality should be signed as part of the recruitment process of the employees.
  • It is absolutely necessary to avail also of a disciplinary process to come into play in case of failure of employees to comply with security policies and processes.
  • In case of major modifications in the policies and processes related with the security of personal data, such modifications should be communicated to the employees via new trainings and the knowledge on the security of personal data should be kept updated.
  • In case personal data are shared with third persons in data entry or other processing activities, it is the responsibility of the company to adopt security measures.
  • It is necessary for companies and the parties qualified as data processors to sign a written contract necessitating processing of personal data only in accordance with company instructions and ensuring adequate security for processing of personal data.

3.2.3. Designation of personal data security policies and processes

  • Accurate and consistent policies and processes related with security of personal data and the referred policies and processes should be integrated according to the working style and operation of the data controller.
  • Thus, regular checks should be made, these checks should be documented, the matters requiring to be developed should be identified and regular checks should be continued upon the conduct of relevant updates.
  • The risks which may arise for each personal data category and the way in which security violations will be managed should also be clearly specified.

3.2.4. Reduction of personal data as much as possible

As per items (b) and (d), clause two of Article 4 of Law No. 6698, personal data should be accurate and updated where necessary and should be kept for a period envisaged by the relevant legislation or in line with the necessary period.

Companies should also justify why they need to retain data they have processed for a certain period (see Section 5.6). Those obliged to be registered at the Data Controller Registry should include the referred periods in the personal data disposal policy which they will prepare.

Besides, in order to prevent unauthorized access, even in case of alignment with the purposes of personal data processing, it is recommended to keep personal data not requiring frequent access by data controllers and which are kept for archiving purposes, to be stored in more secure environments, while to dispose of unneeded personal data in accordance with the personal data retention and disposal policy and the regulation on the deletion, destruction or anonymization of personal data in a safe manner.

3.2.5. Management of relations with data processors

In case data controllers receive service from data processors in order to meet IT requirements, data processors should ensure that a security level which is by minimum at the level provided by data controllers regarding personal data is provided. In fact, as per clause two, Article 12 of Law No. 6698, also data processors are jointly responsible together with the data controller for ensuring personal data security. A contract should be signed with the data processor and the following provisions should be included into the contract:

  • The data processor will act in line with the legislation on the protection of personal and the Personal Data Retention and Disposal Policy in line with the purpose and scope indicated in the contract only according to the instructions of the data controller,
  • The data processor will be subjected to an indefinite confidentiality obligation regarding the personal data he/she processes,
  • In case of any data violation, the data processor will be obliged to forthwith report this to the data controller and the data controller will be obliged to forthwith report this to the Personal Data Protection Board and the relevant person,
  • It will be necessary to specify under a separate article the personal data category and type transferred to the data processor by the data controller as much as permitted by the content of the contract.

However, the data controller may conduct or ensure the conduct of relevant audits on the system containing personal data and may inspect on-site the reports resulting from the inspection and the service provider.

The administrative measures which may be adopted by the data controllers are shown in summarized format in Table I.

Table I. Administrative measures

  • Preparation of personal data processing inventory
  • Training and awareness activities (Information Security and Law)
  • Corporate policies (Access, Information security, Utilization, Retention and disposal, etc.)
  • Contracts (Data controller – Data controller, Data Controller – Data processor)
  • Confidentiality commitments
  • In-house periodic and/or random inspections
  • Risk analyses
  • Employment agreement, Disciplinary Regulation (addition of suitable provisions to the Law)
  • Corporate communication (Crisis management, processes for information the Board and the relevant person, reputation management, etc.)
  • Notification to data controllers’ registry information system (VERBİS)

3.3. Technical measures pertaining to personal data security

3.3.1. Ensuring cyber-security

The approach recommended for ensuring cyber-security involves the implementation of a serious of measures which have a complementary qualification and are regularly checked within the framework of many principles. The prioritized measures which may be adopted against unauthorized access threats coming via the internet into the IT systems comprising personal data are listed below:

  • Establishment of a firewall to stop violations from deeply penetrating into the currently utilized network,
  • Utilization of an internet gateway to prevent access of the employees to the websites or online services which constitute a threat for personal data security,
  • Utilization of products like antiviruses and anti-spams which detect regularly screen the network for being protected from malware and ensuring that they are updated,
  • Removal of software with security gaps and unused software and services from the devices,
  • Conduct of patch management and software updates,
  • Limitation of access to systems containing personal data, o Provision of access to the employees for relevant systems upon granting access authorization and utilizing username and password as much as required for the job and duties they perform and their powers and responsibilities, o Full validation or testing of the databases containing personal data used in pharmacovigilance to ensure that they enable detection of modifications made in the data and limitation of access to these databases only to designated persons, o When creating a password, preference of combinations comprising small and capital letters, numbers and symbols instead of easy to guess number or letter series associated with personal information, o Establishment of an access authorization and control matrix by data controllers and separate access policies and processes and implementation of these policies and processes within the data controller organization, o Limitation of the number of password entry attempts to achieve protection from widespread attacks such as use of brute force algorithm, o Ensuring frequent renewal of passwords, o Opening of admin account and admin authorization to be used only when needed, o Immediate deletion of accounts or blocking access of the employees dismissed by the data controller, o In case personal data will be obtained by the data controller from various websites and/or mobile application channels, the conduct of connections via SSL or a more secure path.

3.3.2. Follow-up of personal data security

The following measures should be adopted to enable the data controller to prevent potential attacks to their systems or exposure to cyber-crimes or malware:

  • Checking which software and services are working in their information network,
  • Designation of whether there is penetration or unexpected movement in their information network,
  • Regularly keeping record the transaction movements of all users (like log records),
  • Establishment of an official reporting process for reporting of security issues,
  • Reporting to the security issues to the data controller as soon as possible.

In undesirable events such as collapse of the IT system, malware, attacks causing service unavailability, deficient or erroneous data entry, violations disruption confidentiality and integrity and abuse of the IT system despite the measures adopted, evidence should be collected and safely stored.

3.3.3. Ensuring security of the environment comprising personal data

  • If personal data are kept in the devices or electronic or paper-based environments in the campuses of data controllers or outside, adoption of physical security measures against threats such as theft or loss; furthermore, protection of physical environments with suitable methods against external risks (such as fire, flood, etc.) and controlling entry into and exit from these environments,
  • Not leaving unattended the documents containing pharmacovigilance data, adoption of a clean table policy by companies for pharmacovigilance documents,
  • In case personal data are in an electronic environment, limitation of access between network components or separation of components,
  • Sending of personal data to be transferred by e-mail or post carefully and upon adoption of adequate measures,
  • Adoption of adequate security measures during access to the IT network of the personal electronic devices of employees,
  • Moving of documents on paper, services, back-up devices, and devices such as CDs, DVDs and USB sticks containing personal data to another room with additional security measures, adoption of measures aimed at increasing physical security such as keeping the referred room locked when unused and keeping record of entries and exits,
  • Authorization of access control and/or utilization of encryption methods against loss or theft of devices containing personal data (laptops, mobile phones, flash discs, etc.), keeping the encryption key only in places that can be accessed by authorized persons and prevention of unauthorized access,
  • Keeping documents in paper format under lock, in places which can only be accessed by authorized persons, in secure and robust areas such as fireproof cupboards/archives,
  • Regardless of the encryption method used, ensuring that personal data are fully protected and preference of the utilization of internationally accepted encryption programs to serve this purpose.

3.3.4. Storage of personal data on cloud

  • In order to enable storage of personal data on cloud, controlling of the data controller to verify whether the security measures adopted by the cloud storage service provider are adequate and suitable,
  • Having detailed knowledge on the personal data stored on cloud, ensuring their backup and synchronization and, where required, conduct of a two-step identity verification for remote access,
  • Conduct of encryption during storage and utilization via cryptographic methods, storing data on cloud upon encrypting them and utilization of separate encryption keys for each cloud solution from which service is received,
  • Upon termination of the cloud IT service relationship, all copies of encryption keys should be destroyed.
  • Servers of the company from which cloud services are received should be located in our country or in one of the countries included into the list of reliable countries declared by the Authority. This rule shall not apply in case explicit consent has been received from the data subject.

3.3.5. Procurement, development and maintenance of IT systems

  • Consideration of security requirements in the designation of the needs related with the procurement, development of new systems by the data controller or improvement of the current systems,
  • Conduct of controls to verify that the inputs of application systems are accurate and adequate, establishment of control mechanisms to check whether the data entered correctly is disrupted erroneously or intentionally during the transaction,
  • Designing of the applications in a manner so that the probability of the errors occurring during a transaction of disrupting data integrity is minimized,
  • If devices which are broken down or are sent to third parties, such as the manufacturer, seller or service due to maintenance contain personal data, dismantling and storage of the data storage medium in these devices prior to sending the devices to repair and maintenance and sending only of parts which are broken down,
  • In case of arrival of external personal for repair and maintenance, adoption of relevant measures to ensure that the data are not copied and carried outside the organization.

3.3.6. Backing up of personal data

  • Backed up personal data should be accessed only by the system administrator and the data set backups should always be kept outside the network,
  • The physical security of all backups should also be ensured.

The technical measures which may be adopted by data controllers are shown in Table II in summarized form:

Table II. Technical measures

  • Authority matrix
  • Authority control
  • Access logs
  • User account management
  • Network security
  • Application security
  • Encryption
  • Penetration test
  • Attack detection and prevention systems
  • Log records
  • Data masking
  • Data loss prevention software
  • Backing up
  • Firewall
  • Updated anti-virus systems
  • Deletion, destruction or anonymization
  • Key management

3.3.7. Transfer of data abroad

Entry of the pharmacovigilance data to the main pharmacovigilance system of the company outside Turkey or to a database which is accessible from outside Turkey means the transfer of personal data abroad within the scope of the data protection legislation.

If the pharmacovigilance data composed of personal data are stored in the main system outside Turkey or have been backed up here, the pharmacovigilance data will be regarded as transfer of personal data abroad even though these pharmacovigilance data are not seen outside Turkey.

Except circumstance where an adequate protection is provided for the rights of data subjects on the processing of personal data of the country or region receiving the data or, in more general terms, in case of failure to comply with the provisions stipulated in Article 9 of Law No. 6698, the transfer of personal data abroad shall be forbidden as a rule.

In case of absence of adequate protection in the country to which the personal data will be transferred, such personal data may be transferred abroad without seeking for the explicit consent of the relevant person provided that the data controllers in Turkey and the data controllers in the relevant foreign country commit in written an adequate protection and that permission is granted by the Personal Data Protection Board. In this case, the company should put in place the relevant arrangements to ensure an adequate protection for the processing of personal data. Furthermore, PDPB may introduce supplementary arrangements for the transfer of data abroad.

Personal data may be transferred abroad without seeking for the explicit consent of the relevant person to the countries regarded to be providing adequate protection outside Turkey, in accordance with the limitations laid down in Law No. 6698.

The current transfer solutions of companies should be reliable for the transfer of pharmacovigilance data. In case of absence of a current solution, the data should not be transferred abroad, or, otherwise;

  • A limit should be imposed on the transfers and access should be provided to the pharmacovigilance data only from Turkey, or
  • The data should be anonymized prior to the transfer. The same data protection principles apply for the administrative authorities outside Turkey, third parties with whom a legal cooperation is made and the organization to which data transfer is made. In order for personal data to become anonymized, the Guideline on the Deletion, Destruction or Anonymization of Personal Data, prepared by the Personal Data Protection Authority, may be utilized.

Section IV – Access, correction and objection rights

4.1. Access to personal data

The relevant person (data subject) is entitled to access pharmacovigilance data related with him/her with the same rights for accessing his/her other personal data.

4.2. Responding to the request for access of the relevant person

The relevant person should submit his/her request for access in written or via other methods to be designated by the Personal Data Protection Board to the data controller.

The requests of the relevant persons are evaluated as per Article 13 of Law No. 6698. Thus, the data controller finalizes the requests presented in the application free of charge within the shortest period and latest within thirty days according to the characteristics of the request. In case the application made to the data controller and the relevant transaction necessitates an extra fee, such fee should be paid in line with the provisions of the “Notification on the Application Procedures and Principles to the Data Controller”.

The data controller will accept the request or reject it by giving the relevant justification and will send his/her response to the relevant person in written or in electronic format. If the request presented in the application is accepted, the data controller will conduct relevant action.

A person is entitled to access only the personal data related to him/her. Therefore, companies should take reasonable steps for verifying the identity of the requesting person (A person may submit a request via a third person; in this case, the company should be convinced that the third party entitled to act on behalf of the relevant person). Provisions of Law No. 6698, the Regulation on Patient Rights and the Regulation on Personal Health Data, regarding sharing of pharmacovigilance data with the relatives and proxy of the relevant person.

The information presented should be understood by the person making a request; for instance, the technical terms and abbreviations should be described.

In case the data subject would like to use the rights stipulated in Article 11 of Law No. 6698, it is recommended that such application is managed by the Legal Department and/or the Data Protection Officer of the company or the person authorized to respond regarding this matter.

Reminder: In case reporting is made by a HCP, companies cannot avail of full identity of a patient. In such notifications, the request of the patient for access or correction should be fulfilled by the HCP.

4.3. Deletion, destruction or anonymization of personal data

Deletion, destruction or anonymization of personal data should be performed on the basis of provisions on Article 7 of Law No. 6698 and the provisions of the “Regulation on the Deletion,

Destruction or Anonymization of Personal Data”.

In case the reasons for processing are removed and there is no reason to preserve data for a long period, despite the fact that the data are processed in accordance with the provisions of other relevant laws, the personal data should be deleted, destroyed or anonymized by the data controller ex-officio or upon the request of the relevant person.

In case a person objects to the accuracy of the data kept regarding himself/herself, the referred information should be modified or deleted assuming that there is no reason to inquire the accuracy of the information.

The pharmacovigilance source document should not be destroyed even if requested by the data subject (except for any personal data which may lead to the detection of the identity of the data subject). These documents should be kept and not be modified.

The disposal processes of personal data should be conducted in line with the Personal Data Retention and Disposal Policy, prepared by the data controllers responsible for being registered in the Data Controllers’ Registry.

As per Article 28 of the Regulation on the Drug Safety pharmacovigilance data and documents related with drugs should not be disposed as long as the registration of the relevant drug preserves its validity and for at least 10 years following the end of validity of the registration.

4.4. Objection to processing of personal data

The data subject is entitled to object to processing of personal data in case processing of data leads to a major loss or issue or if there is such a possibility. If the processing transaction is conducted for the purpose of fulfilling a legal liability for pharmacovigilance, the company should explain why such a request cannot be met when responding to this request.

Companies should respond to data subject applications within 30 days upon receipt of the request. It should be explained in the response why the company will continue to process the personal data relating to that person in part or in full or how the request will be met.

For instance: Within the framework of laws, companies are obliged to collect minimum information associated with persons who have experienced adverse event or a potential adverse reaction that developed against their own drug for the purpose of inspecting the safety of their drugs.

Section V – Retention and correction of personal data

5.1. Retention of personal data

As per Law 6698, companies should not retain the personal data for a period longer than required for a data processing activity and should not be kept longer than required depending on intended purpose of processing of the data. Furthermore, personal data should be associated with the collection and/or intended purposes and be adequate, but they should not contain more information than required. Therefore, the data entered into the relevant databases associated with safety should be processed only for pharmacovigilance purposes and should not be processed for reasons other than those disclosed to the data subject with DPDS.

5.2. Correction of personal data

Companies should perform “data minimization” for duly performing the safety reporting activities; so, minimum amount of personal data should be designated. In case a company puts at risks the pharmacovigilance obligations of performing these transactions, an anonymization transaction should not be conducted, or the personal data should not be corrected.

5.3. Personal data relating to patients

When designating whether the personal data components will be corrected, companies should take into account if there is a just cause for keeping the data in the safety database (detection of duplicated transactions and implementation of follow-up activities).

Components recommended to be retained for an effective pharmacovigilance evaluation: Initials of the patient or case reference number, gender, date of birth, initial age/age group and adverse events, symptoms, outcome, duration, suspected drug, medical history, concomitant drugs

Components which are generally not mandatory for an effective pharmacovigilance and for which editing is recommended: Name of patient, contact information (address, telephone number, email address) and file number. Companies should consider removal of the components which are not necessary for source data (e.g.; with a black felt-tipped pen on the paper document; with the editing tool of Adobe Acrobat on screened documents in the records) and not enter the name and address information into the database. In case the patient is also the person who did the reporting or where there is a single source for obtaining the follow-up information, the retention of such information may be accepted.

5.4. Personal data of healthcare professionals

As it may be necessary to re-evaluate adverse events even if the follow-up activities are completed, it may be recommended to retain data such as the name and contact information of HCPs.

5.5. Sharing of safety data with business partners and suppliers

When an adverse event reporting is communicated to another company, only information which is reasonably required by the recipient and consistent with the purposes of the pharmacovigilance should be transferred. As indicated in Section 2.1, the DPDS should provide details to the recipients.

5.6. Retention period

It is indicated in Article 28 of the Regulation on Drug Safety that the pharmacovigilance data and documents related drugs should be retained as long as the registration of the relevant drug preserves its validity and for at least 10 years following the end of validity of the registration.

The source safety documents received from the sections other than pharmacovigilance and comprising the personal data retained in the databases should be managed by the pharmacovigilance department in the same manner.

Companies should designate the conditions for retaining the pharmacovigilance documents in the contracts signed with business partners and suppliers and it should be explained that the pharmacovigilance documents should not be destroyed without informing the other party.

Section VI – Reporting

6.1. Reporting

Real persons and legal entities processing personal data are obliged to be registered in the Data Controllers’ Registry, except for those who have been exempted. The scope of the referred exemption will be decided by the Personal Data Protection Board.

Including also the transactions performed for pharmacovigilance, a notification which encompasses all data processing activities of the company will be sufficient. Such registration should be made in line with the details made in clause three, Article 16 of Law No. 6698.

Application for registration in the Data Controllers’ Registry should be made with a notification containing the following aspects:

  • Identity and address details of the data controller and his/her representative, where applicable,
  • Purpose for which the personal data will be processed,
  • Explanation on the group and groups of the persons subject to data and the data categories of these persons,
  • Recipients or recipient groups to whom personal data may be transferred,
  • Personal data foreseen to be transferred to foreign countries,
  • Measures adopted in relation with the security of personal data,
  • Maximum period required for the purpose of processing personal data. Companies may provide a brief explanation such as the one provided below relating to the processing of relevant data associated with pharmacovigilance:

Collection of information on the adverse reactions of drugs from healthcare professionals and patients, their follow-up and evaluation.

Section VII – Sanctions

7.1. Sanctions

PDPB may conduct transactions directed at processing of data in line with Law No. 6698, ex- officio inspections or inspections conducted upon complaints may be conducted in relation with violations. PDPB is also entitled to impose an administrative fine on real persons who are data controllers and legal persons subject to private law. Illegal data processing activities may be penalized also with imprisonment sanction within the scope of Article 135 of the Turkish Penal law with No. 5237.

Selected Legislation:

Laws:

  • “Turkish Penal Code” dated 26/09/2004, with No. 5237
  • “Personal Data Protection Law”, dated 24/03/2016, with No. 6698

Regulations:

  • “Regulation on the Drug Safety , published on the Official Gazette dated 15/04/2014, with No. 28973
  • “Regulation on the Deletion, Destruction or Anonymization of Personal Data”, published on the Official Gazette dated 28/10/2017, with No. 30224
  • “Regulation on the Working Procedures and Principles of the Personal Data Protection Board”, published on the Official Gazette dated 16/11/2017, with No. 30242
  • “Regulation on the Data Controllers’ Registry”, published on the Official Gazette dated 30/12/2017, with No. 30286
  • “Regulation Amending the Regulation on the Deletion, Destruction or Anonymization of Personal Data”, published on the Official Gazette dated 28/04/2019, with No. 30758
  • “Regulation Amending the Regulation on Data Controllers’ Registry”, published on the Official Gazette dated 28/04/2019, with No. 30758
  • “Regulation on Personal Health Data”, published on the Official Gazette dated 21/06/2019, with No. 30808

Notification:

  • “Notification on the Working Procedures and Principles to be Complied with in the Fulfilment of the Disclosure Obligation”, published on the Official Gazette dated 10/03/2018, with No. 30356
  • “Notification on Procedures and Principles for Application to the Data Controller”, published on the Official Gazette dated 10/03/2018, with No. 30356.

Decision:

  • Decision dated 31/01/2018, with No. 2018/10 of the Personal Data Protection Board regarding the “Adequate Measures to be Adopted by Data Controllers in Processing of Sensitive Personal Data”
  • Announcement Regarding the Decision dated 24/01/2019, with No. 2019/10 of the Personal Data Protection Board on the Procedures and Principles Regarding Personal Data Reporting Violations
  • Decision dated 24.01.2019, with No. 2019/9 of the Personal Data Protection Board on the Calculation of the Periods for Application to the Data Controller and Complaint Filing to the Board
  • Decision dated 19/07/2018, with No. 2018/87 on the Personal Data Protection Board Regarding “Data Controllers to be Kept Exempt from Obligation to be Registered in the Data Controllers’ Registry”

Guideline and Handbook

  • “Good Pharmacovigilance Practices (GPP) Guideline, Module I – Management and Reporting of Adverse Drug Reactions”, published on 12/06/2014
  • Handbook on Security of Personal Data (Technical and Administrative Measures)
  • Deletion, Destruction or Anonymization of Personal Data
  • Handbook on Fulfillment of Disclosure Obligation
  • Handbook on Personal Data Processing Inventory

Annex – Samples of Data Protection Disclosure Statements

The following draft “data protection disclosure statement (DPDS)” is provided as an example; considering that special conditions may arise, relevant amendments on these upon receiving legal views on them.

Website

Data protection disclosure statement

We would like to provide information to you, as [NAME OF COMPANY], in accordance with Personal Data Protection Law, with No. 6698, on the collection and processing of your personal data in relation with our pharmacovigilance activities, as per Article 10 entitled “Disclosure Obligation of the Data Controller” of the referred Law, in the capacity of a Data Controller.

You may access detailed information on processing of your personal data within the scope of the Disclosure Statement from the Personal Data Protection and Processing Policy of [NAME OF COMPANY] located at the address [company website].

1. Purpose of Processing of Personal Data

Pharmaceutical companies are obliged to conduct activities for detecting, evaluating, defining and preventing adverse reactions (side effects) during drug use and other potential issues related with drugs. As a result of these activities named pharmacovigilance, it is possible to monitor drug safety and protect public health upon adopting a series of measures at national or international level, where necessary.

All personal data that reach our company in relation with adverse drug reactions and other pharmacovigilance activities are only used for pharmacovigilance activities. Your personal data are collected and processed in line with PDPL. We collect the name of the rapporteur, contact information and his/her occupation/affiliated organization during the pharmacovigilance activities. Where necessary, we may need to collect also additional personal data related with the medical history and health of the person who has experienced the adverse event during the processing of adverse events for pharmacovigilance purposes.

2. Parties to Whom Personal Data May Be Transferred and Purpose of Transfer

The information you will provide will be utilized for fulfilling the legal obligations foreseen in the legislation directed at monitoring of drug safety and may be shared with the Medicines and Medical Devices Agency of Turkey. These data may be entered upon being anonymized in the database of the World Health Organization within the scope of the Program for Drug Monitoring and Cooperation.

Our company may share the information you have provided us with our parent company, affiliated companies, business partners and service providers (suppliers, legally authorized institutes and organizations and legally authorized private legal entities) in order to process pharmacovigilance database and fulfill the requirements of pharmacovigilance legislation.

It is necessary for our company to report some pharmacovigilance data also to healthcare authorities in Europe and the rest of the world, including countries with differences in data protection levels. However, although these reports comprise detailed information on the event, they contain personal data at a limited level:

  • Patients: Information including the age or date of birth/year, gender and initials of the patient (the Name of the patient is not specified explicitly).
  • Rapporteur: Information such as name, occupation, initials, address, email and telephone number which enable the Authority to follow up the reporting person.

3. Personal Data Collection Method and Legal Reason

Your personal data are collected on paper or in an electronic environment. Your data relating to pharmacovigilance are processed on the basis of clause three, Article 6 of Law No. 6698, for protecting public health and for preventive medicine purposes; your personal data are processed within the scope of the “obligation to fulfill the legal obligation of the data controller”, stipulated in item (d), clause two, Article 5 of Law No. 6698.

4. Retention

As information on pharmacovigilance (adverse event reports) is important in terms of public health, it should be retained for a minimum period of 10 years following the withdrawal of the drug from last country where it is marketed.

5. Rights of Data Subjects

As per Article 11 of Law No. 6698, you are entitled for the following rights as a personal data subject:

  • To learn whether your personal data have been processed,
  • To request for relevant information in case personal data have been processed,
  • To learn the purpose of processing of your personal data and whether these have been utilized in line with the intended use,
  • To learn the third parties to whom your personal data are transferred domestically or abroad,
  • To request for correction in case your personal data have been processed deficiently or erroneously and for the communication of the transaction performed within this scope to the third parties to whom the personal data are transferred,
  • To request for the deletion or removal of your personal data in case the reasons necessitating processing no longer apply although these data are processed in line with Law No. 6698 and provisions of other relevant laws, and to request for the communication of the transaction performed within this scope to the third parties to whom the personal data are transferred,
  • To object to the emergence of a result against the relevant person upon analysis of your processed data exclusively via automatic systems,
  • To request for the compensation of the loss in case of incurrence of loss due to illegal processing of your personal data. However, as per the obligations of the pharmacovigilance legislation, our company may not delete the data processed for pharmacovigilance or not limit their processing.

In case you submit your requests regarding below-mentioned rights to [NAME OF COMPANY], located at the address [company website] as personal data subjects, via the methods indicated in the Personal Data Protection and Processing Policy, your requests will be evaluated and finalized by our Company as soon as possible and in any case within 30 (thirty) days.

Name and contact information of the data controller: Name, address of the company: Email: ……….

Telephone

The following shall apply when a department designed to receive adverse events responds to a call.

Tell the caller that he/she is reporting an adverse event and present a DPDS such as the one provided below before processing any personal data:

All the information and personal data you will share in this phone call will be protected and kept confidential in line with [COMPANY’S STANDARD OPERATING PROCEDURE or POLICY] and local regulations. The information you will provide will be utilized for drug safety monitoring purposes [and enable us to handle your request appropriately] and may be shared with health authorities. You are entitled to access your personal data which we are retaining. You may obtain detailed information from the “Personal Data Protection Disclosure Statement” presented on our website.

The other parties with whom the personal data are shared should be categorically specified in the PDPS.

In case the call is erroneously answered by other departments, the person responding the call should tell the caller that he/she is reporting an adverse event, that they are not the person they should talk to, but that they will ensure that they are called by the right person upon receiving certain details or that the call will be transferred. A DPDS should be provided in any circumstance where personal data are processed; this should be provided only once.

The calls may not be answered directly by the relevant department/person in smaller companies or affiliated offices. The person answering the call should tell the person making the call that he/she is reporting an adverse event, but that they will take note so that the right person may call them back.

A DPDS should be provided especially in the automatic voice messages answering the calls received outside working hours and the caller should be requested to confirm the following statement by leaving a message:

All the information and personal data you will leave in the voice message will be protected and kept confidential in line with [COMPANY’S STANDARD OPERATING PROCEDURE or POLICY] and local regulations. The information you will provide will be utilized for drug safety monitoring purposes [and enable us to handle your request appropriately] and may be shared with health authorities. You are entitled to access your personal data which we are retaining.

Email

A “Confirmation of Receipt” containing a DPDS should be sent via email to the sender. Companies may use the same automatic “Confirmation of Receipt” or DPDS outside working hours, upon specifying that this is an automatic response:

We have received your email. All the information and personal data you will share with us via email will be protected and kept confidential in line with [COMPANY’S STANDARD OPERATING PROCEDURE or POLICY] and local regulations. The information you will provide will be utilized for drug safety monitoring purposes [and enable us to handle your request appropriately] and may be shared with health authorities. You are entitled to access your personal data which we are retaining.

Face-to-face

Companies are obliged to train all their employees on what is an adverse event and what they need to do when an adverse event is reported. Employees should guarantee to their customers that their personal data will be handled appropriately:

All the information and personal data you have provided me today will be protected and kept confidential. The information you will provide will be utilized for drug safety monitoring purposes [and enable us to handle your request appropriately].

Digital media

There should be a DPDS such as the one provided below in the company supported (controlled) digital activities in which adverse events are reported via the “contact us” page or the “Adverse event reporting link”:

All the information and personal data you have shared with us upon your request for information will be protected and kept confidential in line with [COMPANY’S STANDARD OPERATING PROCEDURE or POLICY] and local regulations. The information you have provided will be utilized for drug safety monitoring purposes [and enable us to handle your request appropriately] and may be shared with health authorities. You are entitled to access your personal data which we are retaining.

This announcement may be placed on the home page of the website or appear as a pop-up prior to the reporting of the adverse event via the website.

Websites not supported (controlled) by the company: Companies may not place a DPDS on a website they do not control. However, any message received from a website not supported by the company and containing contact information should be handled as a message sent via e-mail.

Requests/reporting on products not belonging to the company

Companies are not obliged to provide information on the products not included into their own product portfolio. It is up to the company to decide on how its employees will handle such requests. Companies may assist the callers by providing them the contact information of the relevant company.

Follow-up of pharmacovigilance data

A DPDS will be required in all correspondences made with the reporting person. The following announcement may be added to company-specific follow-up request forms or adverse event forms sent to and to be completed by the reporting person:

All the information and personal data you have shared with us will be protected and kept confidential in line with [COMPANY’S STANDARD OPERATING PROCEDURE or POLICY] and local regulations. The information you have provided will be utilized for drug safety monitoring purposes [and enable us to handle your request appropriately] and may be shared with health authorities. You are entitled to access your personal data which we are retaining.

More guidelines