Pain: equality of care and support in the community (PEACS) - ST21-P162

Description

Summary of the work . Expected Contract Length Two years Latest start date Wednesday 1 December 2021 Budget Range Up to £24,999 with additional budget in year two for data linkages with EMIS / expansion if the initial pilot is successful. Why the Work is Being Done This project aims to co-develop and test a bio-psycho-social approach in primary care to caring for people living with chronic pain. This approach will include screening, GP consultation and support from a mental health practitioner and the voluntary care sector. Chronic pain is one of the most common long-term conditions in England, as well as locally in Lambeth. Research suggests that chronic pain is more prevalent amoung people with Black backgrounds. There are also a range of factors that contribute to inequalities of patient experience, access and health outcomes for this population. Effort will go into outreach and engagement with people from Black communities to co-develop the approach. Programme development will start in late 2021, with an aim to start using the digital platform in March 2022. Problem to Be Solved Patients will need a web based platform where they can answer questions about their health and wellbeing remotely, and the data can be provided in a report format to their GP to identify bio-psycho-social need in relation to chronic pain. The data will need to be stored on a cloud based fosted database with the potential of linking to EMIS data sources. Who Are the Users As a patient, I need to be able easily access set of questions on my own device (phone / PC / tablet) answer question to answer questions about my health and wellbeing so that my GP can understamnd my needs. As a GP, I need to easily and quickly access the responses from patients including an algorithm to provide any relevant scoring and recommendations so that I can understand the needs of my patient. Early Market Engagement We have spoken to companies who have supported us with digital delivery to consider routes to delivering a solution. Work Already Done We have already delivered similar work in a secondary care (hospital) outpatient context. We are keen to adapt and develop this for use in a primary care context and coproducing with people from black communities to improve access in groups of patients to understand their experiences of accessing care. Clinical content is established, alongside existing branding and their is an existing website (www.imparts.org). We will be undertaking an exploratory phase with a user design partner, Comuzi. Current functionality allows a weblink to be shared with patients to complete on a digital device. Existing Team The team includes KHP, clinicians, IT, Comuzi, the trusts Charity Current Phase Discovery Skills & Experience • Demonstrable experience in full life-cycle development of large, public-facing, remote clinical tools (discovery/research, stakeholder management, design, build, content creation/migration, launch, hosting, maintenance, support) • Full service digital agency with a full range of roles including design, IA, UX, technical, content strategy, project management, analytics • Experience working with NHS or public-sector organisations. Knowledge of health technology environment and evolving standards from NHS Digital. Understanding of electronic patient record systems in primary care eg EMIS. • Evidence of providing responsive customer support service; relationships with satisfied clients. • Evidence of creating projects that support digital inclusion and contrent types that optimise engagement • Can demonstrate experience of rapid turnaround delivery to agreed timescales • Ability to deliver high quality but low technical maintenance digital solutions • Evidence of delivering effective training on the use of solutions - training for different levels of users should be offered, to support initial rollout • Demonstrate compliance with government’s accessibility standards for public sector websites, WCAG 2.1 AA accessibility standard (without compromising on design quality) and GDPR regulations and other regulations for public sector websites • Can explore options for personalisation and user authentication • Can demonstrate Information Governance toolkit certificate / DTAC compliance / Compliant with Records Management: NHS Code of Practice. • Production of DR and BC plans before sevice commencement. Measures in accordance with good industry practice. • Experience of use of data for population health management including data reporting on access to the system and usage, enable data for population segmentation and access to data for analysis • Electronic versions of the questionaires should be rendered as per the owner of the measures specifications • Functionality to link with EMIS for record transfer (in year 2 subject to success of pilot • Works well with clients of varying technical expertise Nice to Haves • Experience running UX, workshops, understanding needs. Agile user testing, to make sure that the solution meets the needs established at UX and design stage before launch. • Can provide options for translation. • Supports interfaces with NHS Digitals Secure Electronic File transfer (SEFT) interface for the purposes of secure data exchange. Work Location Counting House, Guy's hospital, currently enabled to work remotely so there is flexibility with location. Working Arrangments Mainly off-site, with visits to our offices as required by the project. Security Clearance Not required Additional T&Cs . No. of Suppliers to Evaluate 3 Proposal Criteria • Technical solution • Approach and methodology • How the approach or solution meets user needs • How the approach or solution meets the Trusts policies and or goal • Estimated timeframes for the work • Risks and dependencies and offered approaches to manage them • Team structure • Value for Money Cultural Fit Criteria • We are looking to appoint a partner company that can demonstrate to us that they are thinking about our future • Will need the expertise and experience to understand emerging technology that will make a difference to our user • While we want to be a leader in NHS technology, we also want to make sure we are only taking advantage of technology that adds true value • Works as a team with our organisation and other suppliers where necessary • Ready to challenge the status quo • Champions equality, diversity and digital inclusion • Is innovative and forward thinking • Shares knowledge and experience with clients • Provides honest and expert feedback • Uses innovative, cost effective techniques to engage website users • Takes responsibility for the quality of their work • Transparent and collaborative when making decisions • Works well with clients of varying technical expertise • User experience at the heart of how they work Payment Approach Capped time and materials Assessment Method • Case study • Work history • Reference • Presentation Evaluation Weighting Technical competence 60% Cultural fit 20% Price 20% Questions from Suppliers 1. We understand the development of the platform should be based on existing e-IMPARTS solution and will be about adapting the existing solution to meet the project requirements. Is that correct? Could we learn more about the tech stack of the existing solution? We would like to create a platform for the collection of patient reported outcome measures from patients. The current IMPARTS solution does this already, so we are able to share and learn from how this is currently done. However, the current solution does not work outside of the setting in which it is currently used, which is why we are not able to use it. We are happy to set up a call with the current tech supplier to learn about the existing solution. 2. Concerning content of the patient questionnaires: would all users fill the same version of a questionnaire (that will be defined during the project development) or there could be multiple questionnaires, e.g. for different user groups? For the pilot, we will be asking all users to complete the same questionnaire. 3. Recommendations for GP analysing the responses are mentioned. Could you elaborate or give an example of such recommendation? Do we need to define and build an algorithm for recommendations or does it exist in your current solution already? For example, if a patient scores above X on a questionnaire, the recommendation would be for the GP to refer them to Y service. On our current IMPARTS platform, we have around 100 questionnaires and algorithms, so there might be some that we could re-use, but we will likely have to define and build some from scratch. We will support this through conversations with clinical teams. 4. How patients and GPs should be authenticated in the application? Should NHS Login service be used or is there other authentication/identity provider in place already? We currently use NHS numbers to allow patients to sign in and complete their questionnaires. 5. On technical note, is SEFT required due to the fact that there could be files (e.g. photos) attached to the response form? Not expecting photos to be added to response in pilot stage but all data transfers will be expected to meet NHS Data standards - SEFT will only be required if necessary for data transfer to EMIS 6. Concerning on-site visits, how many visits/time on-site (e.g. for working with Comuzi) would you foresee for the project? (this will be useful for our budget calculation) We think this will likely involve joining a few virtual calls (approx. 5-10 hours) and some testing within the GP practice. This could be done remotely. 7. We understand the development of the platform should be based on existing e-IMPARTS solution and will be about adapting the existing solution to meet the project requirements. Is that correct? Could we learn more about the tech stack of the existing solution? We would like to create a platform for the collection of patient reported outcome measures from patients. The current IMPARTS solution does this already, so we are able to share and learn from how this is currently done. However, the current solution does not work outside of the setting in which it is currently used, which is why we are not able to use it. We are happy to set up a call with the current tech supplier to learn about the existing solution.