The flowchart below shows the PRIDES process. Below is an accessible text version of the flowchart.
The top half of the flowchart shows the Research Delivery Pathway, from early contact and engagement, study set up, to study delivery. The Research Delivery Amendment Pathway is also in the study delivery section.
The bottom half of the flowchart shows the lead and supporting Regional Research Delivery Network (RRDN) Health Informatics Development and Utilisation Pathways. These feed into the Research Delivery Pathway.
The flowchart begins with the study sponsor/team engaging with the Clinical Research Network (CRN). This stage involves the Clinical Research Network Coordinating Centre (CRNCC) Business Development Management (BDM) or Study Support Service (SSS) (Early Contact and Engagement (EC&E)), and PRIDES triage and referral. The study chief investigators (CIs) closest RRDN's Study Support Service (SSS) are also involved in PRIDES triage and referral.
Once triage and referral is complete, the study CIs closest RRDN or lead RRDN PRIDES team carry out a resource assessment. In this stage, the portfolio eligibility must be approved, and the study is added to the portfolio.
Then the lead RRDN set up the study. The participant identification centre (PIC) model is agreed and added to the costings in the contract (and text message delivery).
Study set-up comprises the Lead RRDN PRIDES team development stage. This requires the lead RRDN to discuss whether Health Informatics are needed and basic details are added to the Study Start-Up and Delivery Tool to support participating sites with their Assess, Arrange and Confirm (AAC) processes. The SSS then triage and review.
Study delivery begins with site selection. Primary Care PIC GP sites or GP research sites are opened, and implement the HI solution. Patients are then identified, and participate in the study at a primary or secondary care research site.
The Research Delivery Amendment Pathway begins with the study or sponsor team engaging with the CRN. The CRNCC or an RRDN identify the need for additional or enriched recruitment, so the lead RRDN PRIDES team review and amend resources accordingly. RRDNs can then ensure that GPs have access to relevant HIs.
Health Informatics Development begins with the lead RRDN carrying out a PRIDES resource assessment, and a decision is made on the appropriate HI model. Then the lead RRDNs PRIDES team develops the initial HI for GP systems, such as EMIS, SystmOne and Vision. The HI may be developed by the lead RRDN, or the lead RRDN with support from an RRDN with IT capability to develop HIs, in conjunction with the local Principle Investigator (PI).
The National IT Expert Group are consulted for complex developments and the RRDN developing the HI then reciprocate feedback and support between them. The lead RRDN PRIDES team carries out Quality Assurance (QA). HI development includes local user testing and QA before roll out to other sites, RRDNs and Devolved Administrations.
Once QA is complete, the lead RRDN uploads the HI to the appropriate sharing platform, such as their local PRIDES website and/or local GP system sharing platform.
Once the lead RRDN has uploaded the HI onto the sharing platform, another RRDN (for example, RRDN X) will download the HI, test it, and amend it based on local needs. RRDN X’s own PRIDES team then carries out QA. RRDN X then uploads the HI to their sharing platform (again, such as their local PRIDES website and/or local GP system sharing platform).
Both the lead and supporting RRDNs have now uploaded their HIs to appropriate sharing platforms. RRDNs can then ensure that GP sites have access to relevant HIs, enabling the opening of primary care PIC GP sites, in turn leading to the opening of primary care GP research sites.