FQHC Referral Coordination: Keep One Shared Record of the Handoff

The practical starting point is one handoff that staff repeatedly have to reconstruct. A specialist may ask for an existing document, a patient may need help reaching the scheduling office, or a return message may arrive at a different health center site. The record should show what happened and who is acting next.

Describe the handoff before choosing tools

Write down where a referral begins, where the outside response arrives and how staff know a task has changed hands. Include the work that happens outside the main screen: a returned fax, a message to another site or a call whose outcome someone later needs to enter.

This is a practical application of the responsibility and communication activities described in AHRQ's care coordination resources. A shared view is useful only if it helps people locate the information and responsibility needed for the next step.

For a health center, separate the shared operating rules from local partner details. The organization may use one status dictionary while individual sites maintain different contact routes or office instructions. Record the source of those instructions and the last confirmation date. A central directory without provenance can simply spread an old assumption more widely.

The broader FQHC and community health center overview describes the setting. This guide focuses on keeping the referral handoff understandable across people and locations.

Give every open referral a visible owner

Name the owner of the referral and the owner of its next task. They may be the same person, but they do not have to be. A records team might supply an existing document while a coordinator remains responsible for confirming that the outside office received it.

Define how ownership transfers during leave, reassignment or cross-site coverage. A shared queue is not a substitute for an accepted assignment. The receiving team should be able to identify what it has taken on and what remains with the sending team.

Keep clinical questions separate from administrative follow-up. The operating record can show that a clarification is needed and route it to an appropriate clinician. It should not turn an administrative status into a clinical routing rule.

Prior authorization also needs its own record and accountable steps when relevant. A referral acknowledgment does not answer an authorization question. The FQHC prior authorization guide covers that adjacent workflow.

Build a shared record that supports coverage

The following fields form a suggested operating template. They are not a regulatory reporting specification.

Use the health center's authorized systems and access rules for patient information. A training worksheet can use synthetic identifiers and contain no patient details.

Here is a hypothetical example. Site A sends referral R-208. The receiving office asks for an attachment. Site B covers the queue while the original coordinator is away. The shared record shows the response reference, the missing item and the records team assigned to locate it. Site B can continue the same request and record the new transmission without creating a duplicate referral merely to obtain ownership.

If that example resembles a recurring coordination problem, book a demo to map the shared record your sites need. Bring the handoff fields and local status meanings rather than patient-identifiable examples.

Keep local access information separate from assumptions

Record what an outside office has confirmed and the context in which it was confirmed. A response about one location or plan should not automatically become a rule for every location or plan. When instructions conflict, retain the source messages and assign someone to clarify them.

Give partner-information updates an owner. Staff should know where to report a failed contact route or a changed packet instruction. The update should reach the shared record, not remain in one coordinator's inbox.

The same discipline applies to patient communication preferences and requests for help. Preserve information in the approved workflow and route requests to the appropriate team. Do not infer a person's preference or support need from a demographic label.

For later stages, closed-loop referral management addresses how information returns after the referral moves forward. Sending the request is only one event in that record.

Aunt Martha's coordination across a multi-site network

Linear Health's Aunt Martha's Health & Wellness case study provides one customer example. Community health organization in the Chicago area, more than 100 providers across more than 20 locations, on athenahealth. Referral coordination, care gap closure and voice AI running across the network.

Before go-live, outbound referrals from primary care to external specialists were handled by hand: faxing packets, calling to confirm receipt, chasing consult notes and tracking status. Managed care payer files were also worked by hand. After go-live, outbound referrals are processed automatically and coordinators oversee the automated workflow and handle the exceptions. The case study records the workflow change in these terms:

These are customer-reported results. They do not establish that another health center will achieve the same change or that one workflow element caused the result. The useful question is which activities and responsibilities your own team needs to make visible.

Choose one bounded change and inspect it

Start with a defined set of referrals and one administrative handoff, such as returned packets awaiting an existing attachment. Document the current record, owner and unresolved count. Then test whether the proposed process preserves the source response and assigns the next task clearly.

Review both successfully transferred work and exceptions. Can a covering coordinator find the latest instruction? Can the team distinguish a task completed internally from confirmation by the outside office? Does a reassignment leave a clear trail?

Keep operational referral measures separate from quality reporting. If a referral supports a quality program, the quality team must apply that program's definitions and evidence requirements. HRSA's UDS reporting guidance is the reporting reference; a local referral-status label is not a replacement for it. The related FQHC care-gap workflow has a different task from this operating record.

Where Linear Health fits

Referral coordination software should be evaluated against the handoffs the health center actually uses. Ask to see how an outside response, a staff assignment and the next confirmation stay connected. Keep product-specific integration and workflow requirements explicit in that evaluation.

Book a demo to walk through one cross-site referral handoff. A concrete record and a known exception make the discussion more useful than an assumed staffing or savings target.

Frequently asked questions

Sources

Sources accessed October 15, 2026. The AHRQ and HRSA pages describe their own guidance; the case study records customer-reported results.

• AHRQ: Care Coordination.
• HRSA: UDS Reporting Guidance.
• Linear Health: Aunt Martha's Health & Wellness case study, customer context and workflow changes.