# Lot 2 — Clinical and Operational Support Solutions **Research checked: 17 October 2026.** The proposed lot covers services that extend or support foundation GP capabilities. Its estimated value is **£135,301,480 excluding VAT**. The notice lists 27 capabilities, but leaves detailed appointment requirements to the tender. [SRC-109](https://copper-tiger.pages.dev/sources/index.md#src-109) Return to the [framework overview](https://copper-tiger.pages.dev/gp-it-framework/index.md), or compare [Lot 1](https://copper-tiger.pages.dev/gp-it-lot-1/index.md) and [Lot 3](https://copper-tiger.pages.dev/gp-it-lot-3/index.md). ## The 27 named capabilities These are the notice's capability names. The grouping in the first column is an editorial reading aid, not published sub-lots. [SRC-109](https://copper-tiger.pages.dev/sources/index.md#src-109) | Reading group | Published capabilities | |---|---| | Clinical advice and planning | Advice and Guidance (Professional to Professional); Care Plans; Clinical Decision Support; Medicines Optimisation; Social Prescribing | | Coordinating people and work | Caseload Management; Cross Organisation Appointment Booking; Cross Organisation Workforce Management; Custom Workflows; Task Management | | Documents and communication | Communication Management; Digital Dictation; Document Management; Medical Reports; Scanning | | Investigations and intelligence | Digital Diagnostics; GP Extracts Verification; Population Health Management; Reporting; Risk Stratification | | Care beyond the consultation room | Domiciliary Care; Remote Patient Monitoring; Telecare; Video Consultation | | Operational functions | Dispensing; Emergency Alerts; Self-Service Appointment Check In | The label **Non-Foundation** describes the broader support category in the notice. It does not mean that every product implements all 27 capabilities. Nor does it establish that a product named in the wider catalogue belongs in this lot. [SRC-109](https://copper-tiger.pages.dev/sources/index.md#src-109) [SRC-115](https://copper-tiger.pages.dev/sources/index.md#src-115) ## Why capability labels need closer reading The existing DSIC specifications distinguish mandatory **MUST** epics from **MAY** epics. A contracting vehicle or supplementary standard can make a MAY epic mandatory. Read the version, applicable contract and acceptance criteria together. [SRC-116](https://copper-tiger.pages.dev/sources/index.md#src-116) | Effective specification examined | Mandatory core | Additional functionality that must be checked | |---|---|---| | Digital Diagnostics, C8 v1.0.2 | Request information management, E00432; viewing received results, E00433 | Request/result reconciliation, E00434, is MAY. Capability coverage alone does not prove that outstanding investigations are identified. | | Task Management, C50 v1.1.0 | Creating, viewing, amending and deleting tasks, E00267 | Assignment/reassignment, E00269, and overdue flags, E00270, are MAY. A task list alone does not establish accountable handover or escalation. | These are current published specification distinctions. They do not establish the final DPC tender's mandatory selection. Both specifications list Digital Primary Care among their contracting vehicles. [SRC-126](https://copper-tiger.pages.dev/sources/index.md#src-126) [SRC-127](https://copper-tiger.pages.dev/sources/index.md#src-127) ## Terms with a history before this procurement DSIC roadmap change **RM270**, effective **26 February 2026**, introduced **Digital Dictation**, **Medical Reports** and **Self-service Appointment Check-in**, while deprecating **Productivity**. These names therefore predate the October notice. Their appearance in Lot 2 does not prove a new implementation or an AI requirement. [SRC-118](https://copper-tiger.pages.dev/sources/index.md#src-118) The capability list is also not a list of national interfaces. Advice and Guidance is not automatically e-RS; Digital Diagnostics is not automatically a laboratory connection. Evidence must identify the actual [exchange route](https://copper-tiger.pages.dev/exchange-mechanisms/index.md), profile, participants and clinical workflow. ## Implications for NHS–Defence care For the proposed COPPER TIGER model, evaluate the whole clinical task: request, receipt, interpretation, action, filing and escalation. Preserve the distinction between data arrival and accepted clinical responsibility. For example, a diagnostic pathway needs an owner for missing results as well as a display of results received. A cross-service referral needs an accepting recipient as well as a message transport. These are design implications grounded in the [correspondence model](https://copper-tiger.pages.dev/clinical-correspondence/index.md), not evidence of a deployed Defence product. National-service assurance applies to the listed function and version. It does not establish framework admission or a complete clinical workflow. [SRC-026](https://copper-tiger.pages.dev/sources/index.md#src-026) ## Evidence limits and independent reading Read [Digital Diagnostics](https://nhse-dsic.atlassian.net/wiki/spaces/DCSDCS/pages/1391133770), [Task Management](https://nhse-dsic.atlassian.net/wiki/spaces/DCSDCS/pages/12417368065) and [RM270](https://nhse-dsic.atlassian.net/wiki/spaces/DCSDR/pages/14709391361) alongside the [framework notice](https://www.find-tender.service.gov.uk/Notice/094419-2026). The attachment remains inaccessible; final versions, bundles and admission thresholds remain [parked](https://copper-tiger.pages.dev/validation-queue/index.md). [SRC-109](https://copper-tiger.pages.dev/sources/index.md#src-109)