Open
Conversation
lwjohnst86
requested changes
Apr 9, 2026
Member
lwjohnst86
left a comment
lwjohnst86
left a comment
There was a problem hiding this comment.
Neat
| @@ -0,0 +1,412 @@ | |||
| # ON LiMiT Feasibility data protection risk assessment | |||
Member
There was a problem hiding this comment.
Suggested change
| # ON LiMiT Feasibility data protection risk assessment | |
| --- | |
| date: 2026-02-01 | |
| date-modified: 2026-02-24 | |
| --- | |
| # Data protection risk assessment |
Comment on lines
+3
to
+7
| Date of risk assessment: 24-02-2026 | ||
|
|
||
| Prepared by: Kristiane Beicher | ||
|
|
||
| Last revised : 01-02-2026 |
Member
There was a problem hiding this comment.
Suggested change
| Date of risk assessment: 24-02-2026 | |
| Prepared by: Kristiane Beicher | |
| Last revised : 01-02-2026 |
This are not necessary/I moved them up into the YAML header.
|
|
||
| Last revised : 01-02-2026 | ||
|
|
||
| ## 1 Responsible parties |
Member
There was a problem hiding this comment.
Suggested change
| ## 1 Responsible parties | |
| ## Responsible parties |
Comment on lines
+29
to
+31
| Name: Søren Gregersen | ||
|
|
||
| Department: Department of Clinical Medicine / Steno Diabetes Centre Aarhus |
Member
There was a problem hiding this comment.
Suggested change
| Name: Søren Gregersen | |
| Department: Department of Clinical Medicine / Steno Diabetes Centre Aarhus | |
| - Name: Søren Gregersen | |
| - Department: Department of Clinical Medicine / Steno Diabetes Center Aarhus |
Comment on lines
+13
to
+19
| Aarhus University | ||
|
|
||
| Nordre Ringgade 1 | ||
|
|
||
| DK-8000 Aarhus | ||
|
|
||
| CVR no.: 31119103 |
Member
There was a problem hiding this comment.
Suggested change
| Aarhus University | |
| Nordre Ringgade 1 | |
| DK-8000 Aarhus | |
| CVR no.: 31119103 | |
| Aarhus University\ | |
| Nordre Ringgade 1\ | |
| DK-8000 Aarhus\ | |
| CVR no.: 31119103 |
| +------------+------------+------------+------------+------------+ | ||
| | Consequences X Likelihood | No or insignificant consequences | Inconvenient consequences | Critical consequences | Unacceptable consequences | | ||
| +============+============+============+============+============+ | ||
| | Unlikely | 1☐ | 2☐ | 3☐ | 4☐ | |
Member
There was a problem hiding this comment.
This doesn't look too nice. What are those characters after the numbers? I think we can simplify this table into a simple "Not very likely, inconvenient consequences" text.
Comment on lines
+325
to
+331
| - [ ] Unlikely (1) | ||
|
|
||
| - [X] Not very likely (2) | ||
|
|
||
| - [ ] Likely (3) | ||
|
|
||
| - [ ] Expected (imminent) (4) |
Member
There was a problem hiding this comment.
Suggested change
| - [ ] Unlikely (1) | |
| - [X] Not very likely (2) | |
| - [ ] Likely (3) | |
| - [ ] Expected (imminent) (4) | |
| - [ ] Unlikely (1) | |
| - [X] Not very likely (2) | |
| - [ ] Likely (3) | |
| - [ ] Expected (imminent) (4) |
Comment on lines
+337
to
+343
| - [ ] No or insignificant consequences (1) | ||
|
|
||
| - [X] Inconvenient consequences (2) | ||
|
|
||
| - [ ] Critical consequences (3) | ||
|
|
||
| - [ ] Unacceptable consequences (4) |
Member
There was a problem hiding this comment.
Suggested change
| - [ ] No or insignificant consequences (1) | |
| - [X] Inconvenient consequences (2) | |
| - [ ] Critical consequences (3) | |
| - [ ] Unacceptable consequences (4) | |
| - [ ] No or insignificant consequences (1) | |
| - [X] Inconvenient consequences (2) | |
| - [ ] Critical consequences (3) | |
| - [ ] Unacceptable consequences (4) |
Comment on lines
+370
to
+376
| - [ ] Unlikely (1) | ||
|
|
||
| - [ ] Not very likely (2) | ||
|
|
||
| - [X] Likely (3) | ||
|
|
||
| - [ ] Expected (imminent) (4) |
Member
There was a problem hiding this comment.
Suggested change
| - [ ] Unlikely (1) | |
| - [ ] Not very likely (2) | |
| - [X] Likely (3) | |
| - [ ] Expected (imminent) (4) | |
| - [ ] Unlikely (1) | |
| - [ ] Not very likely (2) | |
| - [X] Likely (3) | |
| - [ ] Expected (imminent) (4) |
Comment on lines
+384
to
+390
| - [ ] No or insignificant consequences (1) | ||
|
|
||
| - [ ] Inconvenient consequences (2) | ||
|
|
||
| - [X] Critical consequences (3) | ||
|
|
||
| - [ ] Unacceptable consequences (4) |
Member
There was a problem hiding this comment.
Suggested change
| - [ ] No or insignificant consequences (1) | |
| - [ ] Inconvenient consequences (2) | |
| - [X] Critical consequences (3) | |
| - [ ] Unacceptable consequences (4) | |
| - [ ] No or insignificant consequences (1) | |
| - [ ] Inconvenient consequences (2) | |
| - [X] Critical consequences (3) | |
| - [ ] Unacceptable consequences (4) |
github-project-automation
bot
moved this from In Review
to In Progress
in Data development
lwjohnst86
requested changes
Apr 9, 2026
Member
lwjohnst86
left a comment
lwjohnst86
left a comment
There was a problem hiding this comment.
Neat
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
There are probably plenty of typos etc in here. I also need to create the two diagrams with colours at the end, and get the second section fleshed out.
Needs a quick review.
Checklist
just run-all