Skip to content

Research and evidence change log

Renderer, navigation, build and service history is recorded separately in the technical change log.

20 July 2026

  • Implemented the approved second Cloudflare deployment phase as a bounded Ask Wiki tool. The public Zensical search index remains the only runtime retrieval corpus; the generated answer is explicitly non-evidential and must be checked against retrieved pages and their registered primary sources.
  • Reused the InterSystems shared-key interaction pattern while giving Regulation 28 its own encrypted secret. The Pages Function fails closed, uses constant-time comparison, fixed-model and request caps, same-origin client requests, non-persistent key handling and no-store responses.
  • Added clinical-safety prompt boundaries that preserve the source-to-assurance authority chain, distinguish coronial findings from responses and Defence translations, and prohibit patient-specific advice, unsupported DMICP/product causation and prevalence or trend claims from corpus recurrence.
  • Confirmed against current Cloudflare documentation that Pages Functions support the Workers AI binding, encrypted secrets are not readable after creation, Wrangler deployment includes the root functions/ directory, Workers AI local inference incurs usage, and static routes should be excluded from Function invocation. No new source record was created because these are deployment controls rather than study evidence.
  • Runtime validation established that Pages projects reject the Workers ratelimits configuration field even though Wrangler's general schema and type generator recognise it. The unsupported binding was removed before secret creation or deployment; no per-user or WAF rate limit is claimed.

14 July 2026

  • Received the initial scope and five named examples from the project sponsor.
  • Verified primary Judiciary pages for Stephen Rhodes, Rachelle Ross, Alexander Braund, and Morris Reddington.
  • Separated verified report content from sponsor-supplied discovery claims.
  • Ingested the ICMM 2026 project brief unchanged into research/briefs/ and created the rapid-review workspace, protocol, coding framework, datasets, abstract, oral outline and submission checklist.
  • Checked the current official ICMM event page, guidelines and parent-congress page. Recorded a live deadline conflict: 3 August 2026 on the event page versus 14 July 2026 on the parent page.
  • Confirmed the statutory distinction between the reporting duty in Schedule 5 paragraph 7 of the Coroners and Justice Act 2009 and the report/response procedure in Regulations 28–29.
  • Logged 50 unique PFD candidates and completed full-schema extraction for an initial 30-case focused series; generated non-exclusive code counts directly from the CSV rather than hand-maintaining totals.
  • Corrected Ross: the missing input was national non-responder status, while vendor responses said due/outstanding smear alerts existed.
  • Corrected Braund: the live SystmOne audit trail retained amendment metadata and prior text; the problem described was visibility in the printed/editable summary used for investigation.
  • Verified the provisional Derby case as Stephen Stringer, PFD 2024-0555, and avoided attributing the incident to a supplier not named in official materials.
  • Extracted the Reddington joint response and separated its proposed FHIR delivery remedy from the coroner's finding.
  • Added Eric Thompson, Stephen Cassidy, Samuel Jordan and Audrey King as representative narrative cases and linked the wider dataset to official Judiciary sources.
  • Ran a scoped literature-orientation search. Located peer-reviewed PFD collection/thematic-analysis precedents, a 2025 military EHR systematic review and an EHR-interoperability incident analysis; recorded the absence of a located digital-PFD synthesis as a search limitation, not a novelty claim.
  • Separated a Welsh Government claim about growth in all PFD reports from the unproven proposition that digital-health PFD reports are increasing.
  • Resolved all 17 eligible-pending candidates against full official reports and available recipient responses. The current pass now contains 47 fully extracted reports from 50 candidates, with 3 protocol exclusions and no unresolved screening decisions.
  • Populated the working abstract with the current-pass report and non-exclusive theme counts, retained explicit single-reviewer/corpus limitations, and added automated title, body-word, keyword and placeholder checks.

15 July 2026

  • Reconsidered the information architecture against the 47-report corpus, current traceability, official evidence-synthesis guidance, patient-safety thematic-review practice and Zensical capabilities.
  • Adopted a reader model based on evidence base, findings, Defence application, methods and outputs; classified conference and technical materials as derivatives rather than peer evidence domains.
  • Registered methodological and information-architecture sources SRC-030 to SRC-037, including JBI, PRISMA, NHS England thematic-review guidance, Judiciary search guidance, evidence-mapping practice and living-review context. These guide transparency and labelling; they do not convert the project into a systematic or scoping review.
  • Relabelled the product as a targeted evidence map and thematic case synthesis, retained the focused-series boundary and documented explicit inductive, deductive, context-facet and Defence-translation layers.
  • Added controlled primary workflow, setting, boundary, verification and response-status facets to all 47 included rows without replacing their detailed extraction or non-exclusive mechanism codes.
  • Generated a complete all-report catalogue, 47 individual report records and a case–mechanism map from the canonical included-case dataset. Empty map cells are explicitly not labelled evidence gaps.
  • Replaced the former product-oriented theme layer with six mechanism-first findings and a cross-cutting human-factors lens, each recording recurrence, variation, counter-considerations and limits.
  • Added CLM-015 for Audrey King's hybrid paper–electronic medication workflow, so every representative case now has a stable claim trace.
  • Established 13 candidate Defence requirements (REQ-001 to REQ-013) and 13 designed assurance scenarios (AST-001 to AST-013). No requirement is validated for Defence and no scenario has been executed.
  • Separated transferability limits and 12 DMICP evidence gaps from civilian findings; retained wrong-practice population invisibility as an explicit Defence hypothesis rather than a system finding.
  • Registered recipient-response provenance one document per stable source ID. Thirty-five known official attachments are now row-linked across 18 reports; each generated report page separates those respondent accounts from the coroner's report and warns that a response does not demonstrate implementation or effectiveness.
  • Split the previously bundled Ross vendor record into separate TPP and EMIS sources and recorded attachment-specific limitations where a response addresses only another concern, supplies policy context, or reports a recipient's contested position.
  • Completed a bounded historical 2018 publication-cohort backfill: 379 unique Judiciary PFD pages were enumerated; 121 report PDFs yielded direct text and 258 scanned reports (682 pages) were OCR-processed with no extraction failures. The canonical audit records literal official-query zero results, report-text hit counts and the publication-date/report-date limitation.
  • Recovered the exact 379-row working cohort index and extraction artefacts, published a canonical CSV manifest with official page/attachment URLs, PDF hashes, extraction routes and base query-family hits, and corrected the evidence boundary: 36 cohort rows have retained contextual decisions while 343 do not, so complete enumeration/extraction is not described as complete row-level screening.
  • Integrated 24 eligible reports dated in 2018, including Karl Willis as an online-prescribing workflow case and Mavis Reeves as a deliberately bounded telecare/health-IT design case. Four pages without a displayed official reference received transparent UNREF-2018-… project identifiers.
  • Promoted eight strongly matched 2018 report claims into the controlled claim-to-requirement trace, replacing REQ-008's indirect Stringer mapping and retaining REQ-012 as a partial scope extension because offline synchronisation remains unsupported.
  • Retained eight report-dated-2018 exclusions and five mechanism-relevant reports dated in 2017 as explicit out-of-scope screening decisions. Recorded the later-migrated 2018-0405 report and opened rechecks for other later migrations and the Cuthbert Hingert reference discrepancy.
  • Queried the canonical graph and five sibling-project evidence trails before extending the DMICP analysis. The internal audit is retained at research/audits/dmicp-sibling-audit-2026-07-15.md; no row-level practice, facility or population data were copied into the wiki.
  • Registered SRC-130 to SRC-135 for current published DCB0129/DCB0160 and patient-safety context. Distinguished patient-safety learning from DCB clinical-risk management, and recorded that the 2018 DCB releases remain current while NHS England's 2026 national review is in progress.
  • Cross-walked the 71-report corpus from patient-safety workflows to the existing non-exclusive clinical-safety mechanisms, stable CLM- claims, candidate REQ- requirements and designed AST- scenarios. Counts remain recurrence within this targeted dataset, not prevalence, trend, causation or product comparison.
  • Corrected the DMICP system description after sibling and primary-source review: official sources support a long-running fixed/deployed Defence EPR; CGI historically described a hosted EMIS PCS-based service; no reviewed public evidence independently proves the current build/topology or a quantified four-nation national-service limitation.
  • Extended the open-source architecture search after the sponsor described DMICP as an on-premises-hosted, EMIS PCS-based solution within the MCN/Defence environment. Registered current 2025/26 DMICP use, the official 2019 legacy EMIS DPCS platform notice, historical CGI central secure hosting, MODNet access and the public procurement definitions of MCN/MODNet.
  • Recorded the sponsor's subsequent clarification that MCN means MOD Core Network and that “on-premises hosted” means a centrally hosted DMICP server estate inside Defence/MCN infrastructure, with medical centres and users accessing through MCN/MODNet client terminals or devices—not practice-local servers. This resolves the terminology and intended topology distinction in the supplied context; no located public source independently confirms the complete current topology or exact DMICP-to-MCN path.
  • Recorded the sponsor's confirmation that the live DMICP clinical application is EMIS PCS/DPCS. This promotes the current product family from historical lineage to sponsor-supplied operational context, while leaving the exact live version, Defence adaptations, component baseline and independent architecture confirmation open.
  • Recorded the sponsor's current national-service boundary: e-RS is separate browser access to an HSCN/Spine web application rather than DMICP integration; EPS, GP Connect, NHS App, Summary Care Record and the Scottish, Welsh and Northern Irish national platforms are unavailable to Defence. Retained PDS as the documented current DMICP integration and pathology as dated interface evidence. Isolated local systems/manual routes are not used to imply meaningful national-platform availability.
  • Closed the sponsor clarification sequence with DMICP's clinical-safety regime recorded as unknown: the sponsor cannot presently confirm DCB0129/DCB0160 or a Defence equivalent, a named Clinical Safety Officer, Hazard Log or Clinical Safety Case. No inference of absence, inadequacy or non-conformity is made.
  • Replaced the earlier broad connectivity formulation with a bounded integration/access account: registered Spine PDS integration, dated pathology-report messaging, browser-only e-RS access, the named unavailable national services, the paper-based NHS–DMS transfer limitation and dated CQC workflow evidence. Brawdy also records age-related DMICP slowness, outages and newer-technology compatibility as widely affecting DPHC. The CQC material is labelled as inspection evidence under the DMSR-invited programme; isolated examples evidence local work as done but are not treated as national-platform availability, a representative comparison, DCB assessment or complete interface inventory.
  • Triangulated the PFD-derived hazard questions with CQC's 2022/23 and 2024/25 Defence medical-centre findings, preserving their inspection/date boundary and avoiding a DCB-conformity or product-causation inference.
  • Added a two-page thematic output under Outputs that maps PFD evidence to DCB0129/DCB0160 controls and to bounded DMICP/CORTISONE assurance questions. It remains derivative of the canonical evidence, claims, requirements and tests.