# Lot 1 — Foundation EPR Solutions **Research checked: 17 October 2026.** The proposed lot is **Foundation Electronic Patient Record (EPR) Solutions**, valued at **£649,447,889 excluding VAT**. It covers the operational GP system. The notice remains planned procurement; appointment requirements await 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 2](https://copper-tiger.pages.dev/gp-it-lot-2/index.md) and [Lot 3](https://copper-tiger.pages.dev/gp-it-lot-3/index.md). For the concept first, read [Systems and capabilities](https://copper-tiger.pages.dev/foundations/systems-and-capabilities/index.md). Foundation EPR Solutions support the GP record's source role and additional primary record of care (PRC) role. A shared care view provides access across records; it does not by itself maintain those GP functions. ## Six foundation capabilities The notice names six capabilities. The questions below are COPPER TIGER's interpretation for clinical continuity, not additional tender requirements. [SRC-109](https://copper-tiger.pages.dev/sources/index.md#src-109) | Published capability | Question for the proposed clinical model | |---|---| | Appointments Management - GP | Can a patient reach the appropriate clinician and service? | | Consultation Management - GP | Can the receiving clinician record the assessment, decisions and follow-up? | | Patient Information Maintenance - GP | Can the practice maintain the patient's identity, history and continuing record? | | Prescribing - GP | Can prescribing use the relevant history, allergies and current medicines? | | Referral Management - GP | Can requests reach the intended service and remain traceable? | | Resource Management | Can the system support the staff and resources needed to provide care? | Current [DSIC](https://copper-tiger.pages.dev/dsic/index.md) guidance requires all six core capabilities for a foundation classification. Additional capabilities may extend a foundation product. A viewer or integration engine cannot establish that classification through interoperability alone. [SRC-115](https://copper-tiger.pages.dev/sources/index.md#src-115) ## Patient Information Maintenance and history The official **C13** capability gives substance to this label. At this review, **v10.0.3** is Effective from **13 October 2026**. It covers registration, demographics, maintaining a comprehensive EPR and viewing historical care information. It also addresses citizen access and record transfer. Epic **E00177** concerns transfer and integration of the EPR following registration. [SRC-125](https://copper-tiger.pages.dev/sources/index.md#src-125) This helps explain the operational record role. It does not define a universal lifelong record architecture or establish that every historic item survives a particular migration. COPPER TIGER must still account for civilian records, specialist correspondence, provenance and unfinished clinical work. **Version distinction:** the same research surfaced a published **v14.0.0** with an effective date of **20 April 2027**. Published future requirements are not the effective October baseline. The current page lists Digital Primary Care among its contracting vehicles; final tender documents must identify the applicable versions. [SRC-125](https://copper-tiger.pages.dev/sources/index.md#src-125) ## Migration is a separate clinical problem NHS England's TIF assurance explanation assesses migration mapping and compares loaded records with the original system. Clinical walkthroughs include medicines and allergies. These are useful comparators for continuity, rather than verified Lot 1 acceptance conditions. [SRC-117](https://copper-tiger.pages.dev/sources/index.md#src-117) | Process | Boundary to preserve | |---|---| | A patient changes registered practice | [GP2GP](https://copper-tiger.pages.dev/primary-record/index.md) is a patient-record transfer service with its own scope. | | A practice changes clinical supplier | Whole-practice migration needs planning, data checking, cutover and go-live support. | | A new foundation supplier enters service | National assurance and onboarding are additional activities. The established-supplier migration guide is not intended for this route, although some steps may apply. | | A shared-record platform consumes information | Viewing or aggregation does not itself update the PRC or transfer responsibility for maintaining it. | The first three distinctions follow the published GP2GP and migration guidance. The final row states the project's [record-role distinction](https://copper-tiger.pages.dev/architecture/index.md). [SRC-007](https://copper-tiger.pages.dev/sources/index.md#src-007) [SRC-123](https://copper-tiger.pages.dev/sources/index.md#src-123) For COPPER TIGER, the design evidence should cover mapping completeness, reconciliation, failed imports, cutover, recovery and ownership of pending results. These are proposed evaluation questions. No reviewed source establishes a Defence migration contract or implemented solution. ## Evidence limits and independent reading The capability documents deepen the six labels; they do not replace the inaccessible procurement attachment. Final scoring, capability versions and commercial obligations remain in [VAL-012](https://copper-tiger.pages.dev/validation-queue/index.md). Read the [official C13 specification](https://nhse-dsic.atlassian.net/wiki/spaces/DCSDCS/pages/1391134180), [migration guide](https://digital.nhs.uk/services/digital-services-for-integrated-care/clinical-system-migration-guide) and [TIF assurance explanation](https://digital.nhs.uk/services/digital-services-for-integrated-care/tech-innovation-framework/it-solutions-for-managing-patient-care) alongside the notice. [SRC-109](https://copper-tiger.pages.dev/sources/index.md#src-109) [SRC-125](https://copper-tiger.pages.dev/sources/index.md#src-125)