Incident briefing note for governance review

You are preparing an evidence ledger from a de-identified healthcare administrative or operational incident record. This is not clinical advice. Do not assess care, diagnose, recommend treatment, or reach conclusions about fault.

First check the text for identifiable patient information or staff personal information. If you find any, stop and return only: "Remove or replace identifiable information before processing this record." Do not repeat the information.

Read the document titled **Administrative or operational incident record** below. Extract only statements supported by the record. Do not infer missing events, dates, roles, reasons, outcomes or policy requirements.

Return a Markdown table with these columns:
| Record reference | Date and time | Event or statement | Person or team role | Source within record | Evidence status |

Use `Confirmed` where the record states the point directly. Use `Reported` where it attributes a statement to a person or document. Use `Unclear` where wording, timing or ownership is uncertain. If a field is absent, write `Not stated`.

After the table, add these headings:
- **Conflicts or inconsistencies**: list conflicting dates, accounts, times or role descriptions.
- **Missing evidence**: list documents, logs, approvals, communications or records referred to but not supplied.
- **Safe summary**: write no more than 120 words, using only confirmed or reported facts.

Administrative or operational incident record:
[paste a fully de-identified incident record here]

Draft a factual governance briefing note from the de-identified document titled **Administrative or operational incident record** below. This is an administrative and operational document, not clinical advice. Do not make clinical assessments, legal conclusions, findings of fault, disciplinary recommendations, or statements about compliance unless the supplied record explicitly states them.

Before processing, check for identifiable patient information or staff personal information. If any appears, stop and return only: "Remove or replace identifiable information before processing this record." Do not quote it.

Use only facts in the supplied record. Do not fill gaps with likely explanations. Where the evidence is incomplete, write `Not stated`, `Unconfirmed`, or `Requires verification`, as appropriate. Keep language neutral. Attribute reported accounts, for example, "The record reports...".

Return a Markdown document with exactly these headings:
## Purpose
## Incident scope
## Timeline
## Immediate actions recorded
## Current position
## Missing evidence and verification needed
## Questions for the governance meeting
## Record limitations

Requirements:
- In **Timeline**, use a table with columns `Date and time`, `Event`, `Source`, and `Evidence status`.
- In **Immediate actions recorded**, distinguish actions completed, actions reported but unverified, and actions not stated.
- In **Missing evidence and verification needed**, state why each item matters to the briefing.
- In **Questions for the governance meeting**, ask factual governance questions only. Do not suggest answers.
- Keep the full note under 900 words.

Administrative or operational incident record:
[paste a fully de-identified incident record here]

Create a factual timeline from the de-identified document titled **Administrative or operational incident record** below. This task concerns healthcare administration and operations only. It is not clinical advice.

Check for identifiable patient information or staff personal information first. If present, stop and return only: "Remove or replace identifiable information before processing this record." Do not reproduce any part of the record.

Extract every dated or time-linked event. Include entries with partial timing, such as a date without a time or wording such as "later that day". Do not guess a date, time, sequence or cause. Treat conflicting accounts as separate entries.

Return these sections in Markdown:
## Chronological timeline
Use a table with columns `Sequence`, `Date`, `Time`, `Event`, `Role or team`, `Source reference`, `Confidence`.

Use `Exact`, `Partial`, `Relative`, or `Unknown` in **Confidence**. Sort exact and partial dates first. Put relative and unknown timing in a separate subsection at the end.

## Sequence gaps
List events that may be missing between known entries. For each, state the last known event, the next known event, and the evidence needed to establish what happened.

## Date or account conflicts
List each conflict without resolving it. State what each source says and which document or log would help verify it.

## Timeline statement for briefing note
Write a neutral summary of no more than 150 words. Use only the timeline facts above.

Administrative or operational incident record:
[paste a fully de-identified incident record here]

Review the de-identified document titled **Administrative or operational incident record** below for missing evidence needed to prepare a factual governance briefing note. This is not clinical advice. Do not assess treatment, decide fault, interpret legal duties, or recommend sanctions.

If the text contains identifiable patient information or staff personal information, stop and return only: "Remove or replace identifiable information before processing this record." Do not reproduce it.

Identify only evidence gaps arising from what the record says, what it relies on, or what it leaves unclear. Do not create a generic investigation checklist. Do not assume a document exists merely because it is common practice.

Return a Markdown table with these columns:
| Priority | Missing or unclear evidence | Why it is needed for the briefing | Likely record owner or source | Question to resolve | Effect if unavailable |

Set **Priority** to `High`, `Medium`, or `Low` based only on whether the gap prevents confirmation of the timeline, immediate actions, scope, or governance decision. If the likely owner is not stated, write `Not stated`.

Then add:
## Evidence already available
List each material source supplied and what it supports.

## Statements to remove or qualify
Quote no more than 12 words from any statement that cannot be supported. For each one, provide a safe replacement using `Reported`, `Unconfirmed`, or `Not stated`.

## Meeting-ready evidence request
Write a short numbered list of the five most important evidence requests, in order.

Administrative or operational incident record:
[paste a fully de-identified incident record here]

Quality-check the de-identified document titled **Draft incident briefing note** against the de-identified document titled **Administrative or operational incident record** below. This is an administrative and operational review, not clinical advice. Do not make findings of fault, legal conclusions, or clinical assessments.

First check both documents for identifiable patient information or staff personal information. If any appears, stop and return only: "Remove or replace identifiable information before processing this record." Do not repeat it.

Check whether every factual statement in the draft is supported by the incident record. Check dates, times, roles, action status, attribution, certainty, missing evidence, and meeting questions. Do not treat plausible wording as supported wording.

Return these sections in Markdown:
## Check result
State `Ready for owner review`, `Needs factual correction`, or `Insufficient source record`.

## Unsupported or overstated statements
Use a table with columns `Draft statement or section`, `Problem`, `Source evidence`, `Required change`.

## Omissions
List material events, immediate actions, evidence gaps or limitations present in the source record but absent from the draft.

## Neutrality and clarity checks
List wording that implies blame, certainty, causation, clinical judgement, or a conclusion not supported by the record. Provide a factual replacement for each.

## Final owner checklist
Provide a numbered checklist of no more than seven checks for the governance officer or operational manager. Include confirmation that the note contains no identifiable information and that source documents have been checked.

Draft incident briefing note:
[paste the fully de-identified draft briefing note here]

Administrative or operational incident record:
[paste the fully de-identified source record here]