For homeless services organizations and hospital partners
Hospital referrals deserve a confirmed handoff.
Sent
An authorized discharge or community referral is initiated.
Received
The next organization acknowledges it. That does not complete the handoff.
Arrived
Arrival with the named community partner is confirmed.
Homeless services can break after a hospital discharge is complete. An authorized referral may be sent to a community organization, yet no one can see whether it was received, accepted, or acted on. Operation Iron Gate, powered by Ninety-Nine Systems, Inc., is a proposed confirmed-handoff referral system that Pathfinders for Hope is preparing to test through the Vallejo Pilot. It is designed to make the hospital-to-community handoff visible without replacing a hospital’s EHR, a community organization’s HMIS, or either partner’s responsibility for service.
The pilot has not launched. Recruiting for it has.
The failure point
A referral is marked complete the moment it is sent — never when the person actually arrives.
The record ends here
100
Referrals sent
Every one of them arrived.
100
Referrals sent
Not one of them arrived.
Identical in every report
Logged
The send
A discharge planner sends the referral and closes the task. On their screen the work is finished. The person is still standing in the lobby holding a piece of paper.
No record
The silence
If they never walk through the next door, nothing comes back. No alert, no flag, no follow-up — because no field exists anywhere to hold the answer.
No record
The cost
The same person surfaces weeks later, further behind than before. Nobody can point to where the handoff broke, so nobody can fix it.
Referral accountability for homeless services
How a closed loop referral can keep a hospital handoff from ending in silence.
20
designed case statuses in one state machine
A system requirement keeps every case in a defined status so an unresolved handoff stays visible.
12
planned barrier codes
The pilot design records the reason a person is stuck in a consistent, countable form.
2 hrs
target for routing an intake without ID to a resource
This is a pilot workflow target, not a published outcome. Identity recovery becomes the next action instead of a reason to abandon the referral.
90 days
planned follow-up point for verifying a handoff
The pilot design checks whether the connection held, not only whether the referral was sent.
7 yrs
planned minimum record-retention rule
The software design preserves corrections as new entries instead of erasing the original record.
2
required reviewers plus one documented basis for a denial
This is a system design rule intended to prevent a single unsupported decision from ending the handoff.
For homeless services organizations and hospital partners
What accountable homeless-services referrals require
A clear record of whether the referral reached homeless services.
The proposed model separates a referral that was sent from one that was received, accepted, and confirmed at arrival. That distinction gives homeless-services organizations and their hospital partners a shared way to review where an authorized transition paused.
A reviewable record for every partner.
Hospital and community teams can retain their own systems and workflows. The proposed layer focuses on the external handoff status, named next action, and documented reason when a referral cannot move forward.
A way to keep uncertainty from becoming abandonment.
A missed call, a full program, a changed phone number, or an intake barrier should not look like a completed referral. The proposed workflow keeps the handoff open until a defined state is documented.
Boundaries that respect each organization’s role.
Operation Iron Gate is not an EHR, HMIS, clinical tool, discharge department, or replacement for Coordinated Entry. Any future pilot partner keeps control of its own policies, records, consent process, and service decisions.
The proposed workflow
What a hospital-to-homeless-services pilot would test
A proposed Vallejo pilot would test whether hospital and homeless-services partners can build a verifiable referral record — without replacing hospital systems, HMIS, or Coordinated Entry.
Every partner keeps its own privacy, consent, EHR, HMIS and reporting obligations. The model covers one authorized cross-organization handoff, and uses only the information a participating workflow permits.
01
Sent
The initiating team records that it sent an authorized referral. A discharge planner, with the person’s authorization, hands off to a community provider.
Handoff record
02
Received
The receiving organization records when it can actually view the referral. Nothing about the person has happened yet.
Handoff record
03
Accepted
That organization decides whether it can take the referral. It still makes its own service decision, on its own criteria.
Handoff record
04
Arrived
The person arrives for the named next step. This is the one state the whole record exists to confirm — and the one nothing else captures today.
Handoff record
05
Served
What the receiving organization actually provided. Tracked on its own terms, not inferred from arrival.
Separate state
06
Outcome verified
Confirmed afterwards, on its own evidence. Never assumed because a service was delivered.
Separate state
Six states. Not interchangeable.
The only three exits
When a referral cannot move forward
A program is full. A person chooses another path. An intake requires a different eligibility step. These are real outcomes, and each one has a name. A referral that is received but cannot proceed stays reviewable — the record stays open until the team documents one of three things.
A denial reason
Why it cannot proceed, in a fixed code that can be counted across every partner.
A named next action
What happens instead, and which organization owns it.
Another defined state
The referral moves somewhere else in the machine — never to nothing.
Silence is never recorded as success.
What this model is not
- Not a promise of service. A referral begins an authorized handoff, nothing more.
- Not a guarantee of housing, clinical care, benefits, or eligibility.
- Not a replacement for a hospital EHR, an HMIS, or Coordinated Entry.
- Not a shared database. No partner is asked to pool its records.
- Not surveillance. Review is practical accountability between organizations, and partners decide what may be used and who may see it.
- Not live. This is a proposed model — not a claim that a hospital partner is already using it.
Where the record stops
One door out. No record of the next one.
A discharge area is the last place a sending organization can see a person. Everything the six states describe happens after this doorway — which is exactly why none of it is captured today.
Record state at this doorway
The one question
Every state, every code and every rule in this model exists to answer one thing.
Did the person arrive?
Precisely: after an authorized referral leaves one organization, did the person reach the next agreed step — and if not, why?
did the person arrive
0 results
The record ends at sent. Nothing after it was ever written, so there is nothing to return — not an arrival, not a refusal, not a reason.
That is the only thing this pilot proposes to change.
Hospital care coordination covers clinical decisions, patient preferences, and many responsibilities that belong to care teams. This model addresses that one narrow question — and nothing else.
Built to sit beside existing systems
It does not replace a hospital EHR, HMIS, or discharge process.
The proposed model is limited to the handoff status that can disappear between organizations.
The sending organization
Hospital EHR
The clinical record, discharge planning, and every care decision that belongs to the care team.
Unchanged · stays yours
The authorized handoff
The only thing Operation Iron Gate records — and the only place a person is currently lost.
The receiving organization
HMIS & Coordinated Entry
The system of record, intake rules, eligibility, and the decision about whether to accept a referral.
Unchanged · stays yours
Hospitals and community organizations maintain their own systems, workflows, privacy obligations, and reporting rules. Operation Iron Gate is proposed as a narrow coordination and evidence layer for the external referral handoff. It does not claim to be an EHR, HMIS, clinical record, or substitute for discharge planning.
The Agency for Healthcare Research and Quality identifies transitions of care, accountability, follow-up, and links to community resources as care-coordination activities. This proposed model applies those ideas to an authorized hospital-to-community referral while leaving service and clinical decisions with the organizations responsible for them. Read AHRQ’s care coordination overview.
Who joins
Built for the people who own homeless-services handoffs
Sends
Starts an authorized referral and records that it left — then finds out whether the person arrived, which is the part that does not exist today.
- Hospital discharge teams
- Emergency departments
Receives
Confirms the referral was seen, accepts or declines on its own criteria, and names a reason instead of letting it go quiet.
- Homeless-service providers
- Behavioral health partners
Reviews
Sees where handoffs hold and where they break across every partner — counted the same way, in the same codes.
- Continuum of Care leads
- City and county human-services teams
A proposed pilot conversation
What a hospital-to-community pilot would involve
-
Map the handoff
Identify one authorized referral route from discharge planning to a community organization, and define what each status means before anything is built.
What you walk away with
- One named referral route, end to end
- A plain-language rule for each of the six statuses
- Agreement on what counts as an arrival
- The barrier codes that apply to your intake
-
Write the boundaries
Both organizations set the limits in writing — who does what, what may be shared, and which systems stay the system of record.
What you walk away with
- Roles, named on both sides
- The consent practice you already use
- Data boundaries — what is shared, what never is
- An escalation path when a handoff stalls
- Your systems of record, confirmed unchanged
-
Decide together
Participation is voluntary. Nothing is deployed, and no partnership is claimed, until an organization agrees to a clearly bounded pilot.
Either outcome is a real outcome
- A bounded pilot scope both sides signed
- Or a no — with the map and boundaries still yours to keep
Straight answers
Common questions
Clear answers for homeless-services organizations and hospital partners considering this proposed referral-accountability model.
The honest tally
05
answers are no
01
answer is yes
Not used by a hospital yet. Not an EHR or a discharge process. Not a government program. No published field results. No transfer of responsibility. The one yes: it is free to talk about.
Five of these six answers are no. That is deliberate.
Is Operation Iron Gate already used by a hospital system?
No. There is no hospital deployment or hospital partnership to claim. The Vallejo pilot is being prepared to test the model with organizations that choose to participate.
Does this replace a hospital EHR or discharge process?
No. Operation Iron Gate is not an EHR, HMIS, clinical record, or discharge department. A future participant retains its own system of record, policies, consent process, and service decisions.
Is participation free?
Yes. There is no fee to discuss or consider participation in the Vallejo pilot.
Is this a government program?
No. Pathfinders for Hope is a nonprofit organization. Operation Iron Gate is powered by Ninety-Nine Systems, Inc. The pilot is not a government program and does not claim government endorsement.
Are there published field results?
No. The pilot has not launched, so there are no field results to report. Any future measurements must be identified as pilot measurements, not as established outcomes.
Does a referral transfer responsibility?
No. Each organization remains responsible for its own services and relationship with the person served. The proposed model records the status of a handoff. It does not transfer clinical, service, housing, benefits, or case-management responsibility.
Next step
Bring your whole organization in.
If your organization sends or receives referrals in Vallejo, the pilot is open to talk to you now — before anything is built around you.