Data protection recommendation screen

[c0c0n3]

Summary

I as a data manager, when planning to protect data, would like the Portal to tell me, for each data type, what are the fields that are likely to contain sensitive info so I can keep data from prying eyes.

Outcome

The data manager gets to know about pieces of info that should be protected and that she wasn't initially aware of.

How will it work?

We're going to implement the UI part to fulfill this user story and make the UI drive the definition of a backend REST API which will actually provide recommendations. The UI will display the following info for each data type (JSON object type)

• Top-level field names.
• For each field name whether the system recommends to protect its content or no protection is needed. In the case the system recommends to protect the field data, we need to tell the user by which means, either encryption or anonymisation.
• For each field name that needs protection we need to tell the user whether the field data should be protected at rest, in transit or both.

[c0c0n3]

Here's a screenshot of the whiteboard we filled during the brainstorming session on 13th June, 2023.

[c0c0n3]

@Valecant if you could please use real-world field names for a patient record as we agreed.

[c0c0n3]

@Valecant as you suggested, let’s go ahead with a unified UI for both the "current status" (#199) and recommendations.