North West London Imaging Analytics Slack

Description

Summary of the work Development of Slack functionality for the NWL Last Mile Analytics system to establish new 'canary alerts' for patients on cancer pathways and bespoke business intelligence bots. This work will interface with work being carried out using Jira and GitHub. This is part of a NWL 3 year strategic plan. Expected Contract Length Up to March 2025 (subject to ongoing funding availability) Latest start date Tuesday 28 February 2023 Budget Range There is a budget of up to £75,000 for the required works. We will be seeking the most competitive price available. 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 Are the Users 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. Work Already Done The system has been initially developed by Imperial College Healthcare NHS Trust (ICHT), 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 May involve work with other suppliers (TBC) Current Phase Beta Skills & Experience • Have experience in creating Slack bots and linking them to SQL modules (please give examples of the work you have done) • Have experience of working with healthcare IT services within the NHS. Please provide references. • Be able to manage a Slack organisation, including tags for National, Regional and Local reporting • Be able to manage bots for Wait Times, Demand Volume, Performance Queues, and Appointment Utilisation • Be able to create dedicated channels for automated SQL bots, including profile photos to monitor daily app re-loads and highlight failed database tasks • Be able to onboard users across 4 organisations, all on different infrastructures. Please explain what your approach would be • Provide Slack platform for 10 external users • Provide support to Slack platform until March 2025 Nice to Haves • Be able to code automated links to post issues and set priorities in Jira • Be able to automate PDF outputs into Slack channels for various common reports Work Location London - across multiple sites. It is anticipated the work can be completed remotely. Working Arrangments Work will be carried out remotely as working with Slack will not require a physical presence on NHS sites (unless agreed by exception between the Buyer and Supplier). No. of Suppliers to Evaluate 3 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 Assessment Method • Case study • Work history • Reference Evaluation Weighting Technical competence 65% Cultural fit 5% Price 30% Questions from Suppliers 1. Can you provide more information about the data sources that will be used for the analysis? The data sources will be the Radiology Information Systems (RIS), Picture Archiving and Communication Systems (PACS) and Trust Electronic Health Record (EHRs) for each of the 4 North West London Trusts. 2. Are there any specific reporting or analytical requirements that need to be incorporated into the system? The reporting and analytical requirements will include the standard national reporting requirements such as Diagnostics Waiting Time and Activity (DM01), NWL Integrated Care Board and Trust specific reporting requirements. We will be able to provide a list of required reports. 3. Are there any specific timelines or deadlines that need to be met? The work will need to be complete by the end of the financial year (31/03/2023). 4. 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. 5. Is Slack in use in the organisation already or would the initial setup be completed as part of this piece of work?Has the long term owner of the Slack instance been identified already?Is network connectivity between the Slack instance and supporting data sources in place already? No, it’s not in use at all in the organisation. Yes, initial setup would be completed as part of this project.The "owner" of Slack will be the supplier for the first 24 months. Then we will tender for a 5-10 year Analytics Prime Operator. It is unlikely that the organisation(s) will “own” Slack. For this project, we will only require one connection at 4 Trusts. We will have an Analytics role at each Trust requiring access to Slack. A potential additional phase of this project is likely to come out mid-2023 if we want to build out more users. 6. Is there an incumbent supplier, and if so who is it? There is currently no incumbent supplier. 7. Please could you provide detail on the existing technical stack for the bots? We use T-SQL on alternating fail-over data warehouses, with a Qlikview front end for select data browsing. Slack will likely sit outside this stack, just connecting the handful of initial users via app on their BYOD phones. For outputs/automation we’ve already built in Qlikview, we can copy them over to Slack if appropriate, or link the Slack to our T-SQL directly and recreate the logic that Qlik was using. 8. Please could you provide detail on the existing technical stack for the bots? We use T-SQL on alternating fail-over data warehouses, with a Qlikview front end for select data browsing. Slack will likely sit outside this stack, just connecting the handful of initial users via app on their BYOD phones. For outputs/automation we’ve already built in Qlikview, we can copy them over to Slack if appropriate, or link the Slack to our T-SQL directly and recreate the logic that Qlik was using. 9. Please could you provide, at a high-level, the historical support that’s been required to support the service? Also what are the support hours and SLA for this service? There is 1 Trust with 2WTE, 1 Trust with 1WTE, 1 Trust with some outsourced support and 1 Trust with no WTE/outsourcing. As a result the historical support that exists for Imaging Analytics varies. There is little scope for bespoke reporting, but it does happen at some Trusts.Typically the response time has been from several hours to several weeks and, at times, missed. We expect the procurement to improve this significantly, but it is reasonable that support hours will be 10am-4pm and SLA will be 24hrs for responses. Ideally, some level of “instant support” will be programmed into Slack. 10. Q1. Is there an incumbent supplier?Q2. Have you done work like this in the past either in-house or with a supplier?Q3. There are 2 other “imaging analytics” procurements that have gone live (Jira, GitHub) – do you expect them to be delivered by the same supplier?Q4: Is there a technology stack that the bot must be deployed within (Azure, On-prem etc.)Q5: Is the support until 2025 included in the budget? Q1. NoQ2 Yes, the project lead has done almost exactly this same project in-house at a previous NHS organisation. The endpoint is well defined, we just need a supplier who had the bandwidth to build this for us.Q3. Ideally, we prefer to maximise modularity and creativity by choosing a variety of suppliers. Suppliers who work well with other suppliers are preferred.Q4.No. We are early enough in this project that we haven’t build any dedicated infrastructure yet. Your advice will be useful for our next round of procurement in mid-2023 when we build upon this.Q5. Yes