Co-create a TRE standard

[Davsarper]

Goal Title

What will this work achieve?
Develop the SATRE specification that UK TREs can evaluate themselves against

Description

• Write the specification
• Evaluate existing TREs against the specification
• Plan necessary work to meet missing requirements

Definition of Done

SATRE specification published

Details

• RACI
  • Accountable team or person: @jemrobinson @martintoreilly @harisood
  • Responsible team or person: SATRE team
  • Informed and consulted people: UK TRE community
• Estimated effort FTE: 1.8
  • RPM: 0.05 + SATRE Agreements, Budget & Invoices #38

Resourcing

August

• REG: 2
• RAM: 0.75
• RPM: 0.1 (excluding contracts)

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.

• WP1 - Evaluation and Reference Specification.
• WP2: Patient and Public Involvement and Engagement (PPIE).
• WP3: Formalisation of the pluggable reference architecture
• WP4: Implementation and assessment of a reference TRE architecture
• WP 5: Community building & engagement

The specification (output) lives here and the project activites is recorded here

Report progress

1 November 4 December

Had wrap-up and post project meeting, it was identified how ongoing work it is necessary to communicate and ensure engagement and usage as well as to prepare for the next DARE phase.

We have decided to keep fortnightly meetings to keep some momentum.

Is that enough? do we want to dedicate any more resources to ensure the necessary actions happen?

10 October to 30 October 2023

• Final month of this funded phase, we have focused on reporting and laying out the next steps. There is commitment to take this work and the specification forward
• Outputs:
  • SATRE specification V1
  • Internal DARE report, link will be added and published openly
  • User report: characterises users, with a wider notion than we started of what users are. Lays the fundation for futher usability work, going beyong technicla features and into training and documentation
  • UK TRE Community - SATRE WG
• final project showcase, presenting the work done for SATRE (Chris presented as PI with slides prepared by each wp), and the final project meeting and collaboration café
• Held the self-evaluation workshop
• During the last proejct meeting it was decided to have yet another one focused on next steps and possibilites for collaboration

19 September to 9 October 2023

• Specification v1, announcements to go out wc 9Oct. Big focus of the team on wp1
• Stakeholder engagement: self-evaluation invitation and event on 25 October
• Collab cafes:
  • on the UX of the specification: resulted in changes. notes including suggestions on FAQs
  • Session with members of the public, invite only
  • Unstructured collab cafe: 3 attendees, useful conversation on possible ways to make PPIE a part of future specs/standards. Notes here
• Spec changes:
  • Added FAQs page
  • Added some suggestions from HDR UK
  • Updating evaluation of the DSH to include answers to new statements PR#271
  • Next month priority: reporting
    • 11 October: share materials with Chris or showcase
    • 20 October: finalise each WP report
    • 31 October: final report due, to be submitted by Dundee

14 August to 18 September 2023

• Self evaluation: via several long sessions DSH was evaluated against SATRE specification. Merged PR
  • Producing evaluations for DSH and TREEHOOSE is a key objective of SATRE
  • Takeaways: @JimMadge @jemrobinson @harisood do you have takeways/lessons to share form the slef evaluation?
  • Method of evaluation: from a suggestion in a collaboration cafe it was suggested to create a tiered evaluation system which DSH agrees would be valuable and appropiatte, there is not however resources to make it happen as part of DARE funded SATRE. Will consider as future work
  • Scoring system was revised to be clearer
• RSEcon presentation: prepared materials for talk presenting the project and progress. On top of the specific talk the TRE Community day also had short talks and led to discussions on the project and the need for specifications
  • Throughtout the days at RSEcon attendees showed interest on SATRE and expressed the need for it
• Continued adding to the specification: added statements on output checking, draft PR to edit and include TRE roles
• Collaboration cafes
  • Wrote blogs about previous collaboration cafes on Usability and Implementaiton, text on Teams here & Principles, text on Teams here
  • Held collaboration cafes on evaluation methods

10 July to 14 August 2023

• Closing off SATRE survey, analysis of free text responses. Output:
• Collaboration cafes on Usability and Implementation and Principles and implications
  • Outputs: working on blog posts and converting discussion points into issues in the specification repo
• User Testing: lead by Turing, facilitated by Ulster. Usability test of DSH and TREEHOOSE with a common analysis challenge. It was possible thanks to Turing approved ethics
  • Output: additional data necessary for the project report on Users
• DSA draft shared & FY22-23 Q1 Invoiced (Data Sharing agreement for SATRE #22)
• Specification changes through PRs 1 2 which relate to loggin user actions, added sections for security levels and tiering. Changes to Computing Pillar via Update computing pillar sa-tre/satre-specification#186
• Self evaluation

[Davsarper]

I have translated weekly updates into reporting in the issue body, please use comments to discuss and complete

• I have not reported on 3 as it is closed but not merged?
• Self evaluation detail needed
• @harisood and @jemrobinson please review and add outputs/value where needed. What did the activites above deliver?

[harisood]

I am now seeing the benefit of recording everything on here for reporting purposes... I think it looks good, maybe highlighting how long the self-evaluation is taking

[Davsarper]

October: porject closure, reporting, meet in Edinburgh.. both priority and urgent

• Run evaluations

[Davsarper]

Dec planning

There is follow up, and a lot to do to ensure SATRE impact.

• get more evaluations
• implicate NHS and other bodies
• Iterate

Do we want to dedicate active ELA-core time into it? Take decision to the Monthly.

Matt wrote a report of the comaprison paper, where it is, and what we need to get it publish.

It is important to maintain the momentum we got, we have difficulty to resource it. We require new funding/push for it.