Skip to content

LLM Wiki entry point

Read first

  1. Repository AGENTS.md.
  2. .wiki-standard.yaml.
  3. knowledge/index.md.
  4. Context map.
  5. docs/project/status.md.
  6. The manifest's roles.authoring_policy path, or AUTHORING.md when no path is mapped, before writing new original English prose.
  7. DESIGN.md for rendered changes.
  8. Knowledge graph query results when Graphify is selected.

Operating model

  • Ingest: register a target source, preserve its identity, add its stable exact-row anchor, update the relevant concept and evidence state, add links, and record the change.
  • Query: select the smallest authoritative target context, expose uncertainty, and cite registered evidence through individual internal source-row links.
  • Lint: find contradictions, stale claims, unsupported authority, ungoverned exact repetitions of the declared canonical question, bare or misdirected source identities, unregistered named-authority URLs, missing links, and generated-output drift.
  • Propose: after a user-authored reusable improvement is implemented, verified, and committed locally, preserve it in a tracked Standard proposal. Validate direct states and terminal transitions offline, prepare a disposable scrubbed payload, and bind approval to the exact digest and governed form revision. The user submits; intake, Standard decision, exact registry/release evidence, and optional adoption remain separate authorities. Never reuse the Standard's sole historical bridge.

Never treat an LLM answer, rendered page, or graph edge as new evidence.

Apply the DenchCo ASD-STE100-inspired 80% house style in the mapped authoring policy (AUTHORING.md when no path is mapped) to all new original English Wiki prose. 80% is a pragmatic aim, not a computed score or a claim of ASD-STE100 compliance. Review meaning and source fidelity before style, preserve protected text and necessary technical terms, and record material exceptions with their scope and reason. Follow explicit user instructions and stricter applicable local policy. Do not bulk-rewrite existing prose or change consumer pins to apply the default.

In a Standard Production maintenance workspace, a file-changing development turn remains incomplete until its persistent changes are recorded in the required end-of-turn JJ commit under DKBWS-PROV-001.

Use the tracked proposal workflow for a governed upstream handoff. If the form, label, marker search, provenance, or digest evidence is unavailable or ambiguous, preserve the record and stop; filing does not amend the pinned Standard or authorize migration.

Development responses route Human or LLM Wiki destinations through the configured live canonical HTTP(S) origin under DKBWS-PROMPT-002. File, editor, absolute-path, and repository-relative Markdown links do not substitute for Wiki navigation; plain repository paths identify only implementation artifacts with no rendered route. Captured drafts check Markdown, HTML links, and plain GFM-autolinked URLs. Managed local drafts add --managed-live to require exact service identity, canonical URL equality, and HTTP 200 for every displayed route; STD-VAL-007 remains the host boundary for uncaptured output.

Persistent preview handoff uses npm run service:preview only after all twelve registry fields, the exact installed/loaded job, canonical URL, and marker identity pass. Live service evidence belongs to maintainer verification; distribution/CI leaves DKBWS-RUNTIME-002 not checked.

Use project status for zero to three current priorities and the validation queue for parked work. Apply the AGENTS.md completion and cycle guard before recommending any follow-up; a completed answer does not need a Next Steps section.

Subject context

Read programme definition, operating model, internal architecture and national interfaces before applying the detailed reference material. COPPER TIGER is the evolving definition that may drive Care Hub, a potential rebranding of Programme Cortisone.

Preserve all Defence population, settings, partners and purposes. Coordination and occupational health/readiness have only a marginal initial emphasis. England is a reference, with devolved, overseas and allied requirements considered from the outset. Policy and responsibilities are open to change with technology.

Use Defence healthcare for the wider inclusive scope. In the owner’s framing, occupational health-led qualifies military medicine, not all Defence healthcare. Preserve specific occupational-care examples, purpose-based access rules and earlier wording as dated history. This is proposed programme terminology, not an official taxonomy or new access authority. 221

The two linked governing questions address maintaining patients’ lifelong GP records in line with applicable NHS conventions and standards, and developing the complementary internal DShCR. PRC maintenance supports continuity and record transfer from and to NHS general practice when Defence care arrangements begin and end. Scope includes Armed Forces and civilian patients. Keep service-leaving examples bounded and preserve the exact approved wording in its declared reader set. The revision does not change the wider scope or prior priority ranking. 219, 220

The leading hypothesis is continuing PRC alongside a governed Defence Shared Care Record (DShCR). The DShCR is a comprehensive, primarily read-only overview across multiple clinical source systems and relevant supporting tools. “Contiguous” means connected presentation across sources; “longitudinal” means extending over time. Authorised access to complete contributing clinical source records is an objective bounded by coverage, currency and permissions. Source systems retain their authored accounts and corrections. Applicable NHS conventions and standards govern PRC maintenance and contributions. 212, 220

The associated Integration Platform (IntP) is fundamentally a message broker with publish–subscribe services. It coordinates two-way information exchange, including back to independent specialist source systems. Conditions, medications, vaccinations and allergies should support clinical decision support systems (CDSS) within those systems. Authority, provenance, currency and reconciliation rules remain unresolved; no automatic overwrite follows. Do not assign workflow, caseload or patient-flow processing to the broker by default. 220

The Healthcare Provider Directory (HPD) supports configurable user profiles and provider relationships, including temporary deployed facilities with controlled location information. The Enterprise Master Patient Index (EMPI) supports identity matching, persistent identifier linkage and shared demographics. Registration, appointments and patient movements belong to other tools or features. Demographic-authority resolution is required; its method remains open.

Keep business continuity options—retained information, consultation capture and subsequent reconciliation—and patient-facing services as options to explore. Forms may sit alongside the DShCR or in another tool; they do not make the overview a jointly authored source record. Patient contributions and return flows are desired options, with routing and incorporation rules unresolved. Patient-facing records, potentially personal health records (PHRs), are distinct from the PRC. Apply the five record, interaction, work, purpose and assurance patterns internally, then specify external interfaces.

The wiki is supplier agnostic and future-looking. Historical sources retain official identities but do not select a product or fix future architecture. Owner rollout qualifications remain historical context and cannot establish a current public baseline. Separate public evidence, proposed direction and unresolved discovery. No undisclosed operational evidence is requested or inferred.

Use Foundations to explain the concepts, the capability landscape for categories, and the reading path to connect them. Release history identifies the preserved earlier wiki. Raw internal working records remain outside the reader corpus and generated graph/export boundary.

Expanded public-source reference

The NHS reference model develops the architecture into information objects and separate clinical, exchange and work states. Use correspondence, exchange mechanisms and ADT events for flow detail. Use legal authority and GP Connect constraints for purpose and service-access decisions. The Defence mechanism map then compares the proposed model with public evidence of use.

Include both conceptual and implementation detail. New factual research uses public primary sources only; record undocumented Defence mechanisms as unknown. Retain earlier project records with their original attribution.

Keep content-model, protocol/profile, API and contract versions separate. An active standard is not proof of deployment; a local inspection is not estate-wide evidence. Distinguish source publication dates, retrieval dates, cached/indexed passages and direct inspection.

The GP IT framework research records the October 2026 planned procurement and anticipated MOD buyer scope. Keep UK3 planning, UK4 competition, supplier appointment and local call-off distinct. The structured EOI field does not override the notice's no-response instruction. Procurement does not itself establish national-service access, supplier capability or Defence implementation.

The linked lot pages explain foundation records, clinical support and R&D. Use DSIC for requirement and assurance structure, TIF for modern core systems, and the framework glossary for terminology. A MAY epic can become mandatory through its contract; published future versions must not replace effective requirements without an applicable date.