Source types and authority

The source register assigns stable IDs across several evidence roles. These roles must not be collapsed into one confidence score.

Primary statutory and coronial sources

PFD reports: SRC-001 to SRC-004, SRC-014, SRC-019 to SRC-022, SRC-038 to SRC-075, SRC-106 to SRC-129, and SRC-181 to SRC-221.
Statutory framework: SRC-010 and SRC-011.

These are authoritative for the report text, the coroner's expressed concern and the legal procedure. A PFD concern need not be a finding that the issue caused the death.

Four 2018 official pages do not display a PFD reference. Their UNREF-2018-… values are stable project report IDs used for deduplication and routing, not official references. The source register links each ID to the official Judiciary page.

Official recipient responses

SRC-015 to SRC-018, SRC-023, SRC-076 to SRC-105, SRC-170 to SRC-180, SRC-222 to SRC-245, SRC-247 to SRC-254 and SRC-255 to SRC-283 record respondent explanations, qualifications and proposed actions. Each ID identifies one document and one official Judiciary attachment URL. They can clarify technical circumstances, but they remain distinct from coronial findings and do not establish that a proposed remedy was implemented or effective. Attachments that address only another concern in the same report are registered but must not be used to support the digital mechanism.

SRC-246 is an official NHS England homebirth-review circular attached to the Pippa Gillibrand page. It predates that PFD, concerns an earlier report and required no response, so it is registered as supporting context rather than counted as a Gillibrand response letter.

SRC-005 and SRC-012: sponsor briefs and discovery direction; not independent evidence.
SRC-013: the local screening and included-report datasets; authority for recorded review counts and coding, not for new case facts.
SRC-169: the supplied 400-page reference document; a secondary synthesis and discovery artefact whose case and framework assertions require independent primary-source verification.

Supplied material can trigger a recheck or search. It cannot displace a primary report, become evidence merely because it is detailed, or validate its own Defence translation.

Official method and reporting guidance

SRC-030 to SRC-033 and SRC-036 to SRC-037: evidence-synthesis, reporting, patient-safety thematic-review, Judiciary search/procedure, evidence-mapping and update-method guidance.
These support transparent conduct and labelling; they do not make the current pass systematic, exhaustive or a living review.

Information architecture and data-publication context

SRC-034 to SRC-035 and SRC-284 to SRC-286 cover government user-needs guidance, renderer capabilities, data-catalogue disclosure and evidence-map navigation.
They support reader-task organisation, generated distribution metadata and drill-down patterns only. They do not validate the corpus, confer DCAT conformance or turn the project into an evidence-gap map.

Clinical- and patient-safety standards and guidance

SRC-130 to SRC-134 record the current published DCB0129/DCB0160 specifications, implementation context and the active national review.
SRC-135 records PSIRF as the patient-safety learning framework used to distinguish system learning from DCB clinical-risk management and from coronial investigation.

These sources define responsibilities, processes and evidence expectations. They do not demonstrate that DMICP, CORTISONE or any named deployment conforms or fails to conform.

Defence system and programme context

SRC-136 to SRC-138, SRC-140 to SRC-141 and SRC-143 to SRC-154, plus SRC-156 to SRC-158, are official MOD, parliamentary, NHS operational, CQC inspection and procurement sources. The CQC material comes from the DMSR-invited programme rather than CQC's usual statutory/enforcement regime. These sources are date-bounded context, not a current DMICP architecture pack or clinical safety file.
SRC-139 and SRC-155 are historical vendor implementation context and must remain explicitly attributed to CGI.
SRC-142 is a project-internal sibling-source audit. It routes to primary sources and preserves claim limits; it is not independent evidence. No row-level practice or facility data should be published from the sibling analytical material without owner and information-governance review.

The source set distinguishes current use, sponsor-supplied current context, historical platform lineage, hosting, access, network terminology and individual interfaces. SRC-005 records the sponsor's product/hosting model and current service boundary: e-RS is browser-only access to a separate HSCN/Spine application, while the other named national services are unavailable to Defence. It also records that the sponsor cannot currently confirm DMICP's clinical-safety regime or core artefacts; these remain unknown, which is not evidence of absence or non-conformity. SRC-005 is not independent product, architecture or assurance evidence. Current use in SRC-145 does not make the 2015/2019 version or architecture in SRC-139, SRC-146 or SRC-155 current; the contract definition of MCN/MODNet in SRC-147 does not prove DMICP's route; and PDS/current and pathology/dated evidence in SRC-148/SRC-149 does not constitute a complete assured interface catalogue. Site-level CQC reports in SRC-150/SRC-151 and SRC-156 to SRC-158 evidence work as done at those facilities/dates, not general national-platform availability or a representative comparison.

Official contextual, publication and technical sources

SRC-007, SRC-008 and SRC-009: ICMM publication requirements and deadline status.
SRC-159 to SRC-161: BMJ Military Health/BMJ article-formatting and AI-use requirements. They govern the derivative submission product, not the clinical argument.
SRC-028: official Welsh Government context on PFD reporting; not evidence of a digital-specific trend.
SRC-006, SRC-034 and SRC-035: renderer, service-design and information-architecture documentation; technical authority only, not study evidence.

Peer-reviewed methodological and contextual literature

SRC-024 to SRC-027, SRC-029 and SRC-162 to SRC-168 support method choice, sociotechnical framing and external contextualisation. The two BMJ Military Health letters (SRC-167 and SRC-168) are direct Defence context but remain publication-specific observations. None replaces the primary PFD source for a case claim or proves a DMICP defect.

Use the exact source IDs in report analyses, claims and requirements so a reader can distinguish what was reported, what a recipient said, what the project coded and what was translated for Defence. The included-report dataset now row-links 107 official response letters across 63 reports, plus the separately classified supporting circular at SRC-246. Some responses are deliberately registered as non-supporting for a digital mechanism. The 49 included reports without a registered response letter remain an explicit review gap rather than an inferred absence.