Skip to content

Commit

Permalink
NHS SDE breakout
Browse files Browse the repository at this point in the history
  • Loading branch information
harisood committed Nov 28, 2023
1 parent 482ad78 commit 63db54f
Show file tree
Hide file tree
Showing 8 changed files with 55 additions and 31 deletions.
Original file line number Diff line number Diff line change
@@ -1,7 +1,9 @@
# Hosting TRE/SDEs locally vs cloud

**Chair**: Adam Marsh (Optimum Patient Care)

## Prompts

- What is the split (if any) between TRE/SDEs being hosted locally vs cloud?
- What are the merits of either option?
- [assuming there are participants who have hosted locally] Are there any challenges or tips for building and hosting locally?
- [assuming there are participants who have hosted locally] Are there any challenges or tips for building and hosting locally?
Original file line number Diff line number Diff line change
@@ -0,0 +1,10 @@
# NHS England’s SDE Network

**Chair**: Adam Keeley (University of Leeds)

## Prompts

- What is the future of independent TREs for health data?
- How will primary data collection and linkage be managed in the SDE network?
- What, if any, will be the accreditation standards SDEs hold them to?
- What are the current options for unmet technical capability?
Original file line number Diff line number Diff line change
@@ -1,9 +1,11 @@
# TRE Federation: appetite for a standards working group(s)?

**Chair**: Rob Baxter (DARE UK)

## Prompts
Federating TREs to enable linked-data research is a big topic, with lots of current activity.
DARE UK have tried, in the spirit of George Box*, to draw the current threads together into a common architecture.

Federating TREs to enable linked-data research is a big topic, with lots of current activity.
DARE UK have tried, in the spirit of George Box\*, to draw the current threads together into a common architecture.
But what next? Forming a community working group to develop the architecture and technical standards seems like a good thing to do.

- How much enthusiasm is there to form a WG? Assuming there is some…
Expand All @@ -12,4 +14,4 @@ But what next? Forming a community working group to develop the architecture and
- What outputs would we aim for, on what timescales?
- How best would we organise and collaborate? Docs on GH webpages, with issues, boards etc? Something else?

*_All models are wrong, but some are useful_
\*_All models are wrong, but some are useful_
37 changes: 17 additions & 20 deletions docs/events/wg_workshops/2023-12-05-december-meeting/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@

## Background

​The UK TRE Community is a community of over 200 people that has grown organically over the last year for anyone interested in TREs, including researchers, operators, information governors, managers and more, from all sectors and disciplines.
​The UK TRE Community is a community of over 200 people that has grown organically over the last year for anyone interested in TREs, including researchers, operators, information governors, managers and more, from all sectors and disciplines.

​The core aims of fostering collaboration and sharing of innovative ideas to support the delivery of groundbreaking research with sensitive data have resonated across the UK and beyond.

Expand All @@ -12,26 +12,27 @@

This agenda will be continuously updated as more sessions are confirmed.

| Time | Agenda Item |
| ---- | ----------- |
| 13:30 - 13:45 | Welcome and intro |
| 13:45 - 14:30 | Keynote + discussion |
| 14:30 - 14:45 | Community updates |
| 14:45 - 14:55 | Break |
| Time | Agenda Item |
| ------------- | ----------------------- |
| 13:30 - 13:45 | Welcome and intro |
| 13:45 - 14:30 | Keynote + discussion |
| 14:30 - 14:45 | Community updates |
| 14:45 - 14:55 | Break |
| 14:55 - 15:00 | Intro to breakout rooms |
| 15:00 - 15:45 | Breakout rooms |
| 15:45 - 15:55 | Break |
| 15:00 - 15:45 | Breakout rooms |
| 15:45 - 15:55 | Break |
| 15:55 - 16:00 | Intro to breakout rooms |
| 16:00 - 16:45 | Breakout rooms |
| 16:45 - 17:00 | Wrap up |
| 16:00 - 16:45 | Breakout rooms |
| 16:45 - 17:00 | Wrap up |

### Keynote

A talk by the Community Management working group on the latest developments, funding and plans for the community.
A talk by the Community Management working group on the latest developments, funding and plans for the community.
This will be followed by dedicated time to ask questions and discuss any proposals.

### Community updates
*A chance for anyone in the community to share quick updates with everyone on the call.*

_A chance for anyone in the community to share quick updates with everyone on the call._

- `SDEs, TREs etc - terminology and definitions` working group introduction (Pete Barnsley & Madalyn Hardaker)
- `The citizen and their increased / retained agency` working group introduction (Pete Barnsley)
Expand All @@ -49,14 +50,10 @@ For now, please find more detail about each below!
- [](./workshop-package-allow-lists.md)
- [](./workshop-manual-output-checking.md)
- [](./workshop-researcher-passports.md)


- [](./workshop-automated-output-checking-coi.md)

#### Discussions

- [](./discussion-local-cloud-hosting.md)
- [](discussion-tre-federation.md)




- [](./discussion-tre-federation.md)
- [](./discussion-nhs-sde.md)
Original file line number Diff line number Diff line change
@@ -1,10 +1,13 @@
# Evaluation of Automated Output Checking and AI Model Risk Assessment Community of Interest

## Summary

TBD

## Preparation

TBD

## Target audience
TBD

TBD
Original file line number Diff line number Diff line change
@@ -1,19 +1,22 @@
# Streamlining manual output checking

**Lead:** Rachael Williams (MHRA)

## Summary

This workshop will bring the community together to brainstorm strategies and tools for streamlining manual output checking in TREs.
This workshop will bring the community together to brainstorm strategies and tools for streamlining manual output checking in TREs.

Whilst automated output checking is going some way to minimising bottlenecks, manual verification is seen by many as a crucial step in maintaining confidentiality and in making sure that outputs align with the intentions of individual projects.
Whilst automated output checking is going some way to minimising bottlenecks, manual verification is seen by many as a crucial step in maintaining confidentiality and in making sure that outputs align with the intentions of individual projects.
This manual step can be time-consuming and prone to errors.

Participants will brainstorm effective techniques for optimising this process, including best practices to enhance efficiency without compromising governance.

By the end of the workshop, it is hoped that participants will be equipped with practical insights to enhance the speed and accuracy of manual output checking, ultimately improving the overall research workflow.

## Preparation

Please bring your experience, ideas, and questions, around what works and what doesn’t in the world of manual output checking, such as checklist development, collaborative workflows, and quality assurance measures.

## Target audience
All involved in manual output checking – both from a policy and procedures perspective, and with hands on experience.

All involved in manual output checking – both from a policy and procedures perspective, and with hands on experience.
Original file line number Diff line number Diff line change
@@ -1,24 +1,28 @@
# Package allow lists

**Lead:** Jim Madge (Alan Turing Institute)

## Summary

The [packages repository](https://github.com/uk-tre/packages) was created recently as a place for TRE operators to share their decisions on packages allowed in their TREs.

The lists are structured as JSON documents conforming to a schema, which sets out what information is required.
The lists are structured as JSON documents conforming to a schema, which sets out what information is required.
In this way, the lists can easily be validated and parsed to be used by other tools.

In the workshop we'll discuss adding your allowlists to the repository, making improvements and building tooling to use the lists.

We hope that sharing our decisions like this will encourage us to be honest and confident about our security and to benefit from using the data.

## Preparation

Attendees are encouraged to look at [the repository](https://github.com/uk-tre/packages) beforehand and bring ideas to the workshop.

For example, you might want to add your own organisation, you might want to propose a change to the schema, you might want to add tooling to create, modify or analyse the lists.

A good output would be to open a pull request or issue suggesting improvements.

## Target audience

TRE builders and operators with an interest in managing packages in TREs.

The session will be quite technical - the repository currently uses JSONSchema and Python.
The session will be quite technical - the repository currently uses JSONSchema and Python.
Original file line number Diff line number Diff line change
@@ -1,10 +1,13 @@
# Researcher Passports

## Summary

TBD

## Preparation

TBD

## Target audience
TBD

TBD

0 comments on commit 63db54f

Please sign in to comment.