Pathfinders for Hope · Operation Iron Gate North Bay Pilot

How Should HMIS and Referral Follow-Up Work Together?

HMIS referral follow-up should fit the local Continuum of Care’s data rules and the tools its partners actually use. First check which referral and follow-up functions already exist. Then resolve any communication gaps without creating conflicting records or unnecessary copies of personal information.

Start with the local HMIS and define the handoff boundary

HMIS capabilities and workflows depend on the local implementation. For example, Nashville’s Office of Homeless Services describes referrals and priority lists within its HMIS. That is one community’s implementation, not a specification for Vallejo. It is inaccurate to assume that HMIS can never track referrals or that every community uses it in the same way. Read Nashville’s HMIS overview.

Ask the HMIS lead and participating organizations to demonstrate a fictional referral from creation through follow-up. Identify what is already visible, who can update it, which partners are outside the workflow, and where a phone call or other authorized communication is still required.

Map three different questions

What must be recorded? Follow the applicable HMIS standards, reporting requirements, and local procedures.
What action needs an owner? Decide who checks receipt, handles a clarification, or follows up on the next appointment.
What may each partner see? Apply the approved access and information-sharing rules. Participation in a partnership does not itself authorize access to every record.

A useful workflow answers all three without treating them as interchangeable. A saved record may satisfy one documentation step while the receiving partner still needs to respond.

Decide where each fact belongs

Use a locally approved source-of-truth map. For each operational status, identify the authoritative system, the staff role permitted to update it, and the correction process. If a status is also displayed elsewhere, define how it stays synchronized. Do not introduce a second spreadsheet or platform merely because it appears easier to edit.

Suggested questions include: Does “accepted” mean eligibility confirmed or only assessment agreed? Who can change an incorrect status? How are duplicates recognized within permitted access? Which record is used when two systems disagree? These are implementation questions for the local teams, not new HUD data elements.

Check exceptions before connecting systems

Review role-based access, audit history, retention, permissions, and the partner’s ability to stop an inappropriate disclosure. Have qualified staff assess requirements for victim-service providers and other sensitive contexts before proposing a shared workflow. Do not assume a common partner agreement makes every data exchange permissible.

Use fictional test records to exercise a wrong destination, withdrawn permission, unavailable capacity, an incorrect update, and a partner leaving the workflow. Confirm how staff correct or restrict information in each situation before using real records.

Example: one status, two meanings

Hypothetical example: a local workflow uses “referred” for a record sent to a program. A partner interprets that label as an appointment accepted. The teams retain the required local field and agree on a separate, approved operational acknowledgment instead of changing the meaning of the reporting field. They document who can supply that acknowledgment and where it belongs.

Seven HMIS referral follow-up questions to resolve locally

Effective HMIS referral follow-up begins with a shared definition of the handoff. The sending and receiving teams should agree on what they need to know, which system holds each fact, and who is authorized to update it. The following questions help teams identify communication gaps without creating a second source of truth.

1. What event starts follow-up?

Define whether HMIS referral follow-up begins when a referral is created, transmitted, viewed, or acknowledged. If teams use different starting events, response-time reports will not be comparable.

2. Who owns the next action?

Name the role responsible for checking receipt, answering a clarification, contacting the person, or recording an unavailable service. A status without a responsible role can leave a referral visible but still unattended.

3. What does each status mean?

Document the difference between sent, received, accepted for assessment, appointment scheduled, service started, and closed. HMIS referral follow-up should not use one label for several different events.

4. Which record is authoritative?

Identify where the official referral status, service record, and correction history belong. If another approved tool displays a limited operational acknowledgment, define how staff resolve disagreement and avoid copying unnecessary personal information.

5. What information may be shared?

Confirm authorization, role-based access, minimum necessary information, and any special restrictions before exchanging data. The AHRQ care-coordination resource provides healthcare referral background, but local privacy and organizational requirements still control implementation.

6. How are barriers recorded?

HMIS referral follow-up should distinguish an unanswered request, unavailable capacity, missing information, a declined option, a changed destination, and an outcome that cannot be verified. Those states are not interchangeable.

7. When does follow-up end?

Set a defined completion rule. Depending on the locally approved workflow, completion may require an authorized acknowledgment, a confirmed next appointment, a documented barrier, or another agreed event. Closing a task because it was sent does not establish what happened next.

Before using real records, test the HMIS referral follow-up process with fictional examples. Include a wrong destination, corrected status, withdrawn authorization, unavailable service, and a receiving organization that leaves the workflow. Record who responds, where the correction appears, and how staff know which next action remains open.

Standards and pilot scope

Obtain the current HUD HMIS data standards through the local HMIS lead. For broader official program background, consult HUD’s Continuum of Care program information. This planning guide does not amend those standards or establish an integration, certification, or data-sharing agreement.

Pathfinders for Hope’s Operation Iron Gate and HMIS overview explains the intended pilot relationship. For practical status distinctions, read how to confirm referral receipt; for sensitive referrals, read safe, consent-based referral planning.

Frequently asked question

How should HMIS referral follow-up boundaries be defined?

The local HMIS remains governed by its lead agency, applicable standards, approved access rules, and participating organizations. Any additional follow-up process must have a defined boundary and may not create conflicting records or unauthorized access.

For how the two layers differ, see referral accountability versus referral tracking and what Operation Iron Gate is.

Operation Iron Gate North Bay Pilot

Pathfinders for Hope is developing the pilot with organizational partners. Public intake is not open, and no service or placement is guaranteed. GATEHOUSE, our community platform and a smaller version of Operation Iron Gate, is open now: register on GATEHOUSE. Discuss the pilot with Pathfinders for Hope or browse the resource hub.

Prepared by Pathfinders for Hope. Updated September 5, 2026. Resource scope and sources.