Home / Opportunities / Opportunity
PROCUREMENT OPPORTUNITY

NCL integration hub & patient identity capability

University College London Hospitals NHS FT · compiled

Tender information last checkedLast checked 29 Sept 2026, 20:59.

Opportunity overview

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.<br/>Suppliers are invited to register their interest to deliver such a solution on behalf on NCL.

Classification

  • CPV48900000 — Miscellaneous software package and computer systems

Lots

  • 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.<br/>Suppliers are invited to register their interest to deliver such a solution on behalf on NCL.<br/><br/>High level requirements<br/>1. Integration hub<br/>The NCL integration hub shall:<br/>• 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.<br/>• Support the use of industry integration and data standards (e.g. HL7 v2, HL7 FHIR, use of NHS number).<br/>• Provide data interoperability to ensure safe and successful integration.<br/>• Support synchronous and asynchronous integration patterns.<br/>• Implement loosely coupled and scalable integration.<br/>• Provide security of data both at rest and in transit.<br/>• Be capable of supporting large volumes of information exchanges.<br/>• Implement audit and logging of all information exchanges.<br/>• Provide integration resilience through support for industry best practice integration patterns.<br/>• Be designed to support future growth and innovation of the solution.<br/><br/>2. Patient identity capability<br/>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).<br/>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).<br/>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.<br/><br/>Initial scope<br/>Suppliers should consider the following initial scope for the integration hub and patient identity capability:<br/>a. Receive HL7 v2 ADT messages from seven Trusts, mediating and routing those messages to up to three regional/national systems.<br/>b. Receive HL7 v2 Radiology Order messages from a regional order communications system, mediating and routing those messages to up to four Trusts.<br/>c. Receive HL7 v2 Radiology Order and Result messages from seven Trusts, mediating and routing those messages to up to two regional/national systems.<br/>d. Receive HL7 v2 Pathology Order and Result messages from five Trusts, routing and mediating those messages to a national system.<br/>e. Receive HL7 v2 Order messages from a national system, routing those messages to up to five Trusts.<br/>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.<br/>g. Connectivity via HSCN will be required.<br/>h. All information exchanges will need to be encrypted in transit.<br/>i. The solution must be hosted in accordance with NHS guidelines.<br/>j. The solution must be capable of passing a DTAC assessment.<br/><br/>Suppliers are requested to provide expressions of interest including, where appropriate, any pertinent solution details which are felt pertinent to that supplier’s offering.<br/><br/>This notice does not constitute a formal call for competition. <br/><br/>Expressions of interest should be e-mailed to steviejay.cavanagh@nhs.net by 15:00 on 30th January 2025. Additional information: This notice does not constitute a formal call for competition. <br/><br/>Expressions of interest should be e-mailed to steviejay.cavanagh@nhs.net by 15:00 on 30th January 2025.Value not stated

Published notice details

Additional information from the published procurement release. Fields appear only when supplied by the source; check the original notice and tender documents before acting.

Scope, procedure and submissions

Id
ocds-h6vhtk-04cff6
Status
planned
Main Procurement Category
goods

Covered By

GPA

Legal basis

Id
32014L0024
Scheme
CELEX

Communication

Future Notice Date
14 Jan 2025, 00:00

Classification

Id
48900000
Scheme
CPV
Description
Miscellaneous software package and computer systems

Lots and requirements

Entry 1
Id
1
Status
planned
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.<br/>Suppliers are invited to register their interest to deliver such a solution on behalf on NCL.<br/><br/>High level requirements<br/>1. Integration hub<br/>The NCL integration hub shall:<br/>• 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.<br/>• Support the use of industry integration and data standards (e.g. HL7 v2, HL7 FHIR, use of NHS number).<br/>• Provide data interoperability to ensure safe and successful integration.<br/>• Support synchronous and asynchronous integration patterns.<br/>• Implement loosely coupled and scalable integration.<br/>• Provide security of data both at rest and in transit.<br/>• Be capable of supporting large volumes of information exchanges.<br/>• Implement audit and logging of all information exchanges.<br/>• Provide integration resilience through support for industry best practice integration patterns.<br/>• Be designed to support future growth and innovation of the solution.<br/><br/>2. Patient identity capability<br/>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).<br/>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).<br/>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.<br/><br/>Initial scope<br/>Suppliers should consider the following initial scope for the integration hub and patient identity capability:<br/>a. Receive HL7 v2 ADT messages from seven Trusts, mediating and routing those messages to up to three regional/national systems.<br/>b. Receive HL7 v2 Radiology Order messages from a regional order communications system, mediating and routing those messages to up to four Trusts.<br/>c. Receive HL7 v2 Radiology Order and Result messages from seven Trusts, mediating and routing those messages to up to two regional/national systems.<br/>d. Receive HL7 v2 Pathology Order and Result messages from five Trusts, routing and mediating those messages to a national system.<br/>e. Receive HL7 v2 Order messages from a national system, routing those messages to up to five Trusts.<br/>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.<br/>g. Connectivity via HSCN will be required.<br/>h. All information exchanges will need to be encrypted in transit.<br/>i. The solution must be hosted in accordance with NHS guidelines.<br/>j. The solution must be capable of passing a DTAC assessment.<br/><br/>Suppliers are requested to provide expressions of interest including, where appropriate, any pertinent solution details which are felt pertinent to that supplier’s offering.<br/><br/>This notice does not constitute a formal call for competition. <br/><br/>Expressions of interest should be e-mailed to steviejay.cavanagh@nhs.net by 15:00 on 30th January 2025. Additional information: This notice does not constitute a formal call for competition. <br/><br/>Expressions of interest should be e-mailed to steviejay.cavanagh@nhs.net by 15:00 on 30th January 2025.

Items and delivery

Item 1
Id
1
Related Lot
1

Delivery Location

Description
250 Euston Road<br/>London<br/>NW1 "PG

Delivery locations

Entry 1
Region
UKI31

Buyer, suppliers and contacts

Organisation 1
Id
GB-FTS-14675
Name
University College London Hospitals NHS FT

Roles

buyer

Address

Region
UKI31
Locality
London
Postal Code
NW1 2PG
Country Name
United Kingdom
Street Address
250 Euston Road

Details

Classifications

Entry 1
Id
BODY_PUBLIC
Scheme
TED_CA_TYPE
Description
Body governed by public law
Entry 2
Id
07
Scheme
COFOG
Description
Health

Identifier

Legal Name
University College London Hospitals NHS FT

Contact

Name
Stevie Cavanagh

Recorded locations

  • Buyer location · London · UKI31 · NW1 2PG · United Kingdom
  • Delivery location · UKI31

Notice and amendment history

1 published notice version reviewed by ProcuraAxis.

1 VERSION
  1. ocds-h6vhtk-04cff6-2025-01-14T15:36:55Zcompiled ·