Section one: Contracting authority
one.1) Name and addresses
University College London Hospitals NHS FT
250 Euston Road
London
NW1 2PG
Contact
Stevie Cavanagh
Country
United Kingdom
Region code
UKI31 - Camden and City of London
Internet address(es)
Main address
Buyer's address
one.3) Communication
Additional information can be obtained from the above-mentioned address
Electronic communication requires the use of tools and devices that are not generally available. Unrestricted and full direct access to these tools and devices is possible, free of charge, at
https://health-family.force.com/s/Welcome
one.4) Type of the contracting authority
Body governed by public law
one.5) Main activity
Health
Section two: Object
two.1) Scope of the procurement
two.1.1) Title
NCL integration hub & patient identity capability
two.1.2) Main CPV code
- 48900000 - Miscellaneous software package and computer systems
two.1.3) Type of contract
Supplies
two.1.4) Short description
North Central London (NCL) ICB is delivering numerous digital healthcare projects, many of which involve information exchanges between systems across Trust boundaries. NCL wishes to explore the option of creating an ICS-wide integration hub and patient identity capability.
Suppliers are invited to register their interest to deliver such a solution on behalf on NCL.
two.1.5) Estimated total value
Value excluding VAT: £500,000
two.1.6) Information about lots
This contract is divided into lots: No
two.2) Description
two.2.3) Place of performance
NUTS codes
- UKI31 - Camden and City of London
Main site or place of performance
250 Euston Road
London
NW1 "PG
two.2.4) Description of the procurement
North Central London (NCL) ICB is delivering numerous digital healthcare projects, many of which involve information exchanges between systems across Trust boundaries. NCL wishes to explore the option of creating an ICS-wide integration hub and patient identity capability.
Suppliers are invited to register their interest to deliver such a solution on behalf on NCL.
High level requirements
1. Integration hub
The NCL integration hub shall:
• Provide a mechanism for routing, filtering and transforming information exchanges between systems. Typically, this involves mediating between Trust Integration Engines (TIEs) and regional or national systems.
• Support the use of industry integration and data standards (e.g. HL7 v2, HL7 FHIR, use of NHS number).
• Provide data interoperability to ensure safe and successful integration.
• Support synchronous and asynchronous integration patterns.
• Implement loosely coupled and scalable integration.
• Provide security of data both at rest and in transit.
• Be capable of supporting large volumes of information exchanges.
• Implement audit and logging of all information exchanges.
• Provide integration resilience through support for industry best practice integration patterns.
• Be designed to support future growth and innovation of the solution.
2. Patient identity capability
The NCL patient identity capability shall support the adoption of NHS Number as the primary patient identifier used in NCL digital healthcare projects. Many Trust systems remain dependent on the use of local patient identifiers (e.g. MRNs).
This will require the solution to be able to mediate between patient records dependent on local patient identifiers and records that are dependent on NHS Number (e.g. the patient record held within GP systems or on NHS PDS).
The patient identity capability will be used in conjunction with the NCL integration hub to ensure the relevant patient details are presented to each integrated system.
Initial scope
Suppliers should consider the following initial scope for the integration hub and patient identity capability:
a. Receive HL7 v2 ADT messages from seven Trusts, mediating and routing those messages to up to three regional/national systems.
b. Receive HL7 v2 Radiology Order messages from a regional order communications system, mediating and routing those messages to up to four Trusts.
c. Receive HL7 v2 Radiology Order and Result messages from seven Trusts, mediating and routing those messages to up to two regional/national systems.
d. Receive HL7 v2 Pathology Order and Result messages from five Trusts, routing and mediating those messages to a national system.
e. Receive HL7 v2 Order messages from a national system, routing those messages to up to five Trusts.
f. The solution must provide a mechanism, enriching message content as appropriate, to mediate between patient records dependent on local patient identifiers and records that are dependent on NHS Number.
g. Connectivity via HSCN will be required.
h. All information exchanges will need to be encrypted in transit.
i. The solution must be hosted in accordance with NHS guidelines.
j. The solution must be capable of passing a DTAC assessment.
Suppliers are requested to provide expressions of interest including, where appropriate, any pertinent solution details which are felt pertinent to that supplier’s offering.
This notice does not constitute a formal call for competition.
Expressions of interest should be e-mailed to steviejay.cavanagh@nhs.net by 15:00 on 30th January 2025.
two.2.14) Additional information
This notice does not constitute a formal call for competition.
Expressions of interest should be e-mailed to steviejay.cavanagh@nhs.net by 15:00 on 30th January 2025.
two.3) Estimated date of publication of contract notice
14 January 2025
Section four. Procedure
four.1) Description
four.1.8) Information about the Government Procurement Agreement (GPA)
The procurement is covered by the Government Procurement Agreement: Yes
Section six. Complementary information
six.3) Additional information
This notice does not constitute a formal call for competition.
Expressions of interest should be e-mailed to steviejay.cavanagh@nhs.net by 15:00 on 30th January 2025.