121dictionary rows
152coded values documented
51required rows within scope
52derived, counted, or assigned rows
| ID / reference | Field | Meaning | Type / values | Required? | Derived / source method | Checks / source |
|---|---|---|---|---|---|---|
| RSR-FILE-001 | XML declaration Web form / system field File structure |
Declares the XML version and UTF-8 character encoding. Source note: This is required file structure, not a client data value. |
Fixed XML text <?xml version="1.0" encoding="UTF-8"?> |
Required Every client-level XML file. 1 per file; first line |
No Generated as fixed text by the submitting software. |
File must use the .xml extension and conform to the XSD. RSR XML Implementation Guide v3.10 · Guide pp. 2, 21 (§§2.1, 4.1) |
| RSR-FILE-002 | RSR:ROOT root element and namespace attributes/RSR:ROOTFile structure |
Opens the RSR file and identifies its XML schema and namespaces. Source note: This is required file structure. Confirm against the current official XSD. |
Complex XML element RSR:ROOT with xsi:schemaLocation="urn:rsrNamespace RsrClientSchema.xsd"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xmlns:RSR="urn:rsrNamespace" |
Required Every client-level XML file. 1 root element per file |
No Generated as fixed XML structure by the submitting software. |
All three attributes are required; file must conform to the XSD and element order. RSR XML Implementation Guide v3.10 · Guide pp. 2, 21 (§§2.2, 4.1) |
| RSR-FILE-003 | XmlVersion container/RSR:ROOT/XmlVersionFile structure |
Groups the schema, software, contact, and report-year file information. Source note: Container only; its submitted leaf values are separate dictionary rows. |
Complex XML element Contains RSR-FILE-004 through RSR-FILE-010 in XSD order |
Required Every client-level XML file. 1 per file; before ClientReport records |
No Generated by the submitting software. |
Element order is enforced through XSD conformance. RSR XML Implementation Guide v3.10 · Guide pp. 3–5, 21–22 (§§3.1, 4.2) |
| RSR-FILE-004 XV1 |
SchemaVersion/RSR:ROOT/XmlVersion/SchemaVersionFile Metadata |
Identifies the RSR XML schema version currently supported. Source note: Not defined in the manual client-element section. Guide cover says Implementation Guide v3.10; this field is the separate XML schema version 5.2.0. |
Version string 5.2.0 |
Required Every client-level XML file. 1 per file |
No Configured in the XML-generating application. |
XSD conformance; rejection if invalid RSR XML Implementation Guide v3.10 · Guide p.4, section 3.1.1 |
| RSR-FILE-005 XV2 |
Originator/RSR:ROOT/XmlVersion/OriginatorFile Metadata |
Names the application that generated the XML file. Source note: Not defined in the manual client-element section. The guide does not enumerate which special characters are excluded. |
Text 1–150 characters; special characters are excluded but the excluded set is not listed. |
Required Every client-level XML file. 1 per file |
No Configured in the XML-generating application. |
XSD conformance RSR XML Implementation Guide v3.10 · Guide p.4, section 3.1.2 |
| RSR-FILE-006 XV3 |
VersionNumber/RSR:ROOT/XmlVersion/VersionNumberFile Metadata |
Version of the application that generated the XML file. Source note: Not defined in the manual client-element section. The guide does not enumerate which special characters are excluded. |
Text 1–150 characters; special characters are excluded but the excluded set is not listed. |
Required Every client-level XML file. 1 per file |
No Configured in the XML-generating application. |
XSD conformance RSR XML Implementation Guide v3.10 · Guide p.4, section 3.1.3 |
| RSR-FILE-007 XV4 |
TechnicalContactName/RSR:ROOT/XmlVersion/TechnicalContactNameFile Metadata |
Technical contact for the application that generated the file. Source note: Not defined in the manual client-element section. The guide does not enumerate which special characters are excluded. |
Text 1–150 characters; special characters are excluded but the excluded set is not listed. |
Required Every client-level XML file. 1 per file |
No Configured in the XML-generating application. |
XSD conformance RSR XML Implementation Guide v3.10 · Guide p.5, section 3.1.4 |
| RSR-FILE-008 XV5 |
TechnicalContactEmail/RSR:ROOT/XmlVersion/TechnicalContactEmailFile Metadata |
Email for the technical contact. Source note: Not defined in the manual client-element section. No maximum length is stated in the guide. |
Email Valid email address |
Required Every client-level XML file. 1 per file |
No Configured in the XML-generating application. |
XSD conformance RSR XML Implementation Guide v3.10 · Guide p.5, section 3.1.5 |
| RSR-FILE-009 XV6 |
TechnicalContactPhone/RSR:ROOT/XmlVersion/TechnicalContactPhoneFile Metadata |
Phone number for the technical contact. Source note: Not defined in the manual client-element section. The comma-separated phone format is literal in the guide. |
Phone 999,999,9999 x99999; extension is optional and requires one space before x. |
Required Every client-level XML file. 1 per file |
No Configured in the XML-generating application. |
XSD conformance RSR XML Implementation Guide v3.10 · Guide p.5, section 3.1.6 |
| RSR-FILE-010 SV5 |
ReportYear/RSR:ROOT/XmlVersion/ReportYearFile Metadata |
Identifies the reporting period. Source note: The manual describes reporting-period rules but does not list ReportYear as a client element. The sample uses 2020 even though the guide is for 2025; the rule, not the sample year, controls. |
Four-digit year YYYY; must equal the submission reporting period year (2025 for this dictionary). |
Required Every client-level XML file. 1 per file |
Derived Use the reporting year assigned to the RSR submission. Configured in the XML-generating application. |
Client check 39 Error compares BirthYear to report year; multiple date validations compare dates to reporting period RSR XML Implementation Guide v3.10; 2025 RSR Validation Report · Guide p.5, section 3.1.7; Validation pp.8-13 |
| RSR-FILE-011 | ClientReport container/RSR:ROOT/ClientReportFile structure |
Contains the submitted values for one client. Source note: Empty or NULL tags are prohibited; omit an optional element when no value is available. The guide separately shows a conflicting xsi:nil poverty example. |
Complex XML element Child elements must follow the order in the official XSD |
Required Every reportable client. 1 record set per client; multiple clients per file |
No Generated from the provider source system and submitted in XML. |
Only one record set per client; duplicate ClientUci values and invalid order are rejected. 2025 RSR Instruction Manual; RSR XML Implementation Guide v3.10 · Manual pp. 74–76; Guide pp. 3, 21–23 (§§3, 4) |
| RSR-REC-001 Q1a |
Official mailing address — street Web form / system field General Information — official mailing address |
Street line of the recipient official mailing address. Source note: The web-form technical schema is not included in the repository. |
Text (formal length not specified) No formal length or pattern is published in the reviewed documents. |
Required Every Recipient Report. 1 per Recipient Report |
Prepopulated Pulled from the organization profile in HRSA EHBs. Prepopulated from HRSA EHBs; recipient reviews and updates as needed. |
Check 200 Error 2025 RSR Instruction Manual; 2025 RSR Validation Report · Manual p. 19; Validation p. 2 |
| RSR-REC-002 Q1b |
Official mailing address — city Web form / system field General Information — official mailing address |
City of the recipient official mailing address. Source note: The web-form technical schema is not included in the repository. |
Text (formal length not specified) No formal length or pattern is published in the reviewed documents. |
Required Every Recipient Report. 1 per Recipient Report |
Prepopulated Pulled from the organization profile in HRSA EHBs. Prepopulated from HRSA EHBs; recipient reviews and updates as needed. |
Check 188 Error 2025 RSR Instruction Manual; 2025 RSR Validation Report · Manual p. 19; Validation p. 2 |
| RSR-REC-003 Q1c |
Official mailing address — state Web form / system field General Information — official mailing address |
State of the recipient official mailing address. Source note: The web-form technical schema is not included in the repository. |
State code / selection (formal options not specified) No formal length or pattern is published in the reviewed documents. |
Required Every Recipient Report. 1 per Recipient Report |
Prepopulated Pulled from the organization profile in HRSA EHBs. Prepopulated from HRSA EHBs; recipient reviews and updates as needed. |
Check 199 Error 2025 RSR Instruction Manual; 2025 RSR Validation Report · Manual p. 19; Validation p. 2 |
| RSR-REC-004 Q1d |
Official mailing address — ZIP code Web form / system field General Information — official mailing address |
ZIP code of the recipient official mailing address. Source note: The web-form technical schema is not included in the repository. |
ZIP code stored as text Required address component; keep leading zeros in ZIP codes. |
Required Every Recipient Report. 1 per Recipient Report |
Prepopulated Pulled from the organization profile in HRSA EHBs. Prepopulated from HRSA EHBs; recipient reviews and updates as needed. |
Check 202 Error 2025 RSR Instruction Manual; 2025 RSR Validation Report · Manual p. 19; Validation p. 2 |
| RSR-REC-005 Q2a |
EIN Web form / system field General Information — organization identification |
The recipient Employer Identification Number. | Identifier (formal pattern not specified here) Valid EIN; exact pattern is not stated in the reviewed documents. |
Required Every Recipient Report. 1 |
Prepopulated Pulled from the organization profile. Prepopulated from EHBs and reviewed. |
Check 217 Error: EIN is required. 2025 RSR Instruction Manual; 2025 RSR Validation Report · Manual p. 19; Validation p. 2 |
| RSR-REC-006 Q2b |
UEI Alias: DUNS number (stale validation wording) Web form / system field General Information — organization identification |
The recipient Unique Entity Identifier. Source note: Use UEI as the current field. Treat DUNS as a legacy alias in the validation message, not a second field. |
12-character alphanumeric identifier Valid 12-character UEI assigned through SAM.gov. |
Required Every Recipient Report. 1 |
Prepopulated Pulled from the organization profile. Prepopulated from EHBs and reviewed. |
Check 218 Error still says DUNS number is required. 2025 RSR Instruction Manual; 2025 RSR Validation Report · Manual p. 19; Validation p. 2 |
| RSR-REC-007 Q3a |
Submission contact — name Web form / system field General Information — submission contact |
Contact information for the person responsible for this Recipient Report submission. | Text (formal length not specified) No formal length or pattern is published in the reviewed documents. |
Required Every Recipient Report. 1 |
No Prepopulated or entered in the web form. |
Check 197 Error 2025 RSR Instruction Manual; 2025 RSR Validation Report · Manual p. 19; Validation p. 2 |
| RSR-REC-008 Q3b |
Submission contact — title Web form / system field General Information — submission contact |
Contact information for the person responsible for this Recipient Report submission. | Text (formal length not specified) No formal length or pattern is published in the reviewed documents. |
Required Every Recipient Report. 1 |
No Prepopulated or entered in the web form. |
Check 201 Error 2025 RSR Instruction Manual; 2025 RSR Validation Report · Manual p. 19; Validation p. 2 |
| RSR-REC-009 Q3c |
Submission contact — phone Web form / system field General Information — submission contact |
Contact information for the person responsible for this Recipient Report submission. | Phone (formal pattern not specified) No formal length or pattern is published in the reviewed documents. |
Required Every Recipient Report. 1 |
No Prepopulated or entered in the web form. |
Check 198 Error 2025 RSR Instruction Manual; 2025 RSR Validation Report · Manual p. 19; Validation p. 2 |
| RSR-REC-010 Q3c (extension) |
Submission contact — extension Web form / system field General Information — submission contact |
Contact information for the person responsible for this Recipient Report submission. | Text / digits (formal pattern not specified) No formal length or pattern is published in the reviewed documents. |
Optional When applicable. 1 |
No Prepopulated or entered in the web form. |
No listed validation check 2025 RSR Instruction Manual; 2025 RSR Validation Report · Manual p. 19; Validation p. 2 |
| RSR-REC-011 Q3d |
Submission contact — fax Web form / system field General Information — submission contact |
Contact information for the person responsible for this Recipient Report submission. | Phone (formal pattern not specified) No formal length or pattern is published in the reviewed documents. |
Optional When applicable. 1 |
No Prepopulated or entered in the web form. |
No listed validation check 2025 RSR Instruction Manual; 2025 RSR Validation Report · Manual p. 19; Validation p. 2 |
| RSR-REC-012 Q3e |
Submission contact — email Web form / system field General Information — submission contact |
Contact information for the person responsible for this Recipient Report submission. | Email A valid email address. |
Required Every Recipient Report. 1 |
No Prepopulated or entered in the web form. |
Check 193 Error 2025 RSR Instruction Manual; 2025 RSR Validation Report · Manual p. 19; Validation p. 2 |
| RSR-REC-013 Q4 |
Received Minority AIDS Initiative designation Web form / system field General Information — Minority AIDS Initiative |
Whether a Part C or Part D recipient received an MAI designation during the reporting period. | Single select Yes or No. YES_NO · 2 values
|
Conditional RWHAP Parts C and D Recipient Reports. 1 when applicable |
No Entered or confirmed in the web form from the Notice of Award. |
Check 196 Error: a response is required. 2025 RSR Instruction Manual; 2025 RSR Validation Report · Manual p. 19; Validation p. 2 |
| RSR-REC-014 Q4 follow-up |
Most recent MAI percentage designation Web form / system field General Information — Minority AIDS Initiative |
The most recent MAI percentage designation for the reporting period. | Percentage (precision/range not formally specified) Numeric percent from the Notice of Award. |
Conditional When the MAI designation response is Yes. 1 when applicable |
Prepopulated / source document Use the most recent official percentage designation for the reporting period; do not calculate from client data. Entered from the most recent applicable Notice of Award. |
Check 195 Error: percentage required when MAI designation was received. 2025 RSR Instruction Manual; 2025 RSR Validation Report · Manual p. 19; Validation p. 2 |
| RSR-REC-015 Q7 / GCMS |
Funded provider organization Web form / system field Program Information |
An organization funded to provide services during the reporting period. | Repeated provider relationship Provider organizations whose GCMS contract dates overlap the reporting period. |
Prepopulated / confirm At least one provider must be listed for each Recipient Report. 1 or more per Recipient Report |
Prepopulated Select contracts whose dates overlap the RSR period. Pulled from GCMS contracts; recipient reviews and synchronizes. |
Check 187 Error: at least one provider is required. 2025 RSR Instruction Manual; 2025 RSR Validation Report · Manual pp. 21–22; Validation p. 2 |
| RSR-REC-016 Q7 / GCMS |
Funded service categories by provider Web form / system field Program Information |
The service categories each provider was funded to deliver with the award. | Multi-select relationship One or more RSR service categories per provider. PROVIDER_SERVICE_CATEGORY · 33 values
|
Prepopulated / confirm Every listed provider must have at least one funded service. 1 or more per provider |
Prepopulated Combined from applicable contracts, including RWHAP-related funded services. Pulled from GCMS contracts; recipient reviews and synchronizes. |
Check 191 Error: each provider must be funded for at least one service. 2025 RSR Instruction Manual; 2025 RSR Validation Report · Manual pp. 21–22, 28; Validation p. 2 |
| RSR-REC-017 Q8 |
Provider exempt from separate reporting Web form / system field Program Information — provider exemptions |
Whether the provider meets an allowed exemption and will be reported through another Provider Report. | Checkbox / Yes-No Exempt or not exempt. YES_NO · 2 values
|
Required For each listed provider. 1 per provider |
No Recipient selects the exemption status. |
Check 194 Error: the recipient cannot exempt all providers; at least one Provider Report must still be required. 2025 RSR Instruction Manual; 2025 RSR Validation Report · Manual pp. 23–25; Validation p. 2 |
| RSR-REC-018 Q8 follow-up |
Provider exemption explanation Web form / system field Program Information — provider exemptions |
A short explanation showing why the provider meets an exemption criterion. | Text (formal length not specified) Brief reason based on one or more manual exemption criteria. |
Conditional When the provider exemption box is selected. 1 per exempted provider |
No Entered by the recipient. |
No separate check is listed; the manual directs the recipient to enter an explanation. 2025 RSR Instruction Manual · Manual p. 24 |
| RSR-REC-019 Certification comment |
Certification comment Web form / system field Certification |
Meaningful feedback about the submission process. | Text (formal length not specified) Free text; do not include protected health information. |
Optional When the submitter has useful feedback. 0–1 |
No Entered during certification. |
No listed validation check. 2025 RSR Instruction Manual · Manual p. 26 |
| RSR-REC-020 Certification checkbox |
Accuracy and completeness certification Web form / system field Certification |
The recipient attests that the report is accurate and complete. | Required checkbox / attestation Checked / certified. |
Required Before certifying the Recipient Report. 1 |
No Recipient attestation. |
Certification cannot be completed without the attestation. 2025 RSR Instruction Manual · Manual p. 26 |
| RSR-CLD-001 SV2 |
ProviderID/RSR:ROOT/ClientReport/ProviderID/ Provider Linkage |
Links the client record to the provider organization. Source note: Manual p. 75 lists ProviderID in Table 3 and p. 76 defines it. Only the guide states that batch submissions must include it; the guide says Required: No, unless batch submittal. |
Integer Existing HAB-assigned provider ID |
Conditional Required only for a batch submission; normally not required for a file uploaded inside one Provider Report. 0-1 per client |
System-assigned Assigned in the RSR web system; when submitted it is cross-checked against the Provider Report. Assigned by the RSR system. |
Upload is rejected if supplied value does not match the Provider Report provider ID 2025 RSR Instruction Manual; RSR XML Implementation Guide v3.10 · Manual pp. 75–76; Guide p. 6 |
| RSR-CLD-002 SV3 |
RegistrationCode/RSR:ROOT/ClientReport/RegistrationCode/ Provider Linkage |
Links a client record to the provider registration. Source note: Manual p. 75 lists RegistrationCode in Table 3 and p. 76 defines it. Batch submission wording appears only in the guide, which labels this value optional. The guide schema example calls it a numeric string. |
Numeric string Existing HAB-assigned registration code |
Optional May be included and cross-checked; not required for a normal web upload. 0-1 per client |
System-assigned Assigned in the RSR web system; when submitted it is cross-checked against the Provider Report. Assigned by the RSR system. |
Upload is rejected if supplied value does not match the Provider Report registration code 2025 RSR Instruction Manual; RSR XML Implementation Guide v3.10 · Manual pp. 75–76; Guide p. 6 |
| RSR-PROV-001 | EIN Web form / system field General Information — organization details |
The provider Employer Identification Number. | Identifier (formal pattern not specified) Valid EIN. |
Optional Expected for the Provider Report; missing data creates a warning rather than an error. 0–1 |
Prepopulated Pulled from the organization profile. Prepopulated from EHBs and reviewed. |
Check 219 Warning if missing. 2025 RSR Instruction Manual; 2025 RSR Validation Report · Manual p. 40; Validation p. 3 |
| RSR-PROV-002 | UEI Alias: DUNS number (stale validation wording) Web form / system field General Information — organization details |
The provider Unique Entity Identifier. Source note: Use UEI as the current field. Treat DUNS as stale/legacy validation wording. |
12-character alphanumeric identifier Valid 12-character UEI assigned through SAM.gov. |
Optional Expected for the Provider Report; missing data creates a warning rather than an error. 0–1 |
Prepopulated Pulled from the organization profile. Prepopulated from EHBs and reviewed. |
Check 220 Warning still says DUNS number. 2025 RSR Instruction Manual; 2025 RSR Validation Report · Manual p. 40; Validation p. 3 |
| RSR-PROV-003 | NPI Web form / system field General Information — organization details |
The 10-digit National Provider Identifier for the HIV services provider. | 10-digit identifier stored as text Exactly 10 digits; preserve leading zeros if any. |
Optional Report when the provider has an NPI. 0–1 |
No Entered or reviewed in the organization profile. |
No listed 2025 validation check. 2025 RSR Instruction Manual · Manual pp. 40, 69 |
| RSR-PROV-004 | Official mailing address — street Web form / system field General Information — organization details |
Street line of the provider official mailing address. | Text (formal length not specified) Required address component. |
Required Every Provider Report. 1 |
Prepopulated Pulled from the organization profile. Prepopulated from EHBs and reviewed. |
Check 9 Error: official mailing address requires street, city, state, and ZIP. 2025 RSR Instruction Manual; 2025 RSR Validation Report · Manual p. 40; Validation p. 3 |
| RSR-PROV-005 | Official mailing address — city Web form / system field General Information — organization details |
City of the provider official mailing address. | Text (formal length not specified) Required address component. |
Required Every Provider Report. 1 |
Prepopulated Pulled from the organization profile. Prepopulated from EHBs and reviewed. |
Check 9 Error: official mailing address requires street, city, state, and ZIP. 2025 RSR Instruction Manual; 2025 RSR Validation Report · Manual p. 40; Validation p. 3 |
| RSR-PROV-006 | Official mailing address — state Web form / system field General Information — organization details |
State of the provider official mailing address. | State code / selection Required address component. |
Required Every Provider Report. 1 |
Prepopulated Pulled from the organization profile. Prepopulated from EHBs and reviewed. |
Check 9 Error: official mailing address requires street, city, state, and ZIP. 2025 RSR Instruction Manual; 2025 RSR Validation Report · Manual p. 40; Validation p. 3 |
| RSR-PROV-007 | Official mailing address — ZIP code Web form / system field General Information — organization details |
ZIP code of the provider official mailing address. | ZIP code stored as text Required address component. |
Required Every Provider Report. 1 |
Prepopulated Pulled from the organization profile. Prepopulated from EHBs and reviewed. |
Check 9 Error: official mailing address requires street, city, state, and ZIP. 2025 RSR Instruction Manual; 2025 RSR Validation Report · Manual p. 40; Validation p. 3 |
| RSR-PROV-008 | Organization contact — name Web form / system field General Information — organization contacts |
A contact detail for a provider organization contact. | Text (formal length not specified) Repeat for each contact; at least one organization contact is required. |
Conditional At least one contact record must be present. 0–many contacts |
No Entered or maintained in the EHBs organization profile. |
Check 242 Error: at least one organization contact must be specified. 2025 RSR Instruction Manual; 2025 RSR Validation Report · Manual p. 40; Validation p. 3 |
| RSR-PROV-009 | Organization contact — title Web form / system field General Information — organization contacts |
A contact detail for a provider organization contact. | Text (formal length not specified) Repeat for each contact; at least one organization contact is required. |
Conditional At least one contact record must be present. 0–many contacts |
No Entered or maintained in the EHBs organization profile. |
Check 242 Error: at least one organization contact must be specified. 2025 RSR Instruction Manual; 2025 RSR Validation Report · Manual p. 40; Validation p. 3 |
| RSR-PROV-010 | Organization contact — phone number Web form / system field General Information — organization contacts |
A contact detail for a provider organization contact. | Phone (formal pattern not specified) Repeat for each contact; at least one organization contact is required. |
Conditional At least one contact record must be present. 0–many contacts |
No Entered or maintained in the EHBs organization profile. |
Check 242 Error: at least one organization contact must be specified. 2025 RSR Instruction Manual; 2025 RSR Validation Report · Manual p. 40; Validation p. 3 |
| RSR-PROV-011 | Organization contact — email Web form / system field General Information — organization contacts |
A contact detail for a provider organization contact. | Email Repeat for each contact; at least one organization contact is required. |
Conditional At least one contact record must be present. 0–many contacts |
No Entered or maintained in the EHBs organization profile. |
Check 242 Error: at least one organization contact must be specified. 2025 RSR Instruction Manual; 2025 RSR Validation Report · Manual p. 40; Validation p. 3 |
| RSR-PROV-012 | Organization contact — fax Web form / system field General Information — organization contacts |
A contact detail for a provider organization contact. | Phone (formal pattern not specified) Repeat for each contact; at least one organization contact is required. |
Optional When applicable. 0–many contacts |
No Entered or maintained in the EHBs organization profile. |
Check 242 Error: at least one organization contact must be specified. 2025 RSR Instruction Manual; 2025 RSR Validation Report · Manual p. 40; Validation p. 3 |
| RSR-PROV-013 | Organization contact — primary point of contact Web form / system field General Information — organization contacts |
A contact detail for a provider organization contact. | Checkbox / Yes-No Repeat for each contact; at least one organization contact is required. YES_NO · 2 values
|
Optional When applicable. 0–many contacts |
No Entered or maintained in the EHBs organization profile. |
Check 242 Error: at least one organization contact must be specified. 2025 RSR Instruction Manual; 2025 RSR Validation Report · Manual p. 40; Validation p. 3 |
| RSR-PROV-014 | Provider type Web form / system field General Information — provider profile |
The single category that best describes the provider agency. | Single select Select one provider type. PROVIDER_TYPE · 11 values
|
Required Every Provider Report. 1 |
No Entered or reviewed in the organization profile. |
Check 3 Error if missing. 2025 RSR Instruction Manual; 2025 RSR Validation Report · Manual pp. 40–41; Validation p. 3 |
| RSR-PROV-015 | Other provider type description Web form / system field General Information — provider profile |
A description of a provider that does not fit a listed provider type. | Text (formal length not specified) Free text description. |
Conditional When Provider type is Other provider type. 0–1 |
No Entered in the organization profile. |
Manual requires a description when Other is selected. 2025 RSR Instruction Manual · Manual p. 41 |
| RSR-PROV-016 | Section 330 funding received Web form / system field General Information — provider profile |
Whether the provider received Section 330 funding during the reporting period. | Single select Yes; No; Unknown. YES_NO_UNKNOWN · 3 values
|
Required Every Provider Report. 1 |
No Entered or reviewed in the organization profile. |
Check 4 Error if missing. 2025 RSR Instruction Manual; 2025 RSR Validation Report · Manual p. 41; Validation p. 3 |
| RSR-PROV-017 | Ownership type Web form / system field General Information — provider profile |
The category that describes who owns and operates the provider. | Single select Select one ownership type. OWNERSHIP_TYPE · 7 values
|
Required Every Provider Report. 1 |
No Entered or reviewed in the organization profile. |
Check 5 Error if missing. 2025 RSR Instruction Manual; 2025 RSR Validation Report · Manual p. 42; Validation p. 3 |
| RSR-PROV-018 | Faith-based organization Web form / system field General Information — provider profile |
Whether the provider considers itself faith-based. | Single select Yes or No. YES_NO · 2 values
|
Required Every Provider Report. 1 |
No Entered or reviewed in the organization profile. |
Check 2 Error if missing. 2025 RSR Instruction Manual; 2025 RSR Validation Report · Manual p. 42; Validation p. 3 |
| RSR-PROV-019 | Part of a real-time electronic data network Web form / system field General Information — provider profile |
Whether the provider is part of a network that lets authorized providers share and manage client health information. | Single select No; Yes; Unknown. YES_NO_UNKNOWN · 3 values
|
Required Every Provider Report. 1 |
No Entered or reviewed in the organization profile. |
Check 215 Error if missing. 2025 RSR Instruction Manual; 2025 RSR Validation Report · Manual p. 42; Validation p. 3 |
| RSR-PROG-001 Q1a |
Submission contact — name Web form / system field Program Information — submission contact |
Contact information for the person responsible for the Provider Report submission. | Text (formal length not specified) No formal length or pattern is published in the reviewed documents. |
Required Every Provider Report. 1 |
No Entered in the Provider Report. |
Check 23 Error 2025 RSR Instruction Manual; 2025 RSR Validation Report · Manual p. 47; Validation p. 4 |
| RSR-PROG-002 Q1b |
Submission contact — title Web form / system field Program Information — submission contact |
Contact information for the person responsible for the Provider Report submission. | Text (formal length not specified) No formal length or pattern is published in the reviewed documents. |
Required Every Provider Report. 1 |
No Entered in the Provider Report. |
Check 28 Error 2025 RSR Instruction Manual; 2025 RSR Validation Report · Manual p. 47; Validation p. 4 |
| RSR-PROG-003 Q1c |
Submission contact — phone Web form / system field Program Information — submission contact |
Contact information for the person responsible for the Provider Report submission. | Phone (formal pattern not specified) No formal length or pattern is published in the reviewed documents. |
Required Every Provider Report. 1 |
No Entered in the Provider Report. |
Check 26 Error 2025 RSR Instruction Manual; 2025 RSR Validation Report · Manual p. 47; Validation p. 4 |
| RSR-PROG-004 Q1c (extension) |
Submission contact — extension Web form / system field Program Information — submission contact |
Contact information for the person responsible for the Provider Report submission. | Text / digits (formal pattern not specified) No formal length or pattern is published in the reviewed documents. |
Optional When applicable. 1 |
No Entered in the Provider Report. |
No listed check 2025 RSR Instruction Manual; 2025 RSR Validation Report · Manual p. 47; Validation p. 4 |
| RSR-PROG-005 Q1 (fax) |
Submission contact — fax Web form / system field Program Information — submission contact |
Contact information for the person responsible for the Provider Report submission. | Phone (formal pattern not specified) No formal length or pattern is published in the reviewed documents. |
Optional When applicable. 1 |
No Entered in the Provider Report. |
No listed check 2025 RSR Instruction Manual; 2025 RSR Validation Report · Manual p. 47; Validation p. 4 |
| RSR-PROG-006 Q1d |
Submission contact — email Web form / system field Program Information — submission contact |
Contact information for the person responsible for the Provider Report submission. | Email A valid email address. |
Required Every Provider Report. 1 |
No Entered in the Provider Report. |
Check 22 Error 2025 RSR Instruction Manual; 2025 RSR Validation Report · Manual p. 47; Validation p. 4 |
| RSR-PROG-007 Q2 |
Clinical quality management program status Web form / system field Program Information |
The current status of the provider clinical quality management program. | Single select Select one status. CQM_STATUS · 4 values
|
Required Every Provider Report. 1 |
No Entered in the Provider Report. |
Check 21 Error if missing. 2025 RSR Instruction Manual; 2025 RSR Validation Report · Manual p. 48; Validation p. 4 |
| RSR-PROG-008 Q3 |
Funding source certification Web form / system field Program Information |
The provider confirms that the displayed RWHAP, RWHAP-related, and EHE funding sources and services are correct. | Required checkbox / attestation Acknowledged / certified. |
Prepopulated / confirm Every Provider Report. 1 |
Prepopulated Combined from GCMS/Recipient Report funding relationships. Funding sources are pulled from recipient contracts; provider reviews and acknowledges. |
Check 27 Error if not acknowledged. 2025 RSR Instruction Manual; 2025 RSR Validation Report · Manual p. 49; Validation p. 4 |
| RSR-PROG-011 Q7 |
Delivered funded service category Web form / system field Service Information |
A funded service category the provider actually delivered during the reporting period. | Multi-select / checkbox by service Mark Delivered for each applicable funded service. PROVIDER_SERVICE_CATEGORY · 33 values
|
Conditional For each service delivered using RWHAP, RWHAP-related, or EHE funding. 0–many service categories |
Derived Compare program/service records with the funded service list and mark each category actually delivered. Provider confirms delivered services; funded categories are prepopulated from contracts. |
Checks 30, 32, 33, and 34 Warnings compare funded, delivered, and uploaded CLD services. 2025 RSR Instruction Manual; 2025 RSR Validation Report · Manual pp. 50–53; Validation p. 5 |
| RSR-PROG-012 Q7a |
Additional service category delivered Web form / system field Service Information — additional services |
A service delivered by a provider-only agency using its own RWHAP-related funding, including program income or pharmaceutical rebates. | Multi-select / checkbox by service Select applicable additional service categories. PROVIDER_SERVICE_CATEGORY · 33 values
|
Conditional Provider-only agencies that generated and used their own RWHAP-related funding for the service. 0–many service categories |
Derived Include only services delivered with the provider’s own RWHAP-related funding. Selected from program and service records. |
Check 238 Warning if selected but absent from the uploaded CLD. 2025 RSR Instruction Manual; 2025 RSR Validation Report · Manual pp. 50–53; Validation p. 5 |
| RSR-PROG-013 Validation comment |
Warning validation comment Web form / system field Validation |
A short explanation for an unresolved warning. | Text (formal length not specified) Free text related to the warning; never include protected health information. |
Conditional For each warning that remains when submitting the Provider Report. 0–many, one or more per unresolved warning as needed |
No Entered in the validation results. |
Warnings require correction or a comment; alerts do not require a comment. 2025 RSR Instruction Manual · Manual pp. 62–63 |
| RSR-PROG-014 Submission comment |
Submission comment Web form / system field Submission |
Meaningful feedback about the submission process. | Text (formal length not specified) Free text; do not include protected health information. |
Optional When the submitter has useful feedback. 0–1 |
No Entered during submission. |
No listed validation check. 2025 RSR Instruction Manual · Manual p. 64 |
| RSR-PROG-015 Certification checkbox |
Accuracy and completeness certification Web form / system field Submission |
The provider attests that the report data are accurate and complete. | Required checkbox / attestation Checked / certified. |
Required Before submitting the Provider Report. 1 |
No Provider attestation. |
Submission cannot be completed without the attestation. 2025 RSR Instruction Manual · Manual p. 64 |
| RSR-SITE-001 | Name Web form / system field General Information — service delivery sites |
Name of the individual service-delivery site. Source note: The repository does not include a technical schema for the service-delivery-site form. |
Text (formal length not specified) No formal length or pattern is published in the reviewed documents. |
Required Every listed site. 1 per site |
No Entered or reviewed for each service-delivery site in EHBs. |
Check 6 Error: at least one site when client services are delivered. 2025 RSR Instruction Manual; 2025 RSR Validation Report · Manual pp. 43–47; Validation p. 3 |
| RSR-SITE-002 | Address type Web form / system field General Information — service delivery sites |
Whether the site uses a domestic or international address. Source note: The repository does not include a technical schema for the service-delivery-site form. |
Single select See the named code set. ADDRESS_TYPE · 2 values
|
Required Every listed site. 1 per site |
No Entered or reviewed for each service-delivery site in EHBs. |
Check 6 Error: at least one site when client services are delivered. 2025 RSR Instruction Manual; 2025 RSR Validation Report · Manual pp. 43–47; Validation p. 3 |
| RSR-SITE-003 | Address line 1 Web form / system field General Information — service delivery sites |
Primary street-address line. Source note: The repository does not include a technical schema for the service-delivery-site form. |
Text (formal length not specified) No formal length or pattern is published in the reviewed documents. |
Required Every listed site. 1 per site |
No Entered or reviewed for each service-delivery site in EHBs. |
Check 6 Error: at least one site when client services are delivered. Check 211 Warning if the site address is incomplete. 2025 RSR Instruction Manual; 2025 RSR Validation Report · Manual pp. 43–47; Validation p. 3 |
| RSR-SITE-004 | Address line 2 Web form / system field General Information — service delivery sites |
Additional address information. Source note: The repository does not include a technical schema for the service-delivery-site form. |
Text (formal length not specified) No formal length or pattern is published in the reviewed documents. |
Optional When applicable. 0–1 per site |
No Entered or reviewed for each service-delivery site in EHBs. |
Check 6 Error: at least one site when client services are delivered. 2025 RSR Instruction Manual; 2025 RSR Validation Report · Manual pp. 43–47; Validation p. 3 |
| RSR-SITE-005 | City Web form / system field General Information — service delivery sites |
City where the site is located. Source note: The repository does not include a technical schema for the service-delivery-site form. |
Text (formal length not specified) No formal length or pattern is published in the reviewed documents. |
Required Every listed site. 1 per site |
No Entered or reviewed for each service-delivery site in EHBs. |
Check 6 Error: at least one site when client services are delivered. Check 211 Warning if the site address is incomplete. 2025 RSR Instruction Manual; 2025 RSR Validation Report · Manual pp. 43–47; Validation p. 3 |
| RSR-SITE-006 | State / province Web form / system field General Information — service delivery sites |
State or province where the site is located. Source note: The repository does not include a technical schema for the service-delivery-site form. |
State/province selection or text No formal length or pattern is published in the reviewed documents. |
Conditional Required for a domestic address; international rules are not formally specified. 1 per site |
No Entered or reviewed for each service-delivery site in EHBs. |
Check 6 Error: at least one site when client services are delivered. Check 211 Warning if the site address is incomplete. 2025 RSR Instruction Manual; 2025 RSR Validation Report · Manual pp. 43–47; Validation p. 3 |
| RSR-SITE-007 | ZIP / postal code Web form / system field General Information — service delivery sites |
ZIP or postal code for the site. Source note: The repository does not include a technical schema for the service-delivery-site form. |
Postal code stored as text No formal length or pattern is published in the reviewed documents. |
Required Every listed site under the form rules shown. 1 per site |
No Entered or reviewed for each service-delivery site in EHBs. |
Check 6 Error: at least one site when client services are delivered. Check 211 Warning if the site address is incomplete. 2025 RSR Instruction Manual; 2025 RSR Validation Report · Manual pp. 43–47; Validation p. 3 |
| RSR-SITE-008 | Country Web form / system field General Information — service delivery sites |
Country for an international service-delivery site. Source note: The repository does not include a technical schema for the service-delivery-site form. |
Country selection / text No formal length or pattern is published in the reviewed documents. |
Conditional International addresses. 1 per site |
No Entered or reviewed for each service-delivery site in EHBs. |
Check 6 Error: at least one site when client services are delivered. 2025 RSR Instruction Manual; 2025 RSR Validation Report · Manual pp. 43–47; Validation p. 3 |
| RSR-SITE-009 | Phone number Web form / system field General Information — service delivery sites |
Phone number clients use to access services at the site. Source note: The repository does not include a technical schema for the service-delivery-site form. |
Phone (formal pattern not specified) No formal length or pattern is published in the reviewed documents. |
Optional Expected for each site; missing/incomplete data create a warning. 0–1 per site |
No Entered or reviewed for each service-delivery site in EHBs. |
Check 6 Error: at least one site when client services are delivered. Check 212 Warning if missing/incomplete. 2025 RSR Instruction Manual; 2025 RSR Validation Report · Manual pp. 43–47; Validation p. 3 |
| RSR-SITE-010 | Website URL Web form / system field General Information — service delivery sites |
Web address related to the site. Source note: The repository does not include a technical schema for the service-delivery-site form. |
URL No formal length or pattern is published in the reviewed documents. |
Optional When a website is available; missing or invalid data create alerts. 0–1 per site |
No Entered or reviewed for each service-delivery site in EHBs. |
Check 6 Error: at least one site when client services are delivered. Checks 237 and 241 Alerts if missing or invalid. 2025 RSR Instruction Manual; 2025 RSR Validation Report · Manual pp. 43–47; Validation p. 3 |
| RSR-SITE-011 | Hours of operation Web form / system field General Information — service delivery sites |
Hours when clients can access services at the site. Source note: The repository does not include a technical schema for the service-delivery-site form. |
Structured hours / text (technical schema not specified) No formal length or pattern is published in the reviewed documents. |
Conditional Each active site should report accurate hours; the 2025 form uses a more standardized entry method. 1 per site |
No Entered or reviewed for each service-delivery site in EHBs. |
Check 6 Error: at least one site when client services are delivered. 2025 RSR Instruction Manual; 2025 RSR Validation Report · Manual pp. 43–47; Validation p. 3 |
| RSR-SITE-012 | Services provided at this site Web form / system field General Information — service delivery sites |
RWHAP, RWHAP-related, or EHE services clients can access at the site. Source note: The repository does not include a technical schema for the service-delivery-site form. |
Multi-select See the named code set. PROVIDER_SERVICE_CATEGORY · 33 values
|
Conditional Each delivered/uploaded client service must be linked to at least one site. 1 per site |
No Entered or reviewed for each service-delivery site in EHBs. |
Check 6 Error: at least one site when client services are delivered. Check 234 Alert if an uploaded service is not associated with a site. 2025 RSR Instruction Manual; 2025 RSR Validation Report · Manual pp. 43–47; Validation p. 3 |
| RSR-AGG-001 Manual Q7 / Validation Q8 |
HIV counseling and testing services provided Web form / system field HIV Counseling and Testing Information |
Whether the organization used RWHAP, RWHAP-related, or EHE funding to provide HIV counseling and testing during the reporting period. Source note: The manual numbers these fields 7–11; validation uses Q8–Q12. Use semantic field names as the stable key. |
Single select Yes or No. YES_NO · 2 values
|
Required Every Provider Report. 1 |
Derived Yes when the agency provided qualifying HC&T services during the reporting period. Entered from program activity. |
Check 18 Error if missing; aggregate counts become required when Yes. 2025 RSR Instruction Manual; 2025 RSR Validation Report · Manual pp. 53–54; Validation p. 6 |
| RSR-AGG-002 Manual Q8 / Validation Q9 |
Individuals tested for HIV Web form / system field HIV Counseling and Testing Information |
Number of people tested with an FDA-approved HIV test during the reporting period. Source note: The manual Q numbers are one lower than the validation Q numbers. |
Nonnegative integer Whole number 0 or greater, subject to the stated cross-field limits. |
Conditional When HIV counseling and testing services provided = Yes. 1 when applicable |
Count / aggregate Count qualifying individuals tested. Aggregate from testing and referral records; report all clients served regardless of payor. |
Checks 11, 12, 17, 20, and 35 Errors. 2025 RSR Instruction Manual; 2025 RSR Validation Report · Manual pp. 54–55; Validation p. 6 |
| RSR-AGG-003 Manual Q9 / Validation Q10 |
Individuals who tested negative Web form / system field HIV Counseling and Testing Information |
Number of tested individuals whose HIV test was negative. Source note: The manual Q numbers are one lower than the validation Q numbers. |
Nonnegative integer Whole number 0 or greater, subject to the stated cross-field limits. |
Conditional When HIV counseling and testing services provided = Yes. 1 when applicable |
Count / aggregate Count qualifying negative results/individuals. Aggregate from testing and referral records; report all clients served regardless of payor. |
Checks 12, 20, and 36 Errors: 0 ≤ negative ≤ total and negative + positive ≤ total. 2025 RSR Instruction Manual; 2025 RSR Validation Report · Manual pp. 54–55; Validation p. 6 |
| RSR-AGG-004 Manual Q10 / Validation Q11 |
Individuals who tested positive Web form / system field HIV Counseling and Testing Information |
Number of tested individuals whose HIV test was positive. Source note: The manual Q numbers are one lower than the validation Q numbers. |
Nonnegative integer Whole number 0 or greater, subject to the stated cross-field limits. |
Conditional When HIV counseling and testing services provided = Yes. 1 when applicable |
Count / aggregate Count qualifying positive results/individuals. Aggregate from testing and referral records; report all clients served regardless of payor. |
Checks 17, 20, 204, and 207 Errors: 0 ≤ positive ≤ total. 2025 RSR Instruction Manual; 2025 RSR Validation Report · Manual pp. 54–55; Validation p. 6 |
| RSR-AGG-005 Manual Q11 / Validation Q12 |
Individuals testing positive who were referred to HIV medical care Web form / system field HIV Counseling and Testing Information |
Number of people with a positive test who were referred to HIV medical care. Source note: The manual Q numbers are one lower than the validation Q numbers. |
Nonnegative integer Whole number 0 or greater, subject to the stated cross-field limits. |
Conditional When HIV counseling and testing services provided = Yes. 1 when applicable |
Count / aggregate Count qualifying positive individuals with a documented referral. Aggregate from testing and referral records; report all clients served regardless of payor. |
Checks 11, 206, and 207 Errors: 0 ≤ referred ≤ positive and referred ≤ total. 2025 RSR Instruction Manual; 2025 RSR Validation Report · Manual pp. 54–55; Validation p. 6 |
| RSR-AGG-006 Section 5 |
Client residence ZIP code Web form / system field Clients by ZIP Code |
ZIP code used to group reportable clients by residence. | Five-character ZIP code stored as text Most recent residence ZIP; service-site ZIP as proxy when needed; 99999 when neither residence nor proxy is known. |
Conditional Providers reporting eligible clients in client-level data. 1 row per reported ZIP |
Derived Assign each distinct eligible client to the most recent residence ZIP; use service-site ZIP as proxy when needed, then 99999 only if no residence or proxy exists. Aggregate from the same eligible-client population used for the CLD. |
Check 214 Alert compares the sum of ZIP counts with the CLD client count. 2025 RSR Instruction Manual; 2025 RSR Validation Report · Manual pp. 55–57; Validation p. 7 |
| RSR-AGG-007 Section 5 |
Number of clients in ZIP code Web form / system field Clients by ZIP Code |
Number of reportable clients assigned to the ZIP code in the row. | Positive integer Whole number greater than 0. |
Conditional For every ZIP code row. 1 per ZIP row |
Count / aggregate Count distinct reportable clients assigned to each ZIP. The sum should equal the total clients in the uploaded client-level file(s). Aggregate from distinct eligible client records. |
Check 213 Warning if a ZIP count is not greater than zero; Check 214 Alert if the sum differs from CLD clients. 2025 RSR Instruction Manual; 2025 RSR Validation Report · Manual pp. 55–57; Validation p. 7 |
| RSR-PROG-009 Q4 |
MAT prescribers count Web form / system field Program Information — medication-assisted treatment |
Number of physicians, nurse practitioners, or physician assistants in the funded unit/subunit who prescribed MAT for opioid use disorder during the reporting period. | Nonnegative integer Whole number; enter 0 if none. |
Required Every Provider Report. 1 |
Count / aggregate Count qualifying prescribers in the unit or subunit funded to provide RWHAP services, including subcontract providers. Aggregate from staff/prescribing records. |
The manual requires a response and says to enter 0 when none; no separate check appears in the validation list. 2025 RSR Instruction Manual · Manual pp. 49–50, 69 |
| RSR-PROG-010 Q5 |
Clients treated with MAT count Web form / system field Program Information — medication-assisted treatment |
Number of eligible clients treated with MAT in the funded unit/subunit during the reporting period. | Nonnegative integer Whole number; enter 0 if none. |
Required Every Provider Report; EHE-funded providers count EHE-eligible clients. 1 |
Count / aggregate Count eligible clients treated with MAT by the funded unit/subunit; exclude clients treated only by an outside organization. Aggregate from client treatment records. |
The manual requires a response and says to enter 0 when none; no separate check appears in the validation list. 2025 RSR Instruction Manual · Manual pp. 49–50, 69 |
| RSR-SYS-001 Q7 / system output |
Uploaded client record count Web form / system field Client upload summary |
Number of accepted client records uploaded for the provider. Source note: Validation-only system output; the provider does not submit this as a separate field. |
Whole-number count 0 or greater |
System-tracked Calculated after client-level XML is uploaded. 1 count per Provider Report |
Count / aggregate Count accepted ClientReport records, normally distinct ClientUci values after duplicate records are rejected. Calculated by the RSR system from uploaded XML. |
29 Warning expects at least one record for a funded client service; 214 Alert compares this count with ZIP totals. RSR XML Implementation Guide v3.10; 2025 RSR Validation Report · Guide p. 21; Validation pp. 4, 7 |
| RSR-SYS-002 System-generated placeholder |
Count of Clients Web form / system field Client validation results |
Number of uploaded client records that trigger one validation message. Source note: Validation-only system output; it is not an XML element or a provider-entered field. |
Whole-number count 0 or greater |
System-tracked Calculated whenever a client-level validation check runs. 1 count per validation result |
Count / aggregate For each rule, count distinct client records or ClientUci values that meet the rule’s trigger condition. Calculated by the RSR validation system. |
Displayed as [Count of Clients] in client-level validation messages. 2025 RSR Validation Report · Validation pp. 8–13 |
| RSR-CLD-003 SV4 |
ClientUci/RSR:ROOT/ClientReport/ClientUciIdentifier |
Encrypted identifier generated by HAB UCI tools. Source note: The manual explains full-date-of-birth, sex-at-birth, and consistent name-entry inputs. Its requirement line covers core/support services but omits EHE, while the guide says All. Do not attempt to reverse or invent the unpublished encryption algorithm. |
Uppercase alphanumeric string 40 uppercase hexadecimal characters plus one uppercase letter |
Required The guide requires it for every client record. The manual says all core and support services but omits EHE Initiative Services from this requirement line; confirm EHE scope against the current XSD and live RSR system. 1 per client |
Transformed Generate with an approved HAB UCI/eUCI utility using the client’s full date of birth (year, month, and day), SexAtBirthID, and consistently recorded name inputs. Use complete documented names, not nicknames or initials. The result is 40 uppercase hexadecimal characters plus one A–Z suffix. The reviewed PDFs do not publish the full encryption algorithm. Generated from the provider source system and submitted in XML. |
Section 4.1: duplicate ClientUci within a file is prohibited; format and uniqueness cause rejection 2025 RSR Instruction Manual; RSR XML Implementation Guide v3.10; 2025 RSR Validation Report · Manual pp. 76–78, 82–83; Guide pp. 7, 21 |
| RSR-CLD-004 2 |
VitalStatusID/RSR:ROOT/ClientReport/VitalStatusIDDemographic |
Client vital enrollment status at the end of the reporting period. Source note: Manual p. 78 supplies the last-known-status and funding-end rules and adds EHE Initiative Services to scope. The guide defines CM as medical and non-medical case management but omits EHE. Removed legacy codes 1–5 are invalid. The guide says occurrence 0–1 despite calling the field required for the specified clients. |
Integer code 12=Alive; 6=Deceased; 7=Unknown VITAL_STATUS · 3 values
|
Conditional Clients receiving OAHS, Medical Case Management, Non-Medical Case Management, or EHE Initiative Services. 0-1 per required client |
Time-based selection Use status at the end of the reporting period. If the client left care, use the last known status. If the provider’s funding ended during the year, HAB recommends using the status at the time funding ended. Generated from the provider source system and submitted in XML. |
No dedicated 2025 validation message listed 2025 RSR Instruction Manual; RSR XML Implementation Guide v3.10; 2025 RSR Validation Report · Manual p. 78; Guide p. 7; Validation p. 8 |
| RSR-CLD-005 4 |
BirthYear/RSR:ROOT/ClientReport/BirthYearDemographic |
Client year of birth. Source note: Manual says required for all service categories and that full DOB is used to generate eUCI; consistent apart from the guide's 0-1 occurrence wording. The guide states both required for all and 0-1 occurrence; missing BirthYear is an Error in check 221. |
Four-digit year Valid calendar year meeting the date rules |
Required Every reportable client. 0-1 per client |
Derived Extract YYYY from the locally held full date of birth; only the year is submitted. Generated from the provider source system and submitted in XML. |
39 Error after report year; 40 Error after first OAHS year; 221 Error missing; 84 Alert age 110+; 85 Warning after HIV diagnosis year; 86 Alert after CD4 year; 88 Alert after OAHS date year; 89 Alert after viral-load year; 172 and 174 Warning after HIV-positive/linkage date year 2025 RSR Instruction Manual; RSR XML Implementation Guide v3.10; 2025 RSR Validation Report · Manual pp. 78–79; Guide pp. 7–8; Validation pp. 8, 13 |
| RSR-CLD-006 5 |
EthnicityID/RSR:ROOT/ClientReport/EthnicityIDDemographic |
Client ethnicity. Source note: Manual uses expanded label Hispanic/Latino/a and the same two conceptual categories. Guide says occurrence 0-1 despite required All. |
Integer code 1=Hispanic/Latino; 2=Non-Hispanic/Latino ETHNICITY · 2 values
|
Required Every reportable client. 0-1 per client |
No Generated from the provider source system and submitted in XML. |
No dedicated 2025 validation message listed 2025 RSR Instruction Manual; RSR XML Implementation Guide v3.10; 2025 RSR Validation Report · Manual pp. 79–80; Guide p. 8 |
| RSR-CLD-007 68 |
ClientReportHispanicSubgroup/SubgroupID Alias: HispanicSubgroupID (manual label) /RSR:ROOT/ClientReport/ClientReportHispanicSubgroup/SubgroupIDDemographic |
Hispanic subgroup; report all that apply. Source note: Manual calls the XML variable HispanicSubgroupID; guide shows the actual nested tags ClientReportHispanicSubgroup and SubgroupID. Reconcile by treating the guide path as schema-authoritative. Repeat the SubgroupID tag for each selected value inside one complex container. |
Integer code; multi-select 1=Mexican, Mexican American, Chicano/a; 2=Puerto Rican; 3=Cuban; 4=Another Hispanic, Latino/a or Spanish origin HISPANIC_SUBGROUP · 4 values
|
Conditional When EthnicityID = 1 (Hispanic/Latino/a). 0-4 values per required client |
No Generated from the provider source system and submitted in XML. |
No dedicated 2025 validation message listed 2025 RSR Instruction Manual; RSR XML Implementation Guide v3.10; 2025 RSR Validation Report · Manual p. 80; Guide p. 8 |
| RSR-CLD-008 6 |
ClientReportRace/RaceID Alias: RaceID (manual child label) /RSR:ROOT/ClientReport/ClientReportRace/RaceIDDemographic |
Client race; report all that apply. Source note: Manual calls the leaf XML variable RaceID; guide provides the containing ClientReportRace element. The guide sample incorrectly shows RaceID 6, which is outside the allowed 1-5 range. Use allowed values in the data-element table, not the invalid sample value on guide p.22. |
Integer code; multi-select 1=White; 2=Black or African American; 3=Asian; 4=Native Hawaiian/Pacific Islander; 5=American Indian or Alaska Native RACE · 5 values
|
Required Every reportable client; report all races that apply. 0-5 values per client |
No Generated from the provider source system and submitted in XML. |
No dedicated 2025 validation message listed 2025 RSR Instruction Manual; RSR XML Implementation Guide v3.10; 2025 RSR Validation Report · Manual pp. 80–81; Guide pp. 8–9 |
| RSR-CLD-009 69 |
ClientReportAsianSubgroup/SubgroupID Alias: AsianSubgroupID (manual label) /RSR:ROOT/ClientReport/ClientReportAsianSubgroup/SubgroupIDDemographic |
Asian subgroup; report all that apply. Source note: Manual calls the XML variable AsianSubgroupID; guide shows actual nested tags ClientReportAsianSubgroup and SubgroupID. Repeat SubgroupID for each selected value. |
Integer code; multi-select 1=Asian Indian; 2=Chinese; 3=Filipino; 4=Japanese; 5=Korean; 6=Vietnamese; 7=Other Asian ASIAN_SUBGROUP · 7 values
|
Conditional When RaceID = 3 (Asian). 0-7 values per required client |
No Generated from the provider source system and submitted in XML. |
No dedicated 2025 validation message listed 2025 RSR Instruction Manual; RSR XML Implementation Guide v3.10; 2025 RSR Validation Report · Manual pp. 81–82; Guide p. 9 |
| RSR-CLD-010 70 |
ClientReportNhpiSubgroup/SubgroupID Alias: NHPISubgroupID (manual label) /RSR:ROOT/ClientReport/ClientReportNhpiSubgroup/SubgroupIDDemographic |
NHPI subgroup; report all that apply. Source note: Manual calls the XML variable NHPISubgroupID; guide uses ClientReportNhpiSubgroup and SubgroupID. Capitalization differs. Repeat SubgroupID for each selected value. |
Integer code; multi-select 1=Native Hawaiian; 2=Guamanian or Chamorro; 3=Samoan; 4=Other Pacific Islander NHPI_SUBGROUP · 4 values
|
Conditional When RaceID = 4 (Native Hawaiian/Pacific Islander). 0-4 values per required client |
No Generated from the provider source system and submitted in XML. |
No dedicated 2025 validation message listed 2025 RSR Instruction Manual; RSR XML Implementation Guide v3.10; 2025 RSR Validation Report · Manual p. 82; Guide pp. 9–10 |
| RSR-CLD-011 71 |
SexAtBirthID/RSR:ROOT/ClientReport/SexAtBirthIDDemographic |
Biological sex assigned at birth. Source note: Current manual emphasizes that this value may be Unknown but may not be missing and is used to generate eUCI. Guide says 0-1 even though Required=All. The value 4=Unknown was added for 2025. |
Integer code 1=Male; 2=Female; 4=Unknown SEX_AT_BIRTH · 3 values
|
Required Every reportable client. The value may be Unknown, but the element may not be missing. 0-1 per client |
No Generated from the provider source system and submitted in XML. |
72 Warning: Male or Unknown sex at birth with PregnantID=Yes 2025 RSR Instruction Manual; RSR XML Implementation Guide v3.10; 2025 RSR Validation Report · Manual pp. 7, 82–83; Guide p. 10; Validation p. 8 |
| RSR-CLD-012 9 |
PovertyLevelPercent/RSR:ROOT/ClientReport/PovertyLevelPercentDemographic |
Client percentage of the federal poverty level at end of reporting period. Source note: Manual p. 83 adds EHE Initiative Services, requires no decimals, and says to use the latest value on file. Omit the tag when the value is unavailable. The guide’s xsi:nil example conflicts with its section 4.1 rule against empty or NULL tags. The formula is operational guidance inferred from the meaning of percent of FPL; the guide gives no complete equation. |
Integer Integer up to four digits; no decimals |
Conditional Clients receiving OAHS, Medical Case Management, Non-Medical Case Management, or EHE Initiative Services. 0-1 per required client |
Calculated Calculate income as a percent of the applicable federal poverty measure and report a whole number up to four digits. HAB prefers HHS guidelines unless the agency already uses Census thresholds. Use the latest value on file; an earlier-year collection does not need to be repeated at year end, but changes should be documented. The documents do not give the full household-size or rounding procedure. Generated from the provider source system and submitted in XML. |
96 Warning: missing Poverty Level 2025 RSR Instruction Manual; RSR XML Implementation Guide v3.10; 2025 RSR Validation Report · Manual p. 83; Guide p. 10; Validation p. 8 |
| RSR-CLD-013 10 |
HousingStatusID/RSR:ROOT/ClientReport/HousingStatusIDDemographic |
Housing status at end of reporting period. Source note: Manual adds EHE Initiative Services and gives detailed housing definitions; guide does not mention EHE. CM in the guide includes both medical and non-medical case management. |
Integer code 1=Stable/permanent; 2=Temporary; 3=Unstable HOUSING_STATUS · 3 values
|
Conditional Clients receiving OAHS, Medical Case Management, Non-Medical Case Management, Housing Services, or EHE Initiative Services. 0-1 per required client |
Derived Classify the latest living arrangement using the Stable/permanent, Temporary, and Unstable definitions in the manual. Generated from the provider source system and submitted in XML. |
97 Warning: missing Housing Status 2025 RSR Instruction Manual; RSR XML Implementation Guide v3.10; 2025 RSR Validation Report · Manual pp. 84–85; Guide pp. 10–11; Validation p. 9 |
| RSR-CLD-014 11 |
HousingStatusCollectedDate/RSR:ROOT/ClientReport/HousingStatusCollectedDateDemographic |
Date when end-of-period housing status was collected. Source note: Manual requires the date to be within the reporting period, adds EHE Initiative Services, and prints MM/DD/YYYY. Guide prints comma-delimited mm,dd,yyyy. Confirm the XSD serialization before implementation. A verification that housing status did not change counts as collection per the manual. |
Date serialized as string A valid collection date; Guide examples use mm,dd,yyyy; the manual shows MM/DD/YYYY. Confirm the current XSD. |
Conditional Same client/service scope as HousingStatusID. 0-1 per required client |
No Generated from the provider source system and submitted in XML. |
216 Warning: missing date 2025 RSR Instruction Manual; RSR XML Implementation Guide v3.10; 2025 RSR Validation Report · Manual pp. 85–86; Guide p. 11; Validation p. 9 |
| RSR-CLD-015 12 |
HivAidsStatusID Alias: HIVAidsStatusID (manual capitalization) /RSR:ROOT/ClientReport/HivAidsStatusIDDemographic |
HIV/AIDS status at end of reporting period. Source note: Manual p. 86 says an affected client with unknown HIV status should have no value for this field. The manual prints HIVAidsStatusID while the guide schema tag is HivAidsStatusID; the manual also adds EHE service scope. Use exact XSD capitalization. |
Integer code 1=HIV negative; 2=HIV-positive, not AIDS; 3=HIV-positive, AIDS status unknown; 4=CDC-defined AIDS; 7=HIV indeterminate for infants under 2 only HIV_STATUS · 5 values
|
Conditional Clients receiving OAHS, Medical Case Management, Non-Medical Case Management, or EHE Initiative Services. For an HIV-affected client whose HIV status is unknown, omit this tag. 0-1 per required client |
Derived Classify the status at year end; once CDC-defined AIDS, continue reporting CDC-defined AIDS. Generated from the provider source system and submitted in XML. |
66 Warning indeterminate without perinatal risk; 235 Warning HIV negative with risk factor; 100 Warning indeterminate and over age 2; 209-210, 110, 127, 147, 151, 161, 168, 222-223, 239 and 173/176 use status in cross-field checks 2025 RSR Instruction Manual; RSR XML Implementation Guide v3.10; 2025 RSR Validation Report · Manual pp. 86–87; Guide p. 11; Validation pp. 8–9, 11–13 |
| RSR-CLD-016 14 |
ClientReportHivRiskFactor/HivRiskFactorID Alias: HIVRiskFactorID (manual capitalization/child label) /RSR:ROOT/ClientReport/ClientReportHivRiskFactor/HivRiskFactorIDDemographic |
Initial HIV risk factor; report all that apply. Source note: Manual calls the XML variable HIVRiskFactorID; guide uses nested ClientReportHivRiskFactor/HivRiskFactorID and does not mention EHE while the manual does. Repeat the leaf tag for all applicable factors. |
Integer code; multi-select 1=Male-to-male sexual contact; 2=Injection drug use; 3=Hemophilia/coagulation disorder; 4=Heterosexual contact; 5=Blood transfusion, components, or tissue; 6=Perinatal transmission; 9=Not reported or not identified HIV_RISK_FACTOR · 7 values
|
Conditional Clients receiving OAHS, Medical Case Management, Non-Medical Case Management, or EHE Initiative Services; omit for an affected client whose HIV status is unknown. 0-7 values per client |
No Generated from the provider source system and submitted in XML. |
66 Warning indeterminate without value 6; 235 Warning HIV negative with any risk factor 2025 RSR Instruction Manual; RSR XML Implementation Guide v3.10; 2025 RSR Validation Report · Manual pp. 87–88; Guide pp. 11–12; Validation p. 8 |
| RSR-CLD-017 15 |
ClientReportHealthCoverage/MedicalInsuranceID Alias: MedicalInsuranceID (manual child label) /RSR:ROOT/ClientReport/ClientReportHealthCoverage/MedicalInsuranceIDDemographic |
Health coverage; report all that apply. Source note: Manual pp. 88–90 supplies the full-year multi-select, uninsured-period, COBRA, and exchange rules and adds EHE clients to scope. The guide expresses OA, CM, HI and omits EHE. It excludes ADR-only values 8 and 9. Its sample incorrectly uses MedicalInsuranceID 6; use only 2 and 10–16. |
Integer code; multi-select 10=Private-Employer; 11=Private-Individual; 2=Medicare; 12=Medicaid, CHIP or other public plan; 13=VA, Tricare or other military care; 14=IHS; 15=Other plan; 16=No insurance/uninsured HEALTH_COVERAGE · 8 values
|
Conditional Clients receiving any core medical service, Non-Medical Case Management, or EHE Initiative Services. 0-8 values per required client |
Time-based classification Report every coverage source held during any part of the year. Also report No insurance when the client was uninsured at any time, even if another plan applied during another part of the year. Classify COBRA as Private–Employer and exchange coverage as Private–Individual. Generated from the provider source system and submitted in XML. |
99 Warning: missing Health coverage 2025 RSR Instruction Manual; RSR XML Implementation Guide v3.10; 2025 RSR Validation Report · Manual pp. 88–90; Guide p. 12; Validation p. 9 |
| RSR-CLD-018 72 |
HivDiagnosisYear Alias: HIVDiagnosisYearID (manual label) /RSR:ROOT/ClientReport/HivDiagnosisYearDemographic |
Year of HIV diagnosis, if known. Source note: Manual calls the XML variable HIVDiagnosisYearID and adds EHE service scope. Guide schema/sample uses HivDiagnosisYear. Guide prose writes HivAidsStatusID not equal 1 OR not equal 7, which is logically always true; manual clarifies neither value, meaning AND. Guide says 1 per required client but definition says if known; this merits schema/business-rule confirmation. |
Four-digit year Valid diagnosis year |
Conditional A new client receiving OAHS, Medical Case Management, Non-Medical Case Management, or EHE Initiative Services when HIV status is neither negative nor indeterminate; report if known. 1 per required client |
Derived Extract the year from the documented HIV diagnosis date. Generated from the provider source system and submitted in XML. |
70 Warning after reporting period; 85 Warning before BirthYear; 240 Warning uses diagnosis within report year to require a linkage date 2025 RSR Instruction Manual; RSR XML Implementation Guide v3.10; 2025 RSR Validation Report · Manual p. 90; Guide pp. 12–13; Validation pp. 8, 13 |
| RSR-CLD-019 76 |
NewClient/RSR:ROOT/ClientReport/NewClientDemographic |
Whether the client is new to care at this service provider. Source note: Major conflict: guide says required for All; manual says only clients of EHE-funded providers across core, support, and EHE services. Reconcile against the current XSD and reporting-system logic before enforcing globally. |
Integer code 1=No; 2=Yes YES_NO_NUMERIC · 2 values
|
Conditional Clients of an EHE Initiative-funded provider who received a core medical, support, or EHE service. The guide says All; the manual narrows this to EHE-funded providers. 1 per required client |
Derived Yes only when the person has never received care from this HIV services provider. Generated from the provider source system and submitted in XML. |
232 Warning: missing New Client response 2025 RSR Instruction Manual; RSR XML Implementation Guide v3.10; 2025 RSR Validation Report · Manual pp. 90–91; Guide p. 13; Validation p. 9 |
| RSR-CLD-020 77 |
ReceivedServicePreviousYear/RSR:ROOT/ClientReport/ReceivedServicePreviousYearDemographic |
Whether client received at least one service in the prior year. Source note: Guide omits the manual's EHE-provider limitation and the manual includes EHE Initiative Services in service scope. Guide text prints Required: OA CM. Use provider-level history, not only current-year client XML. |
Integer code 1=No; 2=Yes YES_NO_NUMERIC · 2 values
|
Conditional Clients of an EHE Initiative-funded provider when NewClient = No and the client received OAHS, Medical Case Management, Non-Medical Case Management, or EHE Initiative Services. 0-1 per required client |
Derived Yes when at least one provider service occurred in the calendar year immediately before the report year. Generated from the provider source system and submitted in XML. |
233 Warning: missing response 2025 RSR Instruction Manual; RSR XML Implementation Guide v3.10; 2025 RSR Validation Report · Manual pp. 91–92; Guide p. 13; Validation p. 9 |
| RSR-CLD-021 16, 18, 19, 21–29, 31–34, 36–38, 40–44, 75, 78 |
ClientReportServiceVisits/ServiceVisit/ServiceID/RSR:ROOT/ClientReport/ClientReportServiceVisits/ServiceVisit/ServiceIDService |
Identifies each visit-based service received during the reporting period. Source note: Manual Tables 4–6 give the exact Element ID-to-ServiceID crosswalk; the broad source shorthand has gaps at Element IDs 30, 35, and 39. The manual says Elements 16, 18–19, and 21–27 should be reported only for HIV-positive or HIV-indeterminate clients. The guide snippet shows only core IDs although its allowed-values table also includes support and EHE IDs. |
Integer code 8=OAHS; 10=Oral Health; 11=EIS; 13=Home Health; 14=Home and Community-Based Health; 15=Hospice; 16=Mental Health; 17=Medical Nutrition; 18=Medical Case Management; 19=Substance Abuse Outpatient; 20=Non-Medical Case Management; 21=Child Care; 23=Emergency Financial Assistance; 24=Food Bank/Home-Delivered Meals; 25=Health Education/Risk Reduction; 26=Housing; 28=Linguistic; 29=Medical Transportation; 30=Outreach; 32=Psychosocial Support; 33=Referral; 34=Rehabilitation; 35=Respite; 36=Substance Abuse Residential; 42=Other Professional; 46=EHE Initiative SERVICE_VISIT_ID · 26 values
|
Conditional For each core medical, support, or EHE service category with at least one actual visit day. One ClientReportServiceVisits container; one ServiceVisit per reported service category |
Derived Map the service record to the allowed ServiceID. Generated from the provider source system and submitted in XML. |
38 Warning missing services; Provider 32 Warning delivered but not uploaded; 34 Warning uploaded but not marked delivered; 234 Alert uploaded but no site; 238 Warning additional service delivered but not uploaded 2025 RSR Instruction Manual; RSR XML Implementation Guide v3.10; 2025 RSR Validation Report · Manual pp. 92–94; Guide pp. 14–15; Validation pp. 3, 5, 10 |
| RSR-CLD-022 16, 18, 19, 21–29, 31–34, 36–38, 40–44, 75, 78 |
ClientReportServiceVisits/ServiceVisit/Visits/RSR:ROOT/ClientReport/ClientReportServiceVisits/ServiceVisit/VisitsService |
Number of service visit days in the period for the indicated category. Source note: Manual defines Visits as days and de-duplicates by service date. Its FAQ says service counts must stay within eligible periods, while an OAHS client’s clinical data cover the full year. The guide gives the allowed range 1–365. Do not report zero. |
Integer Whole number 1 through 365 |
Conditional With each reported service-visit ServiceID. 1 per ServiceVisit |
Count / aggregate Count distinct calendar days per client and service category. Multiple same-category services on one day count once; omit zero-visit categories. If client eligibility has a gap, count only visits during eligible periods. Generated from the provider source system and submitted in XML. |
170 Alert: OAHS Visits greater than OAHS date count; 184 Alert: more than 365 visits; 38 Warning missing service 2025 RSR Instruction Manual; RSR XML Implementation Guide v3.10; 2025 RSR Validation Report · Manual pp. 92–94, 102; Guide pp. 14–15; Validation p. 10 |
| RSR-CLD-023 17, 20 |
ClientReportServiceDelivered/ServiceDelivered/ServiceID/RSR:ROOT/ClientReport/ClientReportServiceDelivered/ServiceDelivered/ServiceIDService |
Identifies each delivered core service that is reported as an indicator rather than visit count. Source note: Manual and guide agree on ServiceIDs 9 and 12. Guide lists many removed support ServiceIDs; they are not allowed here. Only report services actually delivered. |
Integer code 9=AIDS Pharmaceutical Assistance LPAP/CPAP; 12=Health Insurance Premium and Cost Sharing Assistance for Low-Income Individuals SERVICE_DELIVERED_ID · 2 values
|
Conditional When AIDS Pharmaceutical Assistance or Health Insurance Premium and Cost-Sharing Assistance was delivered. One ClientReportServiceDelivered container; one ServiceDelivered per delivered category |
Derived Map the delivered non-visit service to ServiceID 9 or 12. Generated from the provider source system and submitted in XML. |
38 Warning missing services; Provider 32, 34, 234 and 238 cross-report checks apply 2025 RSR Instruction Manual; RSR XML Implementation Guide v3.10; 2025 RSR Validation Report · Manual pp. 94–95; Guide pp. 15–16; Validation pp. 3, 5, 10 |
| RSR-CLD-024 17, 20 |
ClientReportServiceDelivered/ServiceDelivered/DeliveredID/RSR:ROOT/ClientReport/ClientReportServiceDelivered/ServiceDelivered/DeliveredIDService |
States that the paired ServiceID was delivered. Source note: Consistent: both guide and manual permit only 2=Yes. Do not submit a No value or a service not delivered. |
Integer code 2=Yes DELIVERED_YES · 1 values
|
Conditional With each reported ServiceDelivered ServiceID. 1 per ServiceDelivered |
Derived Use the fixed value 2 (Yes) when the service was delivered; omit undelivered services. Generated from the provider source system and submitted in XML. |
Cross-report validations 32, 34, 234 and 238 compare delivered/uploaded/site selections 2025 RSR Instruction Manual; RSR XML Implementation Guide v3.10; 2025 RSR Validation Report · Manual pp. 94–95; Guide pp. 15–16; Validation pp. 3, 5, 10 |
| RSR-CLD-025 47 |
FirstAmbulatoryCareDate/RSR:ROOT/ClientReport/FirstAmbulatoryCareDateClinical |
Date of first ambulatory HIV care at this provider. Source note: Manual limits clinical reporting to HIV-positive OAHS clients and prints MM/DD/YYYY; the guide uses comma-delimited dates. The first visit may predate the report year, may be non-RWHAP-funded, and stays unchanged in later reports. With eligibility gaps, clinical data still cover the full year. |
Date serialized as string Valid date; Guide examples use mm,dd,yyyy; the manual shows MM/DD/YYYY. Confirm the current XSD. |
Conditional HIV-positive clients receiving OAHS; not required for HIV-indeterminate infants under age 2. 0-1 per required client |
Derived Use the earliest qualifying HIV OAHS visit with this provider; if the true first date cannot reasonably be found, use the earliest available record. Generated from the provider source system and submitted in XML. |
40 Error BirthYear after first OAHS year; 44 Error date after report period; 45 Error first date after reported OAHS dates; 118 Warning first date but no OAHS visits 2025 RSR Instruction Manual; RSR XML Implementation Guide v3.10; 2025 RSR Validation Report · Manual pp. 95–96, 102; Guide pp. 16–17; Validation pp. 8, 11–12 |
| RSR-CLD-026 48 |
ClientReportAmbulatoryService/ServiceDate Alias: ClientReportAmbulatory > Service > ServiceDate (manual label) /RSR:ROOT/ClientReport/ClientReportAmbulatoryService/ServiceDateClinical |
All OAHS visit dates in the provider's HIV care setting during the reporting period. Source note: Manual labels the structure ClientReportAmbulatory / Service / ServiceDate; the guide uses ClientReportAmbulatoryService / ServiceDate. Confirm the XSD. With an eligibility gap, service counts use eligible periods but OAHS dates and other clinical data cover the full year. |
Date serialized as string One date per distinct qualifying visit day; Guide examples use mm,dd,yyyy; the manual shows MM/DD/YYYY. Confirm the current XSD. |
Conditional HIV-positive clients receiving OAHS; not required for HIV-indeterminate infants under age 2. 0 to number of days in reporting period |
Filtered list Report one date for every distinct qualifying OAHS visit day during the full year, regardless of payor. The number of dates should equal the Element 16 OAHS visit count. Generated from the provider source system and submitted in XML. |
37 Error before period; 48 Error after period; 45 Error before FirstAmbulatoryCareDate; 88 Alert before BirthYear; 170 Alert fewer dates than Visits; 110 Warning HIV negative with dates; 118 Warning absent visits; 127 Warning dates with no visits; 147 Warning missing dates 2025 RSR Instruction Manual; RSR XML Implementation Guide v3.10; 2025 RSR Validation Report · Manual pp. 96, 102; Guide p. 17; Validation pp. 8, 10–12 |
| RSR-CLD-027 49 |
ClientReportCd4Test/Cd4Test/Count/RSR:ROOT/ClientReport/ClientReportCd4Test/Cd4Test/CountClinical |
CD4 result during reporting period. Source note: Manual limits to HIV-positive OAHS clients. Guide calls Count Integer but provides no formal range. Each test pairs exactly one Count and ServiceDate. For a reportable OAHS client with an eligibility gap, report clinical data for the full year (Manual FAQ p. 102). |
Integer Integer; no formal lower or upper schema bound is published |
Conditional HIV-positive clients receiving OAHS; not required for HIV-indeterminate infants under age 2. One Count with each Cd4Test occurrence |
No Generated from the provider source system and submitted in XML. |
161 Warning missing; 208 Warning over 3000; 222 Warning conflicting counts on same date 2025 RSR Instruction Manual; RSR XML Implementation Guide v3.10; 2025 RSR Validation Report · Manual pp. 96–97, 102; Guide pp. 17–18; Validation pp. 8, 11–12 |
| RSR-CLD-028 49 |
ClientReportCd4Test/Cd4Test/ServiceDate/RSR:ROOT/ClientReport/ClientReportCd4Test/Cd4Test/ServiceDateClinical |
Date of CD4 specimen/test in the reporting period. Source note: Manual prints MM/DD/YYYY and says specimen date; guide prints comma-delimited date. Repeat the full Cd4Test element for multiple tests. For a reportable OAHS client with an eligibility gap, report clinical data for the full year (Manual FAQ p. 102). |
Date serialized as string Valid date; Guide examples use mm,dd,yyyy; the manual shows MM/DD/YYYY. Confirm the current XSD. |
Conditional With each reported CD4 Count. One date per Cd4Test occurrence |
No Generated from the provider source system and submitted in XML. |
49 Error after period; 67 Error before period; 86 Alert before BirthYear; 222 Warning conflicting same-date counts 2025 RSR Instruction Manual; RSR XML Implementation Guide v3.10; 2025 RSR Validation Report · Manual pp. 96–97, 102; Guide pp. 17–18; Validation pp. 11–12 |
| RSR-CLD-029 50 |
ClientReportViralLoadTest/ViralLoadTest/Count/RSR:ROOT/ClientReport/ClientReportViralLoadTest/ViralLoadTest/CountClinical |
Viral load result during reporting period. Source note: Manual agrees on conversion and undetectable logic and limits reporting to HIV-positive OAHS clients. The guide example writes 1,412.0 even though it requires Integer; submit the XSD-compliant whole number. For a reportable OAHS client with an eligibility gap, report clinical data for the full year (Manual FAQ p. 102). |
Integer Integer copies/mL; use the assay lower bound, or 0 when an undetectable result has no known bound |
Conditional HIV-positive clients receiving OAHS; not required for HIV-indeterminate infants under age 2. One Count with each ViralLoadTest occurrence |
Transformed Report integer copies/mL. Convert log result L as 10^L. For undetectable results, use the assay lower bound or 0 if the bound is unavailable. Generated from the provider source system and submitted in XML. |
209 Warning over 10000000; 210 Warning result for HIV-negative client; 168 Warning missing; 223 Warning both sides of suppression threshold on same date; 146 Warning result without OAHS record; 239 Warning last count under 200 with missing/No ART 2025 RSR Instruction Manual; RSR XML Implementation Guide v3.10; 2025 RSR Validation Report · Manual pp. 97–98, 102; Guide pp. 18–19; Validation pp. 8, 11–12 |
| RSR-CLD-030 50 |
ClientReportViralLoadTest/ViralLoadTest/ServiceDate/RSR:ROOT/ClientReport/ClientReportViralLoadTest/ViralLoadTest/ServiceDateClinical |
Date of viral load specimen/test in the reporting period. Source note: Manual prints MM/DD/YYYY and says specimen date; guide prints comma-delimited date. Repeat the full ViralLoadTest element for multiple tests. For a reportable OAHS client with an eligibility gap, report clinical data for the full year (Manual FAQ p. 102). |
Date serialized as string Valid date; Guide examples use mm,dd,yyyy; the manual shows MM/DD/YYYY. Confirm the current XSD. |
Conditional With each reported viral-load Count. One date per ViralLoadTest occurrence |
No Generated from the provider source system and submitted in XML. |
50 Error after period; 68 Error before period; 89 Alert before BirthYear; 223 Warning inconsistent same-date results 2025 RSR Instruction Manual; RSR XML Implementation Guide v3.10; 2025 RSR Validation Report · Manual pp. 97–98, 102; Guide pp. 18–19; Validation pp. 11–12 |
| RSR-CLD-031 52 |
PrescribedArtID/RSR:ROOT/ClientReport/PrescribedArtIDClinical |
Whether ART was prescribed at any time during the period. Source note: Manual states Yes/No without codes; guide supplies 1 and 8. Removed legacy reasons 3-7 are not allowed. Guide schema example shows only 1 but allowed values include 8. For a reportable OAHS client with an eligibility gap, report clinical data for the full year (Manual FAQ p. 102). |
Integer code 1=Yes; 8=No PRESCRIBED_ART · 2 values
|
Conditional HIV-positive clients receiving OAHS; not required for HIV-indeterminate infants under age 2. 0-1 per required client |
Derived Yes when ART began or continued at any time in the reporting period; otherwise No. Generated from the provider source system and submitted in XML. |
151 Warning missing; 239 Warning last viral load under 200 with missing or No ART 2025 RSR Instruction Manual; RSR XML Implementation Guide v3.10; 2025 RSR Validation Report · Manual p. 98, 102; Guide p. 19; Validation p. 12 |
| RSR-CLD-032 55 |
ScreenedSyphilisID/RSR:ROOT/ClientReport/ScreenedSyphilisIDClinical |
Whether the client was screened for syphilis during the reporting period. Source note: Guide explicitly says required at age 18 or older; manual describes all HIV-positive OAHS clients and uses Not medically indicated for low-risk/young clients. Scope needs reconciliation. The guide's definition and Required lines are not perfectly aligned for sexually active minors. For a reportable OAHS client with an eligibility gap, report clinical data for the full year (Manual FAQ p. 102). |
Integer code 1=No; 2=Yes; 3=Not medically indicated SYPHILIS_SCREEN · 3 values
|
Conditional HIV-positive clients receiving OAHS; use Not medically indicated when appropriate. The guide separately mentions age 18 or older. 0-1 per required client |
No Generated from the provider source system and submitted in XML. |
No dedicated 2025 validation message listed 2025 RSR Instruction Manual; RSR XML Implementation Guide v3.10; 2025 RSR Validation Report · Manual p. 98, 102; Guide pp. 19–20 |
| RSR-CLD-033 64 |
PregnantID/RSR:ROOT/ClientReport/PregnantIDClinical |
Whether the client was pregnant during the reporting period. Source note: Manual defines eligibility using SexAtBirthID=Female; guide uses the term women. Current validation explicitly uses sex at birth. Validation 72 was revised for 2025 to use sex at birth instead of gender. For a reportable OAHS client with an eligibility gap, report clinical data for the full year (Manual FAQ p. 102). |
Integer code 1=No; 2=Yes; 3=Not applicable PREGNANCY_STATUS · 3 values
|
Conditional HIV-positive OAHS clients whose SexAtBirthID is Female; not required for HIV-indeterminate infants under age 2. 0-1 per required client |
No Generated from the provider source system and submitted in XML. |
72 Warning: Male or Unknown SexAtBirthID with PregnantID=Yes 2025 RSR Instruction Manual; RSR XML Implementation Guide v3.10; 2025 RSR Validation Report · Manual p. 99, 102; Guide p. 20; Validation p. 8 |
| RSR-CLD-034 73 |
HivPosTestDate Alias: HIVPosTestDateID (manual label) /RSR:ROOT/ClientReport/HivPosTestDateHiv Testing/Linkage |
Date of positive confirmatory HIV test. Source note: Manual calls XML variable HIVPosTestDateID and allows a documented test from another site, while the guide schema tag is HivPosTestDate and says confidential confirmatory test. Date delimiter also differs. Confirm exact XSD tag and business definition. For a reportable OAHS client with an eligibility gap, report clinical data for the full year (Manual FAQ p. 102). |
Date serialized as string Valid date; Guide examples use mm,dd,yyyy; the manual shows MM/DD/YYYY. Confirm the current XSD. |
Conditional Newly diagnosed OAHS clients with a documented positive test during the reporting period. 0-1 per required client |
Derived Use the first documented positive test date. A documented test from another site is acceptable; client self-report alone is not. Generated from the provider source system and submitted in XML. |
171 Warning after report period; 172 Warning before BirthYear; 173 Warning for HIV-negative client; 177 Warning linkage before positive test 2025 RSR Instruction Manual; RSR XML Implementation Guide v3.10; 2025 RSR Validation Report · Manual p. 99, 102; Guide p. 20; Validation p. 13 |
| RSR-CLD-035 74 |
OamcLinkDate Alias: OAMCLinkDateID (manual label) /RSR:ROOT/ClientReport/OamcLinkDateHiv Testing/Linkage |
First OAHS visit after positive HIV test. Source note: Manual calls XML variable OAMCLinkDateID; guide schema tag is OamcLinkDate. Manual adds that visit must be with a prescribing provider. Date delimiter differs. Guide headings contain duplicated OamcLinkDate text and spaced-tag typos; do not copy spaces into XML. For a reportable OAHS client with an eligibility gap, report clinical data for the full year (Manual FAQ p. 102). |
Date serialized as string Valid date; Guide examples use mm,dd,yyyy; the manual shows MM/DD/YYYY. Confirm the current XSD. |
Conditional Newly diagnosed OAHS clients; first qualifying OAHS visit on or after the positive test, within the reporting period. 0-1 per required client |
Derived Use the first qualifying OAHS medical visit with a prescribing provider on or after HivPosTestDate. Generated from the provider source system and submitted in XML. |
174 Warning before BirthYear; 175 Warning after period; 176 Warning for HIV-negative client; 177 Warning before positive test; 240 Warning missing/outside period for newly diagnosed client 2025 RSR Instruction Manual; RSR XML Implementation Guide v3.10; 2025 RSR Validation Report · Manual pp. 99–100, 102; Guide pp. 20–21; Validation p. 13 |