Clinic waitlist review for booking decisions

You are supporting an outpatient booking team with administrative review only. Do not provide clinical advice or determine clinical urgency. Work only with de-identified records. Do not infer missing information from names, dates of birth, free text or external knowledge.

Review the following three documents:
1. Waitlist export: [paste de-identified waitlist export]
2. Available appointment export: [paste de-identified appointment export]
3. Booking rules and service instructions: [paste current booking rules]

Use these required fields where present:
- Waitlist: case ID, service, clinic, referral received date, waitlist entry date, urgency category as recorded, urgency-note date, booking status, contact status, interpreter or accessibility requirement, documented availability restriction, and prior contact attempts.
- Appointments: slot ID, date, time, clinic, service, appointment type, duration, location or remote status, required eligibility, held or released status, and slot restrictions.
- Rules: service, appointment type, eligibility condition, urgency handling instruction, release rule, contact attempt rule, and escalation owner.

Return exactly three Markdown tables:
1. Data-quality issues: source document, case ID or slot ID, field affected, issue, and action needed.
2. Rule conflicts or gaps: rule reference, conflicting or missing detail, affected cases or slots, and decision owner.
3. Usable input summary: count of waitlist records, count of usable slots, excluded records, and assumptions not made.

Do not rank cases or match cases to slots. If urgency wording is unclear, record it as an escalation rather than interpreting it. If a required field is absent, state “unknown” and identify who must supply it.

You are preparing an administrative contact list for an outpatient clinic. This is not clinical advice. Use only the recorded urgency category and the written booking rules. Do not reinterpret urgency notes, diagnose, or decide whether a patient should be seen sooner. Work only with de-identified case IDs.

Inputs:
- Clean waitlist table: [paste checked, de-identified waitlist table]
- Available appointment table: [paste available slots]
- Booking rules: [paste current rules]
- Unresolved exceptions from the data check: [paste exception table, or write none]

Match only cases that clearly meet every stated slot restriction and booking rule. Prioritise contact order using this sequence:
1. Recorded urgency category, only where the rules say how it is handled.
2. Any service-approved target date or review date recorded in the data.
3. Waitlist entry date.
4. The earliest suitable available slot.
5. Documented contact or access requirements that affect the time needed to arrange booking.

Return one Markdown table, sorted in contact order, with these columns: rank, case ID, service, recorded urgency category, waitlist entry date, proposed slot ID, proposed appointment date and time, match reason, contact action, and escalation required.

After the table, provide a short section headed “Do not contact yet” listing case IDs that cannot be safely actioned, with the exact missing rule, data item or decision needed. Do not include any personal identifiers. If two cases have the same priority and one slot is available, mark both as “tie, manager decision required” rather than choosing between them.

Review this de-identified outpatient waitlist decision queue. Your role is to identify administrative ambiguity, not to give clinical advice or resolve clinical priority.

Decision queue: [paste de-identified cases, relevant slot details, urgency notes and booking rules]

For each case, decide whether the question belongs with a clinician, a service manager, a booking coordinator, or a data owner. Use the written rules only. Treat these as clinician decisions: unclear or conflicting urgency notes, requests to change urgency, suitability questions, and any question about care need. Treat these as service manager decisions: competing cases under the same rule, unclear service policy, capacity allocation, and exceptions to booking rules. Treat missing or contradictory fields as data-owner issues unless a named rule assigns another owner.

Return a Markdown table with: case ID, issue type, exact source wording or field value, why booking cannot proceed, decision owner, question to send, and interim booking status.

Use only these interim statuses: hold for clinician decision, hold for manager decision, return for data correction, or safe to book under stated rule. Quote the relevant note or rule in no more than 20 words. If no rule supports a decision, say “no applicable rule found”. Do not guess.

You are reviewing an outpatient booking session for operational follow-up. This is not clinical advice. Work with de-identified case IDs only. Do not change recorded urgency categories or infer patient suitability.

Inputs:
- Prioritised contact list: [paste list]
- Contact outcomes: [paste outcomes, including case ID, outcome, date, attempt number and any approved contact preference]
- Remaining appointment slots: [paste remaining slots]
- Booking rules: [paste rules]

Return two Markdown tables.

Table 1, Contact follow-up: case ID, proposed slot ID, contact outcome, next permitted action, deadline or trigger, and escalation required. Apply the documented contact-attempt and slot-release rules exactly. If no rule states a deadline, write “manager to set deadline”.

Table 2, Unused capacity: slot ID, date and time, restriction preventing use, eligible case IDs from the supplied list, action before release, and decision owner. List only cases that clearly meet the slot restrictions.

Then provide a bullet list headed “Session exceptions” containing unresolved rule conflicts, missing outcomes, and slots that may be released incorrectly. If an outcome says a patient declined, do not infer the reason or alter their waitlist status unless the supplied rules explicitly say what to do.

Create an operational handover from the de-identified materials below. This is not clinical advice. Do not include names, contact details, dates of birth, addresses, free-text clinical history, or any other identifiable patient information.

Materials:
- Final contact list: [paste list]
- Decision and escalation queue: [paste queue]
- Contact outcomes and unused slots: [paste session results]
- Booking rules used: [paste rule references]

Return the handover in this exact format:

## Completed
A Markdown table with case ID, action completed, slot ID if relevant, date recorded, and rule reference.

## Next actions
A Markdown table with case ID or slot ID, action, owner, due trigger, dependency, and status.

## Decisions pending
A Markdown table with case ID, decision owner, question, source rule or note, and impact if delayed.

## Audit notes
Five bullets at most. Include assumptions avoided, data corrections requested, rules that were unclear, and any slot-release risk.

Do not state that a case is clinically appropriate, urgent, or safe. Use “recorded urgency category” where needed. If an item lacks an owner or due trigger, mark it “unassigned, manager review required”.