In Poland the key requirements for data protection and data security are set out in the EU General Data Protection Regulation (2016/679) (“GDPR”); and the Act on Processing Personal Data dated 10 May 2018, which brings the Polish legal system in line with the requirements of the GDPR.
Under the above regulations, the following requirements are essential for DTx solutions:
- Data minimisation and purpose limitation – DTx may only collect personal data that is strictly necessary for its functions.
- Privacy by design and by default - The privacy implications of the application/software should be considered at every stage of its development and wherever the user is given a choice. The application/software developer should pre-select the least privacy-invasive choice by default.
- Personal data breach and security measures: As DTx apps processes a high amount of sensitive personal data, a potential data breach can be a major threat for the person concerned. Therefore, DTx owners should be particularly aware of the obligations related to data breaches, such as notification to the authority (in Poland: Urząd Ochrony Danych Osobowych - UODO) and to the data subject - which may mitigate the risk for DTx users.
In addition, DTx software/application providers should implement technical and organisational measures to ensure the confidentiality, integrity and availability of the personal data processed and to protect it against accidental or unlawful loss, access or other unlawful forms of processing. This requirement is of particular importance in Poland, as the UODO's decision-making practice has shown its increased imposition of fines for violations consisting of insufficient technical and organisational measures to ensure information security and insufficient fulfilment of data breach notification obligations. The summary of the most crucial cases is available in our CMS GDPR tracker, which you can find here.
- Profiling - In most DTx, a precise health and/or behavioural profile of the person is created for the solution to work. This practice may entail risks of constant monitoring or the possibility of reusing patient profiles. The DTx developer should therefore take into account the GDPR rule on profiling, e.g. specific legal bases for profiling or that profiling should not be applied to children.
- Data subject rights and information requirements - DTx should be designed in such a way as to ensure that the user can exercise her/his data protection rights, e.g. to access personal data or to request the correction of data. Also, the app/software provider needs to explain to the user how it will use her/his personal data.
The mobile apps providers should also pay attention to UODO’s Sectoral Inspection Plan for 2023 (“Plan”). According to this Plan, and similarly to last year, UODO intends to focus its inspections on how companies secure and share personal data processed within mobile and web apps. These inspections might be crucial, especially given the rapid growth of the mobile application market being used in every conceivable area of our lives.
Additionally, in Poland there are various sector regulations that may regulate the processing of data within DTx technology:
- The Act of 18 July 2002 on Electronically Supplied Services (“ESS Act”):
- The ESS Act sets out the rules for protecting personal data of natural persons using Electronically Supplied Services, e.g. the scope of personal data that a service provider may request to provide a service, or consent requirements for sending commercial information.
- The Act of 16 July 2004 – Telecommunications Law (“Telco Law”):
- The Telco Law applies in particular to the storage of or gaining access to information already stored in telecommunications terminal equipment (e.g. a smartphone) of a subscriber or end user.
- The Act of 6 November 2008 on Patient’s Rights and on the Patient Ombudsman (“Act on Patient’s Rights”):
- The Act on Patient’s Rights sets out the rules for outsourcing that apply to healthcare entities in addition to those stemming from the GDPR. Given that digital health software providers may be considered as data processors, they could be contractually obliged to comply with those requirements.
Please note that other regulations may apply in relation to specific healthcare services. Nevertheless, the above requirements provide a baseline that any company should consider both in the development process and in the actual use of this type of application/software.