| Literature DB >> 35629080 |
Pekka Ruotsalainen1, Bernd Blobel2, Seppo Pohjolainen1.
Abstract
The use of eHealth and healthcare services are becoming increasingly common across networks and ecosystems. Identifying the quality and health impact of these services is a big problem that in many cases it is difficult determine. Health ecosystems are seldom designed with privacy and trust in mind, and the service user has almost no way of knowing how much trust to place in the service provider and other stakeholders using his or her personal health information (PHI). In addition, the service user cannot rely on privacy laws, and the ecosystem is not a trustworthy system. This demonstrates that, in real life, the user does not have significant privacy. Therefore, before starting to use eHealth services and subsequently disclosing personal health information (PHI), the user would benefit from tools to measure the level of privacy and trust the ecosystem can offer. For this purpose, the authors developed a solution that enables the service user to calculate a Merit of Service (Fuzzy attractiveness rating (FAR)) for the service provider and for the network where PHI is processed. A conceptual model for an eHealth ecosystem was developed. With the help of heuristic methods and system and literature analysis, a novel proposal to identify trust and privacy attributes focused on eHealth was developed. The FAR value is a combination of the service network's privacy and trust features, and the expected health impact of the service. The computational Fuzzy linguistic method was used to calculate the FAR. For user friendliness, the Fuzzy value of Merit was transformed into a linguistic Fuzzy label. Finally, an illustrative example of FAR calculation is presented.Entities:
Keywords: Fuzzy attractiveness rating; antecedents; modelling; privacy; trust
Year: 2022 PMID: 35629080 PMCID: PMC9147882 DOI: 10.3390/jpm12050657
Source DB: PubMed Journal: J Pers Med ISSN: 2075-4426
Figure 1Phases of the study.
Figure 2A conceptual model of the eHealth ecosystem.
Specific features of eHealth ecosystems.
| Highly sensitive health-related data (e.g., diseases, symptoms, social behavior, and psychological features) are collected, used and shared |
| Healthcare-specific laws regulate the collection, use, retention and disclosure of PHI |
| To use services, the user must disclose sensitive PHI |
| Misuse of PHI can cause serious discrimination and harm |
| Service provided is often information, knowledge or recommendations without quality guarantee or return policy |
| The service provider can be a regulated or non-regulated healthcare service provider, wellness-service provider or a computer application |
| Service user can be a patient, and there exists a fiducial patient–doctor relationship |
Figure 3Calculation of the Merit of eHealth service.
Typical sources for privacy and trust attributes from [7,54,88,89,90,91,92,93,94,95,96,97].
| Direct measurements, experiences, interactions and observations |
| Service provider’s privacy policy document |
| Content of privacy certificate or seal for the medical quality of information, content of certificate for legal compliance (structural assurance), andaudit trial (transparency). |
| Past experiences, transaction history, previous expertise |
| Information available on service provider’s website |
| Provider’s promises and manifestations |
| Others recommendations and ratings, expected quality of services |
| Information of service provider’s properties and information system |
| Vendor’s type or profile (similarity information) |
Selected privacy attributes and their possible values.
| Name | Meaning of Attribute | Value = 2 | Value = 1 | Value = 0 |
|---|---|---|---|---|
| P1 | PHI disclosed to third parties | No data disclosed to third parties | Only anonymous datais disclosed | Yes/no information |
| P2 | Regulatory Compliance | Compliance certified by experts third-party privacy seals | Demonstrated regulatory complianceAvailable | Manifesto or no information |
| P3 | PHI Retention | Kept no longer than necessary for purposes of collection | Stored in encrypted form for further use | No retention time expressed |
| P4 | Use of PHI | Used only for presented purposes | Used for other named purposes | Purposes defined by the vendor |
| P5 | User access to collected PHI | Direct access via network | Vendor made document of collected PHI is available on request | No access or no information available |
| P6 | Transparency | Customer has access to audit trail | No user access to audit trail | No audit trail or no information |
| P7 | Ownership of the PHI | PHI belongs to DS (user) | Shared ownership of PHI | Ownership of PHI remains at vendor or no information |
| P8 | Support of SerU’s privacy needs | SerU’s own privacy policy supported | Informed consent supported | No support of DS’ privacy policies or no information |
| P9 | Presence of organisation | Name, registered office address, e-mail address and contact address of privacy officer available | Name, physical address, e-mail address available | Only name and e-mail address available |
| P10 | Communication privacy | End-to-end encryption for collected PHI | HTTPS is supported | Raw data collected or no information |
Selected trust attributes for FAR calculation.
| Name | Attribute | Meaning | Sources |
|---|---|---|---|
| T1 | Perceived Credibility | How SerP keeps promises, type of organisation, external seals, ownership of organisation | Previous experiences, website information |
| T2 | Reputation | General attitude of society | Websites, other sources |
| T3 | Perceived competence and professionalism of the service provider | Type of organisation, qualification of employees/experts, similarity with other organisations | Website information, external information |
| T4 | Perceived quality and professionalism of health information | General information quality and level of professionalism, quality of links and scientific references | Own experience, third party ratings, other’s proposals, website information, |
| T5 | Past experiences | Overall quality of past experiences | Personal past experiences |
| T6 | Regulatory compliance | Type and ownership of organisation. Experiences how the SerP keeps its promises | Websites, oral information, social networks and media. Previous experiences |
| T7 | Website functionality and ease of use | Easy to use, usability, understandability, look of the website, functionality | Direct experiences |
| T8 | Perceived quality of the information system | Functionality, helpfulness, structural assurance, reliability (system operates properly) | Own experiences, others recommendations |
Figure 4Used membership function and labels.
Privacy and trust ratings and EXPHI value example.
| P1 = 0. | P2 = 0 | P3 = 0 | P4 = 1 | P5 = 0 | P6 = 0 | P7 = 0 | P8 = 0 | P9 = 1 | P10 = 1 |
|---|---|---|---|---|---|---|---|---|---|
| T1 = M | T2 = MH | T3 = ML | T4 = M | T5 = H | T6 = L | T7 = H | T8 = M | EXPHI = M |
Linguistic values for calculation of FAR.
| Factor | Fuzzy Value | Fuzzy Weight |
|---|---|---|
| Privacy | L (0.0, 0.17, 0.33) | VH (0.8, 1, 1) |
| Trust | (0.375, 0.54, 0.71) | H (0.6, 0.8, 1) |
| EXPHI | M (0.33, 0.5, 0.67) | M (0.4, 0.6, 0.8) |
|
|
|
Privacy Needs and Requirements In Policy Documents and Law from [95,102,103,104,105,121].
| Privacy Needs/Questions | Meaning in a Privacy | Requirements Exressed by Law (General Data Protection Regulation, EU GDPR) 1 |
|---|---|---|
| PHI used only for purposes defined by the service provider | How and why a service provider collects and uses PHI | Limited by what is necessary in relation to purpose. Explicit purpose |
| PHI not disclosed to third parties | What data and how PHI is shared with third party | Personal policiesTransparency |
| Regulatory compliance | Level Regulatory compliance | Lawfully processing Demonstrate regulatory compliance |
| What is the content of a personal privacy policy? | Edit and deletion | Erase, right to become forgotten, right to object processing, explicit purpose |
| What are the service provider’s characteristics? | Type of organisation address | |
| Encryption | Communication privacy | Encryption |
| How PHI is stored for future use | Data retention (stored as long as needed to perform the requested service/indefinitely) | Retention no longer than necessary for purpose |
| User access to audit trail | What data is shared/transparency | Lawfully processing and transparency |
| User access to own PHI | User access, rights to view records | Access to collected PHI. Right to erase and object processing |
| How personal privacy needs are supported | User choice/control | Accept personal privacy policies/explicit consent |
| Does PHI belongs | Ownership of data | The individual owns the rights to their data |
| Does a registered office | Contact information | |
| Privacy guarantees | Third-party seals or certificates | |
| Transparency | Transparency | Right to become informed |
1 The General Data Protection Regulation (GDPR) is an EU-wide privacy and security law put into effect on 25 May 2018.