SATRE: stakeholder engagement and community buy in

[Davsarper]

Goal Title

Ensure that institutions evaluate themselves against SATRE and that the momentum is maintained between funded phases

Description

At the end of the funded phase of SATRE there was a growing community interest, with institutions and stakeholders affirming they would evaluate themselves against it and contribute feedback.

Without ongoing resources the necessary support to ensure that happens cannot be provided and SATRE may end up not being adopted.

Definition of Done

There are a number of self evlauaitons completed, there is feedback on the spec repository and, ideally, there is an active WG within the TRE Community continuing to work on it.

Details

• RACI
  • Accountable team or person: RAM
  • Responsible team or person: RPM, REG
  • Informed and consulted people:
• Estimated effort in total FTE: 0.1 - 0.2

Task and issue breakdown

Breakdown in specific tasks of maximum a month duration, tasks and issues may be added as necessary
Issues may span across repositories when necessary.

• Engage with stakeholders
• Support evlauaitons
• Upload evaluations
• Record feedback and possible modifications
• Establish WG

Checklist

• This Story have been agreed with project members, it tackles prioritised work
  • If not: Label as ForPrioritisation so it discussed in the next monthly meeting, do not set a status
• I have filled in the Team Accountabe field
• I have included this Story in the agreed upon Milestone, set status as Planned
  • If not: set status as Backlog, to be Planned via weekly meetings or async discussions
• The work to be done is likely to span over a month
• I have broken down the work in monthly issues and added them above
• I have labeled this issue according to its main project: SATRE, TRESA, CORE DSH (ELA) or other (please agree and create a new label if necessary)
• If known: sum the total effort (points) of tracked issues and add it on the body
• Select a Story level of effort in the project fields

Reporting

5 February to 8 April 2024

NHS-E R&D Programme Director stated that SATRE has become the reference framework for TREs within the Subnational SDE programme, placing SATRE as a key reference for what TREs are.

We have also seen how institutions that already have other accreditations opt to self evaluate with SATRE because it is the only one specific to TREs.

SATRE has continued to atract the interest of the community, with many attendees to its meeting wanting to be involved.

Comms / impact/ ext engagement

• Aridhia are using SATRE and doing comms around the fact that we should record https://www.aridhia.com/blog/satre-standardised-architecture-for-trusted-research-environments-introduction/
• SATRE featuring heavily on EU project EOSC-ENTRUST for defining an EU blueprint for health data research SPEs https://eosc-entrust.eu/
• The four regional safe havens in scotland using SATRE to harmonise TRE capabilities, via porject funded by Research Data Scotland

[Davsarper]

Agreed and approved to work on, @harisood we will need to better define it and evaluate effort (and where it comes from)

[harisood]

Jan planning

This is part of the UK TRE Community (working as part of the SATRE UK TRE Community working group).

[Davsarper]

February: still part of UK TRE community but dependent on finalising some other work there, in particular website so we can then point to all WGs. Therefore will pick up in March and focus on getting a couple evaluations up in the repo.

[Davsarper]

We have been doing the enabling work as aprt of the community to good success, and SATRE is officially a TRE Comm WG but we have had no capacity to do the active part of this that we said we would (actively engage stakeholders, push for self-assessments).

Propose to close or re-consider what the work within it entails

[Davsarper]

@jemrobinson a co-chair of the SATRE working group, DSH time for James in June will probably be used up on codebase so not a priority this month but soon it should