Stephen Cassidy
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-020 · Return to all included reports · Open the case–mechanism/evidence map
Report metadata
| Field | Value |
|---|---|
| PFD reference | 2023-0337 |
| Registered primary source | SRC-020 |
| Report date | 2023-09-19 |
| Coroner area | Avon |
| Clinical setting | Emergency/hospital care |
| Care transition | Ambulance/primary care to hospital |
| Primary workflow group | Record access and continuity |
| Primary browsing context | Acute and emergency care |
| Predominant information boundary | Between care settings |
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, Secondary acute or outpatient care |
| Information or work-item origin | Primary care |
| Origin care context(s) | Primary care |
| Expected action destination | Secondary acute or outpatient care |
| Destination care context(s) | Secondary care |
| Directional pathway | Primary care → Secondary acute or outpatient care |
| Care-setting span | Multiple care settings |
| Sector boundary | Health services only |
| Failure point | Transfer or interface |
| Classification confidence | high |
Classification note: The known allergy was held in EMIS and the Summary Care Record but did not enter the receiving hospital's prescribing and care workflow; ambulance transport was contextual rather than the information source.
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 | Not assessed in this dataset |
| Registered response sources | None registered for this row |
| Non-exclusive mechanism codes | INT, VIS, HF, GOV |
Qualification recorded in the dataset: Report conclusion directly linked unavailable allergy information to death
“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
Routine access and integration were absent and could cause harm
Requested action
Hospital and national recipients to act
Digital safety characterisation
| Dimension | Project extraction |
|---|---|
| System or record type | Summary Care Record, Careflow/Connect and EMIS |
| Digital function | Allergy/record access |
| Failure mode | Known allergy was not routinely accessible or integrated into hospital EPR |
| Human-factors issue | Access was not routine or easy |
| Workflow issue | No automatic transfer into prescribing/care workflow |
| Information issue | Critical allergy stranded in external record |
Downstream Defence trace
Canonical candidate requirements that cite this report: REQ-003, REQ-006. These links are analytical translations and do not make the requirement a coronial recommendation or a validated Defence control.
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.