Ryan White Client Eligibility Determination SOP

It covers the full eligibility review workflow for a Ryan White client, from intake request through approval or escalation. The steps focus on verifying documented HIV status, household income, service-area residency, and payer-of-last-resort status. It also includes the documentation needed to support the final determination. Use it as the standard process for initial enrollment and recertification.

It can be used for both, but you should tailor the verification cadence to your program rules. Initial eligibility usually requires a full document review, while recertification often rechecks income, residency, and any changed payer information. If your program has shorter renewal intervals or interim change reporting, add those triggers to the SOP. The template is structured so you can adapt it without changing the core control points.

A trained eligibility specialist, case manager, or other designated role should complete the review, with escalation to a supervisor or compliance lead when documents are missing or the case is borderline. The key is that the reviewer is a competent person who understands program rules and documentation standards. If your organization separates intake from final approval, define both roles in the SOP. That reduces inconsistent decisions and rework.

It creates documented information that supports consistent eligibility decisions, which aligns with ISO 9001-style record control practices and internal audit readiness. It also helps staff apply payer-of-last-resort logic and maintain clear evidence for each determination. If your program touches clinical or hazardous workflows elsewhere, keep this SOP separate from operational procedures so the eligibility record stays clean. The template is designed to make the decision traceable, not just verbal.

Common failures include accepting expired proof of income, skipping residency verification, or approving a case without clear HIV documentation. Another frequent issue is failing to document why a case was escalated or denied, which makes later review difficult. The SOP also helps prevent inconsistent application of threshold rules across staff. Using the same steps each time reduces non-conformance in the eligibility file.

Yes. You should customize the income threshold, acceptable proof documents, residency definitions, and any local payer-of-last-resort requirements to match your funding source and service area. You can also add branch logic for minors, household composition, or temporary housing situations if your program needs it. Keep the core sequence intact so staff still review the same control points in the same order.

It can be adapted to fit your workflow in an EHR, case management platform, or shared document repository. Add fields for verification outcome, reviewer name, date, and required attachments so the SOP matches the system of record. If your team uses checklists or task queues, map each step to a status change or task owner. The template works best when the written process and the software workflow mirror each other.

An ad-hoc review depends on memory and individual judgment, which leads to uneven decisions and missing documentation. This SOP gives staff a repeatable sequence, explicit escalation criteria, and a clear approval record. That makes it easier to train new staff, support audits, and resolve disputes. It also shortens review time because the reviewer knows exactly what evidence is required.