Define the administrative checklist
Ask the clinic team which details they need to locate and process a referral, such as the intended service, sender details and a readable attachment. Use the approved requirements for that service rather than a generic checklist copied from another clinic. Mark missing fields explicitly. Do not infer clinical facts or fill gaps with a plausible answer. A document containing all required administrative fields may still need review by an authorised staff member before the clinic decides what happens next.
Keep receipt separate from acceptance
Define distinct states such as received, awaiting administrative information, ready for staff review and reviewed. Use patient-facing wording that matches the actual state. A receipt acknowledgement should not imply that the clinic has accepted the referral or confirmed an appointment. In a fictional example, an uploaded attachment may be readable and correctly labelled but still await staff review. The system can acknowledge receipt while making that remaining step clear. Avoid an automatic success message that promises a booking merely because an upload completed.
Preserve the source and record corrections
Keep the original document associated with the intake record through the clinic-approved system. If extracted details are corrected, distinguish the source text from the staff correction and record who made it. Similar names or repeated uploads should not automatically be merged without an approved matching process. A second document may amend the first rather than duplicate it. Give reviewers enough context to establish that relationship. Do not send full attachments into general-purpose alerts when a controlled link to the authorised record will do.
Assign missing-information follow-up
Give each incomplete item a named team or queue owner, the specific missing detail and the next permitted action. Decide whether staff contact the sender, the patient or another approved party. Automation should follow that instruction rather than choosing a recipient from a guessed address. Keep attempted follow-up separate from information actually received. If a response arrives through another channel, link it to the original task using the clinic process so two staff members do not chase the same missing attachment independently.
Route review without making clinical decisions
Send the administratively prepared item to the approved staff destination. Do not translate document wording into an urgency category or determine suitability unless a separately governed clinical process explicitly handles that decision. This guide concerns administration only. If an unexpected request falls outside the intake rules, hand it to staff with the original context. Make it clear what automation checked and what it did not assess. That boundary helps the receiving person understand the remaining work without assuming an earlier system has already completed it.
Test the complete handover
Use fictional test documents for a complete submission, missing attachment, unreadable file, amended referral and ambiguous record match. Inspect the staff queue as well as the acknowledgement. Confirm that the item has an owner and that its status does not overstate acceptance. Test a failed notification separately from a saved intake record. Review outstanding cases by age and state after launch, while keeping clinical decisions with authorised staff. A clear queue and truthful acknowledgement are more useful than a high processed count that hides unresolved work.