5. Security ans Anonymization

Documentation Moderators Guide
1

5. Security and Anonymization

5.1 Protocol for Verifying the Anonymization of Clinical and Sensitive Data
5.2 Management of Roles and Access Permissions

5.1 Protocol for Verifying the Anonymization of Clinical and Sensitive Data

The anonymization of clinical and sensitive data is essential to comply with regulations such as the GDPR and to ensure the privacy of the individuals involved. This protocol provides a comprehensive checklist to verify that data has been properly anonymized before being published on the platform.

Checklist for Data Anonymization

  • Verification of Directly Identifiable Data

    • Names and surnames: No names, initials, nicknames, or unique identifiers directly associated with a person are present.

    • Addresses: Full or partial addresses, including streets, numbers, postal codes, or small towns, have been removed.

    • Phone numbers: No phone numbers, whether full or partial, are present.

    • Email addresses: Personal or professional email addresses have been removed.

    • Specific identifiers: No personal identification numbers, such as national ID, passports, medical record numbers, or social security numbers, are included.

  • Verification of Indirectly Identifiable Data

    • Relevant dates: Specific dates related to an individual (e.g., birth date, admission date, discharge date) have been generalized or removed.

      • Example: Convert “March 23, 1985” to “March 1985” or “Spring 1985.”

    • Geographic locations: No geographic locations smaller than state or regional levels are mentioned.

      • Example: Replace “Madrid Hospital” with “Regional Hospital.”

    • Unique characteristics: Descriptions that could identify a person, such as specific occupations, rare medical conditions, or anecdotal details, have been removed.

  • Verification of Data Related to Images or Attachments

    • Medical images:

      • Do not contain visible labels with identifiable information (e.g., name, date, ID).

      • Metadata has been reviewed to ensure it does not include sensitive information (use editing tools to clean metadata).

    • Documents and reports:

      • All reports have been reviewed to remove headers, footers, or comments that may contain identifiable information.

      • Exported documents do not contain hidden information in metadata or comments.

  • Verification of Context and Additional Sensitive Data

    • Explicit consent: If clinical cases or individual results are mentioned, it has been confirmed that there is no direct or indirect link to the described person, and that data usage is authorized per the organization’s policies.

    • Avoid re-identification through data combination: Verify that data cannot be combined with external information to re-identify the individual.

      • Example: “Male patient, 45 years old, with a rare disease treated in March 2023” may be identifiable when combined with public data.

      • Solution: Generalize the data further, such as “Male patient, adult, with a rare condition treated recently.”

  • Final Review and Anonymization Testing

    • Independent review: An additional moderator or administrator reviews the data to detect identifiable information the original author may have overlooked.

    • Re-identification tests: Evaluate whether a third party could identify someone using only the published information.

      • If the answer is “yes,” make further adjustments to eliminate risks.

Additional Steps to Ensure Compliance

  • Document the process: Maintain a record of the anonymization process, indicating what data was modified or removed.

  • Communicate policies: Provide clear guides to users on how to anonymize data before publication.

5.1 5.2 Management of Roles and Access Permissions

The management of roles and access permissions is a key tool for ensuring security and privacy within the community. While administrators have primary control over role configuration, the moderator plays a vital role in supervising and collaborating to ensure that permissions align with platform policies.

Actions Moderators Can Take to Ensure Security:

  • Supervision of Assigned Permissions

    • What to do: Regularly review user permissions in the categories managed by the moderator to ensure there are no improper or inconsistent accesses.

    • How to:

      • Request periodic reports from administrators on assigned permissions.

      • Verify if users with access have appropriate roles based on their trust level or community function.

      • Notify administrators of inconsistencies or unnecessary accesses.

  • Management of Specific Groups

    • What to do: Oversee user groups interacting within the moderated category, especially those with access to sensitive information.

    • How to:

      • Review requests to join closed groups and ensure users meet access criteria.

      • Propose the creation of specialized groups with permissions tailored to specific needs (e.g., external collaborators, clinical researchers).

      • Ensure groups are regularly updated to include or exclude members as needed.

  • Monitoring of Suspicious Activity

    • What to do: Identify unusual behaviors that may indicate misuse of permissions, such as unauthorized access attempts or abuse of functions.

    • How to:

      • Review activity logs or relevant interactions to detect attempts to access restricted categories.

      • Immediately inform administrators if suspicious activities are detected, such as multiple failed access attempts.

  • Recommendation of Changes to Permissions

    • What to do: Propose adjustments to roles or permissions based on category needs.

    • How to:

      • Notify administrators about users who need greater or lesser access based on their behavior or contributions.

      • Suggest changes to permission settings if security risks are identified, such as overly broad access in sensitive categories.

  • Education on Roles and Permissions

    • What to do: Guide users on their assigned roles and associated responsibilities.

    • How to:

      • Send direct messages to new users explaining their permissions and how to use them correctly.

      • Publish guides in the moderated category to educate users on interacting with restricted content or collaborating in closed groups.

  • Response to Incidents Related to Permissions

    • What to do: Act quickly upon detecting a security issue related to roles or access.

    • How to:

      • Notify the administrator to immediately revoke access permissions if a user has improper access.

      • Document the incident in the Staff category and collaborate on implementing corrective measures.

Best Practices for Ensuring Security in Roles and Permissions

  • Principle of Least Privilege: Ensure users have only the permissions strictly necessary for their tasks.

  • Access Rotation: Propose that sensitive access permissions be reviewed regularly to adapt to changes in user roles.

  • Periodic Audits: Coordinate with administrators to conduct audits of roles and permissions periodically.

  • Security by Design: Work with administrators to ensure that the most sensitive categories have restrictive permissions from the start.