Avery Hall
Evidence boundary. This page is a structured project extraction from the linked primary Prevention of Future Deaths source. It is not the report text. Do not infer cause, prevalence or product-wide performance beyond the source and the explicit qualification below.
Open the primary Judiciary source · Source register: SRC-056 · Return to all included reports · Open the case–mechanism/evidence map
Report metadata
| Field | Value |
|---|---|
| PFD reference | 2026-0048 |
| Registered primary source | SRC-056 |
| Report date | 2026-02-02 |
| Coroner area | England |
| Clinical setting | General practice/maternity |
| Care transition | Pregnancy information to repeat prescribing |
| Primary workflow group | Medication and prescribing |
| Primary browsing context | Maternity and paediatric care |
| Predominant information boundary | Within a care setting |
The workflow, browsing-context and predominant-boundary fields are retained navigation aids. They are not additional coronial findings, and a single primary value cannot express every aspect of a multi-setting or multi-mechanism report.
Care-pathway classification
This classification distinguishes where safety-relevant information or work arose, where action was expected and where the digital or information workflow failed. It is a project coding of the source, not a coronial statement. “Origin” does not mean the organisation caused the harm.
| Dimension | Project classification |
|---|---|
| Settings and pathway participants | Primary care |
| Information or work-item origin | Primary care |
| Origin care context(s) | Primary care |
| Expected action destination | Primary care |
| Destination care context(s) | Primary care |
| Directional pathway | Primary care → Primary care |
| Care-setting span | One care setting |
| Sector boundary | Health services only |
| Failure point | Receiving or action service |
| Classification confidence | high |
Classification note: Pregnancy was disclosed to the GP and action was expected in the same GP repeat-prescribing workflow; antenatal contacts were contextual rather than the coded digital route.
Classification confidence applies only to this care-pathway coding. It is separate from extraction confidence, source authority and causal certainty.
Evidence status and qualification
| Field | Status |
|---|---|
| Extraction confidence | high |
| Verification status | Primary source linked; high-confidence extraction |
| Response evidence status | Response evidence noted |
| Registered response sources | SRC-080, SRC-081 |
| Non-exclusive mechanism codes | ALERT, IDPOP, LOOP, GOV |
Qualification recorded in the dataset: Primary report and practice response available
“Response evidence noted” means only that the row qualification refers to response/respondent evidence or records a recipient's post-report position. The linked IDs enumerate the official response attachments registered for this row; they do not imply that every response supports every part of the qualification, and they do not establish implementation. “Not assessed” makes no claim about whether a response exists.
Structured project extraction
These fields are analytical summaries, not quotations.
Project summary of the coroner's concern
System warnings and repeat-review controls required action
Requested action
Practice and relevant bodies to act
Digital safety characterisation
| Dimension | Project extraction |
|---|---|
| System or record type | GP prescribing and record system |
| Digital function | Contraindication/repeat prescribing |
| Failure mode | Pregnancy generated no warning and contraindicated candesartan remained on repeat |
| Human-factors issue | Changing patient context did not alter prescribing visibility |
| Workflow issue | Repeat workflow lacked forced reassessment |
| Information issue | Contraindication context not delivered |
Downstream Defence trace
No canonical candidate Defence requirement currently cites this report. This does not imply that the mechanism is irrelevant; any mapping must be added and qualified in the controlled requirements register.
The included-case dataset preserves early legacy_military_relevance and legacy_derived_requirement fields for audit history. They are not published here as requirements and must not override the canonical REQ register. New report rows do not need to populate them.