Skip to content

Defence requirements register

This is the generated human-readable view of the canonical candidate-requirement register. Its 13 items are analytical translations from civilian Regulation 28 evidence and military-EHR context. They are not coronial requirements, accepted CORTISONE requirements, findings about DMICP, or evidence that a named system lacks a control.

The assurance catalogue contains 13 designed but unexecuted scenarios linked back to these candidate requirements. New work should cite the stable REQ- identifier rather than copy requirement prose into another register. Trace-basis values are controlled and mechanically checked against the validation status and linked claims.

Trace-basis definitions

Trace basis Required validation status Meaning
direct_case_claims candidate_trace_complete_defence_unvalidated The cited included reports are covered by direct case-linked claims; applicability to Defence remains unvalidated.
partial_scope_extension candidate_partial_trace_defence_unvalidated The cited reports are claim-traced, but part of the candidate control extends beyond that evidence; applicability to Defence remains unvalidated.

Validation-status definitions

Status Meaning
candidate_partial_trace_defence_unvalidated The cited reports are claim-traced, but part of the candidate control extends beyond that evidence; applicability to Defence remains unvalidated.
candidate_trace_complete_defence_unvalidated The cited included reports are covered by direct case-linked claims; applicability to Defence remains unvalidated.

No item has yet been validated against DPHC workflow evidence, CORTISONE requirement baselines, a clinical-safety case, user research or executed assurance results.

Register

REQ-001 — Identity and current care responsibility

Status: candidate_trace_complete_defence_unvalidated
Trace basis: direct_case_claims

Hazard

Administrative registration, physical location, accountable service and record source diverge, allowing an incomplete record to appear complete

Candidate normative requirement

The system shall represent person identity, physical support location, accountable care service, permanent or temporary registration and contributing record sources as distinct, reconcilable attributes; it shall visibly disclose unresolved conflicts.

Evidence trace

Defence applicability

Posted, attached, embarked, deployed, temporary, evacuated and otherwise mobile personnel

Designed assurance

AST-001, AST-002, AST-003

REQ-002 — Population visibility and accountable recall

Status: candidate_trace_complete_defence_unvalidated
Trace basis: direct_case_claims

Hazard

Eligible people are absent from a safety search, screening cohort or follow-up queue because membership or non-response depends on an incomplete administrative field or manual code

Candidate normative requirement

Population-health functions shall expose the cohort denominator, inclusions, exclusions, response and non-response states, source coverage, data freshness and accountable follow-up without relying on one unassured administrative field or manual code.

Evidence trace

Defence applicability

Screening, immunisation, readiness, chronic-disease surveillance and safety searches

Designed assurance

AST-002

REQ-003 — Longitudinal minimum record and source completeness

Status: candidate_trace_complete_defence_unvalidated
Trace basis: direct_case_claims

Hazard

Recent or safety-critical information remains in another organisation, registration or record source and the receiving view appears complete

Candidate normative requirement

Authorised users shall receive and reconcile a defined minimum clinical dataset across supported Defence, NHS, allied and host-nation sources, including allergies, medicines, active risks and care plans, while visibly disclosing missing sources and time periods.

Evidence trace

  • Included reports: Stephen Cassidy — 2023-0337; Samuel Jordan — 2024-0056
  • Stable claims: CLM-009, CLM-010
  • Sociotechnical mechanism codes: INT, VIS, IDPOP, GOV
  • Traceability qualification: Cassidy supports unavailable allergy information and Jordan supports omitted recent temporary-practice care; the minimum dataset and supported boundaries require Defence agreement.

Defence applicability

Routine, temporary, civilian, allied, deployed, detention, evacuation and receiving care

Designed assurance

AST-003, AST-006

REQ-004 — Critical-result delivery and clinical closure

Status: candidate_trace_complete_defence_unvalidated
Trace basis: direct_case_claims

Hazard

A time-critical result is stored, viewed or filed without accountable delivery, action, escalation or closure

Candidate normative requirement

Time-critical results shall carry machine-readable severity, required action, deadline, accountable owner, acknowledgement, escalation and clinical-closure states; passive availability or filing shall not constitute completion.

Evidence trace

Defence applicability

Laboratory, imaging and other diagnostic workflows in fixed, remote and deployed care

Designed assurance

AST-004, AST-009

REQ-005 — Auditable message, referral and task routing

Status: candidate_trace_complete_defence_unvalidated
Trace basis: direct_case_claims

Hazard

A clinically significant message, referral or recommendation enters an administrative or unowned queue, bypasses the record or has no visible completion state

Candidate normative requirement

Every safety-relevant message, referral and task shall enter an auditable clinical workflow that exposes destination, priority, accountable triage, acceptance, due time, escalation, record incorporation and completion or rejection.

Evidence trace

Defence applicability

Patient messaging, remote consultation, referrals, recommendations, results and distributed teams

Designed assurance

AST-005, AST-009

REQ-006 — Transfer and handover record delivery

Status: candidate_trace_complete_defence_unvalidated
Trace basis: direct_case_claims

Hazard

A transfer record exists outside the receiving workflow, requires unfamiliar access or arrives without a visible draft, final, review or reconciliation state

Candidate normative requirement

Draft and final transfer records shall enter the receiving clinical workflow and longitudinal record automatically where supported, with visible arrival, completeness, finalisation, review and reconciliation states and an accountable recipient.

Evidence trace

Defence applicability

Ambulance, aeromedical and maritime evacuation, civilian referral, unit transfer and repatriation

Designed assurance

AST-006

REQ-007 — Safe hybrid record operation

Status: candidate_trace_complete_defence_unvalidated
Trace basis: direct_case_claims

Hazard

Safety-critical information is split between paper and digital representations or a medication suspension continues without owned review

Candidate normative requirement

Hybrid workflows shall cross-reference safety-critical paper and digital content, preserve attribution and current authority, reconcile changes into the operational record, and create an owned review with a deadline for safety-critical medication holds.

Evidence trace

  • Included reports: Audrey King — 2023-0312; Michael Drewell — 2018-0259
  • Stable claims: CLM-015, CLM-024
  • Sociotechnical mechanism codes: VIS, ALERT, LOOP, HF, PROV
  • Traceability qualification: Drewell directly supports a safety-critical handwritten instruction not reaching the electronic prescribing view, with causal uncertainty preserved; King supports hybrid-record reconciliation and an owned medication review. Defence applicability remains unvalidated.

Defence applicability

Paper fallback, mixed paper-digital care, medication holds and staged digitisation

Designed assurance

AST-007

REQ-008 — Provenance and amendment clarity

Status: candidate_trace_complete_defence_unvalidated
Trace basis: direct_case_claims

Hazard

A late entry, correction or export obscures author, event time, entry time, prior content or amendment status

Candidate normative requirement

Clinical, printed, exported and investigation views shall preserve and clearly display author, event time, entry time, prior content and amendment status without destructive overwrite.

Evidence trace

Defence applicability

Routine care, operational documentation, transfer, investigation, disclosure and medico-legal review

Designed assurance

AST-008

REQ-009 — Actionable and proportionate decision support

Status: candidate_trace_complete_defence_unvalidated
Trace basis: direct_case_claims

Hazard

A high-severity risk receives no alert or an alert is non-actionable, poorly prioritised, unowned or lost among low-value interruptions

Candidate normative requirement

Decision support shall be severity-ranked, contextual, actionable and linked to an accountable workflow, and shall be evaluated for sensitivity, specificity, override, workload effects and downstream ownership in representative use.

Evidence trace

Defence applicability

Results, allergies, screening, medicines, contraindications and other high-severity controls

Designed assurance

AST-004, AST-005, AST-009

REQ-010 — Safety-control migration

Status: candidate_trace_complete_defence_unvalidated
Trace basis: direct_case_claims

Hazard

A proven safety barrier is omitted, weakened or behaves differently when data or workflow moves to a replacement system

Candidate normative requirement

Every existing safety barrier shall map to a tested target-state control or to an explicitly owned and accepted residual risk before migration, with clinical-safety regression evidence across representative workflows.

Evidence trace

  • Included reports: Paula Doreen Hughes — 2025-0511; Margaret Spencer — UNREF-2018-MARGARET-SPENCER
  • Stable claims: CLM-016, CLM-022
  • Sociotechnical mechanism codes: GOV, ALERT, HF
  • Traceability qualification: Spencer directly supports follow-up loss during an IT-system introduction, with migration, training and administrative input jointly implicated; Hughes supports preserving local prescribing safety controls during replacement. Applicability to CORTISONE remains unvalidated.

Defence applicability

CORTISONE transition, data migration, interface replacement and staged rollout

Designed assurance

AST-010

REQ-011 — Distributed transaction integrity

Status: candidate_trace_complete_defence_unvalidated
Trace basis: direct_case_claims

Hazard

Cancellation, correction, reissue, supply, dispensing or administration changes only some endpoints, leaving contradictory action states

Candidate normative requirement

Multi-endpoint clinical transactions shall expose endpoint state, idempotently reconcile partial failure, prevent duplicate or conflicting action, and require accountable resolution of unresolved divergence.

Evidence trace

  • Included reports: Oliver Billings — 2024-0656; Valerie Gibson — 2025-0630
  • Stable claims: CLM-017, CLM-018
  • Sociotechnical mechanism codes: INT, LOOP, PROV, RES, GOV
  • Traceability qualification: Billings directly supports observable cancellation and reissue state across pharmacy endpoints; Gibson directly supports reconciliation across dispensing and administration systems. Defence applicability remains unvalidated.

Defence applicability

Prescribing, dispensing, supply, referrals, orders and messages across disconnected or independently administered services

Designed assurance

AST-011, AST-012

REQ-012 — Degraded-operation resilience and safe synchronisation

Status: candidate_partial_trace_defence_unvalidated
Trace basis: partial_scope_extension

Hazard

Connectivity or power loss forces untracked workaround, silent data loss, conflicting versions or unsafe replay when service returns

Candidate normative requirement

Degraded operation shall define the authoritative record, minimum safe function, attributable fallback, queued-action visibility, conflict-safe synchronisation and accountable reconciliation after restoration.

Evidence trace

Defence applicability

Deployed, maritime, aeromedical, remote, bandwidth-limited and outage conditions

Designed assurance

AST-007, AST-012

REQ-013 — Clinical and operational boundary control

Status: candidate_partial_trace_defence_unvalidated
Trace basis: partial_scope_extension

Hazard

Relevant risk information is unavailable across a clinical-operational boundary, or excessive sharing breaches purpose, proportionality or access constraints

Candidate normative requirement

Clinical and operational systems shall exchange an agreed minimum set of safety-relevant risk signals with explicit purpose, provenance, timeliness, access control, review responsibility and auditable use.

Evidence trace

  • Included reports: Jonathan Thornton — 2026-0200; Anthony Binfield; David Richards; Rolandas Karbauskas — 2025-0079
  • Stable claims: CLM-019, CLM-020
  • Sociotechnical mechanism codes: INT, PROV, GOV
  • Traceability qualification: Thornton directly supports role-appropriate clinical-operational alerts and formal handover; the Binfield, Richards and Karbauskas cluster directly supports shared risk information across prison, healthcare and transition boundaries. Purpose, proportionality, access-control and excessive-sharing controls are Defence governance extensions not established by those claims, so the trace remains partial and Defence applicability unvalidated.

Defence applicability

Detention, evacuation, force protection, command support, occupational health and clinical care boundaries

Designed assurance

AST-013

Maintenance

Edit requirements.csv, then run node scripts/generate-defence-pages.mjs. Do not edit this page directly. Preserve retired identifiers rather than reusing them; record evidence or scope changes in the research log.