Skip to content

Finding–requirement–test crosswalk

This generated route connects the seven finding pages and nine sociotechnical codes to the 13 candidate Defence requirements and 13 designed assurance tests. It is derived from the canonical requirements register and assurance-test register; it is not a parallel source of truth.

Authority and transferability boundary

A code match shows a controlled analytical route from a civilian hazard mechanism to a candidate Defence control. It does not make the requirement a coronial recommendation, establish that the mechanism exists in DMICP or CORTISONE, validate a Defence requirement, or show that an assurance test has passed.

Requirements can appear under more than one finding because mechanism codes are non-exclusive. Repetition in this table is navigational and must not be treated as causal weight, prevalence or independent corroboration.

Route summary

Finding Mapped code(s) Coverage
Information visibility and decision support VIS, ALERT 8 candidate requirements
9 distinct designed tests
Closed-loop work and action ownership LOOP 8 candidate requirements
8 distinct designed tests
Interoperability, identity and continuity INT, IDPOP 7 candidate requirements
8 distinct designed tests
Record integrity and provenance PROV 6 candidate requirements
7 distinct designed tests
Resilience and degraded operation RES 4 candidate requirements
6 distinct designed tests
Governance and assurance GOV 12 candidate requirements
13 distinct designed tests
Human-factors lens HF 6 candidate requirements
6 distinct designed tests

Information visibility and decision support

Open the bounded finding synthesis · Codes: VIS, ALERT

REQ-002 — Population visibility and accountable recall

Trace dimension Current state
Mapped mechanism code(s) ALERT
Requirement status candidate_trace_complete_defence_unvalidated
Trace basis direct_case_claims

Designed assurance scenarios

  • AST-002designed_not_executed

Traceability qualification: Ross directly supports the missing computable non-response mechanism; Defence population completeness remains untested.

Defence applicability remains unvalidated and every linked assurance scenario remains unexecuted.

REQ-003 — Longitudinal minimum record and source completeness

Trace dimension Current state
Mapped mechanism code(s) VIS
Requirement status candidate_trace_complete_defence_unvalidated
Trace basis direct_case_claims

Designed assurance scenarios

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 remains unvalidated and every linked assurance scenario remains unexecuted.

REQ-004 — Critical-result delivery and clinical closure

Trace dimension Current state
Mapped mechanism code(s) VIS, ALERT
Requirement status candidate_trace_complete_defence_unvalidated
Trace basis direct_case_claims

Designed assurance scenarios

Traceability qualification: Caliel Smith-Kwami directly supports the distinction between passive EHR availability and active result notification, while preserving the wider analyser, discharge and follow-up context; Rhodes supports salience and filing risk; Thompson supports accountable delivery and closure.

Defence applicability remains unvalidated and every linked assurance scenario remains unexecuted.

REQ-005 — Auditable message, referral and task routing

Trace dimension Current state
Mapped mechanism code(s) VIS, ALERT
Requirement status candidate_trace_complete_defence_unvalidated
Trace basis direct_case_claims

Designed assurance scenarios

Traceability qualification: Stringer directly supports routing and record-incorporation risk; Rhodes and Thompson support action ownership and closure.

Defence applicability remains unvalidated and every linked assurance scenario remains unexecuted.

REQ-007 — Safe hybrid record operation

Trace dimension Current state
Mapped mechanism code(s) VIS, ALERT
Requirement status candidate_trace_complete_defence_unvalidated
Trace basis direct_case_claims

Designed assurance scenarios

  • AST-007designed_not_executed

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 remains unvalidated and every linked assurance scenario remains unexecuted.

REQ-008 — Provenance and amendment clarity

Trace dimension Current state
Mapped mechanism code(s) VIS
Requirement status candidate_trace_complete_defence_unvalidated
Trace basis direct_case_claims

Designed assurance scenarios

  • AST-008designed_not_executed

Traceability qualification: Braund directly supports divergence between audit and exported views; Lunt supports attributable authorship for temporary staff; report 2018-0405 supports visibility of original content and amendment state. The latter two reports are future-risk concerns rather than digital causal findings.

Defence applicability remains unvalidated and every linked assurance scenario remains unexecuted.

REQ-009 — Actionable and proportionate decision support

Trace dimension Current state
Mapped mechanism code(s) VIS, ALERT
Requirement status candidate_trace_complete_defence_unvalidated
Trace basis direct_case_claims

Designed assurance scenarios

Traceability qualification: Grant directly supports decision-point timing and persistence of an alert, while the root-cause wording remains attributable to the Trust analysis; Rhodes, Ross, King and Thompson support other salience or alerting mechanisms. Defence thresholds and workflow remain unvalidated.

Defence applicability remains unvalidated and every linked assurance scenario remains unexecuted.

REQ-010 — Safety-control migration

Trace dimension Current state
Mapped mechanism code(s) ALERT
Requirement status candidate_trace_complete_defence_unvalidated
Trace basis direct_case_claims

Designed assurance scenarios

  • AST-010designed_not_executed

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 remains unvalidated and every linked assurance scenario remains unexecuted.

Closed-loop work and action ownership

Open the bounded finding synthesis · Codes: LOOP

REQ-002 — Population visibility and accountable recall

Trace dimension Current state
Mapped mechanism code(s) LOOP
Requirement status candidate_trace_complete_defence_unvalidated
Trace basis direct_case_claims

Designed assurance scenarios

  • AST-002designed_not_executed

Traceability qualification: Ross directly supports the missing computable non-response mechanism; Defence population completeness remains untested.

Defence applicability remains unvalidated and every linked assurance scenario remains unexecuted.

REQ-004 — Critical-result delivery and clinical closure

Trace dimension Current state
Mapped mechanism code(s) LOOP
Requirement status candidate_trace_complete_defence_unvalidated
Trace basis direct_case_claims

Designed assurance scenarios

Traceability qualification: Caliel Smith-Kwami directly supports the distinction between passive EHR availability and active result notification, while preserving the wider analyser, discharge and follow-up context; Rhodes supports salience and filing risk; Thompson supports accountable delivery and closure.

Defence applicability remains unvalidated and every linked assurance scenario remains unexecuted.

REQ-005 — Auditable message, referral and task routing

Trace dimension Current state
Mapped mechanism code(s) LOOP
Requirement status candidate_trace_complete_defence_unvalidated
Trace basis direct_case_claims

Designed assurance scenarios

Traceability qualification: Stringer directly supports routing and record-incorporation risk; Rhodes and Thompson support action ownership and closure.

Defence applicability remains unvalidated and every linked assurance scenario remains unexecuted.

REQ-006 — Transfer and handover record delivery

Trace dimension Current state
Mapped mechanism code(s) LOOP
Requirement status candidate_trace_complete_defence_unvalidated
Trace basis direct_case_claims

Designed assurance scenarios

  • AST-006designed_not_executed

Traceability qualification: Welch directly supports urgent cross-jurisdiction image transfer and the failure of the manual fallback; Reddington supports inaccessible ePRF handover; Cassidy supports safety-critical information stranded across a receiving boundary.

Defence applicability remains unvalidated and every linked assurance scenario remains unexecuted.

REQ-007 — Safe hybrid record operation

Trace dimension Current state
Mapped mechanism code(s) LOOP
Requirement status candidate_trace_complete_defence_unvalidated
Trace basis direct_case_claims

Designed assurance scenarios

  • AST-007designed_not_executed

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 remains unvalidated and every linked assurance scenario remains unexecuted.

REQ-009 — Actionable and proportionate decision support

Trace dimension Current state
Mapped mechanism code(s) LOOP
Requirement status candidate_trace_complete_defence_unvalidated
Trace basis direct_case_claims

Designed assurance scenarios

Traceability qualification: Grant directly supports decision-point timing and persistence of an alert, while the root-cause wording remains attributable to the Trust analysis; Rhodes, Ross, King and Thompson support other salience or alerting mechanisms. Defence thresholds and workflow remain unvalidated.

Defence applicability remains unvalidated and every linked assurance scenario remains unexecuted.

REQ-011 — Distributed transaction integrity

Trace dimension Current state
Mapped mechanism code(s) LOOP
Requirement status candidate_trace_complete_defence_unvalidated
Trace basis direct_case_claims

Designed assurance scenarios

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 remains unvalidated and every linked assurance scenario remains unexecuted.

REQ-012 — Degraded-operation resilience and safe synchronisation

Trace dimension Current state
Mapped mechanism code(s) LOOP
Requirement status candidate_partial_trace_defence_unvalidated
Trace basis partial_scope_extension

Designed assurance scenarios

Traceability qualification: Welch directly supports failed cross-system transfer fallback, and Price directly supports loss of a promised callback during a system outage; Reddington, Thompson and King support other fragile transfer, escalation or hybrid mechanisms. Conflict-safe offline synchronisation remains a Defence hypothesis, so the trace basis remains a partial scope extension.

Defence applicability remains unvalidated and every linked assurance scenario remains unexecuted.

Interoperability, identity and continuity

Open the bounded finding synthesis · Codes: INT, IDPOP

REQ-001 — Identity and current care responsibility

Trace dimension Current state
Mapped mechanism code(s) INT, IDPOP
Requirement status candidate_trace_complete_defence_unvalidated
Trace basis direct_case_claims

Designed assurance scenarios

Traceability qualification: Jordan directly supports the record-source hazard; Ross supports dependence on computable status; CLM-007 is an explicitly low-confidence Defence analogy, not a DMICP finding.

Defence applicability remains unvalidated and every linked assurance scenario remains unexecuted.

REQ-002 — Population visibility and accountable recall

Trace dimension Current state
Mapped mechanism code(s) INT, IDPOP
Requirement status candidate_trace_complete_defence_unvalidated
Trace basis direct_case_claims

Designed assurance scenarios

  • AST-002designed_not_executed

Traceability qualification: Ross directly supports the missing computable non-response mechanism; Defence population completeness remains untested.

Defence applicability remains unvalidated and every linked assurance scenario remains unexecuted.

REQ-003 — Longitudinal minimum record and source completeness

Trace dimension Current state
Mapped mechanism code(s) INT, IDPOP
Requirement status candidate_trace_complete_defence_unvalidated
Trace basis direct_case_claims

Designed assurance scenarios

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 remains unvalidated and every linked assurance scenario remains unexecuted.

REQ-006 — Transfer and handover record delivery

Trace dimension Current state
Mapped mechanism code(s) INT
Requirement status candidate_trace_complete_defence_unvalidated
Trace basis direct_case_claims

Designed assurance scenarios

  • AST-006designed_not_executed

Traceability qualification: Welch directly supports urgent cross-jurisdiction image transfer and the failure of the manual fallback; Reddington supports inaccessible ePRF handover; Cassidy supports safety-critical information stranded across a receiving boundary.

Defence applicability remains unvalidated and every linked assurance scenario remains unexecuted.

REQ-011 — Distributed transaction integrity

Trace dimension Current state
Mapped mechanism code(s) INT
Requirement status candidate_trace_complete_defence_unvalidated
Trace basis direct_case_claims

Designed assurance scenarios

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 remains unvalidated and every linked assurance scenario remains unexecuted.

REQ-012 — Degraded-operation resilience and safe synchronisation

Trace dimension Current state
Mapped mechanism code(s) INT
Requirement status candidate_partial_trace_defence_unvalidated
Trace basis partial_scope_extension

Designed assurance scenarios

Traceability qualification: Welch directly supports failed cross-system transfer fallback, and Price directly supports loss of a promised callback during a system outage; Reddington, Thompson and King support other fragile transfer, escalation or hybrid mechanisms. Conflict-safe offline synchronisation remains a Defence hypothesis, so the trace basis remains a partial scope extension.

Defence applicability remains unvalidated and every linked assurance scenario remains unexecuted.

REQ-013 — Clinical and operational boundary control

Trace dimension Current state
Mapped mechanism code(s) INT
Requirement status candidate_partial_trace_defence_unvalidated
Trace basis partial_scope_extension

Designed assurance scenarios

  • AST-013designed_not_executed

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 remains unvalidated and every linked assurance scenario remains unexecuted.

Record integrity and provenance

Open the bounded finding synthesis · Codes: PROV

REQ-005 — Auditable message, referral and task routing

Trace dimension Current state
Mapped mechanism code(s) PROV
Requirement status candidate_trace_complete_defence_unvalidated
Trace basis direct_case_claims

Designed assurance scenarios

Traceability qualification: Stringer directly supports routing and record-incorporation risk; Rhodes and Thompson support action ownership and closure.

Defence applicability remains unvalidated and every linked assurance scenario remains unexecuted.

REQ-007 — Safe hybrid record operation

Trace dimension Current state
Mapped mechanism code(s) PROV
Requirement status candidate_trace_complete_defence_unvalidated
Trace basis direct_case_claims

Designed assurance scenarios

  • AST-007designed_not_executed

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 remains unvalidated and every linked assurance scenario remains unexecuted.

REQ-008 — Provenance and amendment clarity

Trace dimension Current state
Mapped mechanism code(s) PROV
Requirement status candidate_trace_complete_defence_unvalidated
Trace basis direct_case_claims

Designed assurance scenarios

  • AST-008designed_not_executed

Traceability qualification: Braund directly supports divergence between audit and exported views; Lunt supports attributable authorship for temporary staff; report 2018-0405 supports visibility of original content and amendment state. The latter two reports are future-risk concerns rather than digital causal findings.

Defence applicability remains unvalidated and every linked assurance scenario remains unexecuted.

REQ-011 — Distributed transaction integrity

Trace dimension Current state
Mapped mechanism code(s) PROV
Requirement status candidate_trace_complete_defence_unvalidated
Trace basis direct_case_claims

Designed assurance scenarios

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 remains unvalidated and every linked assurance scenario remains unexecuted.

REQ-012 — Degraded-operation resilience and safe synchronisation

Trace dimension Current state
Mapped mechanism code(s) PROV
Requirement status candidate_partial_trace_defence_unvalidated
Trace basis partial_scope_extension

Designed assurance scenarios

Traceability qualification: Welch directly supports failed cross-system transfer fallback, and Price directly supports loss of a promised callback during a system outage; Reddington, Thompson and King support other fragile transfer, escalation or hybrid mechanisms. Conflict-safe offline synchronisation remains a Defence hypothesis, so the trace basis remains a partial scope extension.

Defence applicability remains unvalidated and every linked assurance scenario remains unexecuted.

REQ-013 — Clinical and operational boundary control

Trace dimension Current state
Mapped mechanism code(s) PROV
Requirement status candidate_partial_trace_defence_unvalidated
Trace basis partial_scope_extension

Designed assurance scenarios

  • AST-013designed_not_executed

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 remains unvalidated and every linked assurance scenario remains unexecuted.

Resilience and degraded operation

Open the bounded finding synthesis · Codes: RES

REQ-004 — Critical-result delivery and clinical closure

Trace dimension Current state
Mapped mechanism code(s) RES
Requirement status candidate_trace_complete_defence_unvalidated
Trace basis direct_case_claims

Designed assurance scenarios

Traceability qualification: Caliel Smith-Kwami directly supports the distinction between passive EHR availability and active result notification, while preserving the wider analyser, discharge and follow-up context; Rhodes supports salience and filing risk; Thompson supports accountable delivery and closure.

Defence applicability remains unvalidated and every linked assurance scenario remains unexecuted.

REQ-006 — Transfer and handover record delivery

Trace dimension Current state
Mapped mechanism code(s) RES
Requirement status candidate_trace_complete_defence_unvalidated
Trace basis direct_case_claims

Designed assurance scenarios

  • AST-006designed_not_executed

Traceability qualification: Welch directly supports urgent cross-jurisdiction image transfer and the failure of the manual fallback; Reddington supports inaccessible ePRF handover; Cassidy supports safety-critical information stranded across a receiving boundary.

Defence applicability remains unvalidated and every linked assurance scenario remains unexecuted.

REQ-011 — Distributed transaction integrity

Trace dimension Current state
Mapped mechanism code(s) RES
Requirement status candidate_trace_complete_defence_unvalidated
Trace basis direct_case_claims

Designed assurance scenarios

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 remains unvalidated and every linked assurance scenario remains unexecuted.

REQ-012 — Degraded-operation resilience and safe synchronisation

Trace dimension Current state
Mapped mechanism code(s) RES
Requirement status candidate_partial_trace_defence_unvalidated
Trace basis partial_scope_extension

Designed assurance scenarios

Traceability qualification: Welch directly supports failed cross-system transfer fallback, and Price directly supports loss of a promised callback during a system outage; Reddington, Thompson and King support other fragile transfer, escalation or hybrid mechanisms. Conflict-safe offline synchronisation remains a Defence hypothesis, so the trace basis remains a partial scope extension.

Defence applicability remains unvalidated and every linked assurance scenario remains unexecuted.

Governance and assurance

Open the bounded finding synthesis · Codes: GOV

REQ-001 — Identity and current care responsibility

Trace dimension Current state
Mapped mechanism code(s) GOV
Requirement status candidate_trace_complete_defence_unvalidated
Trace basis direct_case_claims

Designed assurance scenarios

Traceability qualification: Jordan directly supports the record-source hazard; Ross supports dependence on computable status; CLM-007 is an explicitly low-confidence Defence analogy, not a DMICP finding.

Defence applicability remains unvalidated and every linked assurance scenario remains unexecuted.

REQ-002 — Population visibility and accountable recall

Trace dimension Current state
Mapped mechanism code(s) GOV
Requirement status candidate_trace_complete_defence_unvalidated
Trace basis direct_case_claims

Designed assurance scenarios

  • AST-002designed_not_executed

Traceability qualification: Ross directly supports the missing computable non-response mechanism; Defence population completeness remains untested.

Defence applicability remains unvalidated and every linked assurance scenario remains unexecuted.

REQ-003 — Longitudinal minimum record and source completeness

Trace dimension Current state
Mapped mechanism code(s) GOV
Requirement status candidate_trace_complete_defence_unvalidated
Trace basis direct_case_claims

Designed assurance scenarios

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 remains unvalidated and every linked assurance scenario remains unexecuted.

REQ-004 — Critical-result delivery and clinical closure

Trace dimension Current state
Mapped mechanism code(s) GOV
Requirement status candidate_trace_complete_defence_unvalidated
Trace basis direct_case_claims

Designed assurance scenarios

Traceability qualification: Caliel Smith-Kwami directly supports the distinction between passive EHR availability and active result notification, while preserving the wider analyser, discharge and follow-up context; Rhodes supports salience and filing risk; Thompson supports accountable delivery and closure.

Defence applicability remains unvalidated and every linked assurance scenario remains unexecuted.

REQ-005 — Auditable message, referral and task routing

Trace dimension Current state
Mapped mechanism code(s) GOV
Requirement status candidate_trace_complete_defence_unvalidated
Trace basis direct_case_claims

Designed assurance scenarios

Traceability qualification: Stringer directly supports routing and record-incorporation risk; Rhodes and Thompson support action ownership and closure.

Defence applicability remains unvalidated and every linked assurance scenario remains unexecuted.

REQ-006 — Transfer and handover record delivery

Trace dimension Current state
Mapped mechanism code(s) GOV
Requirement status candidate_trace_complete_defence_unvalidated
Trace basis direct_case_claims

Designed assurance scenarios

  • AST-006designed_not_executed

Traceability qualification: Welch directly supports urgent cross-jurisdiction image transfer and the failure of the manual fallback; Reddington supports inaccessible ePRF handover; Cassidy supports safety-critical information stranded across a receiving boundary.

Defence applicability remains unvalidated and every linked assurance scenario remains unexecuted.

REQ-008 — Provenance and amendment clarity

Trace dimension Current state
Mapped mechanism code(s) GOV
Requirement status candidate_trace_complete_defence_unvalidated
Trace basis direct_case_claims

Designed assurance scenarios

  • AST-008designed_not_executed

Traceability qualification: Braund directly supports divergence between audit and exported views; Lunt supports attributable authorship for temporary staff; report 2018-0405 supports visibility of original content and amendment state. The latter two reports are future-risk concerns rather than digital causal findings.

Defence applicability remains unvalidated and every linked assurance scenario remains unexecuted.

REQ-009 — Actionable and proportionate decision support

Trace dimension Current state
Mapped mechanism code(s) GOV
Requirement status candidate_trace_complete_defence_unvalidated
Trace basis direct_case_claims

Designed assurance scenarios

Traceability qualification: Grant directly supports decision-point timing and persistence of an alert, while the root-cause wording remains attributable to the Trust analysis; Rhodes, Ross, King and Thompson support other salience or alerting mechanisms. Defence thresholds and workflow remain unvalidated.

Defence applicability remains unvalidated and every linked assurance scenario remains unexecuted.

REQ-010 — Safety-control migration

Trace dimension Current state
Mapped mechanism code(s) GOV
Requirement status candidate_trace_complete_defence_unvalidated
Trace basis direct_case_claims

Designed assurance scenarios

  • AST-010designed_not_executed

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 remains unvalidated and every linked assurance scenario remains unexecuted.

REQ-011 — Distributed transaction integrity

Trace dimension Current state
Mapped mechanism code(s) GOV
Requirement status candidate_trace_complete_defence_unvalidated
Trace basis direct_case_claims

Designed assurance scenarios

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 remains unvalidated and every linked assurance scenario remains unexecuted.

REQ-012 — Degraded-operation resilience and safe synchronisation

Trace dimension Current state
Mapped mechanism code(s) GOV
Requirement status candidate_partial_trace_defence_unvalidated
Trace basis partial_scope_extension

Designed assurance scenarios

Traceability qualification: Welch directly supports failed cross-system transfer fallback, and Price directly supports loss of a promised callback during a system outage; Reddington, Thompson and King support other fragile transfer, escalation or hybrid mechanisms. Conflict-safe offline synchronisation remains a Defence hypothesis, so the trace basis remains a partial scope extension.

Defence applicability remains unvalidated and every linked assurance scenario remains unexecuted.

REQ-013 — Clinical and operational boundary control

Trace dimension Current state
Mapped mechanism code(s) GOV
Requirement status candidate_partial_trace_defence_unvalidated
Trace basis partial_scope_extension

Designed assurance scenarios

  • AST-013designed_not_executed

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 remains unvalidated and every linked assurance scenario remains unexecuted.

Human-factors lens

Open the bounded finding synthesis · Codes: HF

REQ-004 — Critical-result delivery and clinical closure

Trace dimension Current state
Mapped mechanism code(s) HF
Requirement status candidate_trace_complete_defence_unvalidated
Trace basis direct_case_claims

Designed assurance scenarios

Traceability qualification: Caliel Smith-Kwami directly supports the distinction between passive EHR availability and active result notification, while preserving the wider analyser, discharge and follow-up context; Rhodes supports salience and filing risk; Thompson supports accountable delivery and closure.

Defence applicability remains unvalidated and every linked assurance scenario remains unexecuted.

REQ-005 — Auditable message, referral and task routing

Trace dimension Current state
Mapped mechanism code(s) HF
Requirement status candidate_trace_complete_defence_unvalidated
Trace basis direct_case_claims

Designed assurance scenarios

Traceability qualification: Stringer directly supports routing and record-incorporation risk; Rhodes and Thompson support action ownership and closure.

Defence applicability remains unvalidated and every linked assurance scenario remains unexecuted.

REQ-006 — Transfer and handover record delivery

Trace dimension Current state
Mapped mechanism code(s) HF
Requirement status candidate_trace_complete_defence_unvalidated
Trace basis direct_case_claims

Designed assurance scenarios

  • AST-006designed_not_executed

Traceability qualification: Welch directly supports urgent cross-jurisdiction image transfer and the failure of the manual fallback; Reddington supports inaccessible ePRF handover; Cassidy supports safety-critical information stranded across a receiving boundary.

Defence applicability remains unvalidated and every linked assurance scenario remains unexecuted.

REQ-007 — Safe hybrid record operation

Trace dimension Current state
Mapped mechanism code(s) HF
Requirement status candidate_trace_complete_defence_unvalidated
Trace basis direct_case_claims

Designed assurance scenarios

  • AST-007designed_not_executed

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 remains unvalidated and every linked assurance scenario remains unexecuted.

REQ-009 — Actionable and proportionate decision support

Trace dimension Current state
Mapped mechanism code(s) HF
Requirement status candidate_trace_complete_defence_unvalidated
Trace basis direct_case_claims

Designed assurance scenarios

Traceability qualification: Grant directly supports decision-point timing and persistence of an alert, while the root-cause wording remains attributable to the Trust analysis; Rhodes, Ross, King and Thompson support other salience or alerting mechanisms. Defence thresholds and workflow remain unvalidated.

Defence applicability remains unvalidated and every linked assurance scenario remains unexecuted.

REQ-010 — Safety-control migration

Trace dimension Current state
Mapped mechanism code(s) HF
Requirement status candidate_trace_complete_defence_unvalidated
Trace basis direct_case_claims

Designed assurance scenarios

  • AST-010designed_not_executed

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 remains unvalidated and every linked assurance scenario remains unexecuted.

How to use this view

  1. Open the finding to understand the bounded cross-case mechanism and its limitations.
  2. Open the candidate requirement to inspect its included reports, stable claims, applicability and traceability qualification.
  3. Open the assurance scenario to inspect the proposed method and pass evidence.
  4. Do not promote a requirement or report a pass until Defence workflow evidence, representative execution and an authorised clinical-risk decision are registered.