National Institute for Health and Care Excellence (NICE)

MedTechScan - Horizon scanning of medical technologies for NHS professionals

Incomplete applications

6
Incomplete applications
5 SME, 1 large

Completed applications

7
Completed applications
7 SME, 0 large
Important dates
Opportunity attribute name Opportunity attribute value
Published Thursday 8 June 2017
Deadline for asking questions Thursday 15 June 2017 at 11:59pm GMT
Closing date for applications Thursday 22 June 2017 at 11:59pm GMT

Overview

Overview
Opportunity attribute name Opportunity attribute value
Summary of the work To build a national horizon-scanning system for medical technologies to augment existing clinical and financial planning activities undertaken within the NHS; offering stakeholders a systematic approach to collate timely (commercially sensitive) information to identify, categorise and track emerging medical technologies in development via a secure shared solution.
Latest start date Friday 1 September 2017
Expected contract length Initial 4 month SOW Discovery & Alpha. Stop/Go decision. Potential 12 months total contract period.
Location North West England
Organisation the work is for National Institute for Health and Care Excellence (NICE)
Budget range Initial 4 month contract is capped at £81,856 excl. VAT to deliver to end of Alpha.
Total project cost for 12 months is capped at £322,762 excl. VAT. Bids over the stated budget will not be considered

About the work

About the work
Opportunity attribute name Opportunity attribute value
Why the work is being done • To improve the identification and tracking of new and emerging medical technologies (devices, diagnostics, digital health tools) in development across the UK. To streamline processes and provide access to the required intelligence to inform horizon scanning agencies' outputs/appraisals
• To encourage early engagement of industry with the NHS
• To improve NHS planning for introduction and adoption of technologies that offer the most benefit and meet NHS priorities; to reduce investment in products that do not meet NHS priorities or offer evidenced economic or patient care benefits
• To reduce duplication and inconsistency in horizon-scanning decision-making by NHS professionals
Problem to be solved The NHS in England does not have an effective horizon scanning mechanism to identify transformative medical technologies with potential economic and patient care benefits to the health system. The aim would be:
1. To reduce duplication and inconsistency in horizon-scanning decision-making by NHS professionals
2. To reduce money invested by both NHS and manufacturers in products that do not meet NHS priorities or offer evidenced economic or patient care benefits
3. To reduce development of new technologies of limited value
Who the users are and what they need to do As an authorised user from a horizon-scanning organisation I need a single source of new medical technologies so I can focus on assessing value of technologies, budget-planning and management rather than manually tracking the technologies.
As an authorised user from a match manufacturer I need clarity on early engagement with the NHS on new products so that I can plan a product development portfolio and my device will be more likely to be commissioned.
As a data inputter I need secure access to a system where I can complete an agreed dataset on products which stores and categorises the information
Early market engagement The project will be developed jointly with, and is fully supported by the following stakeholders: NHS England; Industry – represented by the Association of British Healthcare Industries and the British In-Vitro Diagnostics Association; National Institute for Health and Care Excellence; National Institute of Health Research Innovation Observatory; Department of Health Office for Life Sciences; Academic Health Science Networks.
Each of these stakeholders is represented on an Implementation Group which has developed the business plan and secured project approval and funding.
A project consultant based at NICE is working with these agencies to understand the medical technologies horizon scanning landscape and define the initial broad requirements for the service (report due end of June).
An early market engagement session was held on 6 June. PowerPoint slides from the event are available at http://labs.nice.org.uk/medtechscan/.
Any work that’s already been done
Existing team The supplier will be responsible for the delivery of the work but will have contact with the Digital Services team at NICE who will be responsible for the ongoing hosting and management of the solution following the project completion.
Current phase Not started

Work setup

Work setup
Opportunity attribute name Opportunity attribute value
Address where the work will take place Manchester
Working arrangements Virtual working including collaboration/QA with internal NICE Digital Services staff who are based in Manchester.
Weekly sprint updates with NICE leads onsite or online.
Fortnightly 'show and tells' with key NICE/NICE partner stakeholders to meet governance/assurance needs onsite in Manchester.
Representation of a senior lead on NICE governance group twice a month or as required on site in Manchester
Security clearance In addition to the standard contract each individual working on the project will be required to sign a NICE confidentiality agreement and declare any conflicts of interests.

Additional information

Additional information
Opportunity attribute name Opportunity attribute value
Additional terms and conditions On delivery of the Phase 1 (Discovery and Alpha) NICE will seek a stop or go decision from its Senior Management Team and funder. Where the decision is to Go, NICE will proceed to Phase 2 under a separate SOW. Where the decision is to STOP, NICE will terminate the agreement subject to clause 23.

Subject to clause 23, NICE reserves the right to terminate the agreement if NICE considers it may be able to make efficiency savings by re-procuring Phase 2.

Skills and experience

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

Skills and experience
Opportunity attribute name Opportunity attribute value
Essential skills and experience
  • Experience of working within the Healthcare sector. Awareness of where this project fits with the NHS Five Year Forward view and furthers NHS objectives
  • Must be able to start the project from contract award at the beginning of August and deliver Discovery and Alpha phases in a 16 week timeframe from award of contract
  • Experience of undertaking robust user research and complex user journey mapping to deliver a product that achieves desired outcomes and meets user needs
  • Experience of managing high profile stakeholders / end users gather understanding for direction for product development
  • Experience of building a business case to inform project continuation
  • Experience of planning and executing agile projects
  • Experience of providing governance processes including mechanisms for appropriate assurance and quality of delivery
  • Experience of working with commercially sensitive data, demonstrating understanding of data security, confidentiality and integrity
  • Experience in using robust metrics, analytics, search data and user feedback; experience with Google Tag Manager and Google Analytics for usage tracking
  • Demonstrable experience of prototyping, testing and iterating with users and stakeholders
  • Experience of developing content strategies and information architectures for new websites and services. Experience writing documentation for systems including setup, configuration and high level architecture and process
  • Experience with C#, MVC, Razor, SQL, IIS, Nunit/xUnit and a Visual Studio development environment (system must be compatible with NICE core technical stack and with NICE's hosted environment on AWS)
  • Expertise in front-end, UI web development (semantic HTML5/CSS3 and CSS pre-processors); modern front end javascript (including ES6), libraries like jQuery, frameworks like Angular, React; Front-end build tools like Grunt, Gulp
  • Experience of successful development of back-end technologies, databases, developing APIs, meeting data standards, and experience of GitHub and deployment tools such as TeamCity and Octopus Deploy
  • Experience developing scalable, load-balanced web applications: Experience conducting load tests, performance profiling and optimizing performance bottlenecks
  • Experience of delivering software to high level of quality through automated testing (unit/integration/acceptance); mantenance of a good level of automated test code coverage (60-70%). Knowledge of software development best practices
  • Experience in building responsive web applications suitable for a variety of devices and screen sizes and designing for touch devices; Ability to build for IE8+, Chrome, Safari and Firefox.
  • Experience of designing, implementing and testing to meet WCAG 2.0 AA
Nice-to-have skills and experience
  • Experience of working within a medicial technologies environment (devices, diagnostics, digital health tools) or similar
  • Demonstrable understanding of NHS culture and landscape from a technology/digital perspective and the potential barriers this may bring to an agile delivery.
  • Experience with NoSQL databases such as RavenDB, MongoDB, NancyFx Web framework, Docker, dotnet core, Node.js in order to build a system compatible with wider NICE technical stack

How suppliers will be evaluated

How suppliers will be evaluated
Opportunity attribute name Opportunity attribute value
How many suppliers to evaluate 6
Proposal criteria
  • Please respond against the first package of work available at http://labs.nice.org.uk/medtechscan/
  • Proposed approach and methodology for delivery and governance of this project (20%)
  • Proposed approach to gather stakeholder and user needs, and end-to-end user journeys (20%)
  • How will the solution manage the commercial and sensitive data requirements of the project (10%)
  • Proposed deliverables and timeline for Discovery and Alpha (5%)
  • Potential risks and dependencies to the project. How they have been identified? What are suggested approaches to manage them? (5%)
  • Proposed team structure and profile of team members including CVs (10%)
Cultural fit criteria
Payment approach Fixed price
Assessment methods
  • Written proposal
  • Case study
  • Work history
  • Presentation
Evaluation weighting

Technical competence

70%

Cultural fit

10%

Price

20%

Questions asked by suppliers

Questions asked by suppliers
Supplier question Buyer answer
1. "Experience with C#, MVC, Razor, SQL, IIS, Nunit/xUnit and a Visual Studio development environment (system must be compatible with NICE core technical stack and with NICE's hosted environment on AWS)" is mentioned as requirement, but also that NoSQL and Node.js experience would be a nice to have, will an open source technology proposal based on MongoDB and Node be acceptable instead of MS & C#? No, an open source technology proposal based on MongoDB and Node would not be acceptable instead of MS & C#
2. Will NICE be able to provide any key project roles to augment the supplier team? What of the team profile could NICE provide support with to enable a blended team approach, e.g. business analysts, testers, developers, project managers, content specialists? NICE will be able to provide a delivery manager who will act as the product owner and main contact at NICE. It is expected that the supplier will provide all key project roles.
3. Is the budget outlined by NICE for phases 1 & 2 expected to include product licence costs? Or are these budgeted for separately? Yes, the budget published includes any product licence costs. This is the total budget available for the project.
4. Is NICE open to suppliers doing the Discovery & Alpha quicker than the proposed 4 months? Yes
5. Are you using NICEdocs? There is no intention to use NICEdocs during this project.
6. Do NICE plan on undertaking GDS-style Alpha and Beta sign-off assessments? This service does not fall within the scope of the digital spend controls and therefore does not require GDS to undertake service assessments. However, NICE expects suppliers to work in accordance with the GDS 18 point standards as delivery best practice.
7. "Experience with C#, MVC, Razor, SQL, IIS, Nunit/xUnit and a Visual Studio development environment (system must be compatible with NICE core technical stack and with NICE's hosted environment on AWS)" is mentioned as requirement, but also that NoSQL and Node.js experience would be a nice to have, will an open source technology proposal based on MongoDB and Node be acceptable instead of MS & C#? No, an open source technology proposal based on MongoDB and Node would not be acceptable. We require solution to use a C# .NET/SQL stack.
8. Is the budget outlined by NICE expected to include the cost of cloud hosting? No, NICE will absorb the hosting costs via their current AWS contract.
9. Does NICE have the capacity/capability to manage this service once it is in Beta? Or will NICE expect ongoing support/maintenance from the selected supplier? NICE/NHS England will take on support once the service is Live on the assumption appropriate transition of service and transfer of expertise takes place from the supplier. NICE will require a warranty period post launch to Live to ensure this has taken place effectively.
10. Is there a NICE mechanism to access any NICE N3 environments from the public internet cloud? There is no mechanism as NICE does not have an N3 network, nor is NICE connected to the NHS N3 network.
11. Are there existing NICE AWS instances that are already set up for Dev/UAT/Live? No, but NICE Operations will be on hand to build environments when the project has begun and hosting specs/requirements have been defined. The supplier would be expected to liaise with NICE Operations to define hosting requirements.
12. Is there existing connectivity from AWS to the N3 hosting environment? NICE does not have an N3 network, nor is NICE connected to the NHS N3 network. NICE cannot comment on any other existing connectivity from AWS to N3.
13. What environments would NICE require the selected supplier to provide? NICE Operations will provide appropriate hosting environments
14. Are there any other suppliers involved in hosting who the selected supplier would be expected to engage with? No.
15. Is the data being processed commercially sensitive? If so what security controls would be required, e.g. encryption in transit/at rest? Yes, the data is commercially sensitive. Yes, it would need to be encrypted in transit and at rest. NICE will conduct a pen test of the system which will form part of the acceptance/transition criteria and warranty period.
16. Are there existing NICE AWS instances that are already set up for Dev/UAT/Live? No, but NICE Operations will be on hand to build alpha/beta/live environments when the project has begun and hosting specs/requirements have been defined. The supplier would be expected to liase with NICE Operations to define hosting requirements. The supplier would be expected to host their own dev and test environments.
17. Can NICE confirm whether or not there is a full time Product Owner? If so, where are they based? NICE will be able to provide a delivery manager who will act as the product owner and main contact at NICE, based in Manchester. It is expected that the supplier will provide all key project roles.
18. Unfortunately we missed the early engagement day – but we have downloaded the slides from the event (and all other paperwork), This doesn't contain any question asked by other suppliers (or answers) from the supplier day - will you be sharing this? Given that this is a fixed price project, the brief lacks some critical detail around what the alpha is expected to contain/be. Is there a more defined scope you're able to share at this point? A summary of the questions and answers from the Early Engagement Session is now available at:
http://labs.nice.org.uk/medtechscan/. This document includes further information on alpha in the following Q&A:
Q Does NICE have expectations of regarding the functionality of the alpha product?
A The supplier is expected to define the functionality of this product. NICE would expect an alpha product to be a simple prototype of the system which would sufficiently represent all the defined user journeys. For example, mock-ups of input/output screens, click-throughs to represent the user journey from login to log out.