Project updates

14 October 2026 — civilian continuity and military medicine

The owner expanded the research question to make civilian history explicit and cover access and sharing across military clinical services, specialties and requirements. The request permits clearer wording. It is recorded as project intent in ⁰³⁶.

At that stage, the governing question used “including their civilian history”. This preserved the requested emphasis while allowing the record to develop during service. It did not imply that the record remained exclusively civilian or under unchanged NHS control. The primary-record explanation develops the current scope; the Defence context maps the clinical services.

14 October 2026 — rollout timetable under review

The owner supplied a qualification to the earlier published rollout announcement. This remains attributed historical project context, not a public revision or evidence of the current implementation state. It cannot establish the public-source baseline. ^{030, 011}

The future definition is supplier agnostic. Neither the announcement nor the owner qualification fixes the architecture, supplier selection or delivery schedule.

20 October 2026 — programme-wide definition and publication

The owner defined COPPER TIGER as the evolving programme/problem statement/architecture that may drive Care Hub, a potential rebranding of Programme Cortisone. The agreed scope covers the whole Defence population, all healthcare settings and care partners, and responsibilities, workflows, policy, governance, information and technology. ²¹¹

The leading principle is continuing PRC alongside a governed internal Defence shared care record, with national and regional integration. All purposes remain in scope, with appropriate governance. Coordination and occupational health/readiness have only a marginal initial emphasis. Priorities, outcomes and implementation remain to be developed.

The owner authorised preserving the current wiki as its first major release, recording workings internally and publishing the new context. See release history, programme definition and architecture. This records direction, not formal Defence approval. Raw deliberations remain outside the published corpus.

22 October 2026 — shared-record capability clarification

The owner refined the DShCR as a primarily read-only overview across source clinical records and relevant supporting tools. A coupled IntP would broker information flows; workflow processing may sit in other tools. The PRC continues to receive appropriate information under applicable NHS conventions and standards. ²¹²

The proposed HPD covers configurable user profiles and provider relationships, including temporary deployed facilities with controlled location information. The EMPI covers identity matching, persistent identifier linkage and a critical shared demographic profile. Wider patient administration remains elsewhere. Demographic-authority resolution is required, with the method unresolved.

Continuity copies, consultation forms and patient-facing services remain options to explore. This is published owner direction, not formal Defence approval or delivered capability. The architecture and Foundations distinguish these options from core proposed requirements.

22 October 2026 — governing question and inclusive continuity

The owner approved a revised governing question after successive wording changes. It returns lifelong primary (GP) record continuity to the opening focus and makes the complementary DShCR explicit. Maintaining the PRC to applicable NHS conventions and standards is proposed to support continuity and transfer to NHS general practice when care arrangements change. ²¹⁹

The revision uses “maintain patients’” and plural “records of care”. It uses “transfer” in place of “hand-back”. “When care arrangements change” includes civilian patients and avoids treating departure from Armed Forces service as the universal trigger. Civilian history and relevant care during service remain part of the continuing history where applicable.

The question refers to occupational health-led Defence healthcare and the evolving needs of military medicine. Care partners remain in programme scope and the external interface model, but are no longer a clause in the question. This change does not revise the programme's agreed priority ranking or select an implementation.

The overview and architecture use identical approved wording. Related record explanations and programme scope now make population inclusivity explicit. The full wording sequence and rationale are retained in internal project context, outside navigation, search and exports. Publication approval is an editorial decision, not organisational approval of the proposed architecture.

23 October 2026 — linked questions and shared information

The owner approved two linked questions in place of the single long question. The first retains lifelong GP-record maintenance, NHS conventions and standards, and continuity. A further revision explicitly adds record transfer from and to NHS general practice when Defence care arrangements begin and end. It remains inclusive of Armed Forces and civilian patients. The second begins “In parallel” and asks about a complementary internal DShCR across occupational health-led Defence healthcare and military medicine. ²²⁰

The DShCR explanation now explicitly joins information from multiple source systems into a contiguous, longitudinal overview, with authorised access to complete contributing clinical records. Contiguous means connected presentation across sources; longitudinal means continuity over time. Actual coverage, freshness and access conditions remain visible qualifications.

The associated IntP should coordinate exchange in both directions, including back to independent specialist source systems. The EMPI supports identity and shared demographics; the HPD supplies provider context. Core conditions, medications, vaccinations and allergies should support CDSS within specialist source systems. Information authority, provenance, currency, corrections and reconciliation remain design questions. Business continuity options include retained information, consultation capture and subsequent reconciliation. ²²⁰

At the owner's request, the green homepage explanation retains its existing opening paragraph and adds this capability detail. Only the Care Hub/Cortisone clause was removed from the introductory paragraph; its population, operating-environment and interface scope is unchanged. The programme relationship remains explained elsewhere.

The overview and architecture repeat the approved pair in the same order. Related definitions, programme summaries, information flows and discovery are aligned. All wording revisions and their rationale are preserved in internal context; earlier dated records retain their historical wording. This is published proposed direction, not a claim of formal approval, current integration or delivered capability.

The owner then refined the second question’s ending to “across Defence healthcare and occupational health-led military medicine?” The overview and architecture use this exact wording. The earlier formulation, “across occupational health-led Defence healthcare and military medicine?”, remains in the revision history.

Consistency review of the terminology

The subsequent review applied this distinction to current programme terminology, governance headings, portable record/access summaries and maintenance guidance. Defence healthcare retains the wider Armed Forces/civilian scope; occupational health-led qualifies military medicine. The general civilian-history definition also makes clear that military service is not a condition for every patient. ²²¹

Earlier wording in the dated entries above remains unchanged. Public findings, service-leaver guidance and specific occupational-care examples keep their original scope. Treatment, occupational assessment, command disclosure and other purposes still need their own access decisions. The clarification does not introduce a new eligibility rule, official taxonomy or access entitlement.

Homepage reading flow

The homepage review kept both approved questions unchanged and retained the substance of the green architectural explanation. Coverage and access qualifications now sit together beside the shared-view description. The continuity example follows the architecture explanation, before evidence-reading guidance and the onward reading path. Programme scope, including all healthcare purposes, is consolidated in the introduction rather than repeated in the caption.

The gold tiger explanation now closes the page. The diagram, image treatment and existing section anchors remain unchanged. This is an editorial reordering; it introduces no new programme direction, evidence claim or implementation decision. Earlier dated wording remains preserved.

Homepage layout restored

The owner requested restoration of the earlier layout while retaining the revised wording. The gold tiger explanation is again directly beneath the green explanation. The reading path precedes the continuity example; evidence-reading guidance and reference links follow it. The evidence definitions return to a two-column table using the current wording.

Both approved questions, the green architectural substance and the wording refinements remain intact. The preceding flow review records the superseded arrangement; it is retained as dated history.