This opportunity is closed for applications

The deadline was Monday 19 September 2022
NHS England

Beta phase for auditing, notifications and application improvements

2 Incomplete applications

1 SME, 1 large

12 Completed applications

9 SME, 3 large

Important dates

Published
Monday 5 September 2022
Deadline for asking questions
Monday 12 September 2022 at 11:59pm GMT
Closing date for applications
Monday 19 September 2022 at 11:59pm GMT

Overview

Off-payroll (IR35) determination
Contracted out service: the off-payroll rules do not apply
Summary of the work
NHS England are looking for a multi-disciplinary team to help them take a set of alpha prototypes and findings and build, test and iterate these into the existing FutureNHS platform which is currently in private beta.
Latest start date
Tuesday 1 November 2022
Expected contract length
up to 1 year
Location
No specific location, for example they can work remotely
Organisation the work is for
NHS England
Budget range
Up to £600,000

About the work

Why the work is being done
Since 2016 the FutureNHS platform has acted as a key service in supporting the health and care community achieve a “revitalised culture of support and collaboration” to support the delivery of the long-term plan.
In 2021 we began building a new open-source collaboration platform to fully meet the needs of our growing userbase. This new platform is currently in private beta with a view to move into public beta later in 2022.

In undertaking our research, we identified several initiative areas we would like to release when the platform reaches its public beta phase. These new initiatives will help transition existing workspaces onto the new platform and help encourage platform growth.

With the establishment of 42 Integrated Care Systems across the health and care sector in England, it is now more vital than ever to support collaboration efforts across the entire sector.
Problem to be solved
We have identified the following problems that we require to be solved:
- We need to understand what users are accessing on the platform to improve platform reporting and ensure data security both at a platform and group level.
- We need to be able to notify users of the platform of relevant platform activity that requires their action, or could be of interest to them, so we can improve the platform engagement.

From our usability testing during private beta, we have also discovered a series of improvements we need to make to the existing platform functionality. For each of these we have documented user stories and produced prototypes and designs and technical recommendations when needed.

We are looking for a multi-disciplinary team to take the findings, designs and prototypes from our work done to date and build upon them to improve our existing FutureNHS platform (collaborate.future.nhs.uk) in a multi-supplier environment.
Who the users are and what they need to do
Full details of our platform personas and typologies can be found in the Personas section on GitHub.

Users of the platform include staff across the health and social care community in England engaged in a wide range of transformation projects. The users working on these projects can vary in terms of seniority and experience, as well as the type of organisations to which they belong.

They need to be able to connect with, share and learn from other users in the health and care sector, across organisational boundaries and silos.
Early market engagement
We have undertaken pre-market engagement with a number of suppliers to develop our requirements and establish a budget for the work.
Any work that’s already been done
We have documented user stories and created designs and prototypes where required. Full documentation will be provided to suppliers who are selected to provide proposals.
Existing team
The FutureNHS service is currently run by the Strategy & Development team within the Office of Chief Data & Analytics.

The team currently employs a product manager, user researcher/designer and associate product manager directly involved in product development. Aside from this we operate a platform helpdesk and communications and account management team.

We have a support and maintenance agreement with a supplier for our private beta.
Current phase
Beta

Work setup

Address where the work will take place
Remote. We have offices in London and Leeds should face to face time be required.
Working arrangements
We expect the supplier will conduct most of the work remotely and will be able to provide the facilities for remote working with the existing team.

We are looking to work according to the Agile principles as documented in the Government & NHS Digital service manuals. We will expect the chosen supplier to perform and provide evidence of such practices in operation.
We use MS Teams and would look to conduct communication via MS Teams chats.
Delivery is expected to be managed through our existing Azure DevOps project board.
Security clearance

Additional information

Additional terms and conditions
1. All outputs will be owned by NHS England & NHS Improvement and published openly where appropriate using a suitable open license that supports reuse (e.g. MIT and OGL).

2. All materials/outputs derived from the contract shall be the property of NHS England & NHS Improvement.

3. GDPR requirements will be discussed and agreed once the successful supplier has been notified (as part of discussions to agree the wording of the call-off contract).

Skills and experience

Buyers will use the essential and nice-to-have skills and experience to help them evaluate suppliers’ technical competence.

Essential skills and experience
  • Evidence experience in successfully undertaking and passing service assessments, including CDDO or DHSC assessments. Please provide link to published service assessment and contact details for us to validate.
  • Have experience of developing large scale government applications (100,000+ users). Please provide links or evidence to show your experience of developing government applications used by large numbers of users.
  • Have experience of developing applications with Microsoft Azure, .NET, UMBRACO, REACT Next.JS, GOV.UK Notify. Please provide evidence of building applications using these.
  • Have experience of developing code in the open on GitHub. Please provide a link or links to any repositories you actively maintain or contribute to.
Nice-to-have skills and experience
  • Demonstrate experience of working on applications within health and care.
  • Demonstrate experience of working on projects with multiple suppliers.

How suppliers will be evaluated

All suppliers will be asked to provide a written proposal.

How many suppliers to evaluate
3
Proposal criteria
  • Proposed approach and methodology for project
  • Technical recommendations
  • Plan to deliver value for money
  • Proposed team structure and skills
  • Proposed knowledge transfer mechanisms
  • Relevant case study
Cultural fit criteria
  • • How you will deliver in a way that ensures compliance with labour rights, ethical issues and generates social value out of the health pound
  • • Proposed approach for working with multiple suppliers on blended teams
Payment approach
Capped time and materials
Additional assessment methods
  • Reference
  • Presentation
Evaluation weighting

Technical competence

60%

Cultural fit

10%

Price

30%

Questions asked by suppliers

No questions have been answered yet