← Back to search results

plannedFind a Tender · planning

NCL integration hub & patient identity capability

Buyer: University College London Hospitals NHS FT →

BuyerUniversity College London Hospitals NHS FT
Statusplanned
DeadlineNot published
Value£500,000
Published14 Jan 2025

What is being bought

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.

Delivery location

UKI31

Categories

Miscellaneous software package and computer systems 48900000

Lot details

Lot 1

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.

Statusplanned

What is included

ItemCategoryQuantity
1Not publishedNot published

Comparable-procurement analytics

Benchmarked against retained Find a Tender procedures with CPV division 48. The category anchor is Miscellaneous software package and computer systems (48900000); this is a deliberately broad market comparator. The comparison is shown at several levels rather than pretending one company or region is always the best benchmark.

Comparison setProceduresReported bids per procedureNamed award suppliersPrice evidence
Market: CPV division 486,8361 median · 9.6 average (2,488 of 6,836 with a bid count)1.7 average (2,927 of 6,836 with named award suppliers)Not published
Same buyer31 median · 1 average (1 of 3 with a bid count)1 average (1 of 3 with named award suppliers)Not published
Delivery region: UKI31241 median · 2.3 average (13 of 24 with a bid count)1 average (15 of 24 with named award suppliers)Not published
Similar published value (0.5×–2×)5302 median · 2 average (2 of 530 with a bid count)1 average (2 of 530 with named award suppliers)Not published

“Reported bids” is an official aggregate, sometimes reported per lot; it is the closest available competition measure. “Named award suppliers” are winners, not all applicants.

Price-outcome signal

Not enough comparable procedures currently publish both a GBP tender value and a usable lowest-valid-bid value to calculate a responsible price-reduction benchmark. Tenderline deliberately does not infer a saving from named award suppliers or from missing award values.

Procurement strategy & market signals

Framework agreementNot published
Dynamic purchasing systemNot published
Competitive procurementNot published
Recurring requirementNot published
Procurement method rationaleNot published
Rationale classificationsNot published
Special regimeNot published
Covered byGPA
Submission policyNot published
Selection criteriaNot published
Risk detailsNot published

Planning & early market engagement

BudgetNot published
No-engagement rationaleNot published
Planning documents0
Planning milestones0

No planning milestones published.

Related procurements

No linked framework, prior procurement or reprocurement published.

Documents & submission route

No documents are published in the current source record.

Source data inventory

Diagnostic view. “Not published” means this current release does not provide a value.

OCIDocds-h6vhtk-04cff6
Latest release ID001224-2025
Latest release timestampTue Jan 14 2025 15:36:55 GMT+0000 (Coordinated Universal Time)
Sourcefind-a-tender
Official notice URLNot published
Tender statusplanned
Procurement methodNot published
Procurement method detailsNot published
Main procurement categorygoods
Above thresholdNot published
Legal basis32014L0024
Tender period: startNot published
Tender period: endNot published
Expression of interest deadlineNot published
Enquiry deadlineNot published
Award period: startNot published
Award period: endNot published
Submission method detailsNot published
Submission languagesNot published
Electronic catalogue policyNot published
Total tender value£500,000
Tender lots in source1
Tender items in source1
Tender documents in source0
Awards in latest release0
Contracts in latest release0
Parties in latest release1

Notice history

DateEventReference
14 Jan 2025planning001224-2025

All source data

Unmodified official OCDS data retained by Tenderline for this procurement process.

Complete current OCDS release JSON
{
  "id": "001224-2025",
  "tag": [
    "planning"
  ],
  "date": "2025-01-14T15:36:55Z",
  "ocid": "ocds-h6vhtk-04cff6",
  "buyer": {
    "id": "GB-FTS-14675",
    "name": "University College London Hospitals NHS FT"
  },
  "tender": {
    "id": "ocds-h6vhtk-04cff6",
    "lots": [
      {
        "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/>•\tProvide 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/>•\tSupport the use of industry integration and data standards (e.g. HL7 v2, HL7 FHIR, use of NHS number).<br/>•\tProvide data interoperability to ensure safe and successful integration.<br/>•\tSupport synchronous and asynchronous integration patterns.<br/>•\tImplement loosely coupled and scalable integration.<br/>•\tProvide security of data both at rest and in transit.<br/>•\tBe capable of supporting large volumes of information exchanges.<br/>•\tImplement audit and logging of all information exchanges.<br/>•\tProvide integration resilience through support for industry best practice integration patterns.<br/>•\tBe 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.\tReceive HL7 v2 ADT messages from seven Trusts, mediating and routing those messages to up to three regional/national systems.<br/>b.\tReceive HL7 v2 Radiology Order messages from a regional order communications system, mediating and routing those messages to up to four Trusts.<br/>c.\tReceive HL7 v2 Radiology Order and Result messages from seven Trusts, mediating and routing those messages to up to two regional/national systems.<br/>d.\tReceive HL7 v2 Pathology Order and Result messages from five Trusts, routing and mediating those messages to a national system.<br/>e.\tReceive HL7 v2 Order messages from a national system, routing those messages to up to five Trusts.<br/>f.\tThe 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.\tConnectivity via HSCN will be required.<br/>h.\tAll information exchanges will need to be encrypted in transit.<br/>i.\tThe solution must be hosted in accordance with NHS guidelines.<br/>j.\tThe 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": [
      {
        "id": "1",
        "relatedLot": "1",
        "deliveryLocation": {
          "description": "250 Euston Road<br/>London<br/>NW1 \"PG"
        },
        "deliveryAddresses": [
          {
            "region": "UKI31"
          }
        ]
      }
    ],
    "title": "NCL integration hub & patient identity capability",
    "value": {
      "amount": 500000,
      "currency": "GBP"
    },
    "status": "planned",
    "coveredBy": [
      "GPA"
    ],
    "legalBasis": {
      "id": "32014L0024",
      "scheme": "CELEX"
    },
    "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.",
    "communication": {
      "atypicalToolUrl": "https://health-family.force.com/s/Welcome",
      "futureNoticeDate": "2025-01-14T00:00:00Z"
    },
    "classification": {
      "id": "48900000",
      "scheme": "CPV",
      "description": "Miscellaneous software package and computer systems"
    },
    "mainProcurementCategory": "goods"
  },
  "parties": [
    {
      "id": "GB-FTS-14675",
      "name": "University College London Hospitals NHS FT",
      "roles": [
        "buyer"
      ],
      "address": {
        "region": "UKI31",
        "locality": "London",
        "postalCode": "NW1 2PG",
        "countryName": "United Kingdom",
        "streetAddress": "250 Euston Road"
      },
      "details": {
        "url": "https://www.uclh.nhs.uk",
        "buyerProfile": "https://www.uclh.nhs.uk/",
        "classifications": [
          {
            "id": "BODY_PUBLIC",
            "scheme": "TED_CA_TYPE",
            "description": "Body governed by public law"
          },
          {
            "id": "07",
            "scheme": "COFOG",
            "description": "Health"
          }
        ]
      },
      "identifier": {
        "legalName": "University College London Hospitals NHS FT"
      },
      "contactPoint": {
        "name": "Stevie Cavanagh",
        "email": "steviejay.cavanagh@nhs.net"
      }
    }
  ],
  "language": "en",
  "description": "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.",
  "initiationType": "tender"
}
Complete JSON history (1 releases)
14 Jan 2025 · 001224-2025 · planning
{
  "id": "001224-2025",
  "tag": [
    "planning"
  ],
  "date": "2025-01-14T15:36:55Z",
  "ocid": "ocds-h6vhtk-04cff6",
  "buyer": {
    "id": "GB-FTS-14675",
    "name": "University College London Hospitals NHS FT"
  },
  "tender": {
    "id": "ocds-h6vhtk-04cff6",
    "lots": [
      {
        "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/>•\tProvide 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/>•\tSupport the use of industry integration and data standards (e.g. HL7 v2, HL7 FHIR, use of NHS number).<br/>•\tProvide data interoperability to ensure safe and successful integration.<br/>•\tSupport synchronous and asynchronous integration patterns.<br/>•\tImplement loosely coupled and scalable integration.<br/>•\tProvide security of data both at rest and in transit.<br/>•\tBe capable of supporting large volumes of information exchanges.<br/>•\tImplement audit and logging of all information exchanges.<br/>•\tProvide integration resilience through support for industry best practice integration patterns.<br/>•\tBe 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.\tReceive HL7 v2 ADT messages from seven Trusts, mediating and routing those messages to up to three regional/national systems.<br/>b.\tReceive HL7 v2 Radiology Order messages from a regional order communications system, mediating and routing those messages to up to four Trusts.<br/>c.\tReceive HL7 v2 Radiology Order and Result messages from seven Trusts, mediating and routing those messages to up to two regional/national systems.<br/>d.\tReceive HL7 v2 Pathology Order and Result messages from five Trusts, routing and mediating those messages to a national system.<br/>e.\tReceive HL7 v2 Order messages from a national system, routing those messages to up to five Trusts.<br/>f.\tThe 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.\tConnectivity via HSCN will be required.<br/>h.\tAll information exchanges will need to be encrypted in transit.<br/>i.\tThe solution must be hosted in accordance with NHS guidelines.<br/>j.\tThe 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": [
      {
        "id": "1",
        "relatedLot": "1",
        "deliveryLocation": {
          "description": "250 Euston Road<br/>London<br/>NW1 \"PG"
        },
        "deliveryAddresses": [
          {
            "region": "UKI31"
          }
        ]
      }
    ],
    "title": "NCL integration hub & patient identity capability",
    "value": {
      "amount": 500000,
      "currency": "GBP"
    },
    "status": "planned",
    "coveredBy": [
      "GPA"
    ],
    "legalBasis": {
      "id": "32014L0024",
      "scheme": "CELEX"
    },
    "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.",
    "communication": {
      "atypicalToolUrl": "https://health-family.force.com/s/Welcome",
      "futureNoticeDate": "2025-01-14T00:00:00Z"
    },
    "classification": {
      "id": "48900000",
      "scheme": "CPV",
      "description": "Miscellaneous software package and computer systems"
    },
    "mainProcurementCategory": "goods"
  },
  "parties": [
    {
      "id": "GB-FTS-14675",
      "name": "University College London Hospitals NHS FT",
      "roles": [
        "buyer"
      ],
      "address": {
        "region": "UKI31",
        "locality": "London",
        "postalCode": "NW1 2PG",
        "countryName": "United Kingdom",
        "streetAddress": "250 Euston Road"
      },
      "details": {
        "url": "https://www.uclh.nhs.uk",
        "buyerProfile": "https://www.uclh.nhs.uk/",
        "classifications": [
          {
            "id": "BODY_PUBLIC",
            "scheme": "TED_CA_TYPE",
            "description": "Body governed by public law"
          },
          {
            "id": "07",
            "scheme": "COFOG",
            "description": "Health"
          }
        ]
      },
      "identifier": {
        "legalName": "University College London Hospitals NHS FT"
      },
      "contactPoint": {
        "name": "Stevie Cavanagh",
        "email": "steviejay.cavanagh@nhs.net"
      }
    }
  ],
  "language": "en",
  "description": "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.",
  "initiationType": "tender"
}