PRIDES team development: coordination & admin

If you have any accessibility queries in relation to the resources on these pages, please contact the PRIDES Hub at prides-hub@nihr.ac.uk

Please note that although video resources refer to the Clinical Research Network (CRN) and Local Clinical Research Networks (LCRNs), the content is still currently relevant to the service offer of the Research Delivery Network (RDN)

This section focuses on the different considerations you may have when developing processes and systems to coordinate and administer your local PRIDES team. The guidance below looks at a number of issues from communication and work allocation, to recording and monitoring ongoing HI activity.

Communication & work allocation

Guidance on different aspects you may want to consider when structuring communication methods and allocating work to the team

PRIDES team considerations for communication & work allocation

There are differing ways to structure your PRIDES team!
Consider 'single points of contact' and a designated inbox?
Take care allocating work in the RRDN core team if workload pressures exist

If you want to find out more please watch this presentation!

10. Comms & allocation (Final 16/11)

Recording & monitoring activity

Guidance on different aspects you may want to consider when deciding how to record and monitor your local PRIDES workload

PRIDES team considerations for recording & monitoring activity

There are differing ways to record activity...maybe using your LPMS?
Consider reporting requirements when choosing your system
Monitor requests carefully to avoid missing deadlines

If you want to find out more please watch this presentation!

11. Recording & monitoring activity

Structuring a PRIDES HI request

Guidance on different aspects you may want to consider when structuring a HI development request to ensure good communication & an effective product

PRIDES team considerations for using forms to structure the handling of HI requests

Forms can be useful for triggering a request process
Study Team sign-off of HI design can prevent disharmony during delivery
Recording each stage of the design process can provide clarity for all

If you want to find out more please watch this presentation!

12. Structuring requests & forms

Example process for managing HI tool development

Considerations at the design stage of HI tool development
Handling quality assurance of locally developed HI tools
Checking that HI tools received from elsewhere are fit for purpose

If you want to find out more please watch this presentation!

12.5. Structure for managing HI development (Final 17/11)

General considerations

Guidance on different aspects you may want to consider when structuring the administration and coordination of your local PRIDES team

PRIDES team - Administration & Reporting

The method chosen for the administration structure of your PRIDES team can vary from area to area dependent on many factors including the resources available.

This document lists just some of the considerations that you may feel would suit your RRDN's PRIDES service in terms of how activity is recorded and monitored.

If you would like to discuss this scenario further with the Hub, please send your query to the Hub inbox at:

prides-hub@nihr.ac.uk

PRIDES Hub - Administration & reporting - V1.1 - 06/10/2022

Template forms

The following forms can be downloaded and used as templates to help guide local informatics processes. Additional forms relating to other aspects of HI work are available upon request

Example: Initial request form

The purpose of the initial request form is to capture basic data about a study and its needs. This can include study identifiers, named contact details, data outlining the specific HI requirements, and any relevant timelines or deadlines.

Example: Initial request form

Example: Search design form

The search design form allows more detailed data to be captured about a HI request, such as particular inclusion or exclusion criteria specified in a study protocol.

These criteria and specifications can then be signed-off by the study team to confirm that HI work can proceed.

Example: Search request form

Example: Search QA form

The QA form can be used to structure the QA process, to ensure that the draft search meets the criteria specified earlier in the process and performs correctly. Once completed and signed-off, the QA form logs that the search has been checked correctly and should function as required.

Example: Search QA form

Example: Search functionality check form

As with the QA process, the FC form serves to structure (and log) the functionality check process. This is to ensure the correct function of an externally produced search (such as from another RRDN, study team or sponsor).

Example: Search functionality check form

Example: Search amendments form

This form may be useful to log amendments that are made to a study, which will affect the initial HI requirements and require the search to be modified. Additional sections can be added to the single form, to log further amendments as required.

Example: Amendment form

Page updated

Report abuse