Pathfinders for Hope · Operation Iron Gate Vallejo 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, coordinated-entry, 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, not a replacement claim

HMIS capabilities and workflows depend on the local implementation. For example, Nashville's Office of Homeless Services describes coordinated-entry 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.

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

Does Operation Iron Gate replace HMIS?

No. The Vallejo Pilot is being developed around authorized referral handoffs. Any participating organization's HMIS, reporting, privacy, and service responsibilities remain in place; no integration is established by this guide.

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

Operation Iron Gate Vallejo Pilot

Pathfinders for Hope is developing the pilot with organizational partners. Public intake is not open, and no service or placement is guaranteed. 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.

Join the Vallejo Pilot

Tell us how your organization can participate. Pathfinders for Hope will review your application and contact you using the information you provide.

Enter your organization’s full name.
Optional.
Select the option that best describes your organization.
Where does your organization primarily serve?
Briefly describe the services, programs, or resources your organization can offer.
How would you like to participate?
Select every role that applies.
Your Name
The primary person we should contact.
Your role within the organization.
We will use this email to respond to your request.
Optional.
Tell us what you want to strengthen, solve, or contribute.