PARTNERSHIP AGREEMENT
FOR THE IMPLEMENTATION OF PROJECT FROM THE NORWEGIAN
FINANCIAL MECHANISM
UPON APPLYING FOR AND USING THE GRANT
Tallinn, “01” February 2021.
Estonian Ministry of Social Affairs (hereinafter “Applicant of the Grant”) person having the
right of representation,
University of Tartu (hereinafter “Project Partner 1”) person having the right of representation,
hereinafter individually or collectively also referred to as “Applicant of the Grant” / “Project
partner” or “Project partners” or “Parties”,
based on the project’s objective:
- Development of data obfuscation toolkit
o Data audit, based on example data and queries. Data classification based on
sensitivity and use cases.
o Analysis of relevant privacy measures (e.g. k-anonymity, l-Diversity, t-
Closeness, differential privacy, local and global sensitivity, etc.). Determine
the minimal set of measures that are needed to quantify and assure the
required level of privacy.
o Analysis of relevant utility measures. Determine the set of utility measures to
avoid data bias after obfuscation.
o Develop obfuscation methods. Result will be based on PostgreSQL database.
o Optimization, based on example data queries, finding optimal balance of
privacy and utility.
o Building a software application based on the methods. Project partners agree
that the user experience of the software is not the primary priority in this
project and will be improved in next projects. Documentation.
o Test and delivery of the software.
for the implementation of which the grant applicant applies for a grant from Enterprise Estonia
(hereinafter “Enterprise Estonia”) from the programme funded by the Norwegian Financial
Mechanism – NORWAY GRANTS PROGRAMME “GREEN ICT” (hereinafter “Programme”),
have entered into this cooperation agreement (hereinafter “Agreement”) to carry out the project
under the conditions established below:
1. General provisions
1.1 This Agreement establishes binding cooperation principles to carry out project “Health
Sense” (hereinafter “Project”) (hereinafter “Objective of the Agreement”):
1.2 Based on this Agreement, the Project partners are obligated to perform acts, carry out work,
and cover costs agreed to achieve the Objectives of the Agreement and perform the
Agreement.
1.3 Upon performing the Agreement, the Parties are guided by this Agreement, the Documents of
the Agreement provided in clause 3 of the Agreement, and the Programme documents in case
of issues not regulated in the Agreement, and legislation in force in the Republic of Estonia.
1.4 By concluding this Agreement, other Partners authorise the Applicant of the Grant to apply
for a grant on behalf of them as part of the Programme, submit the required data and
documents to Enterprise Estonia, and also perform other obligations provided in the
Documents of the Agreement on behalf of the Project partner.
1.5 Software developed in this project is licensed under GPLv2 (or any later version) license,
unless otherwise agreed by the Parties.
1.6 Unless stipulated otherwise in the Agreement, intellectual property rights of the results of the
Project shall be owned by the Party generating it. When results are generated jointly, it shall
be jointly owned, unless the Parties in question agree on a different solution. The method of
defining joint ownership shall be based on their contributing efforts towards the result in
shares proportionate to their scope of work/budget for that result.
After completion of the Project and termination or expiration of the Agreement, a Party shall
have the non-exclusive, royalty-free right to use, modify, copy, transfer or make derivative
results of the Project generated by another Party. These rights of shall not be limited with
regard to certain rights or to the purpose, term, territory, extent, manner or means of using the
results of the Project.
In case of joint ownership, each of the joint owners shall be entitled to exploit the joint results
as it sees fit, and to grant non-exclusive licenses, without obtaining any consent from, paying
compensation to, or otherwise accounting to any other joint owner, unless otherwise agreed
between the joint owners. The joint owners shall agree on all protection measures and the
division of related cost in advance.
2. Entry into force and term of the Agreement
2.1. The Agreement enters into force from the moment of signing by the Project partners and is
binding on the Partners provided that the Application of the Programme is approved and
Enterprise Estonia concludes the Project Agreement with the Applicant of the Grant.
2.2. The Agreement is valid until the objectives of the Agreement are achieved and the obligations
arising from the Agreement are performed.
3. Documents of the Agreement
3.1. The performance of the Agreement is based on, and as part of the Agreement, the Parties are
obligated to comply with the requirements and obligations arising from the following
documents (hereinafter “Documents of the Agreement”), and in case of any conflicts
between the Documents of the Agreement, their order of competence is the following from
the most important one:
3.1.1. Agreement between the Kingdom of Norway and the European Union on a Norwegian
Financial Mechanism for the period 2014–2016, concluded on 28 May 2016;
3.1.2. “Implementing Regulation of a Norwegian Financial Mechanism” adopted by the
Norwegian Ministry of Foreign Affairs on 23 September 2016;
3.1.3. Memorandum of Understanding between the Republic of Estonia and the Kingdom of
Norway on the implementation of a Norwegian Financial Mechanism for the period
2014–2020 concluded on 9 May 2017;
3.1.4. Programme Agreement between the Estonian Ministry of Finance and the Kingdom of
Norway concluded on 26 April 2018 and its Annexes;
3.1.5. Regulation of the Government of the Republic “Conditions and Procedure for applying
and using the funds from the financial mechanism of the European Economic Area
and the financial mechanism of Norway from 2014–2021”;
3.1.6. Approved by the Management Board of Enterprise Estonia – Programme procedure of
the Norway Grants programme “Green ICT” and its Annexes;
3.1.7. A resolution of the Management Board of Enterprise Estonia on the approval of the
application submitted by the Applicant of the Grant and its Annexes;
3.1.8. This Agreement and its Annexes;
3.1.9. An application submitted to Enterprise Estonia by the Applicant of the Grant and its
Annexes;
3.1.10. The Project contract to be concluded by the Applicant of the Grant.
3.2. A reference to the Agreement also covers the Documents of the Agreement, unless otherwise
established in the wording or content of a specific clause of this Agreement.
4. Cooperation principles
The Project partners agreed to make every effort to achieve the objectives of the Project.
4.1. The obligations of the Partners in carrying out the Project:
4.1.1. Applicant of the Grant is obligated to carry out the following activities:
4.1.1.1.Consult Project partner on the topics described in the Objective of the
Agreement.
4.1.1.2.Provide sufficient amount of representative example data, data queries, and
use cases of the data queries to Project partner for their tasks described in
Annex 1. Requirements for example data are given in Annex 2. Example
data is given to Project partner by the end of the second month of the
project.
4.1.1.3.Acquire technical guidelines and methodology about minimal set of privacy
measures from Statistics Estonia (Statistikaamet) and share them with
Project partner.
4.1.1.4.Organize four to five co-ordination meetings to present the results of the
work of all Parties.
4.1.2. Project partner 1 is obligated to carry out the following activities
4.1.2.1. Build a software for data obfuscation and deliver it to Applicant of the
Grant. The scope and details of the work are described in Annex 1.
4.1.2.2.Exchange work results with Applicant of the Grant.
4.2. Total project budget is 2 000 000 euros and the financing sources are the following:
4.2.1. Grant applied from the Programme in the amount of 1 000 000.00 euros;
4.2.2. Co-financing of the Applicant of the Grant in the amount of 1 000 000.00 euros;
4.2.3. Co-financing of Project partner 1 in the amount of 0.00 euros.
4.3. Project financing is used as follows:
4.3.1. The grant and own contribution and co-financing can only be used to cover eligible
costs established in the Programme procedure according to the conditions set out in the
Project contract and the Programme procedure.
4.3.2. Eight to ten two-day consultation sessions within two years:
4.3.2.1. Initial meeting session one month after the start of the "Health Sense"
project; costs are paid from the Grant applied from the Programme.
4.3.2.2. Six to eight co-ordination meetings for sharing work results between the
parties; costs are paid from the Grant applied from the Programme.
4.3.2.3. Closing meeting session at the end of “Health Sense” project to make
conclusions and to share achieved results; costs are paid from the Grant
applied from the Programme.
4.3.2.4. The costs of the consultation are covered by the consulting parties.
4.4. Project partners cover the project-related costs themselves by using bank transfers to make
payments.
4.5. The eligible costs of the project partners based on the report submitted after every four months
by the Applicant of the Grant are compensated by Enterprise Estonia to the bank account after
the payment application has been approved by the Applicant of the Grant.
4.6. The Applicant of the Grant is obligated to transfer the share of costs made by the Project
partner to the Project partner’s bank account within a reasonable period of time after
Enterprise Estonia has made the transfer.
4.7. If treatment of personal data by Project partners is necessary to fulfil the goals of the Project,
then Parties follow the rules of General Data Protection Regulation (GDPR) and other relevant
legal acts.
5. Obligations of Project partners
Upon receiving a grant, the Project partners are obligated:
5.1. to ensure own contribution or co-financing to the minimum extent provided in the Agreement;
5.2. to carry out the project according to the terms and conditions fixed in the application, the
Project contract, and the Agreement;
5.3. to use the grant and own contribution and co-financing according to the Objective of the
Agreement and in compliance with the grant application, the decision to approve the
application, the Programme procedure, and the Project contract;
5.4. to bear eligible costs related to the project during the eligibility period of the Project;
5.5. The Applicant of the Grant is obligated to prepare the project reports according to the
conditions and forms established in the Project contract, and other Project partners are
obligated to give the required information and documents to the Applicant of the Grant, if
necessary.
5.6. to immediately inform each other of circumstances that influence or may influence the
performance of the Agreement and prevent the achievement of the objectives established in
the Agreement;
5.7. not to change the Project. The Project partners have the right to change the Project only after
a previous agreement between all Project partners and with the consent of Enterprise Estonia;
5.8. to enable Enterprise Estonia to supervise the performance of the Project and the costs related
to the Project, and provide comprehensive assistance to this end, including submit data to
Enterprise Estonia in case of the corresponding claim and within the established time period,
and allow persons who carry out supervision to be present in the rooms and on the territory
related to the implementation of the Project;
5.9. to provide assistance to quickly conduct control, audit, and supervision, and give all required
data and documents to the person conducting the control within 3 (three) business days of
receiving the corresponding notice;
5.10. to make a clear distinction between the costs borne as part of the Project and the expense
receipts and payment documents reflecting these costs from other expense receipts and
payment documents by means of a separate accounting system or codes according to the
accounting practices established in the Accounting Act;
5.11. to store the original documentation related to the performance of the application, grant, and
Project at least until 31 December 2030;
5.12. to ensure that the costs borne as part of the Project comply with the requirements of
applicable legislation;
5.13. to indicate while using the grant that this is a Project funded from the Norwegian financial
mechanisms;
5.14. in case of a grant recovery claim, the Project partner is obligated to pay this part of the
claim, which has arisen from the Project partner’s activities (if the costs borne by the Project
partner do not comply with the eligibility rules, etc.);
5.15. to comply with all relevant national and European Union legislation.
6. Liability of Project partners
6.1. The Project partners bear full proprietary liability for any material damage caused to the other
Project partners by failure to perform the obligations arising from the Agreement duly or at
all.
6.2. All Project partners are liable for proper performance of the Agreement.
6.3. In case of a claim to recover the grant, the repayment is the responsibility of the Applicant of
the Grant who has the right to claim the corresponding amount from the Project partner, whose
activity causes such claim to recovery.
7. Notices between Project partners
7.1. Any notices between the Project partners in relation to the Agreement should be at least in the
form that can be reproduced in writing (email), except in cases where such notices are
informative and their forwarding to the other Project partners has no legal consequences.
7.2. An informative notice may be transferred by telephone.
8. Final provisions
8.1. The Project partners confirm that they have all the powers, consents, and approvals arising
from the legislation for entering into the Agreement and performing the obligations arising
therefrom.
8.2. Entering into the Agreement does neither exceed nor violate:
8.2.1. the competence of the Project partners;
8.2.2. any provisions of the law applicable to the Project partner;
8.2.3. any clause or obligations arising from the Agreement or other agreement applicable to
the Project partner;
8.2.4. requirements of any judgments or court rulings made prior to entering into the
Agreement and binding on the Project partner.
8.3. The Agreement establishes legitimate, valid, and binding obligations for the Project partners
in order to ensure that conditions of the Agreement are performed in a timely, appropriate,
and comprehensive manner.
8.4. The Agreement with its Annexes forms an integral and comprehensive agreement between
the Project partners, replacing all previous written or oral agreements between the same
Project partners.
8.5. Any amendments and modifications to the Agreement enter into force upon their signing by
the Project partners at the moment of signing, or within the time limit established in writing
by the Project partners.
8.6. The Project partner is not allowed to transfer the rights and obligations arising from the
Agreement to a third party without the prior written consent of the other Project partners and
Enterprise Estonia.
8.7. The Project partners are obligated to keep confidential information given from one Project
partner to another and refrain from disclosing this information to third persons without a
previous written consent from the Project partner who has disclosed such information.
8.8. The Project partners are obligated to behave in accordance with the principles of
reasonableness and good faith. Any disagreements and disputes arising from the performance,
interpretation, amendment or termination of the Agreement are resolved by the Project
partners through negotiations based on mutual understanding. In case of failure to reach an
agreement, these are settled in Harju County Court based on the current legislation of the
Republic of Estonia.
8.9. The Project partners should be ready to conduct all necessary activities through web channels
(without physical contact) and have access to digital solutions that enable these activities.
8.10. If during performance of the Agreement the pandemic of COVID-19 continues or occur
other public health and safe living environment issues that impede conducting the activities
necessary for fulfilling the Objective of the Agreement, the Project partners have the right to
change the timeline or tasks described in the Agreement.
8.10.1. Project partner 1 is obligated to submit the request with explanations and justifications
to the Applicant of the Grant that specifies which tasks are possible to conduct in the
agreed timeline and which tasks should be postponed.
8.10.2. New timeline for the tasks that are impeded because of the virus spread or related
restrictions will be agreed by the Project partners within 30 days after the end of the
restrictions.
8.11. The prohibitions and restrictions that are in place for stopping the spread of COVID-19 at
the moment of signing the Agreement are not considered force majeure, because all the
restrictions are known to Project partners and should be considered when planning the
activities of the Project. If additional restrictions are imposed to stop the virus outbreak that
hinder the fulfillment of the Objectives of the Agreement, then Project partners have the right
to rely on force majeure.
Annexes to the Agreement:
Annex 1. Problem scope, tasks and deliverables
Applicant of the Grant Marika Priske
Estonian Ministry of Social Affairs /name, signature/
Registry code 70001952
Suur-Ameerika 1, 10122 Tallinn
Tel +372 626 9301
Email
[email protected]
Project partner 1 Taivo Raud
Name University of Tartu /name, signature/
Registry code 74001073
Ülikooli 18, 50090 , Tartu
Tel +372 737 5100
Email
[email protected]
Account number: EE281010102000234007
Annex 1. Problem, scope, tasks and deliverables.
Problem description
Applicant of the Grant manages large quantities of health data, but their use for research is
limited, due to sensitivity of the data. There is a risk that due to the amount of details in the data,
some individuals could be identified. Therefore, a software tool is needed for applying obfuscation
methods on the data, so that detecting particular individuals would be much more difficult.
Goal
In this Project, a software for conducting data obfuscation is developed.
Scope
The following assumptions are made:
All input data is given in a single table format, no free text columns/fields.
Persons are already pseudonymized in input data (the obfuscation will not be applied to
pseudonyms)
The (obfuscated) result of data query is a single table
The privacy has to be preserved in the context of single result table (if one combines several
result tables, the privacy could be affected)
At least the following obfuscation methods are in the interest in this project (will be
investigated):
o Replacing exact date with year or range of years or year and month or year and
quarter or “unique value”
o Replacing exact address with settlement, city or county level data, “unique” or “not
answered (NA)”
o Replacing exact diagnosis/drug/other hierarchical classifier code with upper level
code or “unique value”
o Replacing value from non-hierarchical classifier with “unique value”
Tasks
Task 1. Data audit, based on example data and queries. Data classification based on sensitivity
and use cases.
Task 2. Analysis of relevant privacy measures (e.g. k-anonymity, l-Diversity, t-Closeness,
differential privacy, local and global sensitivity, etc.). Determine the minimal set of measures
that are needed to quantify and assure the required level of privacy.
Task 3. Analysis of relevant utility measures. Determine the set of utility measures to avoid data
bias after obfuscation.
Task 4. Develop obfuscation methods. Result will be based on PostgreSQL database.
Task 5. Optimization, based on example data queries, finding optimal balance of privacy and
utility.
Task 6. Building a software application based on the methods. Project partners agree that the
user experience of the software is not the primary priority in this project and will be improved in
next projects. Documentation.
Task 7. Test and delivery of the software.
Timeline
Deliverables
Estimated total reimbursement for University of Tartu: 454 260 euros (including 15% indirect
costs).
Month 4 – Data audit (document), describes the data, aggregation levels and sensitivity.
Description and reasoning of selected set of privacy measures and utility measures (document).
Estimated amount of work: 8 PM. Reimbursement for University of Tartu: 75710 euros
(including 15% indirect costs).
Month 8 – Initial set of SQL scripts for data obfuscation (SQL-files with description).
Estimated amount of work: 8 PM. Reimbursement for University of Tartu: 75710 euros
(including 15% indirect costs).
Month 12 – First prototype of the obfuscation software delivered (application files with source
code, installation manual).
Estimated amount of work: 8 PM. Reimbursement for University of Tartu: 75710 euros
(including 15% indirect costs).
Month 16 – Improved set of SQL scripts for data obfuscation (SQL-files with description).
Estimated amount of work: 8 PM. Reimbursement for University of Tartu: 75710 euros
(including 15% indirect costs).
Month 20 – Beta-version obfuscation software delivered with necessary documentation
(application files with source code, installation manual, user manual).
Estimated amount of work: 8 PM. Reimbursement for University of Tartu: 75710 euros
(including 15% indirect costs).
Month 24 – Final version of obfuscation software delivered with necessary documentation
(application files with source code, test report, installation manual, user manual).
Estimated amount of work: 8 PM. Reimbursement for University of Tartu: 75710 euros
(including 15% indirect costs).
Annex 2. Requirements for example data
Example data must well represent the data that will be later used for obfuscation from the point
of structure, content and size. A number of example datasets are highly recommended. These
will be directly used for prototyping and testing the software.
From the perspective of data structure, at least two kinds of structures are expected:
1. Narrow format – each row in the data table represents one event. Typical columns are:
patient ID, date/datetime, event type, event ID
2. Wide format – each row in the data table is one patient, each column is a separate feature
(diagnosis, drug, etc.).
From the perspective of data types, at least the following data types are required:
1. Patient ID (pseudonym for linking data of the same patient)
2. Date
3. Diagnosis
4. Drug
5. Address
We expect that the example data is in CSV/TSV (comma-separated or tab-separated values)
format.