This opportunity is closed for applications

The deadline was Thursday 16 February 2017
Leicestershire Partnership NHS Trust

ChatHealth 2 (replacement for ChatHealth 1) - health advice secure messaging platform

0 Incomplete applications

18 Completed applications

17 SME, 1 large

Important dates

Thursday 2 February 2017
Deadline for asking questions
Thursday 9 February 2017 at 11:59pm GMT
Closing date for applications
Thursday 16 February 2017 at 11:59pm GMT


Summary of the work
Design/development of a secure N3 web-based application for use by clinicians as a communications management portal. Plus, service-user instant messaging application which will be accessible as a web application or as a mobile application downloaded to mobiles via the app stores. A product requirements document will be available.
Latest start date
Expected contract length
No specific location, eg they can work remotely
Organisation the work is for
Leicestershire Partnership NHS Trust
Budget range
£50,000 in Yr1

About the work

Why the work is being done
New development to replace an existing application in order to improve the quality of the service we provide to people seeking health advice. The ChatHealth platform is a tool that organisations can use as part of their digital offer. This is important in the context of the five year plan for the NHS which expects service providers to offer a wider range of choice about how people access services.
Problem to be solved
The current product is now 5 years old and due to the increase in the numbers of staff and organisations using the application, a redesign of the application starting from an enhanced requirements document is needed.
Who the users are and what they need to do
As a person needing health advice, I need to contact a nurse or clinical practitioner so that I can ask for and receive confidential advice. ChatHealth is a communications platform used by the nurses or clinical practitioners to respond to those inquiries and conduct episodes of care via this platform.
Early market engagement
Any work that’s already been done
Existing team
The supplier will need to work with our team which is made up of a non-technical product owner, a Technical Delivery Manager and project management support. Our team reports to a board to ensure governance of the project. The team will help the supplier interface with the User Group of staff which we would involve in the delivery process.
Current phase

Work setup

Address where the work will take place
The supplier will work from their own location with meetings at regular intervals in the midlands and/or virtually.
Working arrangements
Remote working with webinars and face to face meetings.
Security clearance
Before delivery, suppliers will be expected to complete a "Request for Software" form and provide assurances which satisfy the Trust's information security policy.

Additional information

Additional terms and conditions
We have particular requirements on intellectual property rights which support the vendor and the Trust working together to commercialise the output from the contract.

We require a Non Disclosure Agreement to be signed prior to issue of any tender documents.

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
  • Be able to commence work on the project by 20 March 2017
  • Have proven experience of successfully delivering web based and mobile applications involving real time communications platforms including SMS and IM
  • Have security and encryption controls applied to their external communications
  • Have a track record of integrating with other 3rd party applications, data sets and identity management systems
  • Have an open approach to team working and collaboration with non-technical clients
  • Have strong experience of application design, build and delivery of products within an iterative cycle
  • Have a proven experience of formal project management methodologies
  • Have a track record of delivering training for trainers
Nice-to-have skills and experience
  • A track record of succesfully working with the NHS
  • A formal risk and opportunity process
  • Delivery of digital products in the private sector

How suppliers will be evaluated

How many suppliers to evaluate
Proposal criteria
  • The understanding of LPT's requirements
  • How the technical solution meets the requirements
  • Submitted CV's of delivery team members
  • Adequacy of the delivery program
  • Value for money
Cultural fit criteria
  • Work as a team with our organisation
  • Be transparant and collaborative in decision making
  • Be able to work with less tech savvy clients
Payment approach
Fixed price
Assessment methods
  • Written proposal
  • Work history
  • Reference
  • Presentation
Evaluation weighting

Technical competence


Cultural fit




Questions asked by suppliers

1. You mention the desire for either a web-based or mobile tool for service users. As these 2 approaches are distinctly different from a project resource and support point of view, can you provide some insight into the preferred method, please? Our assumption is a mobile, though some clarification on the preferred platform would also support our assumptions. (E.g. iOS, Android or Windows)
We expect that the Instant Messaging service will be available as a mobile application available within app stores. The Instant Messaging service will also be available as a web based responsive application. The Instant Messaging web application will also appear as a chat window in the ChatHealth public facing website, and will be available as a chat widget which can be embedded into partner websites.

The ChatHealth staff messaging console will be available as a web based responsive application and a future phase will see the delivery of the messaging console available as a mobile application available within app stores.
2. Can you clarify if your defined budget assumes support coverage throughout the first year or whether this will be under a separate budget? If a mobile app approach is taken for service-users, have you considered the impact of annual support for an app ecosystem? (E.g. new OS releases, new device compatibility etc...)
The given budget does includes first year support as well as development.
3. Does the current project roadmap indicate an assumed end-of-life for ChatHealth 2? I.e. How long do you envisage the new platform to require supplier engagement. (E.g. Support, iteration etc...)
The engagement under the initial contract award will be two years. When the specification is issued you will see there is a significant road map that goes beyond this current tranche of work.