Programme-definition decision brief
Draft for discussion — 21 October 2026. No programme decisions are recorded here.
Decision sought: agree or amend the wider Defence healthcare case for change, desired outcomes and strategic direction. Establish the coalition and decision authority needed to develop the programme definition.
COPPER TIGER defines the programme and architecture that may drive Care Hub, a potential rebranding of Programme Cortisone. The programme definition records the owner-directed scope. This brief supports discussion across clinical, operational, digital, governance and delivery leadership, with patient and staff participation. 211
The wider case for change — proposed
Defence needs a healthcare operating model that sustains safe care, continuity and readiness across changing clinical, organisational and operational circumstances. Programme definition should establish where current arrangements fall short, preserve effective services and controls, and identify justified changes in people, policy, responsibilities, services, information and technology.
The scope is the whole Defence population and care journey, across Firmbase, Overseas and Operational (MARITIME, LAND and AIR) environments. It includes primary, dental, mental health, rehabilitation, specialist and hospital care, and relationships with NHS, devolved, overseas, allied and contracted providers. Inclusive programme scope does not imply identical care entitlements. 211
Potential concerns include fragmented information, uncertain responsibilities, uneven access, repeated work, service constraints and disruption. Their extent, causes and consequences require evidence. The case for change must also consider occupational health, readiness, command support, planning, population health, surveillance, research and operational analysis, with appropriate governance for each purpose.
These concerns are an evolving problem set. Public evidence below provides a starting point; the scale and relative importance of the problems remain open.
Problem–evidence–outcome map
The first column states proposed concerns to investigate. The middle column separates public evidence and its limits from gaps. The final column states desired outcomes, not measured benefits or approved targets.
| Strategic concern — proposed | Public evidence and limits | Desired outcome — proposed |
|---|---|---|
| Care and readiness across the whole operating model. Where do service arrangements, access, capacity or organisational boundaries constrain Defence needs? | The Ministry of Defence describes Defence Medical Services' clinical, occupational and deployable medical responsibilities. The Medical Operating Concept connects operational support with the strategic base and global foundation. These establish remit and intended direction, not measured shortcomings. 013, 039 | Safe, timely and coordinated care; appropriate support for health, recovery and readiness; clearer responsibilities across services and partners. |
| Continuity through changes of provider, setting and service status. Where does relevant history or responsibility fail to follow the person? | NHS service-leaver guidance describes a summary and a separate request for full military general practice records, which can take months. A January 2026 parliamentary answer describes electronic interoperability work as ongoing. These are dated transition findings, not a complete current assessment of all transfers. 009, 038 | A usable continuing care history, coordinated care and accountable handovers across the Defence population's journey. |
| Information serving distinct purposes. How should care, occupational assessment, readiness, command and wider organisational uses relate? | General Medical Council guidance identifies dual obligations in Armed Forces work and limits disclosure to relevant information. NHS shared-care guidance requires purpose and responsibility mapping. These are governance references, not blanket permission for Defence uses or evidence of a local breach. 033, 032 | Trusted information used for justified purposes, with clear accountability, proportionate disclosure and protection of confidentiality. |
| Resilience across operating conditions. What needs to remain safe and usable when services or connectivity are disrupted? | The Medical Operating Concept advocates digitisation with degraded-operation capability. The Care Quality Commission's 2025 Mount Pleasant report records local functionality and data-transfer constraints alongside continuity planning and reported improved stability. A forward concept and one inspection do not establish current estate-wide capability. 039, 078 | Care and essential work that can continue safely through disruption, with dependable recovery and continuity between operating settings. |
| Experience, learning and sustainable value. Where can change reduce avoidable burden and improve how resources support care? | The Medical Operating Concept proposes better operational data to improve care. The evidence assembled for this brief does not establish programme-wide baselines for patient experience, staff burden, cost or benefits. 039 | Better patient and staff experience, less avoidable duplication, useful evidence for planning and learning, and demonstrable value for money. |
The Medical Operating Concept was published in 2022 and updated in January 2023; it is a forward concept. The Defence Medical Services remit, concept and transition sources were rechecked on 21 October 2026. The Mount Pleasant finding retains its local, dated scope and the indexed-text retrieval qualification in the research log. Guidance describes relevant responsibilities and controls; it does not establish the prevalence of failure.
Safety, continuity, access, readiness, resilience, trust, patient experience, staff workload and value should be assessed together. Measures, baselines, trade-offs and relative priorities remain open. Clinical service coordination and occupational health/readiness have only a marginal initial emphasis. No quantified improvement, saving or delivery target is assumed.
Proposed strategic direction
Develop the operating model and information architecture together. Responsibilities, workforce, service design, policy and governance are part of the change. Examine where organisational or procedural changes are needed alongside technology, and retain what already works.
The leading architectural principle is a continuing primary record of care (PRC) alongside a governed internal Defence shared care record, with readiness to integrate with national and regional records, systems and services. 211
The Defence Shared Care Record (DShCR) would provide a comprehensive, primarily read-only view across multiple source systems and over time. Authorised users could access complete contributing clinical source records through that view, subject to coverage, currency and permissions. Source systems retain their accounts and corrections. 212, 220
An associated Integration Platform (IntP) would coordinate two-way information exchange, including core clinical information returned to specialist source systems for their clinical decision support. Patient identity and shared demographics, provider context and purpose controls would support these flows. Business continuity options include retained information, consultation capture and subsequent reconciliation. Implementation and information-authority rules remain open; workflow processing remains distinct from message brokering. Patient-facing services are also options to explore. 220
Keep clinical accountability explicit and govern each use of information by purpose. Design for connected, degraded and disconnected conditions from the outset. Devolved, overseas, allied and contracted care must inform the direction, with their distinct responsibilities and participation conditions.
Remain supplier agnostic and future-looking. Existing Programme Cortisone commitments and national developments inform constraints and opportunities. They do not select the future design. The proposed direction leaves products, storage arrangements, organisational assignments, investment and delivery sequencing open.
The operating model, internal architecture and national and regional integration develop these principles. They remain proposals and bounded public-source findings, with unresolved decisions identified.
Open strategic questions
- Problem and need: which problems are evidenced, whom do they affect, and how do their causes and consequences differ across populations, services and operating environments?
- Outcomes and priorities: what should improve, how will improvement be recognised, and which tensions between care, readiness, experience, workload, resilience and value need explicit decisions?
- Operating model: which responsibilities, workforce arrangements, service boundaries or policies need change? What should be preserved, and who has authority to decide?
- Information and partnerships: which shared information and external relationships are necessary for the desired outcomes? What purpose-specific governance, national, devolved or international conditions constrain the options?
- Options and evidence: what can existing commitments contribute, which assumptions need challenge, and what public evidence is needed to compare strategic options? Which matters must remain unresolved pending formal organisational decisions?
The validation queue retains the underlying questions. This brief does not select a detailed clinical pathway or a technical implementation as the next programme priority.
Decisions requested
| Strategic decision requested from the programme coalition | Decision record needed |
|---|---|
| Agree or amend the case for change and scope. | The problem statement, populations, settings and purposes; established findings, assumptions, evidence gaps and disagreements. |
| Agree or amend the desired outcomes and initial emphasis. | Outcome ambitions, unresolved trade-offs and the evidence needed to establish priorities and measures. |
| Endorse, amend or defer the leading strategic and architectural direction. | Rationale, constraints and evidence that would trigger reconsideration. |
| Establish responsibility for further programme definition. | Participating roles and their authority, the strategic evidence agenda and the questions for the next programme-level decision. |
A completed discussion should leave a clear record of agreement, disagreement and open questions. It should identify who can take the unresolved decisions and on what evidence. Agreement supports further programme definition; it does not itself approve investment, procurement or implementation.
The project status retains the wider programme priorities.