Ideally, we would import the HUD XSD 2.7, but this is not currently possible, since many of its types are not global in scope, which is a requirement for importing types. So, instead, we've copied the schema into this one as the default namespace. Minnesota Model extensions are added with the mm: namespace to keep them separated. In the future, when the HUD XSD becomes importable in future releases, we will import an "hmis" namespace, or the like. See HMIS Data Integration Package, Version 2.7, Cumulative Overview, Appendix 1. See HMIS Data Integration Package, Version 2.7, Cumulative Overview, Appendix 1. See HMIS Data Integration Package, Version 2.7, Cumulative Overview, Appendix 1. See HMIS Data Integration Package, Version 2.7, Cumulative Overview, Section 3: I.1. Not used in ServicePoint See HMIS Data Integration Package, Version 2.7, Cumulative Overview, Section 3: I.1. Not used in ServicePoint; no need to upload use the ODBID> HMIS Data Integration Package, Version 2.7, Cumulative Overview, Section 3: I.1. Not used in ServicePoint; no need to upload HMIS Data Integration Package, Version 2.7, Cumulative Overview, Section 3: I.1. Not used in ServicePoint; no need to upload See HMIS Data Integration Package, Version 2.7, Cumulative Overview, Section 3: I.1. Not used in ServicePoint; no need to upload See HMIS Data Integration Package, Version 2.7, Cumulative Overview, Section 3: I.1. Not used in ServicePoint; no need to upload See HMIS Data Integration Package, Version 2.7, Cumulative Overview, Section 3: I.1. Not used in ServicePoint; no need to upload See HMIS Data Integration Package, Version 2.7, Cumulative Overview, Section 3: I.1. Not used in ServicePoint; no need to upload See HMIS Data Integration Package, Version 2.7, Cumulative Overview, Section 3: I.1. Not used in ServicePoint; no need to upload See HMIS Data Integration Package, Version 2.7, Cumulative Overview, Section 3: I.1. Not used in ServicePoint; no need to upload See HMIS Data Integration Package, Version 2.7, Cumulative Overview, Section 3: I.2. SP: Only child element used is "ExportDate" HMIS Data Integration Package, Version 2.7, Cumulative Overview, Section 3: I.2. SP Not used in ServicePoint; no need to upload See Data Integration Package Cumulative Overview, Section 3: I.2. See Data Integration Package Cumulative Overview, Section 3: I.2. HMIS Data Integration Package, Version 2.7, Cumulative Overview, Section 3: I.2. SP: This field is used as the FIRST choice as date added, date updated and date effective for children of the Client element that do not fall under ProgramParticipation - such as names and social security numbers) It is used as a third choice for effective date for children of the "Program Participation" element (as well as BarrieScreen, HousingCostSubsidy, EmergencyContacts and TANF Services) if "DataCollectionDate" and "ProgramEntryDate" are not available HMIS Data Integration Package, Version 2.7, Cumulative Overview, Section 3: I.2. SP: Not used in ServicePoint HMIS Data Integration Package, Version 2.7, Cumulative Overview, Section 3: I.2. SP: Not used in ServicePoint; no need to upload HMIS Data Integration Package, Version 2.7, Cumulative Overview, Section 3: I.2. SP: Not used in ServicePoint; no need to upload HMIS Data Integration Package, Version 2.7, Cumulative Overview, Appendix 1. SP: Not used in ServicePoint; no need to upload HMIS Data Integration Package, Version 2.7, Cumulative Overview, Appendix 1. SP: Not used in ServicePoint; no need to upload See HMIS Data Integration Package, Version 2.7, Cumulative Overview, Section 3: II.4. SP: Program information is added manually at this time; no need to include with upload HMIS Data Integration Package, Version 2.7, Cumulative Overview, Section 3: II.4. SP: Not used in ServicePoint; no need to upload See Data Integration Package Cumulative Overview, Section 3: II.4. See Data Integration Package Cumulative Overview, Section 3: II.4. HMIS Data Integration Package, Version 2.7, Cumulative Overview, Section 3: II.4. HMIS Data and Technical Standards, July 30, 2004, Universal Data Element 2.13 HMIS Data and Technical Standards, July 30, 2004, Universal Data Element 2.13 HMIS Data and Technical Standards, July 30, 2004, Universal Data Element 2.13 HMIS Data Integration Package, Version 2.7, Cumulative Overview, Section 3: II.4. HMIS Data Integration Package, Version 2.7, Cumulative Overview, Section 3: II.4. HMIS Data Integration Package, Version 2.7, Cumulative Overview, Section 3: II.4. HMIS Data Integration Package, Version 2.7, Cumulative Overview, Section 3: II.4. HMIS Data Integration Package, Version 2.7, Cumulative Overview, Section 3: II.4. See Data Integration Package Cumulative Overview, Section 3: II.4. See Data Integration Package Cumulative Overview, Section 3: II.4. See HMIS Data Integration Package, Version 2.7, Cumulative Overview, Section 3: I.3. Not used in ServicePoint HMIS Data Integration Package, Version 2.7, Cumulative Overview, Section 3: I.3. See Data Integration Package Cumulative Overview, Section 3: I.3. See Data Integration Package Cumulative Overview, Section 3: I.3. HMIS Data Integration Package, Version 2.7, Cumulative Overview, Section 3: I.3. See Data Integration Package Cumulative Overview, Section 3: I.3. See Data Integration Package Cumulative Overview, Section 3: I.3. See HMIS Data Integration Package, Version 2.7Cumulative Overview, Section 3: III.5. FunderRequiring = "Universal" HMIS Data and Technical Standards, July 30, 2004, Universal Data Element 2.12 SP: The type of ID (String or number) used for PersonID must remain constant throughout all imports SP: Each client's PersonID must remain constant throughout all imports SP: Generates the upload "SystemID" for Client SP: Generates the "Agency Client ID" on ServicePoint' Universal Profile. Use your unique identifier for this client to simplify mapping between your files and ServicePoint files subject: HUD Universal Data Elements: all clients HMIS Data Integration Package, Version 2.7, Cumulative Overview, Section 3: III.5. HMIS Data Integration Package, Version 2.7, Cumulative Overview, Section 3: III.5. HMIS Data and Technical Standards, July 30, 2004, Universal Data Element 2.1 When uploading anonymous clients, populate FirstName element with 'Anonymous'. SP: Only 30 characters will be uploaded into ServicePoint SP: Effective date taken from "DataCollectionDate" subject: HUD Universal Data Elements: all clients FunderRequiring = "Universal" HMIS Data and Technical Standards, July 30, 2004, Universal Data Element 2.1 SP: Only first character will upload into ServicePoint SP: Effective date taken from "DataCollectionDate" subject: HUD Universal Data Elements: all clients FunderRequiring = "Universal" HMIS Data and Technical Standards, July 30, 2004, Universal Data Element 2.1 SP: Only 30 characters will be uploaded into ServicePoint SP: Effective date taken from "DataCollectionDate" subject: HUD Universal Data Elements: all clients FunderRequiring = "Universal" HMIS Data and Technical Standards, July 30, 2004, Universal Data Element 2.1 SP: Only 10 characters will be uploaded into ServicePoint SP: Effective date taken from "DataCollectionDate" subject: HUD Universal Data Elements: all clients FunderRequiring = "Universal" HMIS Data and Technical Standards, July 30, 2004, Universal Data Element 2.2 SP: Effective date taken from "DataCollectionDate" subject: HUD Universal Data Elements: all clients FunderRequiring = "Universal" HMIS Data and Technical Standards, July 30, 2004, Universal Data Element 2.2 SP: Effective date taken from "DataCollectionDate" subject: Universal Data Elements: all clients FunderRequiring = "Universal" HMIS Data and Technical Standards, July 30, 2004, Universal Data Element 2.3 If unsure of birthdate, estimate the year, using 1/1 as the month/day SP: Effective date taken from "DataCollectionDate" SP: Even though minOccurs is 0; this element must be supplied to allow reports to group clients by age. subject: HUD Universal Data Elements: all clients FunderRequiring = "Universal" HMIS Data and Technical Standards, July 30, 2004, Universal Data Element 2.4.1 When mapping for funders that require HUD compliance, "unknown" should be mapped to 0: Non-Hispanic/Latino SP: Effective date taken from "DataCollectionDate" subject: HUD Univesral Data Elements: all clients FunderRequiring = "Universal" HMIS Data and Technical Standards, July 30, 2004, Universal Data Element 2.5 SP: Effective date taken from "DataCollectionDate" subject: HUD Univesral Data Elements: all clients FunderRequiring = "Universal" HMIS Data and Technical Standards, July 30, 2004, Universal Data Element 2.4.2 When mapping to SP schema, first instance of 'Race' will go to 'Primary Race', 2nd instance to 'Secondary Race'. If more than 2 races are listed, coding for 'Primary Race' will be 'other multi-racial' SP: Effective date taken from "DataCollectionDate" subject: HUD Univesral Data Elements: all clients FunderRequiring = "Universal" Enter the city where client was born SP: Effective date taken from "DataCollectionDate" FunderRequiring = "Universal-optional" subject: Universal Assessment: all clients; optional Select the state where this person was born SP: Effective date taken from "DataCollectionDate" subject: Universal Assessment: all clients; optional FunderRequiring = "Universal" Enter the name of the country where this person was born SP: Effective date taken from "DataCollectionDate" subject: Universal Assessment: all clients; optional FunderRequiring = "Universal" SP: Date added and Date updated are both taken from "GoalDate" subject: FHPAP; THP : all clients Timing of Data Collection: When Client exits program FunderRequiring = "FHPAP" FunderRequiring = "THP" HMIS Data and Technical Standards, July 30, 2004, Universal Data Element 2.1 SP: ServicePoint concatenates all child elements of OtherNames to form one 'alias'. subject: HUD Univesral Elements: all clients FunderRequiring = "Universal-Optional" HMIS Data and Technical Standards, July 30, 2004, Universal Data Element 2.1 FunderRequiring = "Universal" HMIS Data and Technical Standards, July 30, 2004, Universal Data Element 2.1 FunderRequiring = "Universal" HMIS Data and Technical Standards, July 30, 2004, Universal Data Element 2.1 FunderRequiring = "Universal" HMIS Data and Technical Standards, July 30, 2004, Universal Data Element 2.1 FunderRequiring = "Universal" See HMIS Data Integration Package, Version 2.7, Cumulative Overview, Section 3: IV.7. subject: HUD, FHPAP, LTH, THP, DHS Youth: all clients See HMIS Data Integration Package, Version 2.7, Cumulative Overview, Section 3: IV.7. SP: Must be consistent across imports; must be unique to this ProgramParticipation within the database. subject: HUD, FHPAP, LTH, THP, DHS Youth: all clients FunderRequiring = "Universal" HMIS Data Integration Package, Version 2.7, Cumulative Overview, Section 3: IV.7. SP: MUST upload the Number, not the string. Cannot upload both FunderRequiring = "Universal" HMIS Data Integration Package, Version 2.7, Cumulative Overview, Section 3: IV.7. SP: Do NOT upload this string; use the ID number, for ServicePoint FunderRequiring = "Universal" SP: Use PPProgramIDNum, not PPProgramIDStr for upload into ServicePoint; use the number assigned to this program by ServicePoint HMIS Data Integration Package, Version 2.7, Cumulative Overview, Section 3: IV.7. SP: Unique identifier for Program, which will be assigned by Bowman; used to identify Program Participation Provider SP: Generates the upload "System ID" for entry-exits FunderRequiring = "Universal" HMIS Data Integration Package, Version 2.7, Cumulative Overview, Section 3: IV.7. SP: Not used in ServicePoint FunderRequiring = "Universal" See HMIS Data Integration Package, Version 2.7, Cumulative Overview, Section 3: IV.7. SP: Not used for ServicePoint, HMIS Data Integration Package, Version 2.7, Cumulative Overview, Section 3: IV.7. FunderRequiring = "Universal" HMIS Data Integration Package, Version 2.7, Cumulative Overview, Section 3: IV.7. FunderRequiring = "Universal" Select Yes If this person is US citizen, No if not a US citizen. FunderRequiring =optional Minnesota Model overriding definition: A veteran is someone who has served on active duty in the Armed Forces of the United States for 180 OR MORE days. This does not include inactive military reserves or the National Guard unless the person was called up to active duty. HMIS Data and Technical Standards, July 30, 2004, Universal Data Element 2.6 Subject: All adults FunderRequiring = "ESG" FunderRequiring = "FHPAP" FunderRequiring = "HUD" FunderRequiring = "LTH" FunderRequiring = "THP" HMIS Data and Technical Standards, July 30, 2004, Universal Data Element 2.7 HUD Suggested question: Do you have a physical, mental, emotional or developmental disability, HIV/AIDS, or a diagnosable substance abuse problem that is expected to be of long duration and substantially limits your ability to live on your own? Impairment which is (a) expected to be of long-continued and indefinite duration, (b) substantially impedes an individual’s ability to live independently, and (c) of such a nature that such ability could be improved by more suitable housing conditions; (3) a developmental disability as defined in section 102 of the Developmental Disabilities Assistance and Bill of Rights Act; (4) the disease of acquired immunodeficiency syndrome or any conditions arising from the etiological agency for acquired immunodeficiency syndrome; or (5) a diagnosable substance abuse disorder. Subject: All adults FunderRequiring = "HUD" FunderRequiring = "LTH" HMIS Data and Technical Standards, July 30, 2004, Universal Data Element 2.8 HUD Suggested question: Where did you stay last night? Where did the participant sleep in the week prior to entering the project? (Choose one place). Note that if a participant came from an institutional psychiatric facility, substance abuse treatment facility, hospital, or jail/prison, but was there less than 30 days and was living on the street or in emergency shelter before entering the treatment facility, he/she should be counted in either the street or shelter category, as appropriate. Subject: All adults and unaccompanied youth FunderRequiring = "ESP" FunderRequiring = "FHPAP" FunderRequiring = "LTH" FunderRequiring = "THP" HMIS Data and Technical Standards, July 30, 2004, Universal Data Element 2.8 Text field to accommodate explanation for answer of 'other' for 'PriorResidence'. Subject: All adults and unaccompanied youth FunderRequiring = "ESP" FunderRequiring = "FHPAP" FunderRequiring = "LTH" FunderRequiring = "THP" *Minesota Model Addition. If client's last address was in MN: City - Where was you last permanent address? "Permanent address" defined as where last resided continuously for 90 days or more. Subject: All adults and unaccompanied youth FunderRequiring = "Universal" *Minesota Model Addition. State - Where was your last permanent address? "Permanent address" defined as where last resided continuously for 90 days or more. Subject: All adults and unaccompanied youth FunderRequiring = "ESP" FunderRequiring = "LTH" FunderRequiring = "THP" *Minesota Model Addition. If last permanent address was in MN: County - Where was your last permanent address? -"Permanent address" defined as where last resided continuously for 90 days or more. Subject: All adults and unaccompanied youth FunderRequiring = "ESP" FunderRequiring = "LTH" FunderRequiring = "THP" HMIS Data and Technical Standards, July 30, 2004, Universal Data Element 2.8 HUD suggested question: After asking , "Where did you stay last night?", followup with "How long did you stay there?" Subject: All adults and unaccompanied youth FunderRequiring = "HUD" FunderRequiring = "LTH" *Minesota Model Addition. How long since client has lived in the same permanent housing for 90 days or more. Emergency shelters or time-limited housing are not considered "permanent housing". Subject: All adults and unaccompanied youth FunderRequiring = "Universal" HMIS Data and Technical Standards, July 30, 2004, Universal Data Element 2.9 The five-digit zip code of the apartment, room, or house where the client last lived for 90 days or more Subject: All adults and unaccompanied youth FunderRequiring = "HUD" FunderRequiring = "LTH" HMIS Data and Technical Standards, July 30, 2004, Universal Data Element 2.9 Subject: All adults and unaccompanied youth FunderRequiring = "HUD" FunderRequiring = "LTH" HMIS Data and Technical Standards, July 30, 2004, Universal Data Element 2.10 Date the client began receiving services from the program. SP: ProgramEntryDate is used for the effective date for children of "ProgramParticipation" SP: Used on ART reports to determine which clients are included in the report. The ProgramEntryDate must be less than or equal to the Report End Date (the last day of the reporting period). SP: ProgramEntryDate is used in ART reporting to determine which assessment information should be included. Answers to most assessment questions will be included ONLY if the effective date is less than or equal to the client’s ProgramEntryDate. subject: HUD, FHPAP, LTH, THP, DHS Youth: all clients FunderRequiring = "Universal" HMIS Data and Technical Standards, July 30, 2004, Universal Data Element 2.11 The date the client exits the program. SP: Used on ART reports to determine which clients are included in the report. The ProgramExitDate must be null or >= Report Start Date (the first day of the reporting period). Also note that on reports showing sub-assessment data at exit (such as income), a record will be included only if the sub-assessment end date is null or >= ProgramExitDate. subject: HUD, FHPAP, LTH, THP, DHS Youth: all clients FunderRequiring = "Universal" Select a type of entry; ths element is unique to this software implementation SP: On Entry Screen; Type of entry into ServicePoint system. Choice is HUD-40118 or Basic. All should default to Basic, except entries to HUD-funded providers. If you need to run the APR for the program this client is entered into, select HUD-40118. subject: HUD, FHPAP, LTH, THP, DHS Youth: all clients HMIS Data and Technical Standards, July 30, 2004, Universal Data Element 2.14 Unique identifier for a household. If a household is uploaded, HouseholdID must be supplied. SP: Generates the upload "System ID" for Households SP: Must be the same for all members of a household across imports; must be unique from all other households with the same Provider number (PProgramID) subject: all clients entering the program with others FunderRequiring = "Universal" HMIS Data Integration Package, Version 2.7, Cumulative Overview, Section 3: IV.7. HMIS Data Integration Package, Version 2.7, Cumulative Overview, Section 3: IV.7. MN addition: Household: type of household selected from a pickList SP: This element MUST be included for each client uploaded within a household to validate with the ServicePoint schema; not required for individuals subject: all clients entering the program with others FunderRequiring = "Universal" *MN addition: Date the client entered the household. SP: If a household is uploaded, this element must be supplied. Suggested default: ProgramEntryDate subject: all clients entering the program with others FunderRequiring = "Universal" *MN addition: Date the client was removed from the household; used for death, divorce, etc. If actual date is unknown, give an approximation. SP: To be included with a household in the HUD APR, “DateRemoved” must be null or less than or equal to the Report End Date. SP: This field is used to filter out household members who have left the household before the reporting period. subject: all clients entering the program with others (and are removed from the household) FunderRequiring = "Universal" See HMIS Data Integration Package, Version 2.7, Cumulative Overview, Section 3: IV.7. Is the client the head of the household? Only one person in a household can be recorded as the head SP: If a household is uploaded, this element is required. subject: all clients entering the program with others FunderRequiring = "Universal" See HMIS Data Integration Package, Version 2.7, Cumulative Overview, Section 3: IV.7. Client's relationship to the head of household. SP: If client is the head of household, omit this element; and be sure to include HeadOfHousehold = true. If a household is uploaded and this client is not the head, this element must be supplied. subject: all clients entering the program with others (except the head of household) FunderRequiring = "Universal" MN addition: Hours case manager spends on client. Subject: FHPAP: Household heads, singles and unaccompanied youth FunderRequiring = "FHPAP" This question is relevant for HIPAA-covered entities. HIPAA relates to agencies rather than clients. If an agency is covered by HIPAA, they should include a question on their agreement form about using their information in database research. Answer = "NO" if the client indicates "I do NOT want the information about me in Minnesota’s HMIS used for research." "Yes" indicates that the client is comfortable having his or her information included in research conducted on data maintained in the database. . Since the risk to the client is minimal, no answer to this question will be treated as "yes" FunderRequiring = "Universal" See HMIS Data Integration Package, Version 2.7, Cumulative Overview, Section 3: V.8. SP: The effective date for data elements in ClientHistorical will be the DataCollectionDate HMIS Data Integration Package, Version 2.7, Cumulative Overview, Section 3: IV.8. See Data Integration Package Cumulative Overview, Section 3: IV.8. See Data Integration Package Cumulative Overview, Section 3: IV.8. HMIS Data Integration Package, Version 2.7, Cumulative Overview, Section 3: IV.8. The DataCollectionType element has four allowable values indicating whether the data were collected at intake, exit, follow-up, or some time in the course of program enrollment. This element is included to conform to HUD 2.7 SP: Not used in ServicePoint; no need to upload HMIS Data Integration Package, Version 2.7, Cumulative Overview, Section 3: IV.8. Date the data was collected. SP: This date will be the 'effective date' for child elements of "ClientHistorical. SP: When uploading data for the first time, the DataCollectionDate should be set to the ProgramEntryDate. When uploading changes to data, the DataCollectionDate should be the date of these changes. SP: DataCollectionDate isn't used directly in ART reports, but the effective date is used, which is filled using the DataCollectionDate. subject: all clients HMIS Data and Technical Standards, July 30, 2004, Program-Specific Data Element 3.3 A physical impairment which is (a) expected to be of long-continued and indefinite duration, (b) substantially impedes an individual’s ability to live independently, and (c) of such a nature that such ability could be improved by more suitable housing conditions. Subject: ESG, FHPAP, HUD, LTH: All clients FunderRequiring = "ESG" FunderRequiring = "FHPAP" FunderRequiring = "HUD" FunderRequiring = "LTH" FunderRequiring = "THP" MN addition; required if a physical disability is recorded. Enter a start date for disability; usually given as the date of program entry Subject: ESG, FHPAP, HUD, LTH: All clients FunderRequiring = "ESG" FunderRequiring = "FHPAP" FunderRequiring = "HUD" FunderRequiring = "LTH" FunderRequiring = "THP" HMIS Data and Technical Standards, July 30, 2004, Program-Specific Data Element 3.4 A severe, chronic disability that is attributed to a mental or physical impairment (or combination of physical and mental impairments) that occurs before 22 years of age and limits the capacity for independent living and economic self-sufficiency. Subject: ESG, FHPAP, HUD, LTH: All clients FunderRequiring = "ESG" FunderRequiring = "FHPAP" FunderRequiring = "HUD" FunderRequiring = "LTH" FunderRequiring = "THP" MN addition; required if a developmental disability is recorded. Enter a start date for disability; usually given as the date of program entry Subject: ESG, FHPAP, HUD, LTH: All clients with Developmental Disability FunderRequiring = "ESG" FunderRequiring = "FHPAP" FunderRequiring = "HUD" FunderRequiring = "LTH" FunderRequiring = "THP" Diagnosed with one of the following documented primary or secondary diagnoses of brain injury or related neurological condition that resulted in significant cognitive and significant behavioral impairment: 1. Acquired brain injury including traumatic brain injury that is not congenital (existing at birth). ; 2. Degenerative disease where cognitive impairment is present and diagnosis is not congenital (existing at birth); or 3. Documented brain impairment from an event, disease or condition that is not congenital (existing at birth). Subject: ESG, FHPAP, HUD, LTH: All clients FunderRequiring = "ESG" FunderRequiring = "FHPAP" FunderRequiring = "HUD" FunderRequiring = "LTH" FunderRequiring = "THP" HMIS Data and Technical Standards, July 30, 2004, Program-Specific Data Element 3.10. Where the client will be staying after they leave the program Subject: HUD, FHPAP, LTH, THP: all clients Information collected at Exit FunderRequiring = "HUD" FunderRequiring = "FHPAP" FunderRequiring = "LTH" FunderRequiring = "THP" HMIS Data and Technical Standards, July 30, 2004, Program-Specific Data Element 3.10. See also Section 5.1.3 for treatment of "other" elements. Text field to elaborate on answer of 'Other' for 'Destination'. Subject: HUD, FHPAP, LTH, THP: all clients FunderRequiring = "HUD" FunderRequiring = "FHPAP" FunderRequiring = "LTH" FunderRequiring = "THP" HMIS Data and Technical Standards, July 30, 2004, Program-Specific Data Element 3.10. After client leaves program, will the move be permanent (more than 90 days) or transitional? Subject: HUD, FHPAP, LTH, THP: all clients FunderRequiring = "HUD" FunderRequiring = "FHPAP" FunderRequiring = "LTH" FunderRequiring = "THP" HMIS Data and Technical Standards, July 30, 2004, Program-Specific Data Element 3.10 As client exits program, does the move involve a HUD subsidy or other subsidy? Subject: HUD, FHPAP, LTH, THP: all clients FunderRequiring = "HUD" FunderRequiring = "FHPAP" FunderRequiring = "LTH" FunderRequiring = "THP" HMIS Data and Technical Standards, July 30, 2004, Program-Specific Data Element 3.10. See also Section 5.1.3 for treatment of "other" elements. Specify subsidy if answer to "SubsidyType" is 'other'. Subject: HUD, FHPAP, LTH, THP: all clients FunderRequiring = "HUD" FunderRequiring = "FHPAP" FunderRequiring = "LTH" FunderRequiring = "THP" HMIS Data and Technical Standards, July 30, 2004, Program-Specific Data Element 3.11 At exit, Identify the reason why the client left the program. If a client left for multiple reasons, record only the primary reason. Subject: HUD, FHPAP, LTH, THP: all clients FunderRequiring = "HUD" FunderRequiring = "FHPAP" FunderRequiring = "LTH" FunderRequiring = "THP" HMIS Data and Technical Standards, July 30, 2004, Program-Specific Data Element 3.11. See also Section 5.1.3 for treatment of "other" elements. Specify Reason if the answer to "ReasonForLeaving" is 'other'. Subject: HUD, FHPAP, LTH, THP: all clients FunderRequiring = "HUD" FunderRequiring = "FHPAP" FunderRequiring = "LTH" FunderRequiring = "THP" MN addition: long term housing need as client leaves program In your judgment, what type of housing does this client need over the long term, regardless of where they are actually going? ** General housing OR ** Permanent Supportive Housing (see below) Using your professional judgment does the primary householder have a physical, mental, or emotional impairment that is expected to be of long-continued and indefinite duration, and substantially impedes his or her ability to live independently without on-going support services. -If yes, the client is in need of Permanent Supportive Housing. Subject: all clients FunderRequiring = "FHPAP" FunderRequiring = "HUD" FunderRequiring = "LTH" FunderRequiring = "THP" HMIS Data and Technical Standards, July 30, 2004, Program-Specific Data Element 3.14 Determine how the client assesses their health in comparison to other people their age. FunderRequiring = "HUD"; currently optional; may be included on future APR's. Subject: all clients FunderRequiring = "HUD" HMIS Data and Technical Standards, July 30, 2004, Program-Specific Data Element 3.1 Minnesota Model will not use the TotalIncome element, as this is calculable. The minOccurs="0" allows this. HMIS Data and Technical Standards, July 30, 2004, Program-Specific Data Element 3.5 Has the client has been diagnosed with AIDS or has tested positive for HIV? If the client does not provide the information and it is not contained in case manager records, leave the response field blank. Subject: ESG, FHPAP, HUD, LTH: all adults and unacompanied youth FunderRequiring = "ESG" FunderRequiring = "FHPAP" FunderRequiring = "HUD" FunderRequiring = "LTH" FunderRequiring = "THP" HMIS Data and Technical Standards, July 30, 2004, Program-Specific Data Element 3.6 A mental health problem may include serious depression, serious anxiety, hallucinations, violent behavior or thoughts of suicide. HUD suggested question: A mental health problem may include serious depression, serious anxiety, hallucinations, violent behavior or thoughts of suicide. Subject: ESG, FHPAP, HUD, LTH: all adults and unacompanied youth FunderRequiring = "ESG" FunderRequiring = "FHPAP" FunderRequiring = "HUD" FunderRequiring = "LTH" FunderRequiring = "THP" HMIS Data and Technical Standards, July 30, 2004, Program-Specific Data Element 3.6 Is mental health problem expected to be of long-continued and indefinite duration and substantially impede client’s ability to live independently? Subject: ESG, FHPAP, HUD, LTH: all adults and unacompanied youth FunderRequiring = "ESG" FunderRequiring = "FHPAP" FunderRequiring = "HUD" FunderRequiring = "LTH" FunderRequiring = "THP" HMIS Data and Technical Standards, July 30, 2004, Program-Specific Data Element 3.7 Does client have an alcohol or drug abuse problem, or is dually diagnosed? Dually diagnosed here is defined as alcohol abuse and drug abuse HUD suggested question: Do you feel that you have a problem with alcohol? Do you feel that you have a problem with drugs? Subject: ESG, FHPAP, HUD, LTH: all adults and unacompanied youth FunderRequiring = "ESG" FunderRequiring = "FHPAP" FunderRequiring = "HUD" FunderRequiring = "LTH" FunderRequiring = "THP" HMIS Data and Technical Standards, July 30, 2004, Program-Specific Data Element 3.7 Is alcohol or drug abuse problem expected to be of long-continued and indefinite duration and substantially impede client’s ability to live independently? Subject: ESG, FHPAP, HUD, LTH: all adults and unacompanied youth FunderRequiring = "ESG" FunderRequiring = "FHPAP" FunderRequiring = "HUD" FunderRequiring = "LTH" FunderRequiring = "THP" HMIS Data and Technical Standards, July 30, 2004, Program-Specific Data Element 3.8 Is client a victim of domestic violence? Subject: ESG: HUD: All adults and unaccompanied youth. FunderRequiring = "ESG" FunderRequiring = "HUD" HMIS Data and Technical Standards, July 30, 2004, Program-Specific Data Element 3.8 If a client has been a victim of domestic abuse, how long ago did the client have the most recent experience? Subject: HUD: All adults and unaccompanied youth FunderRequiring = "HUD" HMIS Data and Technical Standards, July 30, 2004, Program-Specific Data Element 3.12 Select yes if client is currently working HUD-Optional; may be required in future APR's Subject: All adults and unaccompanied youth HMIS Data and TechnicalStandards, July 30, 2004, Program-Specific Data Element 3.12 If the client is employed, record number of hours client worked last week. HUD-Optional; may be required on future APR's Subject: All adults and unaccompanied youth FunderRequiring = "HUD" HMIS Data and Technical Standards, July 30, 2004, Program-Specific Data Element 3.12 If currently employed, is the work permanent, temporary, or seasonal? Seasonal employment is work that can, by the nature of it, ordinarily only be performed during a certain season in the year. Temporary employment is work for a limited time only or for a specific piece of work and that work will last a short duration. HUD-Optional; may be required on future APR's. Subject: All adults and unaccompanied youth FunderRequiring = "HUD" HMIS Data and Technical Standards, July 30, 2004, Program-Specific Data Element 3.12 If the client is not currently working, select 'yes' if they are currently looking for work. HUD-Optional; may be required on future APR's Subject: All adults and unaccompanied youth FunderRequiring = "HUD" *Minnesota Model addition. Select the level of ability to speak English. FunderRequiring = "Universal-optional" *Minnesota Model addition. Primary language spoken and understood by this person. FunderRequiring = "Universal-optional" *Minnesota Model addition. Another language spoken and understood by this person. FunderRequiring = "Universal-optional" HMIS Data and Technical Standards, July 30, 2004, Program-Specific Data Element 3.13; Is client currently in school or working on a degree or certificate? HUD-Optional, but may be required in future APR's Subject: All adults and unaccompanied youth FunderRequiring = "HUD" HMIS Data and Technical Standards, July 30, 2004, Program-Specific Data Element 3.13 HUD suggested question: Have you received any vocational training or apprenticeship certificates? HUD-Optional, but may be required on future APR's Subject: All adults and unaccompanied youth FunderRequiring = "HUD" HMIS Data and Technical Standards, July 30, 2004, Program-Specific Data Element 3.13; Client's highest level of education HUD suggested question: What is the highest level of school that you have completed? HUD-Optional, but may be required on future APR's Subject: All adults and unaccompanied youth FunderRequiring = "HUD" HMIS Data and Technical Standards, July 30, 2004, Program-Specific Data Element 3.15 Select Yes if the client is pregnant. HUD-Optional, but may be required in future APR's Subject: All females of child-bearing age served. FunderRequiring = "HUD" HMIS Data and Technical Standards, July 30, 2004, Program-Specific Data Element 3.15 If client is pregnant, record due date for the birth of child. HUD-Optional, but may be required in future APR's Subject: All females of child-bearing age served. FunderRequiring = "HUD" HMIS Data and Technical Standards, July 30, 2004, Program-Specific Data Element 3.17 HUD suggested question: Is [name of child] currently enrolled in school? Optional, but may be required in future APR's Subject: All children between 5 and 17 years of age. HMIS Data and Technical Standards, July 30, 2004, Program-Specific Data Element 3.17 HUD suggested question: What is the name of the child’s school(s)? Optional, but may be required in future APR's Subject: All children between 5 and 17 years of age. HMIS Data and Technical Standards, July 30, 2004, Program-Specific Data Element 3.17 Type of school child is enrolled in: public or private/parochial? Optional, but may be required in future APR's Subject: All children between 5 and 17 years of age. HMIS Data and Technical Standards, July 30, 2004, Program-Specific Data Element 3.17; when was client's child last entered in school? If the child is not currently enrolled in school, what date was the child last enrolled in school. If the month is unknown, programs are encouraged to record ‘‘01’’ as a default value. Communities that already have a policy of entering another approximate month may continue this policy. If the year is unknown, programs should leave the data field blank. Optional, but may be required in future APR's Subject: All children between 5 and 17 years of age. HMIS Data and Technical Standards, July 30, 2004, Program-Specific Data Element 3.17; Barrier's to enrolling child in school If the child is not enrolled in school, what problems has the head of household had in getting the child enrolled into school. When identifying the problems the head of household encountered when enrolling the child in school, allow clients to identify multiple reasons for not enrolling the child in school. Optional, but may be required in future APR's Subject: All children between 5 and 17 years of age. HMIS Data and Technical Standards, July 30, 2004, Program-Specific Data Element 3.17. See also Section 5.1.3 for treatment of "other" elements. Text box supplied to allow for text explanation when 'BarrierCode' = 'Other' Optional, but may be required in future APR's Subject: All children between 5 and 17 years of age. HMIS Data and Technical Standards, July 30, 2004, Program-Specific Data Element 3.16 HUD suggestied question: In which military service eras did you serve (choose all that apply)?’’ HUD Requirement Status: Optional Subject: All persons who answered ‘‘Yes’’ to Veterans Status data element. FunderRequiring = "HUD" (optional) HMIS Data and Technical Standards, July 30, 2004, Program-Specific Data Element 3.16 Subject: All persons who answered ‘‘Yes’’ to Veterans Status data element. FunderRequiring = "HUD" (optional) HMIS Data and Technical Standards, July 30, 2004, Program-Specific Data Element 3.16 Select yes if the client served in a war zone, otherwise select no. Subject: All persons who answered ‘‘Yes’’ to Veterans Status data element. FunderRequiring = "HUD" (optional) HMIS Data and Technical Standards, July 30, 2004, Program-Specific Data Element 3.16 Select the war zone the client served in. If client served in more than one war zone, complete multiple instances of 'Veteran" Subject: All persons who answered ‘‘Yes’’ to Veterans Status data element. FunderRequiring = "HUD" (optional) HMIS Data and Technical Standards, July 30, 2004, Program-Specific Data Element 3.16. See also Section 5.1.3 for treatment of "other" elements. Subject: All persons who answered ‘‘Yes’’ to Veterans Status data element. FunderRequiring = "HUD" (optional) HMIS Data and Technical Standards, July 30, 2004, Program-Specific Data Element 3.16 Record the number of months the clients served in the war zone (if applicable). Subject: All persons who answered ‘‘Yes’’ to Veterans Status data element. FunderRequiring = "HUD" 9optional) HMIS Data and Technical Standards, July 30, 2004, Program-Specific Data Element 3.16 Select yes (1) if a client received either a friendly fire or hostile fire in a war zone. 0="no" and 1="yes" as per the Federal HMIS data standard. Subject: All persons who answered ‘‘Yes’’ to Veterans Status data element. FunderRequiring = "HUD" (optional) HMIS Data and Technical Standards, July 30, 2004, Program-Specific Data Element 3.16 Subject: All persons who answered ‘‘Yes’’ to Veterans Status data element. FunderRequiring = "HUD" (optionalO HMIS Data and Technical Standards, July 30, 2004, Program-Specific Data Element 3.16. See also Section 5.1.3 for treatment of "other" elements. Subject: All persons who answered ‘‘Yes’’ to Veterans Status data element. FunderRequiring = "HUD" (optional) HMIS Data and Technical Standards, July 30, 2004, Program-Specific Data Element 3.16 Subject: All persons who answered ‘‘Yes’’ to Veterans Status data element. FunderRequiring = "HUD" (optional) MN addition: Dates of military service MN addition: Select Yes if the person has a disability that has been determined to be service related. FunderRequiring = "LTH" HMIS Data and Technical Standards, July 30, 2004, Program-Specific Data Element 3.1. Subject: All clients served To accommodate reporting for MN funders and the HUD APR, a snapshot of client's monthly income is required at entry, at the end of each reporting period, and at exit. subject: FHPAP, HUD, LTH THP: all clients FunderRequiring = "FHPAP" FunderRequiring = "HUD" FunderRequiring = "LTH" FunderRequiring = "THP" HMIS Data and Technical Standards, July 30, 2004, Program-Specific Data Element 3.2. subject: FHPAP, HUD, LTH THP: all clients FunderRequiring = "FHPAP" FunderRequiring = "HUD" FunderRequiring = "LTH" FunderRequiring = "THP" HMIS Data and Technical Standards, July 30, 2004, Program-Specific Data Element 3.2. See also Section 5.1.3 for treatment of "other" elements. subject: FHPAP, HUD, LTH THP: all clients FunderRequiring = "FHPAP" FunderRequiring = "HUD" FunderRequiring = "LTH" FunderRequiring = "THP" MN addition: Start and end dates for income subject: FHPAP, HUD, LTH THP: all clients FunderRequiring = "FHPAP" FunderRequiring = "HUD" FunderRequiring = "LTH" FunderRequiring = "THP" HMIS Data and Technical Standards, July 30, 2004, Program-Specific Data Element 3.1. Record a 'snapshot' of the client's monthly income. SP: Use "No Financial Resources" if and only if the client has no other records in "Income and Sources AND also no records in "NonCashIncomeAndSources" . Record "No Financial Resources" (if appropriate) for all adults and unaccompanied youth. Enter income in each adult's record. Children within a household: enter payments parents receive on a minor child's behalf (such as disability payments) in the household head's record. Do not enter income from a child's job. subject: FHPAP, HUD, LTH THP: all clients FunderRequiring = "FHPAP" FunderRequiring = "HUD" FunderRequiring = "LTH" FunderRequiring = "THP" HMIS Data and Technical Standards, July 30, 2004, Program-Specific Data Element 3.1. subject: FHPAP, HUD, LTH THP: all clients If client has no income and no noncase income, select "No Financial Resources"; leave the amount blank or enter $0 for the amount FunderRequiring = "FHPAP" FunderRequiring = "HUD" FunderRequiring = "LTH" FunderRequiring = "THP" HMIS Data and Technical Standards, July 30, 2004, Program-Specific Data Element 3.1; amount of montly income subject: FHPAP, HUD, LTH THP: all clients FunderRequiring = "FHPAP" FunderRequiring = "HUD" FunderRequiring = "LTH" FunderRequiring = "THP" HMIS Data and Technical Standards, July 30, 2004, Program-Specific Data Element 3.1. See also Section 5.1.3 for treatment of "other" elements. subject: FHPAP, HUD, LTH THP: all clients FunderRequiring = "FHPAP" FunderRequiring = "HUD" FunderRequiring = "LTH" FunderRequiring = "THP" MN addition: Start and end dates for income subject: FHPAP, HUD, LTH THP: all clients FunderRequiring = "FHPAP" FunderRequiring = "HUD" FunderRequiring = "LTH" FunderRequiring = "THP" HMIS Data and Technical Standards, July 30, 2004, Program-Specific Data Element 3.13.; Select educational degree from list Subject: All adults and unaccompanied youth served. FunderRequiring = "HUD" HMIS Data and Technical Standards, July 30, 2004, Program-Specific Data Element 3.13. See also Section 5.1.3 for treatment of "other" elements. Subject: All adults and unaccompanied youth served. FunderRequiring = "HUD" See HMIS Data Integration Package, Version 2.7, Cumulative Overview, Appendix 1.; Is client homeless by HUD definition? Subject: All adults and unaccompanied youth served. FunderRequiring = "ESGP" FunderRequiring = "HUD" See HMIS Data Integration Package, Version 2.7, Cumulative Overview, Appendix 1. Minnesota Model additional documentation: HUD defines “chronic homelessness” as an unaccompanied homeless adult (NOT a family) with a disabling condition who has either been continuously homeless for a year or more OR has had at least four (4) episodes of homelessness in the past three (3) years. To be considered chronically homeless, persons must have been sleeping in a place not meant for human habitation (e.g., on the streets) or in an emergency homeless shelter during that time. Subject: All adults and unaccompanied youth served. FunderRequiring = "HUD" FunderRequiring="ESGP" MN addition: The State of Minnesota defines as homeless any person, individual, unaccompanied youth or family that is without a permanent place to live that is fit for human habitation.” Doubling-up is considered homeless if that arrangement has persisted less than 1 year. The State of Minnesota defines an individual, unaccompanied youth or family as “Long-Term Homeless” if they are without a home for a year or more OR have had at least four (4) episodes of homelessness in the past three (3) years. Any period of institutionalization or incarceration (including transitional housing, prison/jail, treatment, hospitals, foster care, or refugee camps) shall be excluded when determining the length of time the household has been homeless). Subject: All adults and unaccompanied youth served. FunderRequiring = "ESP" FunderRequiring = "FHPAP" FunderRequiring = "LTH" FunderRequiring = "THP" MN addition: Did the client leave any of the listed facilities in the last 3 months? Select the facility the client left most recently. Subject: All adults and unaccompanied youth served FunderRequiring = "DHS Youth" FunderRequiring = "ESGP" FunderRequiring = "ESP" FunderRequiring = "FHPAP" FunderRequiring = "LTH" FunderRequiring = "THP" MN addition: client's address Subject: LTH: All Household Heads, Singles and Unaccompanied youth Enter current address when household moves into housing; Update when client moves. FunderRequiring = "LTH MN addition. FunderRequiring = "Universal-optional" See HMIS Data Integration Package, Version 2.7, Cumulative Overview, Section 3: VI.11. SP: Service Transaction information subject: HUD, FHPAP, LTH, ESGP, ESP THP: all clients HMIS Data and Technical Standards, July 30, 2004, Program-Specific Data Element 3.9 The date the client begins receiving a specific service within a program. There can be multiple services provided from a single ProgramEntryDate. SP: Whether this could be defaulted to ProgramEntyDate would depend on the nature of the program. Some programs enter only services that do start when the client enters the program, but some also enter services that start at other times during the Client’s service period. FunderRequiring = "HUD" FunderRequiring = "FHPAP" FunderRequiring = "LTH" FunderRequiring = "ESGP" FunderRequiring = "ESP" FunderRequiring = "THP" HMIS Data Integration Package, Version 2.7, Cumulative Overview, Section 3: VI.11. The date the client stops receiving a specific service within a program. There can be multiple services provided from a single ProgramEntryDate SP: Whether this could be defaulted to ProgramExitDate depends on the context. All services should definitely have an end date no later than the ProgramExitDate. However, some services involve costs, which could change. In those cases, an end date will need to be added to a service when the cost changes, and a new service will be added. FunderRequiring = "HUD" FunderRequiring = "FHPAP" FunderRequiring = "LTH" FunderRequiring = "ESGP" FunderRequiring = "ESP" FunderRequiring = "THP" HMIS Data Integration Package, Version 2.7, Cumulative Overview, Section 3: VI.11. As of 12/2007: this element is not used in reporting; no need to upload. HMIS Data Integration Package, Version 2.7, Cumulative Overview, Section 3: VI.11. As of 12/2007: this element is not used in reporting; no need to upload. HMIS Data Integration Package, Version 2.7, Cumulative Overview, Section 3: VI.11. As of 12/2007: this element is not used in reporting; no need to upload. HMIS Data Integration Package, Version 2.7, Cumulative Overview, Section 3: VI.11. Minnesota Model will not use the ServiceUnit element, as it does not precisely indicate subsets of family membership receiving services. HouseholdIDs will instead reveal household vs individual service utilization. The minOccurs="0" allows this. HMIS Data Integration Package, Version 2.7, Cumulative Overview, Section 3: VI.11. Minnesota: List of codes available at http://www.211taxonomy.org/search/keyword Codes used by LTH Program: Resident Services Coordination (BH-6900), defined by LTH program: Housing tenancy support services focused on participant maintaining stable housing (includes watchful eye and 24-hour front desk resident services). Individual and Family Support Services (PH), defined by LTH program: “Case-management light”: Case-management-type support services that help a household to maintain stable housing – use this term when the support services do not meet the intensity and threshold of the 6-point ITF definition of case management (see above). Case/Care Management (PH-1000), defined by LTH program: Intensive, full range of services including assessment, case planning, developing an individualized service plan, with specific goals and expected outcomes, based on the assessments, and connection, coordination, and personal advocacy; also includes monitoring progress, as related to reporting, and follow-up to learn outcomes. (NOTE: This term should only be used if the services go beyond “Individual and Family Support Services [PH]”, below, and meet the ITF definition of case management. [see http://www.mnhousing.gov/idc/groups/public/documents/document/mhfa_006125.pdf ] Common codes used for HUD: Domestic Violence Shelter (BH-1800.1500-100) Homeless Shelter (BH-1800.8500) Homeless Motel Vouchers (BH-1800.8500-300) Transitional Housing/Shelter (BH-1800.9500) Mortgage Payment Assistance (BH-3800.5000) Rent Payment Assistance (BH-3800.7000) Rental Deposit Assistance (BH-3800.7250) Housing Search Assistance (BH-3900.3100) Homeless Permanent Supportive Housing (BH-8400.3000) Utility Bill Payment Assistance (BH-8900.9100) Undesignated Temporary Financial Assistance (BR-8900) Transportation Expense Assistance (BT-8300) Criminal Justice and Legal Services (F) Independent Living Skills Instruction (LR-3200) Employment (ND) Individual and Family Support Services (PH) Case/Care Management (PH-1000) Outreach Programs (TJ-6500.6300) Mental Health Care and Counseling (R) General Medical Care (LE) AIDS/HIV (YF-300.027) Substance Abuse Services (LX) Single Room Occupancy Housing (BH-700.460-80) Educational Programs (HH) FunderRequiring = "HUD" FunderRequiring = "FHPAP" FunderRequiring = "LTH" FunderRequiring = "ESGP" FunderRequiring = "ESP" FunderRequiring = "THP" HMIS Data and Technical Standards, July 30, 2004, Program-Specific Data Element 3.9 Not used by MN Model *Minnesota Model addition. This element added so that the Minnesota Model can identify multiple services for a client SP: Generates the upload "System ID for Services SP: must be unique for all ServiceEvent records SP: Each unique ServiceID must remain constant across imports FunderRequiring = "HUD" FunderRequiring = "FHPAP" FunderRequiring = "LTH" FunderRequiring = "ESGP" FunderRequiring = "ESP" FunderRequiring = "THP" *Minnesota Model addition. Type of residence where assisted; select from a list FunderRequiring = "ESGP" *Minnesota Model addition. County client lives in while receiving assistance. FunderRequiring = "FHPAP" *MN addition. Service Transactions: If service provided has a cash equivalent, enter the cost of service (from Source 1) The only services that require entry of costs for the LTH Program: Rent Payment Assistance (BH-380.700) Rental Deposit Assistance (BH-380.725) If Rental Deposit Assistance is selected, DHS SSF programs must enter the Cost of service Enter cost into Household Head's record only Reports are pulled quarterly; either enter the service once with the full quarterly amount, or enter each month, with the monthly amount, which will be summed in the ART report. FunderRequiring = "FHPAP" FunderRequiring = "LTH" *MN addition. Service Transactions: If service provided has a cash equivalent, enter the cost of service (from Source 2) The only services that require entry of costs for the LTH Program: Rent Payment Assistance (BH-380.700) Rental Deposit Assistance (BH-380.725) If Rental Deposit Assistance is selected, DHS SSF programs must enter the Cost of service Enter cost into Household Head's record only SP: Reports are pulled quarterly; either enter the service once with the full quarterly amount, or enter each month, with the monthly amount, which will be summed in the ART report. FunderRequiring = "FHPAP" FunderRequiring = "LTH" *MN addition. Service Transactions: date of planned follow-up. SP: Not used on ART reports FunderRequiring = "optional" *MN addition. Service Transactions: Did follow-up occur? SP: Not used in ART reports. FunderRequiring = "FHPAP" FunderRequiring = "THP" *MN addition. Service Transactions: First source of funding for service FunderRequiring = "FHPAP" FunderRequiring = "LTH" *MN addition. Service Transactions: Second source of funding for service FunderRequiring = "FHPAP" Data Types twovalplus: Applicable to: Social Security Number Quality Code 1 = Full SSN reported 2 = Partial SSN reported 8 = Don't know or don't have SSN 9 = Refused Destination Tenure 1 = Permanent 2 = Transitional 8 = Don't know 9 = Refused fiveval: Applicable to: Race: Values range from 1 to 5 1 = American Indian or Alaskan Native 2 = Asian 3 = Black or African-American 4 = Native Hawaiian or Other Pacific Islander 5 = White Military Branch 1 = Army 2 = Air Force 3 = Navy 4 = Marines 5 = Other Length of Stay at Prior Residence 1 = One week or less 2 = More than a week, but less than a month 3 = One to three months 4 = More than three months, but less than one year 5 = One year or longer twoval: Applicable to: No/Yes Answer 0 = No 1 = Yes Gender 0 = Female 1 = Male Ethnicity 0 = Non-Hispanic/Latino 1 = Hispanic/Latino Service Unit 0 = Entire household 1 = Individual Identifier Hashing 0 = Not Part of Concatenated Hash in PersonID 1 = Part of Concatenated Hash in PersonID Residence Type 1= Emergency shelter 2 = Transitional housing 3 = Permanent housing 4 = Psychiatric hospital or other psychiatric facility 5 = Substance abuse treatment facility or detox center 6 = Hospital (non-psychiatric) 7 = Jail, prison or juvenile detention facility 8 = Don't know 9 =Refused 10 = Room apartment or house that you rent 11 = Apartment or house that you own 12 = Staying or living in a family member's room, apartment or house 13 =Staying or living in a friend's room, apartment or house 14 = Hotel or motel paid for without emergency shelter voucher 15 = Foster care home or foster care group home 16 = Place not meant for habitation 17 = Other “Not meant for habitation” – includes abandoned and formally condemned housing. “Other-specify” – includes substandard (e.g., lacking functional indoor plumbing or electricity) or overcrowded (more than 1 person per room. How Long Since Client had a Permanent Place to Live 1 =Less than 1 Month 2 = 1 - 3 Months 3 = 3 - 6 Months 4 = 6 - 12 Months 5 =1 - 2 Years 6 = 3 -5 Years 7 = 6 - 8 Years 8 = 9 Years or More 0= 0 (Current Residence) Subsidy type 0 = None 1 = Public Housing 2 = Section 8 3 = S + C 4 = HOME program 5 = HOPWA program 6 = Other housing subsidy 8 = Don't know 9 = Refused HealthStatus 1 = Excellent 2 = Very good 3 = Good 4 = Fair 5 = Poor 8 = Don't know threeval: Applicable to: Export Hashing 1 = No 2 = Yes 3 = Mixed Client Identifier Hashing 1 = No hashing 2 = Individually hashed 3 = Concatenated hash Substance Abuse Problem 1 = Alcohol abuse 2 = Drug abuse Employment Tenure 1 = Permanent 2 = Temporary 3 = Seasonal Domestic Violence How Long 1 = Within the past three months 2 = Three to six months ago 3 = From six to twelve months ago 4 = More than a year ago 8 = Don't know 9 = Refused Highest School Level 0 = No schooling completed 1 = Nursery school to 4th grade 2 = 5th grade or 6th grade 3 = 7th grade or 8th grade 4 = 9th grade 5 = 10th grade 6 = 11th grade 7 = 12th grade, no diploma 8 = High school diploma 9 = GED 10 = Post-secondary school Service Era 1 = Persian Gulf Era (August 1991 - Present) 2 = Post Vietnam (May 1975 - July 1991) 3 = Vietnam Era (August 1964 - April 1975) 4 = Between Korean and Vietnam War (February 1955 - July 1964) 5 = Korean War (June 1950 - January 1955) 6 = Between WWII and Korean War (August 1947 - May 1950) 7 = World War II (September 1940 - July 1947) 8 = Between WWI and WWII (December 1918 - August 1940) 9 = World War I (April 1917 - November 1918) tenval: Applicable to: War Zone 1 = Europe 2 = North Africa 3 = Vietnam 4 = Laos and Cambodia 5 = South China Sea 6 = China, Burma, India 7 = Korea 8 = South Pacific 9 = Persian Gulf 10 =Other Barrier Code 1 = None 2 = Residency requirements 3 = Availability of school records 4 = Birth certificates 5 = Legal guardianship requirements 6 = Transportation 7 = Lack of available preschool programs 8 = Immunization requirements 9 = Physical examination records 10 = Other Discharge Type 1 = Honorable 2 = General 3 = Medical 4 = Bad conduct 5 = Dishonorable 6 = Other elevenval: Reason for leaving 1 = Left for a housing opportunity before completing program 2 = Completed program 3 = Non-payment of rent/occupancy charge 4 = Non-compliance with project 5 = Criminal activity/destruction of property/violence 6 = Reached maximum time allowed by project 7 = Needs could not be met by project 8 = Disagreement with rules/persons 9 = Death 10 = Unknown/disappeared 11 = Other Income Source Code 1 = Earned Income 2 = Unemployment Insurance 3 = Suplemental Security Income or SSI 4 = Social security Disability Income (SSDI) 5 = A Veteran's Disability Payment 6 = Private Disability Insurance 7 = Worker's Compensation 8 = Temporary Assistance for Needy Families (TANF) (or local name) 9 = General Assistance (GA) (or local name) 10 = Retirement Income from Social Security 11 = Veteran's Pension 12 = "Pension from a former job 13 = Child Support 14 = Alimony or other spousal support 15 = Other source 16 = No financial resources Degree Code 0 = None 1 = Associates Degree 2 = Bachelors 3 = Masters 4 = Doctorate 5 = Other graduate/professional degree School Type 1 = Public school 2 = Parochial or other private school Program Type Code 1 = Emergency shelter (e.g. facility or vouchers) 2 = Transitional housing 3 = Permanent supportive housing 4 = Street outreach 5 = Homeless prevention 6 = Services only 7 = Other fourval: Applicable to: Individual/Family Code 1 = Individuals 2 = Families 3 = Individuals and Families 4 = Youth DataCollectionType 1 = Entry 2 = During Program Enrollment 3 = Exit 4 = Followup RelationshipToHeadOfHousehold 1 = Child 2 = Spouse 3 = Other family 4 = Non-married partner Type of Service 1 = Food 2 = Housing placement 3 = Material goods 4 = Temporary housing and other financial aid 5 = Transportation 6 = Consumer assistance and protection 7 = Criminal justice/legal services 8 = Education 9 = Health care 10 = HIV/AIDS-related services 11 = Mental health care/counseling 12 = Substance abuse services 13 = Employment 14 = Case/care management 15 = Day care 16 = Personal enrichment 17 = Outreach 18 = Other No Yes Plus 0 = No 1 = Yes 8 = Don't know 9 = Refused Zip Code Quality Code 1 = Full Zip Recorded 8 = Don't Know 9 = Refused