This opportunity is closed for applications

The deadline was Monday 6 February 2023
NHS North West London

North West London Imaging Analytics Github

6 Incomplete applications

5 SME, 1 large

6 Completed applications

6 SME, 0 large

Important dates

Monday 23 January 2023
Deadline for asking questions
Monday 30 January 2023 at 11:59pm GMT
Closing date for applications
Monday 6 February 2023 at 11:59pm GMT


Off-payroll (IR35) determination
Supply of resource: the off-payroll rules will apply to any workers engaged through a qualifying intermediary, such as their own limited company
Summary of the work
Creation of code storage that will contain code related to a Jira based repository of business logic and reporting parameters for the NWL Last Mile Analytics system. This work will interface with work being carried out using Jira and Slack and is part of a 3 year NWL strategic plan.
Latest start date
Tuesday 28 February 2023
Expected contract length
Up to March 2025 (subject to ongoing funding availability)
Organisation the work is for
NHS North West London
Budget range
There is a budget of up to £75,000 for the required works. We will be seeking the most competitive price available.

About the work

Why the work is being done
To enhance the business intelligence available to diagnostic imaging services across North West London and improve the management of patient pathways. It is part of a 3 year strategic plan within the North West London Integrated Care System. The work outlined will need to be completed by 31/03/2023 as part of the first phase of this plan alongside two other interconnected areas of work.
Problem to be solved
Limitations on the analysis of radiology data to inform operational and strategic decision making.
Who the users are and what they need to do
As an operational manager or clinician I need to make the best use of the activity data within our systems so that I can provide the clearest and most accurate information possible to staff and decision making bodies within my own organisation and wider Integrated Care System.
Early market engagement
Any work that’s already been done
The system has been initially developed by Imperial College Healthcare NHS Trust (ICHT) using existing NWL Trusts' clinical information systems, having undergone discovery and alpha project delivery stages. ICHT are now seeking partners to further develop and expand the system's capabilities and provide more complex, responsive reporting to the North West London Integrated Care System as a whole.
Existing team
James Mac, Associate Director of Analytics for the NWL Imaging Network, NHS North West London
Katie Smith, Head of Diagnostic Transformation, NHS North West London
Current phase

Work setup

Address where the work will take place
London - across multiple sites. It is anticipated the work can be completed remotely.
Working arrangements
Work will be carried out remotely as the work will not require a physical presence on NHS sites (unless agreed by exception between the Buyer and Supplier).
Security clearance

Additional information

Additional terms and conditions

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
  • Provide examples of expertise in setting up and managing a GitHub team with multiple collaborators
  • Have experience of working with healthcare IT services within the NHS. Please provide references
  • Demonstrate experience of managing version control, code branching, and pull requests
  • Be able to add inline plain English documentation
  • Demonstrate ability to setup local connections to copy GitHub code to multiple organisations with differing IG requirements
  • Be able to manage code “subsets” for multiple organisations where the maturity of local digital teams may vary, please explain how
  • Must be able to provide GitHub platform for 5 external users, 4 Trusts and the NHS NWL
  • Be able to provide support to GitHub platform until March 2025
Nice-to-have skills and experience
prioritise smaller modular solutions to larger all in modules - please provide an example

How suppliers will be evaluated

All suppliers will be asked to provide a written proposal.

How many suppliers to evaluate
Proposal criteria
  • Technical solution
  • Approach and methodology
  • How the approach reaches the goal
  • How will the solution be delivered within the required timescale
  • Team structure and skill sets
  • Value for money
Cultural fit criteria
  • work as a team with our organisation and other suppliers
  • be transparent and collaborative when making decisions
  • have a no-blame culture and encourage people to learn from their mistakes
Payment approach
Fixed price
Additional assessment methods
  • Case study
  • Work history
  • Reference
Evaluation weighting

Technical competence


Cultural fit




Questions asked by suppliers

1. Does the organisation have a supplier in mind and also would you consider one supplier for all 3 published projects?
We do not have a supplier in mind and would welcome submissions from any supplier able to meet the requirements of the project. We would be open to considering one supplier for all 3 published projects if the supplier is able to demonstrate their ability to deliver across all requirements.
2. What is the timescale following stage 1 submissions – i.e., stage 2 short-listing, stage 2 responses due?
We will be shortlisting by mid February and will provide responses to suppliers shortly thereafter.
3. Please could you advise on the reason for essential skills of experience in NHS?
It is anticipated that a supplier will require prior high-level understanding of NHS systems and how they operate in order to deliver at the required pace of work.
4. Please can you clarify if this is for PS to install and configure, MS to support till March 2025 or the infrastructure (hosting, storage and connectivity) to support the software deployed (Git Hub) or a combination of all of the above. If this includes infrastructure is there any requirements as to the location and security compliance policies of that infrastructure.
No specific security compliance - it won’t be holding patient information. The code will reference tables, columns and data fields, holding no patient data. The code will be considered Intellectual Property so it will need to be protected. You will install and configure the main organisation. We will be procuring long term support, therefore requiring GitHub infrastructure to remain for 2 years. We won’t have the capacity to support it immediately.
Location is TBC, but we want the web address for the organisation to be a dedicated account which can be transferred at the end of two years if needed.