Improve Referral Packet Quality With a Referring-Office Feedback Loop

This program focuses on communication between the sending and receiving offices. A missing-item log can identify a question for that conversation, but it does not establish which office caused the problem. The requirement may be unclear, an attachment may have arrived separately, or the receiving team may have overlooked an available field.

Why a source-office program is different

The method below is editorial guidance, not a measured result. It is designed to sit alongside, not replace, the acceptance workflow described in our article on specialist referral acceptance rates and the intake process described in referral intake automation.

The AHRQ Workflow Assessment for Health IT Toolkit frames health IT as something that affects both clinical and administrative workflow, and notes that once implemented, health IT can provide information to help reorganize and improve workflow (AHRQ). Use that general workflow perspective to examine what the intake record captures. Verify its review coverage and omissions before using it to characterize a referring office. The detailed scorecard below is an original editorial application, not an AHRQ method.

Step 1: Use the receiving practice's approved administrative requirements

Use the receiving practice's approved administrative list for the referral type being reviewed. Record its version, effective date and owner. Staff check the presence of an applicable item; they do not independently add requirements or decide whether its content is clinically sufficient.

Possible fields for discussion include the approved patient reference, referring-office contact, stated referral request and an applicable administrative attachment. These are examples, not a universal minimum packet. Keep an item marked not applicable when the approved list says it is unnecessary. If applicability is uncertain, route the question to the list owner rather than counting it as a source-office omission.

Requirements for clinical records, coverage, authorization or medical necessity belong with the designated professionals. The feedback program can record an approved request and its administrative status, but it does not create a reason to refuse or delay care.

Check how referring offices received the current instructions. If the receiving practice changed an attachment requirement during the sample period, record the change. Do not judge older packets against a later list without explaining the difference.

Step 2: Record the missing item and the work required to resolve it

Keep three questions separate: was the applicable item available at initial receipt, was it found during the first review, and what work followed? An item discovered later inside the original packet is a receiving-side retrieval finding, not proof that the sender omitted it.

These fields can overlap without conflicting: an item may require several contacts and eventually come from the patient. Avoid a single category that mixes contact count with source. Report unknown effort as unknown rather than estimating it from the number of missing fields.

Step 3: Build a fair source-office scorecard with a defined denominator

Define what counts as one initial packet, how resends and later pages are linked, which referral types are eligible and what period is observed. Report both received units and reviewed units. If only a sample is reviewed, first-receipt completeness describes that reviewed sample, not every referral the office sent.

For a simple sample measure, divide reviewed packets with every applicable administrative item present at initial receipt by all eligible reviewed packets whose initial completeness could be determined. Report excluded or unresolved classifications separately. Preserve the rule across comparisons; disclose changes in referral mix, requirements and review coverage.

Linear Health's Operational AI Evaluation Kit asks for raw counts, denominators and exclusions and separates activity from outcomes. Applying that discipline to this scorecard is editorial guidance.

Synthetic example

The following invented cohort assumes all eligible initial packets were reviewed under the same list version, with no unresolved completeness classifications.

These are illustrative counts, not benchmarks or customer data. Each office's leading item may overlap with other omissions in the same packet. The table does not establish rework time, relative clinical importance or who caused a gap. Review the underlying classifications and referral mix with the office before choosing a change. A small sample can still support a specific correction conversation even when it cannot support a reliable ranking.

Step 4: Send specific feedback and agree an improvement test

Feedback should be short, factual, and framed as a shared workflow fix. A template:

Subject: Referral packet check for [Office name], [window]

We reviewed [N] referral packets your office sent between [dates]. [X] were complete on first receipt. The item most often missing was [item], absent in [count] packets. Resolving those took [count] follow-up contacts from our team.

Proposed change to test: [one concrete step, e.g. attach the insurance card image to the referral order before sending].

We will review the next [N] packets after [date] and share the result. Our contact for questions is [name, phone].

Agree a focused change where practical, and record other changes occurring during the observation period. Fewer simultaneous changes can make interpretation easier, but a before-and-after sample does not by itself prove what caused a difference. Agree the next sample rule and observation cutoff before reviewing the result. Use aggregate feedback through the approved communication route; any case-level examples must follow the authorized access and sharing process.

If you are building this loop on top of an intake platform, the practical question is whether the system can capture the missing-item and resolution-category fields at the point of intake rather than in a separate spreadsheet. You can book a demo to ask Linear Health to demonstrate whether the proposed workflow captures those fields, with the understanding that field-level behavior in your environment needs to be demonstrated, not assumed.

Step 5: Review the next sample without confusing packet quality with clinical acceptance

When the follow-up sample is in, compare only the measures you defined: first-receipt completeness, the top missing item, and resolution effort. Do not fold in whether referrals were clinically accepted, scheduled, or completed. Those outcomes depend on factors outside the referring office's packet, and mixing them in both distorts the scorecard and drifts the program toward clinical judgment it was never meant to carry.

Report the observed counts even when they do not improve. Check whether the list version, referral mix, review coverage, observation time or other workflow changes differ before drawing a conclusion. If the offices agree the revised instruction is useful, record its approval and effective date. Equal window lengths alone do not make two samples comparable.

A practical evaluation method for tooling

If you are evaluating software to run this program, the Linear Health Operational AI Evaluation Kit offers a 0 to 3 evidence scale (not addressed, claimed, demonstrated, verified) and recommends running one real workflow with normal complexity, missing data, and at least one exception rather than a scripted happy path (Linear Health). Applied to this program, ask any vendor to show:

1. One approved synthetic incomplete packet traced from receipt to resolution, including an item already present but missed on the first review.
2. Where those fields are stored and whether they can be exported per referring office with a denominator.
3. What a person must still do when the item is unresolved at sample close.
4. The exact fields read from or written to your EHR, shown rather than described. Linear Health's established integrations are athenahealth, eClinicalWorks, NextGen and Greenway Health; field-level write actions for your configuration need demonstration (Linear Health referral coordination).

The kit treats unresolved privacy, security and accountability issues as gates for the responsible reviewer. Use the evaluation kit to record demonstrated evidence and open questions. For a focused demo, bring a synthetic packet and ask to inspect the original receipt, missing-item classification, correction history and per-office export.

Frequently asked questions

Sources

Sources accessed November 4, 2026.

• AHRQ, Workflow Assessment for Health IT Toolkit.
• Linear Health, Operational AI Evaluation Kit.