Health Data Research UK

Gateway Portal - MVP

Incomplete applications

44
Incomplete applications
37 SME, 7 large

Completed applications

8
Completed applications
7 SME, 1 large
Important dates
Opportunity attribute name Opportunity attribute value
Published Thursday 4 July 2019
Deadline for asking questions Thursday 11 July 2019 at 11:59pm GMT
Closing date for applications Thursday 18 July 2019 at 11:59pm GMT

Overview

Overview
Opportunity attribute name Opportunity attribute value
Summary of the work HDR UK requires a supplier that can provide resources to develop the Health Data Research Innovation Gateway: Gateway Portal to support health data research. The requirements of this infrastructure are laid out in the Health Data Research Innovation Gateway Design Specifation (https://www.hdruk.ac.uk/wp-content/uploads/2019/07/HDR-UK-Gateway-Portal-MVP-Specification.pdf)
Latest start date Monday 23 September 2019
Expected contract length 5 months
Location No specific location, eg they can work remotely
Organisation the work is for Health Data Research UK
Budget range No commitment to minimum spend over the term of the contract.

The maximum spend is £250,000 including VAT.

About the work

About the work
Opportunity attribute name Opportunity attribute value
Why the work is being done This work forms part of the UKRI Industrial Strategy Challenge Fund Digital Innovation Hub Programme, a national initiative which aims to increase the use of health data for research.
Problem to be solved Health data that is available for research cannot be easily found and accessed. Tools exist that sort information available, providing limited search functionality but these do not collect the range of datasets, and require the user to directly contact the data custodians.
Suppliers will be required to develop a Minimum Viable Product for the Gateway Portal that meets the Specification (https://www.hdruk.ac.uk/wp-content/uploads/2019/07/HDR-UK-Gateway-Portal-MVP-Specification.pdf) and improves discoverability and accessibility of health data from the Alliance and other data custodians. This will be required to integrate with an existing metadata catalogue which will be developed through a separate process.
Who the users are and what they need to do As a researcher or innovator, from the NHS, academia or industry, I need to identify, access and link the health data that is available for me so that I can use this for specific purposes such as developing new treatments, evaluating the impact of specific interventions or deciding on the most effective approaches for managing the NHS.
Early market engagement HDR UK has undertaken a six-month Design and Dialogue process as part of the Digital Innovation Hub Programme. Through this process, we have engaged with over 2,700 people and over 350 organisations. This has allowed a detailed insight into the needs of users. For example, over 70% of users from industry identified the inability to quickly access data as being a major barrier to the use of data for research and innovation.

In addition to engaging with potential users of the tool, HDR UK has engaged with many experts and potential suppliers through activities relating to the Digital Innovation Hub programme. In particular, we have hosted five co-design workshops around a series of themes with a combination of industry, NHS and academia. Patients, the public and charities have also provided early input into the design of the Programme.
Any work that’s already been done HDR UK has not developed any work directly. However, there are large numbers of existing tools and services available for users. The HDR UK team have a good understanding of the current infrastructure and the needs of users, as outlined in the ‘Early Market Engagement’ section.
Existing team Suppliers will be required to work alongside the following HDR UK team:
Gerry Reilly, Chief Technology Officer
Caroline Cake, Chief Operating Officer and responsible for DIH programme delivery
Dan Fisher, Technical Solutions Architect
Ben Gordon, Digital Innovation Hub Programme Director
Kay Snowley, Digital Innovation Hub Project Manager
David Seymour, Partnership Director and key contact for the UK Health Data Research Alliance

In addition, the successful suppliers will be required to work with or alongside the team providing the metadata catalogue element of the Gateway which will be addressed through a separate procurement.
Current phase Not applicable

Work setup

Work setup
Opportunity attribute name Opportunity attribute value
Address where the work will take place Remotely, but will need to work closely with the HDR UK team attend the office at:
Health Data Research UK
Gibbs Building
215 Euston Road
London
NW1 2BE
Working arrangements Working remotely.

Key members of the team will be required to join weekly in-person scrums with HDR UK team to review progress and priorities.

Every 2 weeks, the suppliers will be expected to demonstrate a shippable iteration of the product.
Security clearance No expected specific security clearance is required.

Additional information

Additional information
Opportunity attribute name Opportunity attribute value
Additional terms and conditions The standard DOS 3 contract will be used.

Suppliers should subscribe to the Health Data Research UK Principles for Participation, which includes a commitment to open source, open standards and open data, and FAIR data principles.

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
  • Demonstrable skills and experience in design-led thinking, evidenced by a strong design portfolio
  • Experience in use of modern UI frameworks and tools, e.g. Angular, JS, CSS, HTML 5
  • Experience working with metadata, data constructs, modelling and ontology
  • Experience with open source tools, standards and API design
  • Ability to integrate open source logging technologies and open source identity management tools
  • Developing a platform that can work with large scale data in a pragmatic, user-friendly manner
  • Strong agile project management, with experience delivering complex projects in timely manner
  • Agile teams, able to respond to changing environment
  • Integrate with existing and not-yet-developed infrastructure projects through modular development and APIs
  • Experience with multi-modal data from multiple sources
Nice-to-have skills and experience
  • Skill to form technology partnership which could extend into Phase 2 of the Gateway development
  • Experience forming consortium of multiple technology partners, including SMEs
  • Experience working with health data, or other functional public sector data of varying quality

How suppliers will be evaluated

How suppliers will be evaluated
Opportunity attribute name Opportunity attribute value
How many suppliers to evaluate 10
Proposal criteria
  • Technical solution
  • Approach and methodology
  • Proposed timesframes
  • RIsk and dependencies
  • Team Structure
  • Value for money
Cultural fit criteria
  • Demonstrate the organisation’s expertise and track record in governance, management systems and achieving product development at pace.
  • Describe your approach to managing any problems that arise during the delivery of the project.
  • Explain how you develop relationships with stakeholders of varying levels of technical expertise and form consortia of multiple technology partners including SME’s.
  • Describe your approach to user engagement through the design stage.
Payment approach Capped time and materials
Assessment methods
  • Written proposal
  • Case study
  • Work history
  • Reference
  • Presentation
Evaluation weighting

Technical competence

70%

Cultural fit

10%

Price

20%

Questions asked by suppliers

Questions asked by suppliers
Supplier question Buyer answer
1. "In addition, the successful suppliers will be required to work with or alongside the team providing the metadata catalogue element of the Gateway which will be addressed through a separate procurement.
"
When are you anticipating the procurement on this project?
The procurement for the metadata catalogue commenced on 8th July. The requirement was published to Contracts Finder: https://www.contractsfinder.service.gov.uk/Notice/18aac581-2abc-4a35-8b97-4da1faf4ed6c

Full details of all phases of the Gateway Development procurement can be found on our website: https://www.hdruk.ac.uk/gateway-development/
2. Could you clarify what is meant by : Skill to form technology partnership which could extend into Phase 2 of the Gateway development? After a successful MVP HDRUK are looking to form a technology partnership for future development (Phase 2 and beyond). Organisations which deliver elements of the Gateway should demonstrate the ability to work collaboratively with other organisations.
Please note that HDRUK are not mandating that only organisation capable of forming a technical partnership should apply and its a desirable requirement rather than a mandatory requirement.
3. You refer to a need for experience in the use of modern UI frameworks and tools, e.g. Angular, JS, CSS, HTML 5. Do you require experience in these specific technologies or would more broad experience of modern interactive front-end work be sufficient? The design brief is a modern, clean, extensible api driven system, to achieve this HRDUK believe that Angular, JS, CSS and HTML5 offers the best route. However HDRUK is not prescriptive in respect to the technologies, HRDUK believe that Angular, JS, CSS and HTML5 offers a strong base but we will consider other open and standards based approaches.
4. Could you tell us in detail the scope of datasets in the data hub for the MVP? The datasets cover a plethora of health data, stored across multiple data custodians, which must be searchable. Within the MVP there will be no access to this data only the underlying metadata which will represent the initial datasets. The MVP must be extensible to support metadata from a wide range of structured, semi-structured and unstructured datasets from a range of modalities include EHR, imaging and genomics. Examples can be seen from the Health Data Finder http://www.hdf.nihr.ac.uk/
5. Could you kindly provide details of the resources HDR UK will provide e.g. Scrum Master, Product owner, etc. HDRUK will provide access to a hands on CTO together with solution architects who will acts as technical authorities and product owners. The supplier will co-develop with HDR UK and will be responsible for providing project management, with a scrum master is appropriate and an experience architect. They will collaborate with the HDR UK CTO and Technical Solutions Architect, and the HDR UK Programme Management Team.
6. Which environment (e.g.: production?) will the dev and integration works be done before the MVP release? Environments covering Development, Staging / Integration, Testing and Production The project will be conducting using Agile methodology with a CI/CD approach. For the MVP we anticipate development and a deployment environment. Working and deployed code will be available at the end of each iteration will be demonstrated and discussed in an sprint review.
7. Our assumption is that you will provide us with the cloud environment and access for the MVP development – is that correct? Correct, we are currently evaluating our cloud provider selection.
8. Can we use off-shore resources to deliver the solution? The supplier is welcome to use a team that is a mix of UK and off shores resources provided that the requirement to be available for face to face weekly meetings in London can be met, and that attendance at this meetings will including the key project management and technical resources from the supplier.
9. Are expenses included in the funding or is there funding available on top of the £250k? No additional expenses will be provided beyond the 250K including VAT detailed in the requirements specification.
10. What underlying access management system will we need to integrate with and Which identity providers will be in scope for the MVP? Our current design assumption is that we will provide access management through integration with support from the UK Access Management Federation (https://www.jisc.ac.uk/uk-federation), However additional user profile management capability will be required beyond the capability from the UK Access Management Federation.
11. Is the ontology service already available? If not, when will this be ready for integration? Integration with the ontology server is not part of the MVP. However we are actively working with partners on ontology support.
12. Do you have collaboration tools of choice available or is the expectation that this should be provided by the supplier (e.g. Jira, confluence etc.)? Both Jira and Confluence will be provided..
13. Does the supplier also need to provide support of the gateway or is that out of scope for the MVP? A key component of the MVP is first class documentation, coupled with a detailed handover. This should be planned by the supplier to allow HDRUK to support the MVP moving forward.
14. Please can you give examples of the types of new software’s you would expect to be shared as open source? All assets developed within the project, including but not limited to code, web assets, images, reference data is to be the intellectual property of HDRUK which will be open sourced.
15. Can you confirm that suppliers’ existing background IP will not be expected to be open sourced under this contract? HDR UK anticipates that the development an be undertaken without a supplier bringing additional existing proprietary components with background IP. However suppliers are welcome to use open source from established projects.  If the supplier with HDR UK’s approval uses existing proprietary components, the supplier will not be expected to open source those component but would be expected to provide HDR UK with a free, non-exclusive, perpetual and assignable licence to those components.
16. Could you let us know the number of users at MVP go live, number of production users at end of 2019, 2020 etc. please? The MVP will be developed with the input of a small group of expert users. The intention of the MVP is to rapidly deliver a prototype which can be iterated upon and to steer the thinking for further development. The MVP will be required to be able scale seamlessly, we need to support 100s of datasets, 1,000s of registered users but probably only 10 -100s of concurrent active users.
17. Could you let us know of the Geographical location(s) of expected users please? The MVP user community will be based in the UK. That said the solution must be accessible globally and the design and infrastructure must not preclude this.
18. Are there specific asset libraries you would want us to use – for example, should we use GBS Asset library for the portal front end design? HDR UK anticipates that the development can be undertaken without a supplier bringing additional existing proprietary components with background IP. However suppliers are welcome to use open source from established projects. If the supplier with HDR UK’s approval uses existing proprietary components, the supplier will not be expected to open source those component but would be expected to provide HDR UK with a free, non-exclusive, perpetual and assignable licence to those components.
19. Could you confirm what type of meta data we will be working on ? for example: admin, technical, etc As outlined in the detailed specification on the HDR UK website, the metadata will include operational and business as well as technical metadata. All aspects of the datasets will be recorded as metadata so this will include for example provenance, dataset usage, access requirements, usage characteristics, quality information, user feedback as well as coded information on the elements of the dataset. It is anticipate that the metadata for a dataset will fully describe all aspects of the dataset and this will allow migration of metadata between catalogue and the generation of webpages to describe a dataset.
20. Will the successful supplier be expected to handle / process any data, especially PII data? The supplier will not be responsible for processing of any data, they are supplying resources to work under the direction of HDR UK.
21. What level of SLA, if any, will be required for the MVP beyond being “straightforward” and providing a “good user experience”? Service Level Agreements cover availability, recoverability and are covered within Gateway specification.  The successful supplier will be able to demonstrate a history of developing and delivering first rate uses experience and this must be evident in any proposal and subsequent interviews.
Environments covering Development, Staging / Integration, Testing and Production will be provided.
22. What relevant, what development environment and tools will be provided? Environments covering Development, Staging / Integration, Testing and Production The project will be conducting using Agile methodology with a CI/CD approach. For the MVP we anticipate development and a deployment environment. Working and deployed code will be available at the end of each iteration will be demonstrated and discussed in an sprint review. In addition both Confluence and Jira will be provided.
23. Which private cloud technology will be made available to develop and host the web application? All development and deployment will be hosted in a public cloud environment. HDR UK will not be making use of private cloud technology for this application.
24. Will HDRUK provide any Agile delivery tools (e.g. JIRA) to enable the delivery team to deliver fortnightly release increments? Confluence and Jira will be provide to facilitate and manage agile design, development and product delivery.
25. Has any design work been completed on the metadata APIs? If not, does responsibility for API design sit with the metadata catalogue project or the gateway MVP? The required APIs will be described in the epics and user stories being developed in outline by HDR UK. HDR UK and the supplier will collaborate on the detailed design of the APIs. All APIs will be documented and made publicly available.
26. Should we assume that the discoverable elements of the metadata catalogue will be defined before the Gateway Portal MVP commences on 23/09/19? Elements of the metadata catalogue will be available before 23/09/2019. However HDRUK and the project deliverables are agile so expect this to be extended and even changed during the process.
27. Will HDR-UK manage the delivery and dependencies across the metadata catalogue and Gateway deliveries? The HDR UK team will ensure that there is a harmonious relationship across the Catalogue and Gateway developmental and integration landscapes. However it is expected that developers in both landscapes will be proactive and communicate to resolve issues.
28. Will a consistent Agile approach be used across both projects with the same tooling used to manage product backlogs and sprint deliveries? HDR UK will be using a consistent Agile approach across the project. The details of tools and approach will be agreed with the supplier.
29. Is near-shore or off-shore development allowed for this project, if supported by onshore UX expertise? It is key to HDRUK that the project is executed in a agile scrum type fashion, for this reason its envisaged that regular sprint planning, review and retrospectives are required and for these to be face to face.
30. Is there a requirement to provide technical support to the MVP after phase 1 has been completed? As key component of the MVP is first class documentation, this coupled with a detailed handover should be planned by the supplier to allow HDRUK to support the MVP moving forward.
31. Will HDR UK ‘administer’ the platform (e.g. user accounts) once the MVP is completed? HDR UK will own the operation responsibility for the MVP following acceptance of the final iteration. However the MVP will be expected to have self service for key administrative aspects such as user profile management and onboarding of datasets.
32. What volume of users are expected to use the MVP when it is completed? How many concurrent users? The MVP will be developed with the input of a small group of expert users. The intention of the MVP is to rapidly deliver a prototype which can be iterated upon and to steer the thinking for further development. The MVP will be required to be able scale seamlessly, we need to support 100s of datasets, 1,000s of registered users but probably only 10 -100s of concurrent active users.
33. Are there any IG constraints for sharing metadata that need to be considered when designing the MVP? IG is not the responsibility of the supplier. HDR UK will manage the relationship with the data controller and the provision of metadata.
34. What type of roles, if any, will be performed by HDR UK? Is there any shadowing and knowledge transfer in the MVP building? HDRUK will provide access to a Hands on CTO together with solution architects who will acts as technical authorities and product owners.
35. The MVP will follow the security and compliance policies from HDRUK? This will be cover by HDRUK roles? Security and Compliance policies and processes will be managed by HDRUK. The developed gateway platform will need to demonstrate secure best practices in respect to encryption, access management and resistance to issues such as SQL Injection.
36. What is the role of FAIR data in the MVP? FAIR is a set of guiding principles covering the findability, accessibility, interoperability and reusability of the developed stack. Any proposal should detail how the supplier plans to design and deliver to meet these principles. Key principles of FAIR are detailed here https://www.force11.org/group/fairgroup/fairprinciples
37. The MVP will include federated access (SSO)? The MVP is not expected to support federate access, however this will be a key element of the Phase 2 Technology Partnership.
38. The MVP mentions: “Embed analytics capability to assess use in order to understand how to meet the needs of users and support further access to data.” Is this part of phase 2? The MVP will support logging of all queries and user interactions. Metrics from these will be used to inform the requirements of the design of Phase 2. Federated analytics on data is expected to be part of the Phase 2 development.
39. The MVP integrates the meta data engine from the other project but also it needs to provide an engine on top to connect to information coming from other APIs (for example a university library API)? All component of the MVP will be integrated via published APIs. It is also expected that the MVP will need to integrate with other service via APIs to support user identity management and the generation of metrics including potentially dashboard support.
40. The workflow of access to data, depends on off-line decisions? And the Gateway is only used to receive the request and communicate the granted access? Can you provide an example of a flow? In the MVP, the access request management is not expected to be beyond the initial submission of the request with the existing process handling the request from that point forward. As a stretch goal, we would extend to support the full workflow for a limited number of data controllers. Workflows for these controllers will be developed by HDR UK, however ultimately the gateway will be expected to provide a flexible workflow management and rules engine to support a configurable approach to front end the range of workflows from different controllers.
41. The Audit and logging capabilities can be covered by an out-of-the-box solution, like google analytics? HDRUK feels that to achieve the desired outcomes of auditing and logging the ELK stack made up of elastic search, log stash and Kibana would be best served to deliver this, we are open to considering other options. For the purposes of auditing and logging Google analytics will not be able to deliver this as it only covers web based analytics. Audit and Logging will be required to log errors and well as providing MVP based insights through configurable user driven dashboards.
42. Which are the “role model” websites with respect to User Experience for HDR-UK? We would hope that any supplier would have a clear idea of this objective before submitting any proposal. HDRUK will provide and facilitate design thinking workshop to narrow in on this. Any proposal must demonstrate a track record UX lead development, delivering against principles such as Hierarchy, Consistency, Confirmation, User Control and Accessibility.
The deadline for asking questions about this opportunity was Thursday 11 July 2019.