Suggested changes - #193
Open
kuraisle wants to merge 36 commits into
Open
Conversation
…latform patterns. Computational patterns updated and GIFs added to demonstrate what is occuring.
…e and to add more explanations. Added the powerpoint slides that are used to create the GIFS for others to edit/use as necessary
Co-authored-by: Tri Thien Nguyen <119530400+AndrewThien@users.noreply.github.com>
Co-authored-by: Tri Thien Nguyen <119530400+AndrewThien@users.noreply.github.com> Co-authored-by: James Mitchell-White <jamesjimitchell@gmail.com>
…ck, both in the location it was commented, but also where the table originated.
Typos and text changes Co-authored-by: Andy Rae <1127507+AndyRae@users.noreply.github.com> Co-authored-by: Anwar <913028+anwarfg@users.noreply.github.com>
I don't actually agree with the "Connections" section, but that might just be me
prquinlan
requested changes
Jul 14, 2026
prquinlan
left a comment
prquinlan
left a comment
Contributor
There was a problem hiding this comment.
Could you do the changes without the moves - not sure why we want an examples folder - when there are only three patterns which are computational patterns.
anwarfg
reviewed
Jul 15, 2026
| | Required Trust between TREs | Very High | ||
|
|
||
| The pattern captures the movement of data where row level data moves, either persistently or temporarily to perform an analysis. Outside of TREs this is the most common method, where researchers would be accustomed to data being on their data where they can perform any analysis or learning. | ||
| In the pooled pattern row level data moves, either persistently or temporarily, to perform an analysis. |
Contributor
There was a problem hiding this comment.
Suggested change
| In the pooled pattern row level data moves, either persistently or temporarily, to perform an analysis. | |
| In the pooled pattern, row level data moves, either persistently or temporarily, to perform an analysis. |
| ## Variance in implementation | ||
| An emerging implementation of the Pooled Pattern is from the DARE UK TREvolution programme. They are exploring a project-specific network being created between the TREs, to either move or provide the researcher with a view of the data that makes it appear as if the data is all in one location. This approach is by far the most powerful for a user and the analyses and learning are almost unlimited. | ||
|
|
||
| [An emerging implementation](https://zenodo.org/records/10055358) of the Pooled Pattern comes from the [DARE UK TREvolution programme](https://dareuk.org.uk/trevolution/). They are exploring a project-specific network being created between the TREs, to either move or provide the researcher with a view of the data that makes it appear as if the data is all in one location. This approach is by far the most powerful for a user and the available analyses are almost unlimited. |
Contributor
There was a problem hiding this comment.
when you say "this approach is by far the most powerful for a user and the available analyses are almost unlimited." it now looks like you're talking about the trevolution stuff, when I think you mean pooled data in general.
| | Data Movement pattern | Description | | ||
| | --------------------- | ----------- | | ||
| | Summary | A statistical result is shared back that does not relate to any individual but is a calculation based on the confidential data. It is the summary result that moves from the TRE. | | ||
| | Model Parameters | A machine learning algorithm runs on the data at each TRE, and the weights are moved from the TRE. | |
Contributor
There was a problem hiding this comment.
It's not always machine learning, and not always weights/updates.
| |-------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | ||
| | **None** | The egress being requested is set to auto-approve, there can be no manual or automated egress check in place, or no process to mitigate disclosure risks. | | ||
| | **Manual** | At least one person checks the results by eye and approves the release of the data | | ||
| | **None** | The egress being requested is approved by default, there can be no manual or automated egress check in place, or no process to mitigate disclosure risks. | |
Contributor
There was a problem hiding this comment.
Suggested change
| | **None** | The egress being requested is approved by default, there can be no manual or automated egress check in place, or no process to mitigate disclosure risks. | | |
| | **None** | The egress being requested is approved by default, there are no manual or automated egress check in place, and no process to mitigate disclosure risks. | |
| Central egress method: Any | ||
|
|
||
| There are emerging tools (such as [SACRO](https://github.com/AI-SDC)) that can allow for the semi-automated checking of results for a disclosure risk. The decision to release a result is still manual and undertaken by the TRE, with the aim that this semi-automation can first warn the researcher ahead of time that a result may be disclosive and therefore accelerate any disclosure control assessments undertaken at the time of egress from the TRE. | ||
| Emerging tools (such as [SACRO](https://github.com/AI-SDC)) allow for the semi-automated checking of results for a disclosure risk. The decision to release a result is still made by a human being and undertaken by the TRE, with the aim that this semi-automation can first warn researchers and output checkers ahead of time that a result may be disclosive and therefore accelerate any disclosure control assessments undertaken at the time of egress from the TRE. |
Contributor
There was a problem hiding this comment.
Suggested change
| Emerging tools (such as [SACRO](https://github.com/AI-SDC)) allow for the semi-automated checking of results for a disclosure risk. The decision to release a result is still made by a human being and undertaken by the TRE, with the aim that this semi-automation can first warn researchers and output checkers ahead of time that a result may be disclosive and therefore accelerate any disclosure control assessments undertaken at the time of egress from the TRE. | |
| Emerging tools (such as [SACRO](https://github.com/AI-SDC)) allow for the semi-automated checking of results for a disclosure risk. The decision to release a result is still made by a human and undertaken by the TRE, with the aim that this semi-automation can warn researchers and output checkers that a result may be disclosive before a result is released and therefore accelerate any disclosure control assessments undertaken at the time of egress from the TRE. |
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
3 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.
tried to address comments