RWHAP Data Infrastructure In Focus: Data Matching & Sharing with HIV Surveillance
Resource updated 09/19/2023
Resource updated 09/19/2023
Resource updated 09/19/2023
Resource updated 09/14/2023
Resource updated 05/08/2024
Resource updated 03/07/2024
Resource updated 05/31/2024
These charts show improvements in completeness of data reported by Ryan White grantees from 2011 to 2022, measured by known rates for client demographics and clinical information.
Resource updated 09/14/2023
Resource updated 09/19/2023
Resource updated 09/19/2023
This is the second of two trainings developed to support Ryan White HIV/AIDS Program Part F AIDS Education and Training Center (AETC) Programs by providing insight on priority data elements, strategies for more efficient data management processes, and sharing tips for high-quality data submissions.
Resource updated 06/07/2024
This series of videos covers the fundamental concepts behind the Ryan White Services Report (RSR) for new and experienced grantees.
Resource updated 01/29/2024
Event updated 04/24/2024
The Recipient Report is based on your grant year cycle, while the client-level data file (Client Report) is based on a calendar year cycle.
Resource updated 03/21/2023
Guidelines for creating and encrypting the Unique Client Identifier (eUCI). Encryption of the eUCI must be included in the Ryan White Services Report (RSR) and ADAP Data Report (ADR) client-level data XML files.
Resource updated 09/14/2023
Resource updated 04/10/2023
This is information on how to use the Upload Completeness Report (UCR). This becomes available in the Ryan White Services Report (RSR) Web System once client level data is uploaded.
Resource updated 09/19/2023
Resource updated 04/12/2024
As part of the Ryan White Services Report (RSR), you are required to submit de-identified client-level demographic, service, and clinical data. Rather than filling out an online form (as with the Recipient Report and the Provider Report), you must upload these data in an electronic file, with a record for each client, in a specific XML (eXtensible Markup Language) format. Each client record must be assigned an encrypted Unique Client Identifier (eUCI).
Resource updated 09/14/2023
Resource updated 02/08/2024