Optionally allows specification of a deleted record. If record is to be added, do not append this attribute, since "add" is the default, understood behavior.
Optionally allows specification of a deleted record. If record is to be added, do not append this attribute, since "add" is the default, understood behavior.
<xsd:element name="Agency" type="hmis:agency" minOccurs="0" maxOccurs="unbounded"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 2.1" xml:lang="en">To uniquely identify an organization that operates a CoC Program within the CoC.</xsd:documentation><xsd:documentation xml:lang="en">Organization Identifier is mapped to airs:tAgency.Key</xsd:documentation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 2.2" xml:lang="en">To identify the name of each organization that operates a CoC Program within the CoC.</xsd:documentation><xsd:documentation xml:lang="en">Organization Name is mapped to airs:tAgency.Name</xsd:documentation></xsd:annotation></xsd:element>
Optionally allows specification of a deleted record. If record is to be added, do not append this attribute, since "add" is the default, understood behavior.
<xsd:element name="HouseholdID" type="hmis:iDIndex" minOccurs="1"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 3.15" xml:lang="en">To count the number of households served in a program.</xsd:documentation></xsd:annotation></xsd:element>
Optionally allows specification of a deleted record. If record is to be added, do not append this attribute, since "add" is the default, understood behavior.
Optionally allows specification of a deleted record. If record is to be added, do not append this attribute, since "add" is the default, understood behavior.
"Every client receiving services from a contributory CoC program within a CoC is assigned a Personal Identification Number (PIN), which is a permanent and unique number generated by the HMIS application. The PIN is used to obtain an unduplicated count of persons served within a CoC."
Optionally allows specification of a deleted record. If record is to be added, do not append this attribute, since "add" is the default, understood behavior.
<xsd:element name="PersonID" type="hmis:iDIndex"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 3.14" xml:lang="en">"Every client receiving services from a contributory CoC program within a CoC is assigned a Personal Identification Number (PIN), which is a permanent and unique number generated by the HMIS application. The PIN is used to obtain an unduplicated count of persons served within a CoC."</xsd:documentation></xsd:annotation></xsd:element>
<xsd:element name="DateOfBirth" type="hmis:dOBHashingChoice" minOccurs="0"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 3.3" xml:lang="en">The date of birth can be used to calculate the age of persons served at time of program entry or at any point in receiving services.</xsd:documentation></xsd:annotation></xsd:element>
See HMIS XML Version 3.0 Cumulative Package Overview, IV.C..
Source
<xsd:element name="DateOfBirthType" type="hmis:fourValDKRefused2"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 3.3" xml:lang="en">"In another field, record the appropriate date of birth type (data quality code)."</xsd:documentation></xsd:annotation></xsd:element>
<xsd:element name="Ethnicity" type="hmis:fourValDKRefusedHashingChoice" minOccurs="0"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 3.5" xml:lang="en">"Ethnicity is used to count the number of homeless persons who identify themselves as Hispanic or Latino."</xsd:documentation></xsd:annotation></xsd:element>
<xsd:element name="Gender" type="hmis:sevenValDKRefusedHashingChoice" minOccurs="0"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 3.6" xml:lang="en">"To create separate counts of homeless men, women and transgendered clients served."</xsd:documentation></xsd:annotation></xsd:element>
<xsd:element name="LegalFirstName" type="hmis:hashingChoiceStamped" minOccurs="0"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 3.1" xml:lang="en">"The first, middle, last names, and suffix should be collected to support the unique identification of each person served."</xsd:documentation></xsd:annotation></xsd:element>
<xsd:element name="LegalLastName" type="hmis:hashingChoiceStamped" minOccurs="0"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 3.1" xml:lang="en">"The first, middle, last names, and suffix should be collected to support the unique identification of each person served."</xsd:documentation></xsd:annotation></xsd:element>
<xsd:element name="LegalMiddleName" type="hmis:hashingChoiceStamped" minOccurs="0"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 3.1" xml:lang="en">"The first, middle, last names, and suffix should be collected to support the unique identification of each person served."</xsd:documentation></xsd:annotation></xsd:element>
<xsd:element name="LegalSuffix" type="hmis:hashingChoiceStamped" minOccurs="0"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 3.1" xml:lang="en">"The first, middle, last names, and suffix should be collected to support the unique identification of each person served."</xsd:documentation></xsd:annotation></xsd:element>
Optionally allows specification of a deleted record. If record is to be added, do not append this attribute, since "add" is the default, understood behavior.
<xsd:element name="NeedEffectivePeriod" type="hmis:dateRangeOpen" minOccurs="0"><xsd:annotation><xsd:documentation xml:lang="en">When the need is occurring.</xsd:documentation></xsd:annotation></xsd:element>
<xsd:element name="NeedRecordedDate" type="xsd:dateTime" minOccurs="0"><xsd:annotation><xsd:documentation xml:lang="en">This is simply the date the need was determined.</xsd:documentation></xsd:annotation></xsd:element>
Optionally allows specification of a deleted record. If record is to be added, do not append this attribute, since "add" is the default, understood behavior.
Attributes these records to a collecting SiteService. Links to airs:tSiteService.Key
Diagram
Type
xsd:nonNegativeInteger
Properties
content:
simple
minOccurs:
0
Source
<xsd:element name="SiteServiceID" type="xsd:nonNegativeInteger" minOccurs="0"><xsd:annotation><xsd:documentation xml:lang="en">Attributes these records to a collecting SiteService. Links to airs:tSiteService.Key</xsd:documentation></xsd:annotation></xsd:element>
<xsd:element name="ChildEnrollmentStatus" type="hmis:childEnrollmentStatus" minOccurs="0" maxOccurs="unbounded"><xsd:annotation><xsd:documentation xml:lang="en">establishes a sequence for child school enrollment</xsd:documentation></xsd:annotation></xsd:element>
Optionally allows specification of a deleted record. If record is to be added, do not append this attribute, since "add" is the default, understood behavior.
<xsd:element name="ChildEnrollmentStatusID" type="hmis:iDIndex"><xsd:annotation><xsd:documentation xml:lang="en">Establishes a unique ID for the School Enrollment Status sequence.</xsd:documentation></xsd:annotation></xsd:element>
See HMIS XML Version 3.0 Cumulative Package Overview, IV.C..
Source
<xsd:element name="ChildMcKinneyVentoLiaison" type="hmis:fourValDKRefused" minOccurs="0"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.15F" xml:lang="en">"If yes [to ChildCurrentlyEnrolledInSchool], was/is the child connected to the McKinney-Vento Homeless Assistance Act school liaison?"</xsd:documentation></xsd:annotation></xsd:element>
See HMIS XML Version 3.0 Cumulative Package Overview, IV.C..
Source
<xsd:element name="ChildSchoolType" type="hmis:fourValDKRefused2" minOccurs="0"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.15F" xml:lang="en">"If yes [to ChildCurrentlyEnrolledInSchool], type of school."</xsd:documentation></xsd:annotation></xsd:element>
Optionally allows specification of a deleted record. If record is to be added, do not append this attribute, since "add" is the default, understood behavior.
<xsd:element name="BarrierID" type="hmis:iDIndex"><xsd:annotation><xsd:documentation xml:lang="en">Establishes a unique id for the grouping of Barrier Code and BarrierOther.</xsd:documentation></xsd:annotation></xsd:element>
See HMIS XML Version 3.0 Cumulative Package Overview, IV.C..
Source
<xsd:element name="ChildSchoolLastEnrolledDate" type="hmis:date" minOccurs="0"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.15F" xml:lang="en">"If not enrolled, last date of enrollment"</xsd:documentation><xsd:documentation xml:lang="en">If day not known, use "01" for day.</xsd:documentation></xsd:annotation></xsd:element>
<xsd:element name="ChronicHealthCondition" type="hmis:chronicHealthCondition" minOccurs="0" maxOccurs="unbounded"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.5" xml:lang="en">To count the number of persons served with severe health conditions and assess their need for healthcare and other medical services.</xsd:documentation></xsd:annotation></xsd:element>
"For the purposes of this Notice, a chronic health condition means a diagnosed condition that is more than three months in duration and is either not curable or has residual effects that limit daily living and require adaptation in function or special assistance."
See HMIS XML Version 3.0 Cumulative Package Overview, IV.C..
Source
<xsd:element name="HasChronicHealthCondition" type="hmis:fourValDKRefused"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.5" xml:lang="en">"For the purposes of this Notice, a chronic health condition means a diagnosed condition that is more than three months in duration and is either not curable or has residual effects that limit daily living and require adaptation in function or special assistance."</xsd:documentation></xsd:annotation></xsd:element>
"(If yes[to HasChronicHealthCondition]) Currently receiving services or treatment for this condition or received services/treatment prior to exiting the program?
See HMIS XML Version 3.0 Cumulative Package Overview, IV.C..
Source
<xsd:element name="ReceiveChronicHealthServices" type="hmis:fourValDKRefused" minOccurs="0"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.5" xml:lang="en">"(If yes[to HasChronicHealthCondition]) Currently receiving services or treatment for this condition or received services/treatment prior to exiting the program?</xsd:documentation></xsd:annotation></xsd:element>
See HMIS XML Version 3.0 Cumulative Package Overview, IV.C..
Source
<xsd:element name="CurrentlyInSchool" type="hmis:fourValDKRefused" minOccurs="0" maxOccurs="unbounded"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.15B" xml:lang="en">"Currently in school or working on any degree or certificate"</xsd:documentation></xsd:annotation></xsd:element>
<xsd:element name="ContactsMade" type="hmis:contactsMade" minOccurs="0"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.11" xml:lang="en">To record and count the number of contacts with homeless persons by street outreach programs.</xsd:documentation></xsd:annotation></xsd:element>
Optionally allows specification of a deleted record. If record is to be added, do not append this attribute, since "add" is the default, understood behavior.
<xsd:element name="ContactID" type="hmis:iDIndex"><xsd:annotation><xsd:documentation source="Establishes a unique id for the contact" xml:lang="en"/></xsd:annotation></xsd:element>
Because a client may be contacted multiple times on the same day, the response category must include a time stamp (i.e., hour and minute) indicating when the contact occurred in order to uniquely identify each contact. Note that to record a contact in HMIS requires that a client record be established with at least minimal client descriptors included in the Universal Data Elements (e.g., name, gender, race).
See HMIS XML Version 3.0 Cumulative Package Overview, IV.C..
Source
<xsd:element name="ContactDate" type="hmis:contactDate"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.11" xml:lang="en">Because a client may be contacted multiple times on the same day, the response category must include a time stamp (i.e., hour and minute) indicating when the contact occurred in order to uniquely identify each contact. Note that to record a contact in HMIS requires that a client record be established with at least minimal client descriptors included in the Universal Data Elements (e.g., name, gender, race).</xsd:documentation></xsd:annotation></xsd:element>
See HMIS XML Version 3.0 Cumulative Package Overview, IV.C..
Source
<xsd:element name="ContactLocation" type="hmis:contactLocation"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.11" xml:lang="en">For the purpose of the APR, street outreach programs must report the total number of contacts during the operating year by location of contact."</xsd:documentation></xsd:annotation></xsd:element>
<xsd:element name="Degree" type="hmis:degree" minOccurs="0" maxOccurs="unbounded"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.15B" xml:lang="en">If client has received a high school diploma, GED or enrolled in post-secondary education, what degree(s) has the client earned</xsd:documentation></xsd:annotation></xsd:element>
Optionally allows specification of a deleted record. If record is to be added, do not append this attribute, since "add" is the default, understood behavior.
<xsd:element name="DegreeID" type="hmis:iDIndex"><xsd:annotation><xsd:documentation xml:lang="en">Establishes a unique ID for the DegreeCode DegreeOther set.</xsd:documentation></xsd:annotation></xsd:element>
See HMIS XML Version 3.0 Cumulative Package Overview, IV.C..
Source
<xsd:element name="DegreeCode" type="hmis:degreeCode" minOccurs="0" maxOccurs="unbounded"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.15B" xml:lang="en">"If client has received a high school diploma, GED or enrolled in post-secondary education, what degree(s) has the client earned"</xsd:documentation></xsd:annotation></xsd:element>
See HMIS XML Version 3.0 Cumulative Package Overview, IV.C..
Source
<xsd:element name="DegreeOther" type="hmis:string50" minOccurs="0"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.15B. See also Section 5.1.3 for treatment of 'other' elements." xml:lang="en"/></xsd:annotation></xsd:element>
<xsd:element name="Destinations" type="hmis:destinations" minOccurs="0"><xsd:annotation><xsd:documentation xml:lang="en">Groups destination elements into a sequence with ID.</xsd:documentation></xsd:annotation></xsd:element>
Optionally allows specification of a deleted record. If record is to be added, do not append this attribute, since "add" is the default, understood behavior.
<xsd:element name="DestinationID" type="hmis:iDIndex"><xsd:annotation><xsd:documentation xml:lang="en">Establishes a unique ID for the Destinations sequence.</xsd:documentation></xsd:annotation></xsd:element>
See HMIS XML Version 3.0 Cumulative Package Overview, IV.C..
Source
<xsd:element name="DestinationCode" type="hmis:destinationCode" minOccurs="0"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.10" xml:lang="en">Determine the response value that best describes where the client will be staying after they leave the program.</xsd:documentation></xsd:annotation></xsd:element>
See HMIS XML Version 3.0 Cumulative Package Overview, IV.C..
Source
<xsd:element name="DestinationOther" type="hmis:string50" minOccurs="0"><xsd:annotation><xsd:documentation xml:lang="en">If "Other" is chosen for the Destination, place the destination this free text field.</xsd:documentation></xsd:annotation></xsd:element>
Disability condition is needed to help identify clients that meet HUD’s definition of chronically homeless and, depending on the source of program funds, may be required to establish client eligibility to be served by the program.
See HMIS XML Version 3.0 Cumulative Package Overview, IV.C..
Source
<xsd:element name="DisablingCondition" type="hmis:fourValDKRefused" minOccurs="0" maxOccurs="unbounded"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 3.8" xml:lang="en">Disability condition is needed to help identify clients that meet HUD’s definition of chronically homeless and, depending on the source of program funds, may be required to establish client eligibility to be served by the program.</xsd:documentation></xsd:annotation></xsd:element>
<xsd:element name="DevelopmentalDisability" type="hmis:developmentalDisability" minOccurs="0" maxOccurs="unbounded"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.4" xml:lang="en">To count the number of developmentally disabled persons served, determine eligibility for disability benefits, and assess their need for services.</xsd:documentation></xsd:annotation></xsd:element>
"For the purposes of this Notice, a developmental disability means 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."
See HMIS XML Version 3.0 Cumulative Package Overview, IV.C..
Source
<xsd:element name="HasDevelopmentalDisability" type="hmis:fourValDKRefused"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.4" xml:lang="en">"For the purposes of this Notice, a developmental disability means 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."</xsd:documentation></xsd:annotation></xsd:element>
"(If yes[to HasDevelopmentalDisability]) Currently receiving services or treatment for this condition or received services/treatment prior to exiting the program?
See HMIS XML Version 3.0 Cumulative Package Overview, IV.C..
Source
<xsd:element name="ReceiveDevelopmentalDisabilityServicesTreatment" type="hmis:fourValDKRefused" minOccurs="0"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.4" xml:lang="en">"(If yes[to HasDevelopmentalDisability]) Currently receiving services or treatment for this condition or received services/treatment prior to exiting the program?</xsd:documentation></xsd:annotation></xsd:element>
Ascertaining whether a person is a victim of domestic violence is necessary to provide the person with the appropriate services to prevent further abuse and to treat the physical and psychological injuries from prior abuse. Also, ascertaining that a person may be experiencing domestic violence may be important for the safety of program staff and other clients. At the aggregate level, knowing the size of the homeless population that has experienced domestic violence is critical for determining the resources needed to address the problem in this population.
<xsd:element name="DomesticViolence" type="hmis:domesticViolence" minOccurs="0" maxOccurs="unbounded"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.9" xml:lang="en">Ascertaining whether a person is a victim of domestic violence is necessary to provide the person with the appropriate services to prevent further abuse and to treat the physical and psychological injuries from prior abuse. Also, ascertaining that a person may be experiencing domestic violence may be important for the safety of program staff and other clients. At the aggregate level, knowing the size of the homeless population that has experienced domestic violence is critical for determining the resources needed to address the problem in this population.</xsd:documentation></xsd:annotation></xsd:element>
See HMIS XML Version 3.0 Cumulative Package Overview, IV.C..
Source
<xsd:element name="DomesticViolenceSurvivor" type="hmis:fourValDKRefused"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.9" xml:lang="en">"...determine (a) if the client has ever been a victim of domestic violence..."</xsd:documentation></xsd:annotation></xsd:element>
See HMIS XML Version 3.0 Cumulative Package Overview, IV.C..
Source
<xsd:element name="DVOccurred" type="hmis:sixValDKRefused2" minOccurs="0"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.9" xml:lang="en">"...and (b), if so [if 'yes' to DomesticViolenceSurvivor], how long ago did the client have the most recent experience."</xsd:documentation></xsd:annotation></xsd:element>
<xsd:element name="Employment" type="hmis:employment" minOccurs="0" maxOccurs="unbounded"><xsd:annotation><xsd:documentation xml:lang="en">Groups employment elements into a sequence with ID.</xsd:documentation></xsd:annotation></xsd:element>
Optionally allows specification of a deleted record. If record is to be added, do not append this attribute, since "add" is the default, understood behavior.
See HMIS XML Version 3.0 Cumulative Package Overview, IV.C..
Source
<xsd:element name="CurrentlyEmployed" type="hmis:fourValDKRefused" minOccurs="0"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.15A" xml:lang="en">"...determine: (1) if the client is currently employed..."</xsd:documentation></xsd:annotation></xsd:element>
See HMIS XML Version 3.0 Cumulative Package Overview, IV.C..
Source
<xsd:element name="HoursWorkedLastWeek" type="hmis:nonNegativeInteger" minOccurs="0"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.15A" xml:lang="en">"...determine: ... (2) if currently employed, how many hours did the client work in the last week..."</xsd:documentation></xsd:annotation></xsd:element>
See HMIS XML Version 3.0 Cumulative Package Overview, IV.C..
Source
<xsd:element name="EmploymentTenure" type="hmis:fiveValDKRefused" minOccurs="0"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.15A" xml:lang="en">"...if currently employed, is the work permanent, temporary, or seasonal..."</xsd:documentation></xsd:annotation></xsd:element>
See HMIS XML Version 3.0 Cumulative Package Overview, IV.C..
Source
<xsd:element name="LookingForWork" type="hmis:fourValDKRefused" minOccurs="0"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.15A" xml:lang="en">[If unemployed] Is the client looking for work? [If employed] Is the client looking for additional employment or increased hours at their current job?</xsd:documentation></xsd:annotation></xsd:element>
The definition of a client engagement may vary among programs and communities. As a matter of general principle, an engagement is defined as an interactive client relationship that results in a deliberate client assessment.
See HMIS XML Version 3.0 Cumulative Package Overview, IV.C..
Source
<xsd:element name="EngagedDate" type="hmis:date" minOccurs="0" maxOccurs="unbounded"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.12" xml:lang="en">The definition of a client engagement may vary among programs and communities. As a matter of general principle, an engagement is defined as an interactive client relationship that results in a deliberate client assessment.</xsd:documentation></xsd:annotation></xsd:element>
See HMIS XML Version 3.0 Cumulative Package Overview, IV.C..
Source
<xsd:element name="HealthStatus" type="hmis:healthStatus" minOccurs="0" maxOccurs="unbounded"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.15C" xml:lang="en">Determine how the client assesses his/her health (and the health of minors with the household, if applicable) in comparison to other people their age.</xsd:documentation></xsd:annotation></xsd:element>
See HMIS XML Version 3.0 Cumulative Package Overview, IV.C..
Source
<xsd:element name="HighestSchoolLevel" type="hmis:highestSchoolLevel" minOccurs="0" maxOccurs="unbounded"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.15B" xml:lang="en">"Highest level of school completed"</xsd:documentation></xsd:annotation></xsd:element>
<xsd:element name="HIVAIDSStatus" type="hmis:hIVAIDSStatus" minOccurs="0" maxOccurs="unbounded"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.6" xml:lang="en">"To count the number persons served who have been diagnosed with AIDS or have tested positive for HIV and assess their need for services."</xsd:documentation></xsd:annotation></xsd:element>
See HMIS XML Version 3.0 Cumulative Package Overview, IV.C..
Source
<xsd:element name="HasHIVAIDS" type="hmis:fourValDKRefused"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.6" xml:lang="en">"...determine if the client (a) has been diagnosed with AIDS or has tested positive for HIV..."</xsd:documentation></xsd:annotation></xsd:element>
See HMIS XML Version 3.0 Cumulative Package Overview, IV.C..
Source
<xsd:element name="ReceiveHIVAIDSServices" type="hmis:fourValDKRefused" minOccurs="0"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.6" xml:lang="en">"(If yes[to HasHIVAIDS]) Currently receiving services or treatment for this condition or received services/treatment prior to exiting the program?</xsd:documentation></xsd:annotation></xsd:element>
"A new data element, Housing Status has been added in order to distinguish persons who are literally homeless from those who are at imminent risk of losing housing, or in a stable housing situation.".
See HMIS XML Version 3.0 Cumulative Package Overview, IV.C..
Source
<xsd:element name="HousingStatus" type="hmis:sixValDKRefused2" minOccurs="0" maxOccurs="unbounded"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 3.11" xml:lang="en">"A new data element, Housing Status has been added in order to distinguish persons who are literally homeless from those who are at imminent risk of losing housing, or in a stable housing situation.".</xsd:documentation></xsd:annotation></xsd:element>
See HMIS XML Version 3.0 Cumulative Package Overview, IV.C..
Source
<xsd:element name="IncomeLast30Days" type="hmis:fourValDKRefused" minOccurs="0" maxOccurs="unbounded"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.1" xml:lang="en">"Income received from any source in past 30 days?"</xsd:documentation></xsd:annotation></xsd:element>
Income and sources of income are important for determining service needs of people at the time of program entry, determining whether they are accessing all income sources for which they are eligible, and describing the characteristics of the homeless population.
<xsd:element name="IncomeAndSources" type="hmis:incomeAndSources" minOccurs="0"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.1" xml:lang="en">Income and sources of income are important for determining service needs of people at the time of program entry, determining whether they are accessing all income sources for which they are eligible, and describing the characteristics of the homeless population.</xsd:documentation></xsd:annotation></xsd:element>
Optionally allows specification of a deleted record. If record is to be added, do not append this attribute, since "add" is the default, understood behavior.
<xsd:element name="IncomeAndSourceID" type="hmis:iDIndex"><xsd:annotation><xsd:documentation xml:lang="en">Establishes a unique ID for Income and Sources transactions.</xsd:documentation></xsd:annotation></xsd:element>
See HMIS XML Version 3.0 Cumulative Package Overview, IV.C..
Source
<xsd:element name="IncomeSourceCode" type="hmis:incomeSourceCode"><xsd:annotation><xsd:documentation xml:lang="en">2010 HUD HMIS Data and Technical Standards, Program-Specific Data Element 4.1.</xsd:documentation></xsd:annotation></xsd:element>
See HMIS XML Version 3.0 Cumulative Package Overview, IV.C..
Source
<xsd:element name="IncomeSourceOther" type="hmis:string50" minOccurs="0"><xsd:annotation><xsd:documentation xml:lang="en">2010 HUD HMIS Data and Technical Standards, Program-Specific Data Element 4.1.</xsd:documentation></xsd:annotation></xsd:element>
"When a client has income, but does not know the amount, a “Yes” response should be recorded for both the overall income question and the specific source, and the income amount should be left blank. ... To reduce data collection and reporting burden, if a client reports receiving no income from any source in the past 30 days, no additional data collection is required. If a client reports receiving income, an HMIS may be designed such that programs only need to directly enter “yes” for the benefits the clients received. The HMIS software may automatically generate a “No” response for the other income sources. The HMIS may also be designed to automatically generate a “Yes” response where income amounts are recorded. However, since clients often know the source of income, but not the precise amount, users should have the ability to enter “Yes” without recording an exact amount."
See HMIS XML Version 3.0 Cumulative Package Overview, IV.C..
Source
<xsd:element name="ReceivingIncomeSource" type="hmis:twoVal"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.1" xml:lang="en">"When a client has income, but does not know the amount, a “Yes” response should be recorded for both the overall income question and the specific source, and the income amount should be left blank. ... To reduce data collection and reporting burden, if a client reports receiving no income from any source in the past 30 days, no additional data collection is required. If a client reports receiving income, an HMIS may be designed such that programs only need to directly enter “yes” for the benefits the clients received. The HMIS software may automatically generate a “No” response for the other income sources. The HMIS may also be designed to automatically generate a “Yes” response where income amounts are recorded. However, since clients often know the source of income, but not the precise amount, users should have the ability to enter “Yes” without recording an exact amount."</xsd:documentation></xsd:annotation></xsd:element>
"Capturing the receipt of cash income from various sources will help to: ensure all income sources are counted in the calculation of total income; enable program staff to take into account the composition of income in determining needs; determine if people are receiving the mainstream program benefits to which they may be entitled; help clients apply for benefits assistance; and allow analysis of changes in the composition of income between entry and exit from the program and annual changes prior to program exit."
See HMIS XML Version 3.0 Cumulative Package Overview, IV.C..
Source
<xsd:element name="IncomeSourceAmount" type="hmis:nonNegativeInteger" minOccurs="0"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.1" xml:lang="en">"Capturing the receipt of cash income from various sources will help to: ensure all income sources are counted in the calculation of total income; enable program staff to take into account the composition of income in determining needs; determine if people are receiving the mainstream program benefits to which they may be entitled; help clients apply for benefits assistance; and allow analysis of changes in the composition of income between entry and exit from the program and annual changes prior to program exit."</xsd:documentation><xsd:documentation xml:lang="en">This is the amount received in the last 30 days.</xsd:documentation></xsd:annotation></xsd:element>
See HMIS XML Version 3.0 Cumulative Package Overview, IV.C..
Source
<xsd:element name="IncomeTotalMonthly" type="hmis:nonNegativeInteger" minOccurs="0" maxOccurs="unbounded"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.1" xml:lang="en">"the client’s total monthly income (rounded to the nearest U.S. dollar)."</xsd:documentation></xsd:annotation></xsd:element>
See HMIS XML Version 3.0 Cumulative Package Overview, IV.C..
Source
<xsd:element name="LengthOfStayAtPriorResidence" type="hmis:sevenValDKRefused2" minOccurs="0" maxOccurs="unbounded"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 3.9" xml:lang="en">To identify the type of residence and length of stay at that residence just prior to (i.e., the night before) program admission.</xsd:documentation></xsd:annotation></xsd:element>
<xsd:element name="MentalHealthProblem" type="hmis:mentalHealthProblem" minOccurs="0" maxOccurs="unbounded"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.7" xml:lang="en">"To count the number of persons with mental health problems served and to assess the need for treatment."</xsd:documentation></xsd:annotation></xsd:element>
See HMIS XML Version 3.0 Cumulative Package Overview, IV.C..
Source
<xsd:element name="HasMentalHealthProblem" type="hmis:fourValDKRefused"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.7" xml:lang="en">"A mental health problem may include serious depression, serious anxiety, hallucinations, violent behavior or thoughts of suicide."</xsd:documentation></xsd:annotation></xsd:element>
See HMIS XML Version 3.0 Cumulative Package Overview, IV.C..
Source
<xsd:element name="MentalHealthIndefinite" type="hmis:fourValDKRefused" minOccurs="0"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.7" xml:lang="en">"(If yes[to HasMentalHealthProblem]) Expected to be of long-continued and indefinite duration and substantially impairs ability to live independently"</xsd:documentation></xsd:annotation></xsd:element>
"(If yes[to HasMentalHealthProblem]) Currently receiving services or treatment for this condition or received services/treatment prior to exiting the program?
See HMIS XML Version 3.0 Cumulative Package Overview, IV.C..
Source
<xsd:element name="ReceiveMentalHealthServices" type="hmis:fourValDKRefused" minOccurs="0"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.7" xml:lang="en">"(If yes[to HasMentalHealthProblem]) Currently receiving services or treatment for this condition or received services/treatment prior to exiting the program?</xsd:documentation></xsd:annotation></xsd:element>
See HMIS XML Version 3.0 Cumulative Package Overview, IV.C..
Source
<xsd:element name="NonCashBenefitsLast30Days" type="hmis:fourValDKRefused" minOccurs="0" maxOccurs="unbounded"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.2" xml:lang="en">Non-cash benefit received from any source in past 30 days?</xsd:documentation></xsd:annotation></xsd:element>
Non-cash benefits are important to determine whether clients are accessing all mainstream program benefits for which they may be eligible and to ascertain a more complete picture of their economic circumstances.
<xsd:element name="NonCashBenefits" type="hmis:nonCashBenefits" minOccurs="0"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.2" xml:lang="en">Non-cash benefits are important to determine whether clients are accessing all mainstream program benefits for which they may be eligible and to ascertain a more complete picture of their economic circumstances.</xsd:documentation></xsd:annotation></xsd:element>
Optionally allows specification of a deleted record. If record is to be added, do not append this attribute, since "add" is the default, understood behavior.
<xsd:element name="NonCashBenefitID" type="hmis:iDIndex"><xsd:annotation><xsd:documentation xml:lang="en">Establishes a unique ID for the non-cash benefit record.</xsd:documentation></xsd:annotation></xsd:element>
"For each source listed below, determine if the client received any non-cash benefits in the past 30 days. Clients may identify multiple sources of non-cash benefits."
See HMIS XML Version 3.0 Cumulative Package Overview, IV.C..
Source
<xsd:element name="NonCashSourceCode" type="hmis:nonCashSourceCode"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.2" xml:lang="en">"For each source listed below, determine if the client received any non-cash benefits in the past 30 days. Clients may identify multiple sources of non-cash benefits."</xsd:documentation></xsd:annotation></xsd:element>
See HMIS XML Version 3.0 Cumulative Package Overview, IV.C..
Source
<xsd:element name="NonCashSourceOther" type="hmis:string50" minOccurs="0"><xsd:annotation><xsd:documentation xml:lang="en">Free text field to record NonCashSource when "Other" is selected in NonCashSourceCode.</xsd:documentation></xsd:annotation></xsd:element>
"If a client reports receiving non-cash benefits, an HMIS may be designed such that programs only need to directly enter “Yes” for the benefits the clients received. The HMIS software may automatically generate a “No” response for the other non-cash benefit sources."
See HMIS XML Version 3.0 Cumulative Package Overview, IV.C..
Source
<xsd:element name="ReceivingNonCashSource" type="hmis:twoVal"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.2" xml:lang="en">"If a client reports receiving non-cash benefits, an HMIS may be designed such that programs only need to directly enter “Yes” for the benefits the clients received. The HMIS software may automatically generate a “No” response for the other non-cash benefit sources."</xsd:documentation></xsd:annotation></xsd:element>
To identify the former geographic location of persons experiencing homelessness or current geographic location of persons who are at risk of homelessness.
See HMIS XML Version 3.0 Cumulative Package Overview, IV.C..
Source
<xsd:element name="IsLastPermanentZIP" type="hmis:twoVal" minOccurs="0"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 3.10" xml:lang="en">To identify the former geographic location of persons experiencing homelessness or current geographic location of persons who are at risk of homelessness.</xsd:documentation></xsd:annotation></xsd:element>
See HMIS XML Version 3.0 Cumulative Package Overview, IV.C..
Source
<xsd:element name="ZIPQualityCode" type="hmis:zIPQualityCode" minOccurs="0"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 3.10" xml:lang="en">"...record the appropriate zip code type (data quality code)."</xsd:documentation></xsd:annotation></xsd:element>
<xsd:element name="PhysicalDisability" type="hmis:physicalDisability" minOccurs="0" maxOccurs="unbounded"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.3" xml:lang="en">To count the number of physically disabled persons served, determine eligibility for disability benefits, and assess the need for services.</xsd:documentation></xsd:annotation></xsd:element>
"For the purposes of this Notice, a physical disability means 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."
See HMIS XML Version 3.0 Cumulative Package Overview, IV.C..
Source
<xsd:element name="HasPhysicalDisability" type="hmis:fourValDKRefused"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.3" xml:lang="en">"For the purposes of this Notice, a physical disability means 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."</xsd:documentation></xsd:annotation></xsd:element>
"(If yes [to HasPhysicalDisability]) Currently receiving services or treatment for this condition or received services/treatment prior to exiting the program?"
See HMIS XML Version 3.0 Cumulative Package Overview, IV.C..
Source
<xsd:element name="ReceivePhysicalDisabilityServices" type="hmis:fourValDKRefused" minOccurs="0"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.3" xml:lang="en">"(If yes [to HasPhysicalDisability]) Currently receiving services or treatment for this condition or received services/treatment prior to exiting the program?"</xsd:documentation></xsd:annotation></xsd:element>
<xsd:element name="Pregnancy" type="hmis:pregnancy" minOccurs="0" maxOccurs="unbounded"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.15D" xml:lang="en">To determine eligibility for benefits and need for services, and to determine the number of women entering CoC programs while pregnant.</xsd:documentation></xsd:annotation></xsd:element>
Optionally allows specification of a deleted record. If record is to be added, do not append this attribute, since "add" is the default, understood behavior.
<xsd:element name="PregnancyID" type="hmis:iDIndex"><xsd:annotation><xsd:documentation xml:lang="en">Establishes a unique ID for the Pregnancy element sequence.</xsd:documentation></xsd:annotation></xsd:element>
See HMIS XML Version 3.0 Cumulative Package Overview, IV.C..
Source
<xsd:element name="PregnancyStatus" type="hmis:fourValDKRefused"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.15D" xml:lang="en">"In separate fields, determine (a) if a client is pregnant..."</xsd:documentation></xsd:annotation></xsd:element>
Optionally allows specification of a deleted record. If record is to be added, do not append this attribute, since "add" is the default, understood behavior.
<xsd:element name="PriorResidenceID" type="hmis:iDIndex"><xsd:annotation><xsd:documentation xml:lang="en">Establishes a unique ID for the Prior Residence element sequence.</xsd:documentation></xsd:annotation></xsd:element>
See HMIS XML Version 3.0 Cumulative Package Overview, IV.C..
Source
<xsd:element name="PriorResidenceCode" type="hmis:residence" minOccurs="0"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 3.9" xml:lang="en">To identify the type of residence and length of stay at that residence just prior to (i.e., the night before) program admission.</xsd:documentation></xsd:annotation></xsd:element>
<xsd:element name="SubstanceAbuseProblem" type="hmis:substanceAbuseProblem" minOccurs="0" maxOccurs="unbounded"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.8" xml:lang="en">"To count the number of persons served with substance abuse problems and to assess the need for treatment."</xsd:documentation></xsd:annotation></xsd:element>
See HMIS XML Version 3.0 Cumulative Package Overview, IV.C..
Source
<xsd:element name="HasSubstanceAbuseProblem" type="hmis:sixValDKRefused"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.8" xml:lang="en">"...determine (a) if the client has an alcohol or drug abuse problem or both,..."</xsd:documentation></xsd:annotation></xsd:element>
"(If client has a substance abuse problem) Expected to be of long-continued and indefinite duration and substantially impairs ability to live independently"
See HMIS XML Version 3.0 Cumulative Package Overview, IV.C..
Source
<xsd:element name="SubstanceAbuseIndefinite" type="hmis:fourValDKRefused" minOccurs="0"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.8" xml:lang="en">"(If client has a substance abuse problem) Expected to be of long-continued and indefinite duration and substantially impairs ability to live independently"</xsd:documentation></xsd:annotation></xsd:element>
"(If client has a substance abuse problem) Currently receiving services or treatment for this condition or received services/treatment prior to exiting the program?
See HMIS XML Version 3.0 Cumulative Package Overview, IV.C..
Source
<xsd:element name="ReceiveSubstanceAbuseServices" type="hmis:fourValDKRefused" minOccurs="0"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.8" xml:lang="en">"(If client has a substance abuse problem) Currently receiving services or treatment for this condition or received services/treatment prior to exiting the program?</xsd:documentation></xsd:annotation></xsd:element>
To collect a more detailed profile of the homeless veteran’s experience and to determine eligibility for Department of Veterans Affairs (VA) programs and benefits.
<xsd:element name="Veteran" type="hmis:veteran" minOccurs="0" maxOccurs="unbounded"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.15E" xml:lang="en">To collect a more detailed profile of the homeless veteran’s experience and to determine eligibility for Department of Veterans Affairs (VA) programs and benefits.</xsd:documentation></xsd:annotation></xsd:element>
<xsd:element name="MilitaryBranches" type="hmis:militaryBranches" minOccurs="0" maxOccurs="unbounded"><xsd:annotation><xsd:documentation xml:lang="en">Establishes a sequence for MilitaryBranch and MilitaryBranchOther Responses</xsd:documentation></xsd:annotation></xsd:element>
Optionally allows specification of a deleted record. If record is to be added, do not append this attribute, since "add" is the default, understood behavior.
<xsd:element name="MilitaryBranchID" type="hmis:iDIndex"><xsd:annotation><xsd:documentation xml:lang="en">Establishes a unique ID for the Military Branches sequence.</xsd:documentation></xsd:annotation></xsd:element>
See HMIS XML Version 3.0 Cumulative Package Overview, IV.C..
Source
<xsd:element name="MilitaryBranch" type="hmis:sevenValDKRefused2" minOccurs="0"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.15E" xml:lang="en">"Branch of the military"</xsd:documentation></xsd:annotation></xsd:element>
See HMIS XML Version 3.0 Cumulative Package Overview, IV.C..
Source
<xsd:element name="MilitaryServiceDuration" type="hmis:nonNegativeInteger" minOccurs="0" maxOccurs="unbounded"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.15E" xml:lang="en">"Duration of active duty"</xsd:documentation></xsd:annotation></xsd:element>
See HMIS XML Version 3.0 Cumulative Package Overview, IV.C..
Source
<xsd:element name="ServedInWarZone" type="hmis:fourValDKRefused" minOccurs="0" maxOccurs="unbounded"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.15E" xml:lang="en">"Served in a war zone"</xsd:documentation></xsd:annotation></xsd:element>
See HMIS XML Version 3.0 Cumulative Package Overview, IV.C..
Source
<xsd:element name="ServiceEra" type="hmis:serviceEra" minOccurs="0" maxOccurs="unbounded"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.15E" xml:lang="en">"...determine: 1) which military service era did the client serve..."</xsd:documentation></xsd:annotation></xsd:element>
See HMIS XML Version 3.0 Cumulative Package Overview, IV.C..
Source
<xsd:element name="VeteranStatus" type="hmis:fourValDKRefused" minOccurs="0" maxOccurs="unbounded"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 3.7" xml:lang="en">To determine the number of homeless veterans.</xsd:documentation></xsd:annotation></xsd:element>
<xsd:element name="WarZonesServed" type="hmis:warZoneServed" minOccurs="0" maxOccurs="unbounded"><xsd:annotation><xsd:documentation xml:lang="en">Establishes a sequence of War Zone related elements.</xsd:documentation></xsd:annotation></xsd:element>
Optionally allows specification of a deleted record. If record is to be added, do not append this attribute, since "add" is the default, understood behavior.
<xsd:element name="WarZoneID" type="hmis:iDIndex"><xsd:annotation><xsd:documentation xml:lang="en">Establishes a unique ID for the War Zone sequence.</xsd:documentation></xsd:annotation></xsd:element>
See HMIS XML Version 3.0 Cumulative Package Overview, IV.C..
Source
<xsd:element name="MonthsInWarZone" type="hmis:nonNegativeInteger" minOccurs="0"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.15E" xml:lang="en">"If yes [to ServedInWarZone], number of months in war zone"</xsd:documentation></xsd:annotation></xsd:element>
See HMIS XML Version 3.0 Cumulative Package Overview, IV.C..
Source
<xsd:element name="WarZone" type="hmis:warZone" minOccurs="0"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.15E" xml:lang="en">"If yes[to ServedInWarZone], name of war zone"</xsd:documentation></xsd:annotation></xsd:element>
See HMIS XML Version 3.0 Cumulative Package Overview, IV.C..
Source
<xsd:element name="WarZoneOther" type="hmis:string50" minOccurs="0"><xsd:annotation><xsd:documentation xml:lang="en">If yes [to ServedInWarZone] See also Section 5.1.3 for treatment of "other" elements.</xsd:documentation></xsd:annotation></xsd:element>
See HMIS XML Version 3.0 Cumulative Package Overview, IV.C..
Source
<xsd:element name="VocationalTraining" type="hmis:fourValDKRefused" minOccurs="0" maxOccurs="unbounded"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.15B" xml:lang="en">"Received vocational training or apprenticeship certificates"</xsd:documentation></xsd:annotation></xsd:element>
<xsd:element name="Race" type="hmis:sevenValDKRefused2HashingChoiceStatic" minOccurs="0" maxOccurs="unbounded"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 3.4" xml:lang="en">Race is used to count the number of homeless persons who identify themselves within five different racial categories.</xsd:documentation></xsd:annotation></xsd:element>
Optionally allows specification of a deleted record. If record is to be added, do not append this attribute, since "add" is the default, understood behavior.
The existence of a service event outside a SiteServiceParticipation is to be used when the person is not enrolled in a SiteService. One use of this could be for point-in-time counts.
<xsd:element name="ServiceEvent" type="hmis:serviceEvent" minOccurs="0" maxOccurs="unbounded"><xsd:annotation><xsd:documentation>The existence of a service event outside a SiteServiceParticipation is to be used when the person is not enrolled in a SiteService. One use of this could be for point-in-time counts.</xsd:documentation></xsd:annotation></xsd:element>
Optionally allows specification of a deleted record. If record is to be added, do not append this attribute, since "add" is the default, understood behavior.
Links the ServiceEvent to a particular SiteService
Diagram
Type
xsd:nonNegativeInteger
Properties
content:
simple
Source
<xsd:element name="SiteServiceID" type="xsd:nonNegativeInteger"><xsd:annotation><xsd:documentation xml:lang="en">Links the ServiceEvent to a particular SiteService</xsd:documentation></xsd:annotation></xsd:element>
<xsd:element name="HouseholdID" type="hmis:id" minOccurs="0"><xsd:annotation><xsd:documentation xml:lang="en">If the person's entire household is also receiving the service, insert the ID of the household receiving this same ServiceEvent.</xsd:documentation></xsd:annotation></xsd:element>
<xsd:element name="FundingSources" type="hmis:fundingSourcesServiceEvent" minOccurs="0"><xsd:annotation><xsd:documentation xml:lang="en">Tracks the fund that paid for the service event.</xsd:documentation></xsd:annotation></xsd:element>
Optionally allows specification of a deleted record. If record is to be added, do not append this attribute, since "add" is the default, understood behavior.
<xsd:element name="AdvanceOrArrears" type="hmis:twoValBase" minOccurs="0"><xsd:annotation><xsd:documentation xml:lang="en">Optional way to indicate if the service event is for a past expenses</xsd:documentation></xsd:annotation></xsd:element>
Programs must record the amount of HPRP financial assistance provided for each instance of one-time or ongoing financial assistance, as described above. Programs may also choose to record information on financial assistance provided through other sources. However, this should be recorded as a separate transaction in order to distinctly record and track HPRP financial assistance payments.
<xsd:element name="FinancialAssistanceAmount" type="hmis:currency" minOccurs="0"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.13">Programs must record the amount of HPRP financial assistance provided for each instance of one-time or ongoing financial assistance, as described above. Programs may also choose to record information on financial assistance provided through other sources. However, this should be recorded as a separate transaction in order to distinctly record and track HPRP financial assistance payments.</xsd:documentation><xsd:documentation xml:lang="en">Also used for HPRP Financial Assistance</xsd:documentation></xsd:annotation></xsd:element>
<xsd:element name="ServiceEventEffectivePeriod" type="hmis:dateRangeOpen" minOccurs="0"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.15H" xml:lang="en">"Record “date of service” as the two-digit month, two-digit day and four-digit year."</xsd:documentation><xsd:documentation xml:lang="en">This data element allows a period of time for the service, instead of just a single date, which is also valid.</xsd:documentation></xsd:annotation></xsd:element>
"Record “date of service” as the two-digit month, two-digit day and four-digit year."
This data element tracks the date the service was given out. This can be used for tracking date arrearage payments made.
Diagram
Type
xsd:date
Properties
content:
simple
minOccurs:
0
Source
<xsd:element name="ServiceEventProvisionDate" type="xsd:date" minOccurs="0"><xsd:annotation><xsd:documentation source="" xml:lang="en">"Record “date of service” as the two-digit month, two-digit day and four-digit year."</xsd:documentation><xsd:documentation xml:lang="en">This data element tracks the date the service was given out. This can be used for tracking date arrearage payments made.</xsd:documentation></xsd:annotation></xsd:element>
This is simply the date the ServiceEvent was recorded in the HMIS system.
Diagram
Type
xsd:dateTime
Properties
content:
simple
minOccurs:
0
Source
<xsd:element name="ServiceEventRecordedDate" type="xsd:dateTime" minOccurs="0"><xsd:annotation><xsd:documentation xml:lang="en">This is simply the date the ServiceEvent was recorded in the HMIS system.</xsd:documentation></xsd:annotation></xsd:element>
<xsd:element name="ServiceEventNotes" type="hmis:notes" minOccurs="0"><xsd:annotation><xsd:documentation xml:lang="en">Any case manager or other notes regarding the service event.</xsd:documentation></xsd:annotation></xsd:element>
Optionally allows specification of a deleted record. If record is to be added, do not append this attribute, since "add" is the default, understood behavior.
<xsd:element name="HMISServiceEventCode" type="hmis:hMISServiceEvent"><xsd:annotation><xsd:documentation xml:lang="en">Groups HMIS Service Type with free text other response.</xsd:documentation></xsd:annotation></xsd:element>
<xsd:element name="TypeOfService" type="hmis:typeOfService" minOccurs="0"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.15H" xml:lang="en">"To determine the services provided to clients during program participation."</xsd:documentation></xsd:annotation></xsd:element>
To determine the type of financial assistance (including rental assistance,security deposits, utility deposits, utility payments, moving cost assistance, and motel and hotel vouchers) and amount provided during program participation.
<xsd:element name="HPRPFinancialAssistanceServiceEventCode" type="hmis:sixValBase" minOccurs="0"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.13" xml:lang="en">To determine the type of financial assistance (including rental assistance,security deposits, utility deposits, utility payments, moving cost assistance, and motel and hotel vouchers) and amount provided during program participation.</xsd:documentation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.13" xml:lang="en">Response categories for the types of financial assistance are consistent with the requirements of the HPRP Notice (FR-5307-N-01).</xsd:documentation></xsd:annotation></xsd:element>
Element serviceEvent / HPRPRelocationStabilizationServiceEventCode
To determine the housing relocation and stabilization services provided during program participation. This data element is required for HPRP-funded programs in order to complete the QPR and APR.
<xsd:element name="HPRPRelocationStabilizationServiceEventCode" type="hmis:fiveValBase"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.14" xml:lang="en">To determine the housing relocation and stabilization services provided during program participation. This data element is required for HPRP-funded programs in order to complete the QPR and APR.</xsd:documentation></xsd:annotation></xsd:element>
Optionally allows specification of a deleted record. If record is to be added, do not append this attribute, since "add" is the default, understood behavior.
See HMIS XML Version 3.0 Cumulative Package Overview, IV.B.3.e..
Links to airs:tSiteService.Key
Diagram
Type
xsd:nonNegativeInteger
Properties
content:
simple
Source
<xsd:element name="SiteServiceID" type="xsd:nonNegativeInteger"><xsd:annotation><xsd:documentation xml:lang="en">See HMIS XML Version 3.0 Cumulative Package Overview, IV.B.3.e..</xsd:documentation><xsd:documentation xml:lang="en">Links to airs:tSiteService.Key</xsd:documentation></xsd:annotation></xsd:element>
<xsd:element name="ParticipationDates" type="hmis:dateRangeOpen"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 3.12 and 3.13" xml:lang="en">This data element is needed for reporting purposes for all programs and to measure lengths of stay for residential programs.</xsd:documentation></xsd:annotation></xsd:element>
Optionally allows specification of a deleted record. If record is to be added, do not append this attribute, since "add" is the default, understood behavior.
<xsd:element name="ReasonForLeavingID" type="hmis:iDIndex"><xsd:annotation><xsd:documentation xml:lang="en">Establishes a unique ID for the ReasonForLeaving element sequence.</xsd:documentation></xsd:annotation></xsd:element>
See HMIS XML Version 3.0 Cumulative Package Overview, IV.C..
Source
<xsd:element name="ReasonForLeaving" type="hmis:elevenVal" minOccurs="0"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.15G" xml:lang="en">Identify the reason why the client left the program. If a client left for multiple reasons, record only the primary reason.</xsd:documentation></xsd:annotation></xsd:element>
See HMIS XML Version 3.0 Cumulative Package Overview, IV.C..
Source
<xsd:element name="ReasonForLeavingOther" type="hmis:string50" minOccurs="0"><xsd:annotation><xsd:documentation xml:lang="en">Free text field used when "Other" is selected in ReasonForLeaving.</xsd:documentation></xsd:annotation></xsd:element>
"Where data are shared across programs, the SSN greatly improves the process of identifying clients who have been served and allows programs to de-duplicate upon program entry. Second, an important Congressional goal is to increase the use of mainstream programs by homeless persons. To achieve this goal, homeless service providers need the SSN along with the other personal identifiers in order to access mainstream services for theirclients."
<xsd:element name="SocialSecurityNumber" type="hmis:sSNHashingChoice" minOccurs="0"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 3.2" xml:lang="en">"Where data are shared across programs, the SSN greatly improves the process of identifying clients who have been served and allows programs to de-duplicate upon program entry. Second, an important Congressional goal is to increase the use of mainstream programs by homeless persons. To achieve this goal, homeless service providers need the SSN along with the other personal identifiers in order to access mainstream services for theirclients."</xsd:documentation></xsd:annotation></xsd:element>
See HMIS XML Version 3.0 Cumulative Package Overview, IV.C..
Source
<xsd:element name="SocialSecNumberQualityCode" type="hmis:fourValDKRefused2"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 3.2" xml:lang="en">"In another field, record the appropriate SSN type (data quality code)."</xsd:documentation></xsd:annotation></xsd:element>
The 2009 Notice proposes the addition of a set of program descriptor data standards – that is, data to be collected about all homeless assistance and HPRP homelessness prevention programs in the CoC.
<xsd:element name="Service" type="hmis:service" minOccurs="0" maxOccurs="unbounded"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 1.2" xml:lang="en">The 2009 Notice proposes the addition of a set of program descriptor data standards – that is, data to be collected about all homeless assistance and HPRP homelessness prevention programs in the CoC.</xsd:documentation></xsd:annotation></xsd:element>
<xsd:element name="COCCode" type="hmis:string5Base" minOccurs="0"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 2.7" xml:lang="en">To associate each CoC Program with a CoC for HUD reporting purposes.</xsd:documentation></xsd:annotation></xsd:element>
"...record the site configuration type as follows: 1. Single site, single building. Housing units (or service encounters) are at one site, in a single structure. 2. Single site, multiple buildings. Housing units (or service encounters) are at one site, in multiple structures (e.g., single apartment complex with multiple buildings and program units in two or more buildings). 3. Multiple sites. Housing units (or service encounters) are at multiple sites (e.g., scattered-site housing, outreach)."
<xsd:element name="Configuration" minOccurs="0" type="hmis:threeValBase"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 2.6A" xml:lang="en">"...record the site configuration type as follows: 1. Single site, single building. Housing units (or service encounters) are at one site, in a single structure. 2. Single site, multiple buildings. Housing units (or service encounters) are at one site, in multiple structures (e.g., single apartment complex with multiple buildings and program units in two or more buildings). 3. Multiple sites. Housing units (or service encounters) are at multiple sites (e.g., scattered-site housing, outreach)."</xsd:documentation></xsd:annotation></xsd:element>
To differentiate CoC Programs in the HMIS that provide direct services from organizations that do not provide direct services (such as HMIS Lead Agencies, organizations that oversee or support CoC Programs, or software solution providers).
<xsd:element name="DirectServiceCode" type="hmis:twoValBase" minOccurs="0"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 2.5" xml:lang="en">To differentiate CoC Programs in the HMIS that provide direct services from organizations that do not provide direct services (such as HMIS Lead Agencies, organizations that oversee or support CoC Programs, or software solution providers).</xsd:documentation></xsd:annotation></xsd:element>
<xsd:element name="FundingSources" type="hmis:fundingSourcesService" minOccurs="0"><xsd:annotation><xsd:documentation xml:lang="en">Provides a place to assign a set of Federal funding sources to the Service.</xsd:documentation></xsd:annotation></xsd:element>
<xsd:element name="GranteeIdentifier" type="hmis:string10Base" minOccurs="0"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 2.13" xml:lang="en">"All subgrantees of a federal HPRP grantee must identify their projects with the original state or local grantee identifier as assigned by HUD."</xsd:documentation></xsd:annotation></xsd:element>
The revised data standards also state: "These data may also be collected separately for distinct sites within a program, as long as they can be aggregated to the program level.". So, inventory is also included as a subelement of SiteService, so that site-based inventories can be conveyed, though site-based inventory tracking is not required.
Alternatively, each bed can be individually reported using an asset.
<xsd:element name="Inventory" type="hmis:inventory" minOccurs="0" maxOccurs="unbounded"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 2.9" xml:lang="en">To record inventory information for each residential CoC Program in order to produce Housing Inventory data for the CoC application and the AHAR.</xsd:documentation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 2.9" xml:lang="en">The revised data standards also state: "These data may also be collected separately for distinct sites within a program, as long as they can be aggregated to the program level.". So, inventory is also included as a subelement of SiteService, so that site-based inventories can be conveyed, though site-based inventory tracking is not required.</xsd:documentation><xsd:documentation xml:lang="en">Alternatively, each bed can be individually reported using an asset.</xsd:documentation></xsd:annotation></xsd:element>
"This is the date when the HMIS participating bed information first applies (i.e., the date when a change in the number of HMIS participating beds occurs for a program’s Bed and Unit Inventory Record)."
<xsd:element name="HMISParticipationPeriod" type="hmis:dateRangeOpen" minOccurs="0"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 2.9J" xml:lang="en">"This is the date when the HMIS participating bed information first applies (i.e., the date when a change in the number of HMIS participating beds occurs for a program’s Bed and Unit Inventory Record)."</xsd:documentation></xsd:annotation></xsd:element>
Optionally allows specification of a deleted record. If record is to be added, do not append this attribute, since "add" is the default, understood behavior.
<xsd:element name="InventoryID" type="hmis:iDIndex"><xsd:annotation><xsd:documentation xml:lang="en">Unique ID to track each inventory.</xsd:documentation></xsd:annotation></xsd:element>
"Describes the availability of beds based on whether beds are available on a planned basis year-round or seasonally (during a defined period of high demand), or on an ad hoc or temporary basis as demand indicates."
This data element arises from HIC requirements. The Service also indicates whether it primarily serves individuals or families, but this is more specific for inventory counts for the HIC.
"describes the type of program beds based on whether beds are: located in a residential homeless assistance program facility (including cots or mats); provided through a voucher with a hotel or motel; other types of beds"
"(Permanent Supportive Housing Programs Only). The chronic homeless bed status data element is an yes/no flag that tracks whether the beds are available for occupancy for chronically homeless persons as of the inventory start date recorded in 2.1.9G."
To arrive at chronic homelessness inventory from the alternate asset tracking method, one would have to look at the asset assignment's person id, then look for any chronic homeless episodes in their person historical data that overlap the bed stay.
"describes the household type served by beds and units counted in the Bed and Unit Inventory Information data elements"
Source
<xsd:element name="BedInventory" type="hmis:bedCountBase" minOccurs="0"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 2.9D" xml:lang="en">"The bed inventory data element is an integer that tracks the total number of beds available for occupancy as of the inventory start date..."</xsd:documentation></xsd:annotation></xsd:element>
"This data element is an integer that tracks the total number of beds participating in HMIS as of the HMIS participation start date recorded in 2.9J."
Diagram
Type
xsd:nonNegativeInteger
Properties
content:
simple
minOccurs:
0
Source
<xsd:element name="HMISParticipatingBeds" type="xsd:nonNegativeInteger" minOccurs="0"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 2.9I" xml:lang="en">"This data element is an integer that tracks the total number of beds participating in HMIS as of the HMIS participation start date recorded in 2.9J."</xsd:documentation></xsd:annotation></xsd:element>
<xsd:element name="InventoryEffectivePeriod" type="hmis:dateRangeOpen" minOccurs="0"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 2.9G" xml:lang="en">"The inventory effective period constrains when the bed and unit inventory information applies."</xsd:documentation></xsd:annotation></xsd:element>
Used for synchronization purposes to differentiate two sets of inventory for the same period.
Diagram
Type
xsd:dateTime
Properties
content:
simple
Source
<xsd:element name="InventoryRecordedDate" type="xsd:dateTime"><xsd:annotation><xsd:documentation xml:lang="en">Used for synchronization purposes to differentiate two sets of inventory for the same period.</xsd:documentation></xsd:annotation></xsd:element>
"The unit inventory data element is an integer that tracks the total number of units available for occupancy as of the inventory start date recorded in 2.1.9G."
Diagram
Type
xsd:nonNegativeInteger
Properties
content:
simple
minOccurs:
0
Source
<xsd:element name="UnitInventory" type="xsd:nonNegativeInteger" minOccurs="0"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 2.9F" xml:lang="en">"The unit inventory data element is an integer that tracks the total number of units available for occupancy as of the inventory start date recorded in 2.1.9G."</xsd:documentation></xsd:annotation></xsd:element>
<xsd:element name="ResidentialTrackingMethod" type="hmis:threeValBase" minOccurs="0"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 2.12">Record the method used to track the actual nights that a client stays in a program.</xsd:documentation></xsd:annotation></xsd:element>
<xsd:element name="ServiceType" type="hmis:serviceType" minOccurs="0"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 2.8" xml:lang="en">To associate each CoC Program with the specific type of service offered.</xsd:documentation></xsd:annotation></xsd:element>
<xsd:element name="ServiceEffectivePeriod" type="hmis:dateRangeOpen" minOccurs="0"><xsd:annotation><xsd:documentation xml:lang="en">Period of time during which this service is in existence.</xsd:documentation></xsd:annotation></xsd:element>
Simply the date when this Service data was added to the system for synchronization purposes. Required.
Diagram
Type
xsd:dateTime
Properties
content:
simple
Source
<xsd:element name="ServiceRecordedDate" type="xsd:dateTime"><xsd:annotation><xsd:documentation xml:lang="en">Simply the date when this Service data was added to the system for synchronization purposes. Required.</xsd:documentation></xsd:annotation></xsd:element>
<xsd:element name="TargetPopulationA" type="hmis:elevenValBase" minOccurs="0"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 2.10" xml:lang="en">"This information may be used to track bed utilization and service gaps."</xsd:documentation></xsd:annotation></xsd:element>
<xsd:element name="TargetPopulationB" type="hmis:fourValBase" minOccurs="0"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 2.11" xml:lang="en">"To allow HMIS to produce the Housing Inventory data for the for the annual CoC application to HUD."</xsd:documentation></xsd:annotation></xsd:element>
'Site' is simply a wrapper for AIRS' definition of Site, so separate AIRS XML doesn't need to be conveyed with HMIS XML to describe the AIRS Agency/Site/Service model.
See HMIS XML Version 3.0 Cumulative Package Overview, Section IV: B.5.
<xsd:element name="Site" type="hmis:site" minOccurs="0" maxOccurs="unbounded"><xsd:annotation><xsd:documentation xml:lang="en">'Site' is simply a wrapper for AIRS' definition of Site, so separate AIRS XML doesn't need to be conveyed with HMIS XML to describe the AIRS Agency/Site/Service model.</xsd:documentation><xsd:documentation xml:lang="en">See HMIS XML Version 3.0 Cumulative Package Overview, Section IV: B.5.</xsd:documentation></xsd:annotation></xsd:element>
<xsd:element name="AgencyKey" type="xsd:nonNegativeInteger" minOccurs="0"><xsd:annotation><xsd:documentation>This represents ID of parent Agency.</xsd:documentation></xsd:annotation></xsd:element>
A "Site" is, in AIRS XML parlance, the parent of a SiteService; a physical location. This ID links back up to the parent Site.Key.
Diagram
Type
xsd:nonNegativeInteger
Properties
content:
simple
Source
<xsd:element name="SiteID" type="xsd:nonNegativeInteger"><xsd:annotation><xsd:documentation xml:lang="en">A "Site" is, in AIRS XML parlance, the parent of a SiteService; a physical location. This ID links back up to the parent Site.Key.</xsd:documentation></xsd:annotation></xsd:element>
See HMIS XML Version 3.0 Cumulative Package Overview, IV.C..
Source
<xsd:element name="GeographicCode" type="hmis:geographicCode" minOccurs="0"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 2.6C" xml:lang="en">For the principal program service site, record the geocode associated with the geographic location of the site.</xsd:documentation></xsd:annotation></xsd:element>
A physical item that can be assigned to an individual. The two types of assets currently covered by the HMIS Revised Data Standard are housing units and shelter beds, so the generic asset type is extended to make the hMISAsset, which has HMIS-specific asset information. The aggregate counts of these can serve as a proxy for an Inventory, found in Service.
<xsd:element name="HMISAsset" type="hmis:hMISAsset" minOccurs="0" maxOccurs="unbounded"><xsd:annotation><xsd:documentation xml:lang="en">A physical item that can be assigned to an individual. The two types of assets currently covered by the HMIS Revised Data Standard are housing units and shelter beds, so the generic asset type is extended to make the hMISAsset, which has HMIS-specific asset information. The aggregate counts of these can serve as a proxy for an Inventory, found in Service.</xsd:documentation></xsd:annotation></xsd:element>
Optionally allows specification of a deleted record. If record is to be added, do not append this attribute, since "add" is the default, understood behavior.
<xsd:element name="AssetID" type="hmis:iDIndex"><xsd:annotation><xsd:documentation xml:lang="en">Assigns a unique identifier to the particular asset.</xsd:documentation></xsd:annotation></xsd:element>
"Describes the availability of beds based on whether beds are available on a planned basis year-round or seasonally (during a defined period of high demand), or on an ad hoc or temporary basis as demand indicates."
This data element arises from HIC requirements. The Service also indicates whether it primarily serves individuals or families, but this is more specific for inventory counts for the HIC.
"describes the type of program beds based on whether beds are: located in a residential homeless assistance program facility (including cots or mats); provided through a voucher with a hotel or motel; other types of beds"
"(Permanent Supportive Housing Programs Only). The chronic homeless bed status data element is an yes/no flag that tracks whether the beds are available for occupancy for chronically homeless persons as of the inventory start date recorded in 2.1.9G."
To arrive at chronic homelessness inventory from the alternate asset tracking method, one would have to look at the asset assignment's person id, then look for any chronic homeless episodes in their person historical data that overlap the bed stay.
"describes the household type served by beds and units counted in the Bed and Unit Inventory Information data elements"
Source
<xsd:element name="AssetCount" type="hmis:bedCountBase"><xsd:annotation><xsd:documentation xml:lang="en">Quantity of asset tracked. Usually, this will be "1", if assigned to an individual.</xsd:documentation></xsd:annotation></xsd:element>
<xsd:element name="AssetType" type="hmis:twoValBase"><xsd:annotation><xsd:documentation xml:lang="en">Currently, the only asset types are beds or units. If it is not one of these, HUD will not need this asset reported.</xsd:documentation></xsd:annotation></xsd:element>
<xsd:element name="AssetEffectivePeriod" type="hmis:dateRangeOpen" minOccurs="0"><xsd:annotation><xsd:documentation xml:lang="en">Similar to the Inventory Start and End Dates in 2.9G and 2.9H, except this only pertains to one bed/unit.</xsd:documentation></xsd:annotation></xsd:element>
Simply tracks the date and time the asset was entered into the system for synchronization purposes.
Diagram
Type
xsd:dateTime
Properties
content:
simple
Source
<xsd:element name="AssetRecordedDate" type="xsd:dateTime"><xsd:annotation><xsd:documentation xml:lang="en">Simply tracks the date and time the asset was entered into the system for synchronization purposes.</xsd:documentation></xsd:annotation></xsd:element>
<xsd:element name="Assignment" type="hmis:assignment" minOccurs="0" maxOccurs="unbounded"><xsd:annotation><xsd:documentation xml:lang="en">Assigns an asset to a person.</xsd:documentation></xsd:annotation></xsd:element>
Optionally allows specification of a deleted record. If record is to be added, do not append this attribute, since "add" is the default, understood behavior.
<xsd:element name="AssignmentID" type="hmis:iDIndex"><xsd:annotation><xsd:documentation xml:lang="en">Assigns a unique identifier to the assignment of the asset to the person.</xsd:documentation></xsd:annotation></xsd:element>
<xsd:element name="PersonID" type="hmis:id"><xsd:annotation><xsd:documentation xml:lang="en">ID of the Person linked to this asset assignment.</xsd:documentation></xsd:annotation></xsd:element>
<xsd:element name="HouseholdID" type="hmis:id" minOccurs="0" maxOccurs="1"><xsd:annotation><xsd:documentation xml:lang="en">Optional unique identifier of a household associated with this asset assignment. The Assignment.PersonID should identify a member of this household.</xsd:documentation></xsd:annotation></xsd:element>
<xsd:element name="AssignmentPeriod" type="hmis:dateRangeCapped" minOccurs="0" maxOccurs="unbounded"><xsd:annotation><xsd:documentation xml:lang="en">Period of time during which the assignment to the Person/Household is in effect.</xsd:documentation></xsd:annotation></xsd:element>
See HMIS XML Version 3.0 Cumulative Package Overview, IV.C..
Source
<xsd:element name="HousingType" type="hmis:sevenVal" minOccurs="0"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 2.6E" xml:lang="en">For the principal program service site, record the appropriate housing type.</xsd:documentation></xsd:annotation></xsd:element>
Inventory counts aggregate bed and unit info for HUD HMIS reporting. SiteService.Inventory is used for Housing Inventory Chart (HIC) reporting. Alternatively, each bed can be individually reported using an asset.
The revised data stnadards also state: "These data may also be collected separately for distinct sites within a program, as long as they can be aggregated to the program level.". The placement of Inventory, here within SiteService, accomodates conveying site-based inventories. However, this is not required, and Inventory is also included as a subelement of Service, so that non-site-based inventories can be conveyed.
<xsd:element name="Inventory" type="hmis:inventory" minOccurs="0" maxOccurs="unbounded"><xsd:annotation><xsd:documentation xml:lang="en" source="2010 HUD HMIS Data and Technical Standards, Section 2.9">Inventory counts aggregate bed and unit info for HUD HMIS reporting. SiteService.Inventory is used for Housing Inventory Chart (HIC) reporting. Alternatively, each bed can be individually reported using an asset.</xsd:documentation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 2.9" xml:lang="en">The revised data stnadards also state: "These data may also be collected separately for distinct sites within a program, as long as they can be aggregated to the program level.". The placement of Inventory, here within SiteService, accomodates conveying site-based inventories. However, this is not required, and Inventory is also included as a subelement of Service, so that non-site-based inventories can be conveyed.</xsd:documentation></xsd:annotation></xsd:element>
The data standards also track the address of this principal site service. That is located by completing information for the parent Site (referenced by SiteService.SiteID) of the principal Site Service at airs:tSite.PhysicalAddress.
In the data standards, it mentions that "Programs without a principal program service site (e.g., mobile programs such as street outreach and scattered-site housing programs) should record the address of their administrative office." The administrative office location is located at airs:tAgency.AgencyLocation.tSite.PhysicalAddress.
In the data standards, it mentions that "Programs may choose to record the Site Information data element for each site or facility operated by the program.", so even if a Site Service is not the principal SiteService, information in section 2.6 can still be tracked.
<xsd:element name="Principal" type="hmis:twoValBase" minOccurs="0"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 2.6B" xml:lang="en">This yes/no element designates whether this SiteService is the "principal program service site".</xsd:documentation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 2.6B" xml:lang="en">The data standards also track the address of this principal site service. That is located by completing information for the parent Site (referenced by SiteService.SiteID) of the principal Site Service at airs:tSite.PhysicalAddress.</xsd:documentation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 2.6B" xml:lang="en">In the data standards, it mentions that "Programs without a principal program service site (e.g., mobile programs such as street outreach and scattered-site housing programs) should record the address of their administrative office." The administrative office location is located at airs:tAgency.AgencyLocation.tSite.PhysicalAddress.</xsd:documentation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 2.6" xml:lang="en">In the data standards, it mentions that "Programs may choose to record the Site Information data element for each site or facility operated by the program.", so even if a Site Service is not the principal SiteService, information in section 2.6 can still be tracked.</xsd:documentation></xsd:annotation></xsd:element>
<xsd:element name="PITCountSet" type="hmis:pITCountSet" minOccurs="0" maxOccurs="unbounded"><xsd:annotation><xsd:documentation xml:lang="en">Holds a set of PIT Count data collected at the program site level.</xsd:documentation></xsd:annotation></xsd:element>
Optionally allows specification of a deleted record. If record is to be added, do not append this attribute, since "add" is the default, understood behavior.
<xsd:element name="PITCountSetID" type="hmis:iDIndex"><xsd:annotation><xsd:documentation xml:lang="en">Establishes a unique ID for the Pregnancy element sequence.</xsd:documentation></xsd:annotation></xsd:element>
<xsd:element name="HUDWaiverReceived" type="hmis:twoValBase" minOccurs="0"><xsd:annotation><xsd:documentation xml:lang="en">for Point In Time Chart, whether HUD granted a waiver for PIT reporting</xsd:documentation></xsd:annotation></xsd:element>
for Point In Time Chart, date HUD granted a waiver for PIT reporting
Diagram
Type
xsd:date
Properties
content:
simple
minOccurs:
0
Source
<xsd:element name="HUDWaiverDate" type="xsd:date" minOccurs="0"><xsd:annotation><xsd:documentation xml:lang="en">for Point In Time Chart, date HUD granted a waiver for PIT reporting</xsd:documentation></xsd:annotation></xsd:element>
<xsd:element name="HUDWaiverEffectivePeriod" type="dateRangeOpen" minOccurs="0"><xsd:annotation><xsd:documentation xml:lang="en">for Point In Time Chart, date range during which HUD granted waiver for PIT reporting is effective.</xsd:documentation></xsd:annotation></xsd:element>
for Housing Inventory Chart and Point In Time Chart
Diagram
Type
xsd:date
Properties
content:
simple
minOccurs:
0
Source
<xsd:element name="LastPITShelteredCountDate" type="xsd:date" minOccurs="0"><xsd:annotation><xsd:documentation xml:lang="en">for Housing Inventory Chart and Point In Time Chart</xsd:documentation></xsd:annotation></xsd:element>
for Housing Inventory Chart and Point In Time Chart
Diagram
Type
xsd:date
Properties
content:
simple
minOccurs:
0
Source
<xsd:element name="LastPITUnshelteredCountDate" type="xsd:date" minOccurs="0"><xsd:annotation><xsd:documentation xml:lang="en">for Housing Inventory Chart and Point In Time Chart</xsd:documentation></xsd:annotation></xsd:element>
<xsd:element name="PITCounts" type="hmis:pITCounts" minOccurs="0"><xsd:annotation><xsd:documentation xml:lang="en">Holds a series of Pit Count data elements.</xsd:documentation></xsd:annotation></xsd:element>
Within each sheltered and unsheltered category, PIT homeless person counts will be recorded in the following household types:a. Number of persons in households without children;b. Number of persons in households with at least one adult and one child; andc. Number of persons in households with only children. This includes only personsage 17 or under, including unaccompanied youth, adolescent parents and theirchildren, adolescent siblings, or other household configurations composed onlyof children.
Source
<xsd:element name="PITCount" type="hmis:pITCount"><xsd:annotation><xsd:documentation xml:lang="en">for Point In Time Chart</xsd:documentation></xsd:annotation></xsd:element>
<xsd:element name="PITCountEffectivePeriod" type="hmis:dateRangeCapped" minOccurs="0"><xsd:annotation><xsd:documentation xml:lang="en">Date range for which the PIT Counts apply.</xsd:documentation></xsd:annotation></xsd:element>
The date this PIT Count is recorded in the originating system, for synchronization purposes.
Diagram
Type
xsd:date
Properties
content:
simple
Source
<xsd:element name="PITCountRecordedDate" type="xsd:date"><xsd:annotation><xsd:documentation xml:lang="en">The date this PIT Count is recorded in the originating system, for synchronization purposes.</xsd:documentation></xsd:annotation></xsd:element>
<xsd:element name="SiteServiceEffectivePeriod" type="hmis:dateRangeOpen" minOccurs="0"><xsd:annotation><xsd:documentation xml:lang="en">When this SiteService was entered into the system, for synchronization purposes.</xsd:documentation></xsd:annotation></xsd:element>
When this SiteService was entered into the system, for synchronization purposes.
Diagram
Type
xsd:dateTime
Properties
content:
simple
minOccurs:
0
Source
<xsd:element name="SiteServiceRecordedDate" type="xsd:dateTime" minOccurs="0"><xsd:annotation><xsd:documentation xml:lang="en">When this SiteService was entered into the system, for synchronization purposes.</xsd:documentation></xsd:annotation></xsd:element>
For the principal program service site, record the site type as follows: 1. Non-residential: services only. The program only provides supportive services and does not provide overnight accommodations. 2. Residential: special needs and non-special needs. Residential housing (i.e., site that provides overnight accommodation) is located within a building or complex that houses both persons with special needs—e.g., homeless or formerly homeless persons, persons with substance abuseproblems, persons with mental illness, or persons with HIV/AIDS—andpersons without any special needs. 3. Residential: special needs only. Residential housing is located within a building or complex that houses only persons with special needs—e.g., homeless or formerly homeless persons, persons with substance abuse problems, persons with mental illness, persons with HIV/AIDS, persons with a physical disability, and/or elderly persons.
<xsd:element name="SiteServiceType" type="hmis:threeValBase" minOccurs="0"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 2.6D" xml:lang="en">For the principal program service site, record the site type as follows: 1. Non-residential: services only. The program only provides supportive services and does not provide overnight accommodations. 2. Residential: special needs and non-special needs. Residential housing (i.e., site that provides overnight accommodation) is located within a building or complex that houses both persons with special needs—e.g., homeless or formerly homeless persons, persons with substance abuseproblems, persons with mental illness, or persons with HIV/AIDS—andpersons without any special needs. 3. Residential: special needs only. Residential housing is located within a building or complex that houses only persons with special needs—e.g., homeless or formerly homeless persons, persons with substance abuse problems, persons with mental illness, persons with HIV/AIDS, persons with a physical disability, and/or elderly persons.</xsd:documentation></xsd:annotation></xsd:element>
The version number of HMIS XML Schema the XML instance document conforms to (e.g. 3.0).
Source
<xsd:complexType name="sources"><xsd:sequence><xsd:element name="Source" type="hmis:source" minOccurs="1" maxOccurs="unbounded"><xsd:annotation><xsd:documentation xml:lang="en">See HMIS XML Version 3.0 Cumulative Package Overview, IV.A.2..</xsd:documentation></xsd:annotation></xsd:element></xsd:sequence><xsd:attribute name="version" type="hmis:version"><xsd:annotation><xsd:documentation xml:lang="en">The version number of HMIS XML Schema the XML instance document conforms to (e.g. 3.0).</xsd:documentation></xsd:annotation></xsd:attribute></xsd:complexType>
Optionally allows specification of a deleted record. If record is to be added, do not append this attribute, since "add" is the default, understood behavior.
<xsd:complexType name="iDIndex"><xsd:sequence><xsd:choice minOccurs="1" maxOccurs="1"><xsd:element name="IDNum" type="xsd:nonNegativeInteger"><xsd:annotation><xsd:documentation xml:lang="en">See HMIS XML Version 3.0 Cumulative Package Overview, Appendix 1.10.</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="IDStr" type="hmis:string32Base"><xsd:annotation><xsd:documentation xml:lang="en">See HMIS XML Version 3.0 Cumulative Package Overview, Appendix 1.10.</xsd:documentation></xsd:annotation></xsd:element></xsd:choice></xsd:sequence><xsd:attributeGroup ref="hmis:deleteStampGroup"><xsd:annotation><xsd:documentation xml:lang="en">Allows for optional deletion of record with this ID. No other elements should be associated with a deleteStampGroup.</xsd:documentation></xsd:annotation></xsd:attributeGroup></xsd:complexType>
<xsd:simpleType name="twoValBase"><xsd:annotation><xsd:documentation xml:lang="en">twoVal: Applicable to:
No/Yes Answer
0 = No
1 = Yes
Advance or Arrears
0 = Advance
1 = Arrears
Asset Type
0 = Bed
1 = Unit
Chronic Homeless Bed
0 = No
1 = Yes
Direct Service Code
0 = No
1 = Yes
Domestic Violence Shelter Bed
0 = No
1 = Yes
HUD Waiver Received
0 = No
1 = Yes
Inventory Individual Family Bed Type
0 = Family
1 = Individual
Receives McKinney Funding
0 = No
1 = Yes
Region Type
0 = HUD COC
1 = HPRP Entitlement Jurisdiction
Service Unit
0 = Entire household
1 = Individual</xsd:documentation></xsd:annotation><xsd:restriction base="xsd:unsignedInt"><xsd:enumeration value="0"/><xsd:enumeration value="1"/></xsd:restriction></xsd:simpleType>
<xsd:complexType name="export"><xsd:sequence><xsd:element name="ExportID" type="hmis:iDIndex"><xsd:annotation><xsd:documentation xml:lang="en">See HMIS XML Version 3.0 Cumulative Package Overview, Section IV: A.3.</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="ExportDate" type="xsd:dateTime"><xsd:annotation><xsd:documentation xml:lang="en">See HMIS XML Version 3.0 Cumulative Package Overview, Section IV: A.3.</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="ExportPeriod" type="hmis:dateRangeCapped" minOccurs="0"><xsd:annotation><xsd:documentation xml:lang="en">See HMIS XML Version 3.0 Cumulative Package Overview, Section IV: A.3.</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="Agency" type="hmis:agency" minOccurs="0" maxOccurs="unbounded"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 2.1" xml:lang="en">To uniquely identify an organization that operates a CoC Program within the CoC.</xsd:documentation><xsd:documentation xml:lang="en">Organization Identifier is mapped to airs:tAgency.Key</xsd:documentation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 2.2" xml:lang="en">To identify the name of each organization that operates a CoC Program within the CoC.</xsd:documentation><xsd:documentation xml:lang="en">Organization Name is mapped to airs:tAgency.Name</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="Household" type="hmis:household" minOccurs="0" maxOccurs="unbounded"><xsd:annotation><xsd:documentation xml:lang="en">See HMIS XML Version 3.0 Cumulative Package Overview, Section IV: B.2.</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="Person" type="hmis:person" minOccurs="0" maxOccurs="unbounded"><xsd:annotation><xsd:documentation xml:lang="en">See HMIS XML Version 3.0 Cumulative Package Overview, Section IV: B.3.</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="Service" type="hmis:service" minOccurs="0" maxOccurs="unbounded"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 1.2" xml:lang="en">The 2009 Notice proposes the addition of a set of program descriptor data standards – that is, data to be collected about all homeless assistance and HPRP homelessness prevention programs in the CoC.</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="Site" type="hmis:site" minOccurs="0" maxOccurs="unbounded"><xsd:annotation><xsd:documentation xml:lang="en">'Site' is simply a wrapper for AIRS' definition of Site, so separate AIRS XML doesn't need to be conveyed with HMIS XML to describe the AIRS Agency/Site/Service model.</xsd:documentation><xsd:documentation xml:lang="en">See HMIS XML Version 3.0 Cumulative Package Overview, Section IV: B.5.</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="SiteService" type="hmis:siteService" minOccurs="0" maxOccurs="unbounded"><xsd:annotation><xsd:documentation xml:lang="en">See HMIS XML Version 3.0 Cumulative Package Overview, Section IV: B.6.</xsd:documentation></xsd:annotation></xsd:element></xsd:sequence></xsd:complexType>
<xsd:complexType name="dateRangeCapped"><xsd:annotation><xsd:documentation xml:lang="en">A date range, both start and end dates are required.</xsd:documentation></xsd:annotation><xsd:sequence><xsd:element name="StartDate" type="xsd:dateTime"/><xsd:element name="EndDate" type="xsd:dateTime"/></xsd:sequence></xsd:complexType>
<xsd:complexType name="agency"><xsd:complexContent><xsd:extension base="airs:tAgency"><xsd:attributeGroup ref="hmis:deleteStampGroup"><xsd:annotation><xsd:documentation xml:lang="en">Allows for the deletion of an agency. Provide only the airs:tAgency.Key when this is used.</xsd:documentation></xsd:annotation></xsd:attributeGroup></xsd:extension></xsd:complexContent></xsd:complexType>
<xsd:complexType name="household"><xsd:sequence><xsd:element name="HouseholdID" type="hmis:iDIndex" minOccurs="1"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 3.15" xml:lang="en">To count the number of households served in a program.</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="HeadOfHouseholdID" type="hmis:iDIndexStamped" minOccurs="0"><xsd:annotation><xsd:documentation xml:lang="en">See HMIS XML Version 3.0 Cumulative Package Overview, Section IV: B.2.</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="Members" type="hmis:members" minOccurs="0"><xsd:annotation><xsd:documentation xml:lang="en">See HMIS XML Version 3.0 Cumulative Package Overview, Section IV: B.2.</xsd:documentation></xsd:annotation></xsd:element></xsd:sequence></xsd:complexType>
Optionally allows specification of a deleted record. If record is to be added, do not append this attribute, since "add" is the default, understood behavior.
<xsd:complexType name="person"><xsd:sequence><xsd:element name="PersonID" type="hmis:iDIndex"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 3.14" xml:lang="en">"Every client receiving services from a contributory CoC program within a CoC is assigned a Personal Identification Number (PIN), which is a permanent and unique number generated by the HMIS application. The PIN is used to obtain an unduplicated count of persons served within a CoC."</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="DateOfBirth" type="hmis:dOBHashingChoice" minOccurs="0"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 3.3" xml:lang="en">The date of birth can be used to calculate the age of persons served at time of program entry or at any point in receiving services.</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="Ethnicity" type="hmis:fourValDKRefusedHashingChoice" minOccurs="0"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 3.5" xml:lang="en">"Ethnicity is used to count the number of homeless persons who identify themselves as Hispanic or Latino."</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="Gender" type="hmis:sevenValDKRefusedHashingChoice" minOccurs="0"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 3.6" xml:lang="en">"To create separate counts of homeless men, women and transgendered clients served."</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="LegalFirstName" type="hmis:hashingChoiceStamped" minOccurs="0"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 3.1" xml:lang="en">"The first, middle, last names, and suffix should be collected to support the unique identification of each person served."</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="LegalLastName" type="hmis:hashingChoiceStamped" minOccurs="0"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 3.1" xml:lang="en">"The first, middle, last names, and suffix should be collected to support the unique identification of each person served."</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="LegalMiddleName" type="hmis:hashingChoiceStamped" minOccurs="0"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 3.1" xml:lang="en">"The first, middle, last names, and suffix should be collected to support the unique identification of each person served."</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="LegalSuffix" type="hmis:hashingChoiceStamped" minOccurs="0"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 3.1" xml:lang="en">"The first, middle, last names, and suffix should be collected to support the unique identification of each person served."</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="Need" type="hmis:need" minOccurs="0" maxOccurs="unbounded"><xsd:annotation><xsd:documentation xml:lang="en">See HMIS XML Version 3.0 Cumulative Package Overview, Section IV: B.3.e.i..</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="OtherNames" type="hmis:otherNames" minOccurs="0" maxOccurs="unbounded"><xsd:annotation><xsd:documentation xml:lang="en">Aliases, nicknames, non-legal names. See HMIS XML Version 3.0 Cumulative Package Overview, IV.B.3.a..</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="PersonHistorical" type="hmis:personHistorical" minOccurs="0" maxOccurs="unbounded"><xsd:annotation><xsd:documentation xml:lang="en">See HMIS XML Version 3.0 Cumulative Package Overview, Section IV: B.3.b..</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="Race" type="hmis:sevenValDKRefused2HashingChoiceStatic" minOccurs="0" maxOccurs="unbounded"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 3.4" xml:lang="en">Race is used to count the number of homeless persons who identify themselves within five different racial categories.</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="ReleaseOfInformation" type="hmis:releaseOfInformation" minOccurs="0" maxOccurs="unbounded"><xsd:annotation><xsd:documentation xml:lang="en">See HMIS XML Version 3.0 Cumulative Package Overview, Section IV: B.3.c..</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="ServiceEvent" type="hmis:serviceEvent" minOccurs="0" maxOccurs="unbounded"><xsd:annotation><xsd:documentation>The existence of a service event outside a SiteServiceParticipation is to be used when the person is not enrolled in a SiteService. One use of this could be for point-in-time counts.</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="SiteServiceParticipation" type="hmis:siteServiceParticipation" minOccurs="0" maxOccurs="unbounded"><xsd:annotation><xsd:documentation xml:lang="en">See HMIS XML Version 3.0 Cumulative Package Overview, Section IV: B.3.e..</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="SocialSecurityNumber" type="hmis:sSNHashingChoice" minOccurs="0"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 3.2" xml:lang="en">"Where data are shared across programs, the SSN greatly improves the process of identifying clients who have been served and allows programs to de-duplicate upon program entry. Second, an important Congressional goal is to increase the use of mainstream programs by homeless persons. To achieve this goal, homeless service providers need the SSN along with the other personal identifiers in order to access mainstream services for theirclients."</xsd:documentation></xsd:annotation></xsd:element></xsd:sequence></xsd:complexType>
<xsd:complexType name="dOBHashingChoice"><xsd:sequence><xsd:choice><xsd:element name="Unhashed" type="hmis:dateStatic" minOccurs="0"/><xsd:element name="Hashed" type="hmis:string50Base" minOccurs="0"/></xsd:choice><xsd:element name="DateOfBirthType" type="hmis:fourValDKRefused2"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 3.3" xml:lang="en">"In another field, record the appropriate date of birth type (data quality code)."</xsd:documentation></xsd:annotation></xsd:element></xsd:sequence></xsd:complexType>
See HMIS XML Version 3.0 Cumulative Package Overview, IV.C..
Source
<xsd:complexType name="dateStatic"><xsd:annotation><xsd:documentation xml:lang="en">ISO date, without timestamp. Different from hmis:date, as staticDate has no "hmis:dateEffective" attribute.</xsd:documentation></xsd:annotation><xsd:simpleContent><xsd:extension base="xsd:date"><xsd:attributeGroup ref="hmis:dateStampGroupStatic"/></xsd:extension></xsd:simpleContent></xsd:complexType>
fourValDKRefused2: Applicable to:Date of Birth Type 1 = Full DOB Reported 2 = Approximate or Partial DOB Reported 8 = Don’t Know 9 = Refused School Type 1 = Public school 2 = Parochial or other private school 8 = Don’t know 9 = RefusedSocial Security Number Quality Code 1 = Full SSN Reported 2 = Partial SSN Reported 8 = Don't Know or Don't have SSN 9 = Refused
<xsd:simpleType name="fourValDKRefused2Base"><xsd:annotation><xsd:documentation xml:lang="en">fourValDKRefused2: Applicable to:
Date of Birth Type
1 = Full DOB Reported
2 = Approximate or Partial DOB Reported
8 = Don’t Know
9 = Refused
School Type
1 = Public school
2 = Parochial or other private school
8 = Don’t know
9 = Refused
Social Security Number Quality Code
1 = Full SSN Reported
2 = Partial SSN Reported
8 = Don't Know or Don't have SSN
9 = Refused</xsd:documentation></xsd:annotation><xsd:restriction base="xsd:unsignedInt"><xsd:enumeration value="1"/><xsd:enumeration value="2"/><xsd:enumeration value="8"/><xsd:enumeration value="9"/></xsd:restriction></xsd:simpleType>
<xsd:complexType name="need"><xsd:sequence><xsd:element name="NeedID" type="hmis:iDIndex"><xsd:annotation><xsd:documentation xml:lang="en">See HMIS XML Version 3.0 Cumulative Package Overview, IV.B.3.f..</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="SiteServiceID" type="xsd:nonNegativeInteger"><xsd:annotation><xsd:documentation xml:lang="en">See HMIS XML Version 3.0 Cumulative Package Overview, IV.B.3.f..</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="ServiceEventID" type="hmis:id" minOccurs="0" maxOccurs="unbounded"><xsd:annotation><xsd:documentation xml:lang="en">See HMIS XML Version 3.0 Cumulative Package Overview, IV.B.3.f..</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="NeedEffectivePeriod" type="hmis:dateRangeOpen" minOccurs="0"><xsd:annotation><xsd:documentation xml:lang="en">When the need is occurring.</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="NeedRecordedDate" type="xsd:dateTime" minOccurs="0"><xsd:annotation><xsd:documentation xml:lang="en">This is simply the date the need was determined.</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="NeedStatus" type="hmis:threeValBase"><xsd:annotation><xsd:documentation xml:lang="en">See HMIS XML Version 3.0 Cumulative Package Overview, IV.B.3.f..</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="Taxonomy" type="airs:tTaxonomy" minOccurs="0"><xsd:annotation><xsd:documentation xml:lang="en">See HMIS XML Version 3.0 Cumulative Package Overview, IV.B.3.f..</xsd:documentation></xsd:annotation></xsd:element></xsd:sequence></xsd:complexType>
<xsd:complexType name="dateRangeOpen"><xsd:annotation><xsd:documentation xml:lang="en">A date range, but either start or end date is optional.</xsd:documentation></xsd:annotation><xsd:sequence minOccurs="0"><xsd:element name="StartDate" type="xsd:dateTime" minOccurs="0"/><xsd:element name="EndDate" type="xsd:dateTime" minOccurs="0"/></xsd:sequence></xsd:complexType>
threeVal: Applicable to: Bed Availability 1 = Year-round 2 = Seasonal 3 = OverflowBed Type 1 = Facility-based 2 = Voucher 3 = Other Bed Status 1 = Current - Been in use for over a year (Current: inventory start date before applicable date - 1 year) 2 = New. Less than a year old (New: Inventory start date > applicable date - 1 year) 3 = Under Development . Under Dev: Inventory start date > applicable date )Export Hashing 1 = No 2 = Yes 3 = MixedLocation of Contact 1 = Place not meant for habitation (e.g. vehicle, abandoned building, bus/train/subway station/airport or anywhere outside that is not a Homeless Connect-type event) 2 = Service setting, non-residential (e.g. Homeless Connect-type event, drop in center, day services center, soup kitchen, etc.) 3 = Service setting, residential (e.g. emergency, transitional or permanent housing; treatment facility, including health, mental health, or substance abuse clinic or hospital; jail, prison, or juvenile detention facility; family or friend’s room, apartment, condo, or house; foster care or group home)Method for Tracking Residential Program HMIS Utilization 0 = Program Entry and Exit Date Comparison 1 = Bed Management Model 2 = Service Transaction ModelNeed Status 1 = Logged 2 = Lapsed 3 = Met PIT Household Type 1 = Households without children 2 = Households with at least one adult and one child 3 = Households with only childrenProgram Site Configuration Type 1 = Single site, single building 2 = Single site, multiple buildings 3 = Multiple sitesSite Type/SiteService Type 1 = Non-residential: services only. 2 = Residential: special needs and non-special needs. 3 = Residential: special needs only.
<xsd:simpleType name="threeValBase"><xsd:annotation><xsd:documentation xml:lang="en">threeVal: Applicable to:
Bed Availability
1 = Year-round
2 = Seasonal
3 = Overflow
Bed Type
1 = Facility-based
2 = Voucher
3 = Other
Bed Status
1 = Current - Been in use for over a year (Current: inventory start date before applicable date - 1 year)
2 = New. Less than a year old (New: Inventory start date > applicable date - 1 year)
3 = Under Development . Under Dev: Inventory start date > applicable date )
Export Hashing
1 = No
2 = Yes
3 = Mixed
Location of Contact
1 = Place not meant for habitation (e.g. vehicle, abandoned building, bus/train/subway
station/airport or anywhere outside that is not a Homeless
Connect-type event)
2 = Service setting, non-residential (e.g. Homeless Connect-type event, drop in center,
day services center, soup kitchen, etc.)
3 = Service setting, residential (e.g. emergency, transitional or permanent housing;
treatment facility, including health, mental health, or substance abuse clinic or
hospital; jail, prison, or juvenile detention facility; family or friend’s room,
apartment, condo, or house; foster care or group home)
Method for Tracking Residential Program HMIS Utilization
0 = Program Entry and Exit Date Comparison
1 = Bed Management Model
2 = Service Transaction Model
Need Status
1 = Logged
2 = Lapsed
3 = Met
PIT Household Type
1 = Households without children
2 = Households with at least one adult and one child
3 = Households with only children
Program Site Configuration Type
1 = Single site, single building
2 = Single site, multiple buildings
3 = Multiple sites
Site Type/SiteService Type
1 = Non-residential: services only.
2 = Residential: special needs and non-special needs.
3 = Residential: special needs only.</xsd:documentation></xsd:annotation><xsd:restriction base="xsd:unsignedInt"><xsd:minInclusive value="1"/><xsd:maxInclusive value="3"/></xsd:restriction></xsd:simpleType>
<xsd:complexType name="personHistorical"><xsd:sequence><xsd:element name="PersonHistoricalID" type="hmis:iDIndex"><xsd:annotation><xsd:documentation xml:lang="en">See HMIS XML Version 3.0 Cumulative Package Overview, Section IV: B.3.b..</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="SiteServiceID" type="xsd:nonNegativeInteger" minOccurs="0"><xsd:annotation><xsd:documentation xml:lang="en">Attributes these records to a collecting SiteService. Links to airs:tSiteService.Key</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="ChildEnrollmentStatus" type="hmis:childEnrollmentStatus" minOccurs="0" maxOccurs="unbounded"><xsd:annotation><xsd:documentation xml:lang="en">establishes a sequence for child school enrollment</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="ChronicHealthCondition" type="hmis:chronicHealthCondition" minOccurs="0" maxOccurs="unbounded"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.5" xml:lang="en">To count the number of persons served with severe health conditions and assess their need for healthcare and other medical services.</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="CurrentlyInSchool" type="hmis:fourValDKRefused" minOccurs="0" maxOccurs="unbounded"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.15B" xml:lang="en">"Currently in school or working on any degree or certificate"</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="ContactsMade" type="hmis:contactsMade" minOccurs="0"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.11" xml:lang="en">To record and count the number of contacts with homeless persons by street outreach programs.</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="Degree" type="hmis:degree" minOccurs="0" maxOccurs="unbounded"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.15B" xml:lang="en">If client has received a high school diploma, GED or enrolled in post-secondary education, what degree(s) has the client earned</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="Destinations" type="hmis:destinations" minOccurs="0"><xsd:annotation><xsd:documentation xml:lang="en">Groups destination elements into a sequence with ID.</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="DisablingCondition" type="hmis:fourValDKRefused" minOccurs="0" maxOccurs="unbounded"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 3.8" xml:lang="en">Disability condition is needed to help identify clients that meet HUD’s definition of chronically homeless and, depending on the source of program funds, may be required to establish client eligibility to be served by the program.</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="DevelopmentalDisability" type="hmis:developmentalDisability" minOccurs="0" maxOccurs="unbounded"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.4" xml:lang="en">To count the number of developmentally disabled persons served, determine eligibility for disability benefits, and assess their need for services.</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="DomesticViolence" type="hmis:domesticViolence" minOccurs="0" maxOccurs="unbounded"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.9" xml:lang="en">Ascertaining whether a person is a victim of domestic violence is necessary to provide the person with the appropriate services to prevent further abuse and to treat the physical and psychological injuries from prior abuse. Also, ascertaining that a person may be experiencing domestic violence may be important for the safety of program staff and other clients. At the aggregate level, knowing the size of the homeless population that has experienced domestic violence is critical for determining the resources needed to address the problem in this population.</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="Employment" type="hmis:employment" minOccurs="0" maxOccurs="unbounded"><xsd:annotation><xsd:documentation xml:lang="en">Groups employment elements into a sequence with ID.</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="EngagedDate" type="hmis:date" minOccurs="0" maxOccurs="unbounded"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.12" xml:lang="en">The definition of a client engagement may vary among programs and communities. As a matter of general principle, an engagement is defined as an interactive client relationship that results in a deliberate client assessment.</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="HealthStatus" type="hmis:healthStatus" minOccurs="0" maxOccurs="unbounded"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.15C" xml:lang="en">Determine how the client assesses his/her health (and the health of minors with the household, if applicable) in comparison to other people their age.</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="HighestSchoolLevel" type="hmis:highestSchoolLevel" minOccurs="0" maxOccurs="unbounded"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.15B" xml:lang="en">"Highest level of school completed"</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="HIVAIDSStatus" type="hmis:hIVAIDSStatus" minOccurs="0" maxOccurs="unbounded"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.6" xml:lang="en">"To count the number persons served who have been diagnosed with AIDS or have tested positive for HIV and assess their need for services."</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="HousingStatus" type="hmis:sixValDKRefused2" minOccurs="0" maxOccurs="unbounded"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 3.11" xml:lang="en">"A new data element, Housing Status has been added in order to distinguish persons who are literally homeless from those who are at imminent risk of losing housing, or in a stable housing situation.".</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="HUDChronicHomeless" type="hmis:twoVal" minOccurs="0" maxOccurs="unbounded"><xsd:annotation><xsd:documentation xml:lang="en">See HMIS XML Version 3.0 Cumulative Package Overview, IV.B.3.B.</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="HUDHomelessEpisodes" type="hmis:dateRangeOpen" minOccurs="0" maxOccurs="unbounded"><xsd:annotation><xsd:documentation xml:lang="en">See HMIS XML Version 3.0 Cumulative Package Overview, IV.B.3.B.</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="IncomeLast30Days" type="hmis:fourValDKRefused" minOccurs="0" maxOccurs="unbounded"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.1" xml:lang="en">"Income received from any source in past 30 days?"</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="IncomeAndSources" type="hmis:incomeAndSources" minOccurs="0"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.1" xml:lang="en">Income and sources of income are important for determining service needs of people at the time of program entry, determining whether they are accessing all income sources for which they are eligible, and describing the characteristics of the homeless population.</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="IncomeTotalMonthly" type="hmis:nonNegativeInteger" minOccurs="0" maxOccurs="unbounded"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.1" xml:lang="en">"the client’s total monthly income (rounded to the nearest U.S. dollar)."</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="LengthOfStayAtPriorResidence" type="hmis:sevenValDKRefused2" minOccurs="0" maxOccurs="unbounded"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 3.9" xml:lang="en">To identify the type of residence and length of stay at that residence just prior to (i.e., the night before) program admission.</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="MentalHealthProblem" type="hmis:mentalHealthProblem" minOccurs="0" maxOccurs="unbounded"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.7" xml:lang="en">"To count the number of persons with mental health problems served and to assess the need for treatment."</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="NonCashBenefitsLast30Days" type="hmis:fourValDKRefused" minOccurs="0" maxOccurs="unbounded"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.2" xml:lang="en">Non-cash benefit received from any source in past 30 days?</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="NonCashBenefits" type="hmis:nonCashBenefits" minOccurs="0"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.2" xml:lang="en">Non-cash benefits are important to determine whether clients are accessing all mainstream program benefits for which they may be eligible and to ascertain a more complete picture of their economic circumstances.</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="PersonAddress" type="hmis:personAddress" minOccurs="0" maxOccurs="unbounded"><xsd:annotation><xsd:documentation xml:lang="en">See HMIS XML Version 3.0 Cumulative Package Overview, IV.B.3.B.</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="PersonEmail" type="hmis:email" minOccurs="0" maxOccurs="unbounded"><xsd:annotation><xsd:documentation xml:lang="en">See HMIS XML Version 3.0 Cumulative Package Overview, IV.B.3.B.</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="PersonPhoneNumber" type="hmis:phoneNumber" minOccurs="0" maxOccurs="unbounded"><xsd:annotation><xsd:documentation xml:lang="en">See HMIS XML Version 3.0 Cumulative Package Overview, IV.B.3.B.</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="PhysicalDisability" type="hmis:physicalDisability" minOccurs="0" maxOccurs="unbounded"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.3" xml:lang="en">To count the number of physically disabled persons served, determine eligibility for disability benefits, and assess the need for services.</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="Pregnancy" type="hmis:pregnancy" minOccurs="0" maxOccurs="unbounded"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.15D" xml:lang="en">To determine eligibility for benefits and need for services, and to determine the number of women entering CoC programs while pregnant.</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="PriorResidence" type="hmis:priorResidence" minOccurs="0" maxOccurs="unbounded"><xsd:annotation><xsd:documentation xml:lang="en">Groups PriorResidence Codes with PriorResidenceOther responses.</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="SubstanceAbuseProblem" type="hmis:substanceAbuseProblem" minOccurs="0" maxOccurs="unbounded"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.8" xml:lang="en">"To count the number of persons served with substance abuse problems and to assess the need for treatment."</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="Veteran" type="hmis:veteran" minOccurs="0" maxOccurs="unbounded"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.15E" xml:lang="en">To collect a more detailed profile of the homeless veteran’s experience and to determine eligibility for Department of Veterans Affairs (VA) programs and benefits.</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="VocationalTraining" type="hmis:fourValDKRefused" minOccurs="0" maxOccurs="unbounded"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.15B" xml:lang="en">"Received vocational training or apprenticeship certificates"</xsd:documentation></xsd:annotation></xsd:element></xsd:sequence></xsd:complexType>
<xsd:complexType name="childEnrollmentStatus"><xsd:sequence><xsd:element name="ChildEnrollmentStatusID" type="hmis:iDIndex"><xsd:annotation><xsd:documentation xml:lang="en">Establishes a unique ID for the School Enrollment Status sequence.</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="ChildCurrentlyEnrolledInSchool" type="hmis:fourValDKRefused" minOccurs="0"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.15F" xml:lang="en">"Current enrollment status"</xsd:documentation></xsd:annotation></xsd:element><xsd:choice><xsd:group ref="hmis:childEnrolledYes"><xsd:annotation><xsd:documentation xml:lang="en">Use this group if the child is currently enrolled in school.</xsd:documentation></xsd:annotation></xsd:group><xsd:group ref="hmis:childEnrolledNo"><xsd:annotation><xsd:documentation xml:lang="en">Use this group if the child is not currently enrolled in school.</xsd:documentation></xsd:annotation></xsd:group></xsd:choice></xsd:sequence></xsd:complexType>
<xsd:complexType name="barrier"><xsd:sequence><xsd:element name="BarrierID" type="hmis:iDIndex"><xsd:annotation><xsd:documentation xml:lang="en">Establishes a unique id for the grouping of Barrier Code and BarrierOther.</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="BarrierCode" type="hmis:barrierCode" minOccurs="0"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.15F" xml:lang="en">"If not enrolled, identify problems in enrolling child"</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="BarrierOther" type="hmis:string50" minOccurs="0"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 2.15F" xml:lang="en"/></xsd:annotation></xsd:element></xsd:sequence></xsd:complexType>
See HMIS XML Version 3.0 Cumulative Package Overview, IV.C..
Source
<xsd:complexType name="date"><xsd:annotation><xsd:documentation xml:lang="en">ISO date, without effective date timestamp.</xsd:documentation></xsd:annotation><xsd:simpleContent><xsd:extension base="xsd:date"><xsd:attributeGroup ref="hmis:dateStampGroupStatic"/></xsd:extension></xsd:simpleContent></xsd:complexType>
<xsd:complexType name="chronicHealthCondition"><xsd:sequence><xsd:element name="HasChronicHealthCondition" type="hmis:fourValDKRefused"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.5" xml:lang="en">"For the purposes of this Notice, a chronic health condition means a diagnosed condition that is more than three months in duration and is either not curable or has residual effects that limit daily living and require adaptation in function or special assistance."</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="ReceiveChronicHealthServices" type="hmis:fourValDKRefused" minOccurs="0"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.5" xml:lang="en">"(If yes[to HasChronicHealthCondition]) Currently receiving services or treatment for this condition or received services/treatment prior to exiting the program?</xsd:documentation></xsd:annotation></xsd:element></xsd:sequence></xsd:complexType>
<xsd:complexType name="contactMade"><xsd:sequence><xsd:element name="ContactID" type="hmis:iDIndex"><xsd:annotation><xsd:documentation source="Establishes a unique id for the contact" xml:lang="en"/></xsd:annotation></xsd:element><xsd:element name="ContactDate" type="hmis:contactDate"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.11" xml:lang="en">Because a client may be contacted multiple times on the same day, the response category must include a time stamp (i.e., hour and minute) indicating when the contact occurred in order to uniquely identify each contact. Note that to record a contact in HMIS requires that a client record be established with at least minimal client descriptors included in the Universal Data Elements (e.g., name, gender, race).</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="ContactLocation" type="hmis:contactLocation"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.11" xml:lang="en">For the purpose of the APR, street outreach programs must report the total number of contacts during the operating year by location of contact."</xsd:documentation></xsd:annotation></xsd:element></xsd:sequence></xsd:complexType>
<xsd:complexType name="degree"><xsd:sequence><xsd:element name="DegreeID" type="hmis:iDIndex"><xsd:annotation><xsd:documentation xml:lang="en">Establishes a unique ID for the DegreeCode DegreeOther set.</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="DegreeCode" type="hmis:degreeCode" minOccurs="0" maxOccurs="unbounded"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.15B" xml:lang="en">"If client has received a high school diploma, GED or enrolled in post-secondary education, what degree(s) has the client earned"</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="DegreeOther" type="hmis:string50" minOccurs="0"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.15B. See also Section 5.1.3 for treatment of 'other' elements." xml:lang="en"/></xsd:annotation></xsd:element></xsd:sequence></xsd:complexType>
<xsd:complexType name="destination"><xsd:sequence><xsd:element name="DestinationID" type="hmis:iDIndex"><xsd:annotation><xsd:documentation xml:lang="en">Establishes a unique ID for the Destinations sequence.</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="DestinationCode" type="hmis:destinationCode" minOccurs="0"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.10" xml:lang="en">Determine the response value that best describes where the client will be staying after they leave the program.</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="DestinationOther" type="hmis:string50" minOccurs="0"><xsd:annotation><xsd:documentation xml:lang="en">If "Other" is chosen for the Destination, place the destination this free text field.</xsd:documentation></xsd:annotation></xsd:element></xsd:sequence></xsd:complexType>
Destination Type1 = Emergency shelter, including hotel or motel paid for with emergency shelter voucher*2 = Transitional housing for homeless persons (including homeless youth)*3 = Permanent supportive housing for formerly homeless persons (such as SHP, S+C, or SRO Mod Rehab)4 = Psychiatric hospital or other psychiatric facility5 = Substance abuse treatment facility or detox center6 = Hospital (non-psychiatric)7 = Jail, prison or juvenile detention facility10 = Rental by client, no ongoing housing subsidy11 = Owned by client, no ongoing housing subsidy12 = Staying or living with family, temporary tenure (e.g., room, apartment or house)13 = Staying or living with friends, temporary tenure (.e.,g, room apartment or house;)14 = Hotel or motel paid for without emergency shelter voucher15 = Foster care home or foster care group home16 = Place not meant for habitation (e.g., a vehicle, an abandoned building, bus/train/subway station/airport or anywhere outside)17 = Other18 = Safe Haven19 = Rental by client, VASH Subsidy20 = Rental by client, other (non-VASH) ongoing housing subsidy 21 = Owned by client, with ongoing housing subsidy:22 = Staying or living with family, permanent tenure23 = Staying or living with friends, permanent tenure24 = Deceased8 = Don’t Know9 = Refused
Diagram
Type
restriction of xsd:unsignedInt
Facets
enumeration
1
Emergency shelter, including hotel or motel paid for with emergency shelter voucher*
enumeration
2
Transitional housing for homeless persons (including homeless youth)*
enumeration
3
Permanent housing for formerly homeless persons (such as SHP, S+C, or SRO Mod Rehab)
enumeration
4
Psychiatric hospital or other psychiatric facility
enumeration
5
Substance abuse treatment facility or detox center
enumeration
6
Hospital (non-psychiatric)
enumeration
7
Jail, prison or juvenile detention facility
enumeration
8
Don’t Know
enumeration
9
Refused
enumeration
10
Rental by client, no ongoing housing subsidy
enumeration
11
Owned by client, no ongoing housing subsidy
enumeration
12
Staying or living with family, temporary tenure (e.g., room, apartment or house)
enumeration
13
Staying or living with friends, temporary tenure (.e.,g, room apartment or house;)
enumeration
14
Hotel or motel paid for without emergency shelter voucher
enumeration
15
Foster care home or foster care group home
enumeration
16
Place not meant for habitation (e.g., a vehicle, an abandoned building, bus/train/subway station/airport or anywhere outside)
enumeration
17
Other
enumeration
18
Safe Haven
enumeration
19
Rental by client, VASH Subsidy
enumeration
20
Rental by client, other (non-VASH) ongoing housing subsidy
<xsd:simpleType name="destinationBase"><xsd:annotation><xsd:documentation xml:lang="en">Destination Type
1 = Emergency shelter, including hotel or motel paid for with emergency shelter voucher*
2 = Transitional housing for homeless persons (including homeless youth)*
3 = Permanent supportive housing for formerly homeless persons (such as SHP, S+C, or SRO Mod Rehab)
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
10 = Rental by client, no ongoing housing subsidy
11 = Owned by client, no ongoing housing subsidy
12 = Staying or living with family, temporary tenure (e.g., room, apartment or house)
13 = Staying or living with friends, temporary tenure (.e.,g, 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 (e.g., a vehicle, an abandoned building, bus/train/subway station/airport or anywhere outside)
17 = Other
18 = Safe Haven
19 = Rental by client, VASH Subsidy
20 = Rental by client, other (non-VASH) ongoing housing subsidy
21 = Owned by client, with ongoing housing subsidy:
22 = Staying or living with family, permanent tenure
23 = Staying or living with friends, permanent tenure
24 = Deceased
8 = Don’t Know
9 = Refused</xsd:documentation></xsd:annotation><xsd:restriction base="xsd:unsignedInt"><xsd:enumeration value="1"><xsd:annotation><xsd:documentation xml:lang="en">Emergency shelter, including hotel or motel paid for with emergency shelter voucher*</xsd:documentation></xsd:annotation></xsd:enumeration><xsd:enumeration value="2"><xsd:annotation><xsd:documentation xml:lang="en">Transitional housing for homeless persons (including homeless youth)*</xsd:documentation></xsd:annotation></xsd:enumeration><xsd:enumeration value="3"><xsd:annotation><xsd:documentation xml:lang="en">Permanent housing for formerly homeless persons (such as SHP, S+C, or SRO Mod Rehab)</xsd:documentation></xsd:annotation></xsd:enumeration><xsd:enumeration value="4"><xsd:annotation><xsd:documentation xml:lang="en">Psychiatric hospital or other psychiatric facility</xsd:documentation></xsd:annotation></xsd:enumeration><xsd:enumeration value="5"><xsd:annotation><xsd:documentation xml:lang="en">Substance abuse treatment facility or detox center</xsd:documentation></xsd:annotation></xsd:enumeration><xsd:enumeration value="6"><xsd:annotation><xsd:documentation xml:lang="en">Hospital (non-psychiatric)</xsd:documentation></xsd:annotation></xsd:enumeration><xsd:enumeration value="7"><xsd:annotation><xsd:documentation xml:lang="en">Jail, prison or juvenile detention facility</xsd:documentation></xsd:annotation></xsd:enumeration><xsd:enumeration value="8"><xsd:annotation><xsd:documentation xml:lang="en">Don’t Know</xsd:documentation></xsd:annotation></xsd:enumeration><xsd:enumeration value="9"><xsd:annotation><xsd:documentation xml:lang="en">Refused</xsd:documentation></xsd:annotation></xsd:enumeration><xsd:enumeration value="10"><xsd:annotation><xsd:documentation xml:lang="en">Rental by client, no ongoing housing subsidy</xsd:documentation></xsd:annotation></xsd:enumeration><xsd:enumeration value="11"><xsd:annotation><xsd:documentation xml:lang="en">Owned by client, no ongoing housing subsidy</xsd:documentation></xsd:annotation></xsd:enumeration><xsd:enumeration value="12"><xsd:annotation><xsd:documentation xml:lang="en">Staying or living with family, temporary tenure (e.g., room, apartment or house)</xsd:documentation></xsd:annotation></xsd:enumeration><xsd:enumeration value="13"><xsd:annotation><xsd:documentation xml:lang="en">Staying or living with friends, temporary tenure (.e.,g, room apartment or house;)</xsd:documentation></xsd:annotation></xsd:enumeration><xsd:enumeration value="14"><xsd:annotation><xsd:documentation xml:lang="en">Hotel or motel paid for without emergency shelter voucher</xsd:documentation></xsd:annotation></xsd:enumeration><xsd:enumeration value="15"><xsd:annotation><xsd:documentation xml:lang="en">Foster care home or foster care group home</xsd:documentation></xsd:annotation></xsd:enumeration><xsd:enumeration value="16"><xsd:annotation><xsd:documentation xml:lang="en">Place not meant for habitation (e.g., a vehicle, an abandoned building, bus/train/subway station/airport or anywhere outside)</xsd:documentation></xsd:annotation></xsd:enumeration><xsd:enumeration value="17"><xsd:annotation><xsd:documentation xml:lang="en">Other</xsd:documentation></xsd:annotation></xsd:enumeration><xsd:enumeration value="18"><xsd:annotation><xsd:documentation xml:lang="en">Safe Haven</xsd:documentation></xsd:annotation></xsd:enumeration><xsd:enumeration value="19"><xsd:annotation><xsd:documentation xml:lang="en">Rental by client, VASH Subsidy</xsd:documentation></xsd:annotation></xsd:enumeration><xsd:enumeration value="20"><xsd:annotation><xsd:documentation xml:lang="en">Rental by client, other (non-VASH) ongoing housing subsidy</xsd:documentation></xsd:annotation></xsd:enumeration><xsd:enumeration value="21"><xsd:annotation><xsd:documentation xml:lang="en">Owned by client, with ongoing housing subsidy:</xsd:documentation></xsd:annotation></xsd:enumeration><xsd:enumeration value="22"><xsd:annotation><xsd:documentation xml:lang="en">Staying or living with family, permanent tenure</xsd:documentation></xsd:annotation></xsd:enumeration><xsd:enumeration value="23"><xsd:annotation><xsd:documentation xml:lang="en">Staying or living with friends, permanent tenure</xsd:documentation></xsd:annotation></xsd:enumeration><xsd:enumeration value="24"><xsd:annotation><xsd:documentation xml:lang="en">Deceased</xsd:documentation></xsd:annotation></xsd:enumeration></xsd:restriction></xsd:simpleType>
<xsd:complexType name="developmentalDisability"><xsd:sequence><xsd:element name="HasDevelopmentalDisability" type="hmis:fourValDKRefused"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.4" xml:lang="en">"For the purposes of this Notice, a developmental disability means 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."</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="ReceiveDevelopmentalDisabilityServicesTreatment" type="hmis:fourValDKRefused" minOccurs="0"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.4" xml:lang="en">"(If yes[to HasDevelopmentalDisability]) Currently receiving services or treatment for this condition or received services/treatment prior to exiting the program?</xsd:documentation></xsd:annotation></xsd:element></xsd:sequence></xsd:complexType>
<xsd:complexType name="domesticViolence"><xsd:sequence><xsd:element name="DomesticViolenceSurvivor" type="hmis:fourValDKRefused"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.9" xml:lang="en">"...determine (a) if the client has ever been a victim of domestic violence..."</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="DVOccurred" type="hmis:sixValDKRefused2" minOccurs="0"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.9" xml:lang="en">"...and (b), if so [if 'yes' to DomesticViolenceSurvivor], how long ago did the client have the most recent experience."</xsd:documentation></xsd:annotation></xsd:element></xsd:sequence></xsd:complexType>
Applicable to:Housing Status 1 = Literally homeless 2 = Housed and at imminent risk of losing housing 3 = Housed and at-risk of losing housing 4 = Stably housed 8 = Don’t Know 9 = Refused When Domestic Violence Occurred 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
<xsd:simpleType name="sixValDKRefused2Base"><xsd:annotation><xsd:documentation xml:lang="en">Applicable to:
Housing Status
1 = Literally homeless
2 = Housed and at imminent risk of losing housing
3 = Housed and at-risk of losing housing
4 = Stably housed
8 = Don’t Know
9 = Refused
When Domestic Violence Occurred
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</xsd:documentation></xsd:annotation><xsd:restriction base="xsd:unsignedInt"><xsd:enumeration value="1"/><xsd:enumeration value="2"/><xsd:enumeration value="3"/><xsd:enumeration value="4"/><xsd:enumeration value="8"/><xsd:enumeration value="9"/></xsd:restriction></xsd:simpleType>
<xsd:complexType name="employment"><xsd:sequence><xsd:element name="EmploymentID" type="hmis:iDIndex"><xsd:annotation><xsd:documentation xml:lang="en">See HMIS XML Version 3.0 Cumulative Package Overview, Section 3: I.2.</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="CurrentlyEmployed" type="hmis:fourValDKRefused" minOccurs="0"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.15A" xml:lang="en">"...determine: (1) if the client is currently employed..."</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="HoursWorkedLastWeek" type="hmis:nonNegativeInteger" minOccurs="0"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.15A" xml:lang="en">"...determine: ... (2) if currently employed, how many hours did the client work in the last week..."</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="EmploymentTenure" type="hmis:fiveValDKRefused" minOccurs="0"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.15A" xml:lang="en">"...if currently employed, is the work permanent, temporary, or seasonal..."</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="LookingForWork" type="hmis:fourValDKRefused" minOccurs="0"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.15A" xml:lang="en">[If unemployed] Is the client looking for work? [If employed] Is the client looking for additional employment or increased hours at their current job?</xsd:documentation></xsd:annotation></xsd:element></xsd:sequence></xsd:complexType>
<xsd:complexType name="hIVAIDSStatus"><xsd:sequence><xsd:element name="HasHIVAIDS" type="hmis:fourValDKRefused"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.6" xml:lang="en">"...determine if the client (a) has been diagnosed with AIDS or has tested positive for HIV..."</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="ReceiveHIVAIDSServices" type="hmis:fourValDKRefused" minOccurs="0"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.6" xml:lang="en">"(If yes[to HasHIVAIDS]) Currently receiving services or treatment for this condition or received services/treatment prior to exiting the program?</xsd:documentation></xsd:annotation></xsd:element></xsd:sequence></xsd:complexType>
<xsd:complexType name="incomeAndSource"><xsd:sequence><xsd:element name="IncomeAndSourceID" type="hmis:iDIndex"><xsd:annotation><xsd:documentation xml:lang="en">Establishes a unique ID for Income and Sources transactions.</xsd:documentation></xsd:annotation></xsd:element><xsd:sequence maxOccurs="unbounded"><xsd:element name="IncomeSourceCode" type="hmis:incomeSourceCode"><xsd:annotation><xsd:documentation xml:lang="en">2010 HUD HMIS Data and Technical Standards, Program-Specific Data Element 4.1.</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="IncomeSourceOther" type="hmis:string50" minOccurs="0"><xsd:annotation><xsd:documentation xml:lang="en">2010 HUD HMIS Data and Technical Standards, Program-Specific Data Element 4.1.</xsd:documentation></xsd:annotation></xsd:element><xsd:choice><xsd:element name="ReceivingIncomeSource" type="hmis:twoVal"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.1" xml:lang="en">"When a client has income, but does not know the amount, a “Yes” response should be recorded for both the overall income question and the specific source, and the income amount should be left blank. ... To reduce data collection and reporting burden, if a client reports receiving no income from any source in the past 30 days, no additional data collection is required. If a client reports receiving income, an HMIS may be designed such that programs only need to directly enter “yes” for the benefits the clients received. The HMIS software may automatically generate a “No” response for the other income sources. The HMIS may also be designed to automatically generate a “Yes” response where income amounts are recorded. However, since clients often know the source of income, but not the precise amount, users should have the ability to enter “Yes” without recording an exact amount."</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="IncomeSourceAmount" type="hmis:nonNegativeInteger" minOccurs="0"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.1" xml:lang="en">"Capturing the receipt of cash income from various sources will help to: ensure all income sources are counted in the calculation of total income; enable program staff to take into account the composition of income in determining needs; determine if people are receiving the mainstream program benefits to which they may be entitled; help clients apply for benefits assistance; and allow analysis of changes in the composition of income between entry and exit from the program and annual changes prior to program exit."</xsd:documentation><xsd:documentation xml:lang="en">This is the amount received in the last 30 days.</xsd:documentation></xsd:annotation></xsd:element></xsd:choice></xsd:sequence></xsd:sequence></xsd:complexType>
Income Source Code1 = Earned Income (i.e., employment income)2 = Unemployment Insurance 3 = Supplemental Security Income (SSI)4 = Social Security Disability Income (SSDI)5 = Veteran's Disability Payment6 = Private Disability Insurance7 = Worker's Compensation10 = Temporary Assistance for Needy Families (TANF) (or use local program name)11 = General Assistance (GA) (or use local program name)12 = Retirement Income from Social Security13 = Veteran’s Pension14 = Pension from a Former Job15 = Child Support16 = Alimony or Other Spousal Support17 = Other Source
Diagram
Type
restriction of xsd:unsignedInt
Facets
enumeration
1
Earned Income (i.e., employment income)
enumeration
2
Unemployment Insurance
enumeration
3
Supplemental Security Income (SSI)
enumeration
4
Social Security Disability Income (SSDI)
enumeration
5
Veteran's Disability Payment
enumeration
6
Private Disability Insurance
enumeration
7
Worker's Compensation
enumeration
10
Temporary Assistance for Needy Families (TANF) (or use local program name)
enumeration
11
General Assistance (GA) (or use local program name)
<xsd:simpleType name="incomeSourceCodeBase"><xsd:annotation><xsd:documentation xml:lang="en">Income Source Code
1 = Earned Income (i.e., employment income)
2 = Unemployment Insurance
3 = Supplemental Security Income (SSI)
4 = Social Security Disability Income (SSDI)
5 = Veteran's Disability Payment
6 = Private Disability Insurance
7 = Worker's Compensation
10 = Temporary Assistance for Needy Families (TANF) (or use local program name)
11 = General Assistance (GA) (or use local program name)
12 = Retirement Income from Social Security
13 = Veteran’s Pension
14 = Pension from a Former Job
15 = Child Support
16 = Alimony or Other Spousal Support
17 = Other Source</xsd:documentation></xsd:annotation><xsd:restriction base="xsd:unsignedInt"><xsd:enumeration value="1"><xsd:annotation><xsd:documentation xml:lang="en">Earned Income (i.e., employment income)</xsd:documentation></xsd:annotation></xsd:enumeration><xsd:enumeration value="2"><xsd:annotation><xsd:documentation xml:lang="en">Unemployment Insurance</xsd:documentation></xsd:annotation></xsd:enumeration><xsd:enumeration value="3"><xsd:annotation><xsd:documentation xml:lang="en">Supplemental Security Income (SSI)</xsd:documentation></xsd:annotation></xsd:enumeration><xsd:enumeration value="4"><xsd:annotation><xsd:documentation xml:lang="en">Social Security Disability Income (SSDI)</xsd:documentation></xsd:annotation></xsd:enumeration><xsd:enumeration value="5"><xsd:annotation><xsd:documentation xml:lang="en">Veteran's Disability Payment</xsd:documentation></xsd:annotation></xsd:enumeration><xsd:enumeration value="6"><xsd:annotation><xsd:documentation xml:lang="en">Private Disability Insurance</xsd:documentation></xsd:annotation></xsd:enumeration><xsd:enumeration value="7"><xsd:annotation><xsd:documentation xml:lang="en">Worker's Compensation</xsd:documentation></xsd:annotation></xsd:enumeration><xsd:enumeration value="10"><xsd:annotation><xsd:documentation xml:lang="en">Temporary Assistance for Needy Families (TANF) (or use local program name)</xsd:documentation></xsd:annotation></xsd:enumeration><xsd:enumeration value="11"><xsd:annotation><xsd:documentation xml:lang="en">General Assistance (GA) (or use local program name)</xsd:documentation></xsd:annotation></xsd:enumeration><xsd:enumeration value="12"><xsd:annotation><xsd:documentation xml:lang="en">Retirement Income from Social Security</xsd:documentation></xsd:annotation></xsd:enumeration><xsd:enumeration value="13"><xsd:annotation><xsd:documentation xml:lang="en">Veteran’s Pension</xsd:documentation></xsd:annotation></xsd:enumeration><xsd:enumeration value="14"><xsd:annotation><xsd:documentation xml:lang="en">Pension from a Former Job</xsd:documentation></xsd:annotation></xsd:enumeration><xsd:enumeration value="15"><xsd:annotation><xsd:documentation xml:lang="en">Child Support</xsd:documentation></xsd:annotation></xsd:enumeration><xsd:enumeration value="16"><xsd:annotation><xsd:documentation xml:lang="en">Alimony or Other Spousal Support</xsd:documentation></xsd:annotation></xsd:enumeration><xsd:enumeration value="17"><xsd:annotation><xsd:documentation xml:lang="en">Other Source</xsd:documentation></xsd:annotation></xsd:enumeration></xsd:restriction></xsd:simpleType>
Applicable to:Branch of the Military 1 = Army 2 = Air Force 3 = Navy 4 = Marines 5 = Other 8 = Don’t know 9 = RefusedLength of Stay in Previous Place 1 = One week or less 2 = More than one week, but less than one month 3 = One to three months 4 = More than three months, but less than one year 5 = One year or longer 8 = Don’t Know 9 = RefusedRace 1 = American Indian or Alaska Native 2 = Asian 3 = Black or African American 4 = Native Hawaiian or Other Pacific Islander 5 = White 8 = Don’t Know 9 = Refused
<xsd:simpleType name="sevenValDKRefused2Base"><xsd:annotation><xsd:documentation xml:lang="en">Applicable to:
Branch of the Military
1 = Army
2 = Air Force
3 = Navy
4 = Marines
5 = Other
8 = Don’t know
9 = Refused
Length of Stay in Previous Place
1 = One week or less
2 = More than one week, but less than one month
3 = One to three months
4 = More than three months, but less than one year
5 = One year or longer
8 = Don’t Know
9 = Refused
Race
1 = American Indian or Alaska Native
2 = Asian
3 = Black or African American
4 = Native Hawaiian or Other Pacific Islander
5 = White
8 = Don’t Know
9 = Refused</xsd:documentation></xsd:annotation><xsd:restriction base="xsd:unsignedInt"><xsd:enumeration value="1"/><xsd:enumeration value="2"/><xsd:enumeration value="3"/><xsd:enumeration value="4"/><xsd:enumeration value="5"/><xsd:enumeration value="8"/><xsd:enumeration value="9"/></xsd:restriction></xsd:simpleType>
<xsd:complexType name="mentalHealthProblem"><xsd:sequence><xsd:element name="HasMentalHealthProblem" type="hmis:fourValDKRefused"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.7" xml:lang="en">"A mental health problem may include serious depression, serious anxiety, hallucinations, violent behavior or thoughts of suicide."</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="MentalHealthIndefinite" type="hmis:fourValDKRefused" minOccurs="0"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.7" xml:lang="en">"(If yes[to HasMentalHealthProblem]) Expected to be of long-continued and indefinite duration and substantially impairs ability to live independently"</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="ReceiveMentalHealthServices" type="hmis:fourValDKRefused" minOccurs="0"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.7" xml:lang="en">"(If yes[to HasMentalHealthProblem]) Currently receiving services or treatment for this condition or received services/treatment prior to exiting the program?</xsd:documentation></xsd:annotation></xsd:element></xsd:sequence></xsd:complexType>
<xsd:complexType name="nonCashBenefit"><xsd:sequence><xsd:element name="NonCashBenefitID" type="hmis:iDIndex"><xsd:annotation><xsd:documentation xml:lang="en">Establishes a unique ID for the non-cash benefit record.</xsd:documentation></xsd:annotation></xsd:element><xsd:sequence maxOccurs="unbounded"><xsd:element name="NonCashSourceCode" type="hmis:nonCashSourceCode"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.2" xml:lang="en">"For each source listed below, determine if the client received any non-cash benefits in the past 30 days. Clients may identify multiple sources of non-cash benefits."</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="NonCashSourceOther" type="hmis:string50" minOccurs="0"><xsd:annotation><xsd:documentation xml:lang="en">Free text field to record NonCashSource when "Other" is selected in NonCashSourceCode.</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="ReceivingNonCashSource" type="hmis:twoVal"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.2" xml:lang="en">"If a client reports receiving non-cash benefits, an HMIS may be designed such that programs only need to directly enter “Yes” for the benefits the clients received. The HMIS software may automatically generate a “No” response for the other non-cash benefit sources."</xsd:documentation></xsd:annotation></xsd:element></xsd:sequence></xsd:sequence></xsd:complexType>
Non-Cash Source Code1 = Supplemental Nutrition Assistance Program (SNAP) (Previously known as Food Stamps)2 = MEDICAID health insurance program (or use local name) 3 = MEDICARE health insurance program (or use local name) 4 = State Children’s Health Insurance Program (or use local name) 5 = Special Supplemental Nutrition Program for Women, Infants, and Children (WIC) 1 = Yes6 = Veteran’s Administration (VA) Medical Services7 = TANF Child Care services (or use local name)10 = TANF transportation services (or use local name)11 = Other TANF-funded services (or use local name)12 = Section 8, public housing, or other ongoing rental assistance13 = Other source14 = Temporary rental assistance
Diagram
Type
restriction of xsd:unsignedInt
Facets
enumeration
1
Supplemental Nutrition Assistance Program (SNAP) (Previously known as Food Stamps)
enumeration
2
MEDICAID health insurance program (or use local name)
enumeration
3
MEDICARE health insurance program (or use local name)
enumeration
4
State Children’s Health Insurance Program (or use local name)
enumeration
5
Special Supplemental Nutrition Program for Women, Infants, and Children (WIC)
enumeration
6
Veteran’s Administration (VA) Medical Services
enumeration
7
TANF Child Care services (or use local name)
enumeration
10
TANF transportation services (or use local name)
enumeration
11
Other TANF-funded services (or use local name)
enumeration
12
Section 8, public housing, or other ongoing rental assistance
<xsd:simpleType name="nonCashSourceCodeBase"><xsd:annotation><xsd:documentation xml:lang="en">Non-Cash Source Code
1 = Supplemental Nutrition Assistance Program (SNAP) (Previously known as Food Stamps)
2 = MEDICAID health insurance program (or use local name)
3 = MEDICARE health insurance program (or use local name)
4 = State Children’s Health Insurance Program (or use local name)
5 = Special Supplemental Nutrition Program for Women, Infants, and Children (WIC) 1 = Yes
6 = Veteran’s Administration (VA) Medical Services
7 = TANF Child Care services (or use local name)
10 = TANF transportation services (or use local name)
11 = Other TANF-funded services (or use local name)
12 = Section 8, public housing, or other ongoing rental assistance
13 = Other source
14 = Temporary rental assistance</xsd:documentation></xsd:annotation><xsd:restriction base="xsd:unsignedInt"><xsd:enumeration value="1"><xsd:annotation><xsd:documentation xml:lang="en">Supplemental Nutrition Assistance Program (SNAP) (Previously known as Food Stamps)</xsd:documentation></xsd:annotation></xsd:enumeration><xsd:enumeration value="2"><xsd:annotation><xsd:documentation xml:lang="en">MEDICAID health insurance program (or use local name)</xsd:documentation></xsd:annotation></xsd:enumeration><xsd:enumeration value="3"><xsd:annotation><xsd:documentation xml:lang="en">MEDICARE health insurance program (or use local name)</xsd:documentation></xsd:annotation></xsd:enumeration><xsd:enumeration value="4"><xsd:annotation><xsd:documentation xml:lang="en">State Children’s Health Insurance Program (or use local name)</xsd:documentation></xsd:annotation></xsd:enumeration><xsd:enumeration value="5"><xsd:annotation><xsd:documentation xml:lang="en">Special Supplemental Nutrition Program for Women, Infants, and Children (WIC)</xsd:documentation></xsd:annotation></xsd:enumeration><xsd:enumeration value="6"><xsd:annotation><xsd:documentation xml:lang="en">Veteran’s Administration (VA) Medical Services</xsd:documentation></xsd:annotation></xsd:enumeration><xsd:enumeration value="7"><xsd:annotation><xsd:documentation xml:lang="en">TANF Child Care services (or use local name)</xsd:documentation></xsd:annotation></xsd:enumeration><xsd:enumeration value="10"><xsd:annotation><xsd:documentation xml:lang="en">TANF transportation services (or use local name)</xsd:documentation></xsd:annotation></xsd:enumeration><xsd:enumeration value="11"><xsd:annotation><xsd:documentation xml:lang="en">Other TANF-funded services (or use local name)</xsd:documentation></xsd:annotation></xsd:enumeration><xsd:enumeration value="12"><xsd:annotation><xsd:documentation xml:lang="en">Section 8, public housing, or other ongoing rental assistance</xsd:documentation></xsd:annotation></xsd:enumeration><xsd:enumeration value="13"><xsd:annotation><xsd:documentation xml:lang="en">Other source</xsd:documentation></xsd:annotation></xsd:enumeration><xsd:enumeration value="14"><xsd:annotation><xsd:documentation xml:lang="en">Temporary rental assistance</xsd:documentation></xsd:annotation></xsd:enumeration></xsd:restriction></xsd:simpleType>
<xsd:complexType name="personAddressBase"><xsd:complexContent><xsd:extension base="hmis:addressBase"><xsd:sequence><xsd:element name="IsLastPermanentZIP" type="hmis:twoVal" minOccurs="0"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 3.10" xml:lang="en">To identify the former geographic location of persons experiencing homelessness or current geographic location of persons who are at risk of homelessness.</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="ZIPQualityCode" type="hmis:zIPQualityCode" minOccurs="0"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 3.10" xml:lang="en">"...record the appropriate zip code type (data quality code)."</xsd:documentation></xsd:annotation></xsd:element></xsd:sequence></xsd:extension></xsd:complexContent></xsd:complexType>
<xsd:complexType name="physicalDisability"><xsd:sequence><xsd:element name="HasPhysicalDisability" type="hmis:fourValDKRefused"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.3" xml:lang="en">"For the purposes of this Notice, a physical disability means 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."</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="ReceivePhysicalDisabilityServices" type="hmis:fourValDKRefused" minOccurs="0"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.3" xml:lang="en">"(If yes [to HasPhysicalDisability]) Currently receiving services or treatment for this condition or received services/treatment prior to exiting the program?"</xsd:documentation></xsd:annotation></xsd:element></xsd:sequence></xsd:complexType>
<xsd:complexType name="pregnancy"><xsd:sequence><xsd:element name="PregnancyID" type="hmis:iDIndex"><xsd:annotation><xsd:documentation xml:lang="en">Establishes a unique ID for the Pregnancy element sequence.</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="PregnancyStatus" type="hmis:fourValDKRefused"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.15D" xml:lang="en">"In separate fields, determine (a) if a client is pregnant..."</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="DueDate" type="hmis:date" minOccurs="0"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.15D" xml:lang="en">"If yes, due date."</xsd:documentation></xsd:annotation></xsd:element></xsd:sequence></xsd:complexType>
<xsd:complexType name="priorResidence"><xsd:sequence><xsd:element name="PriorResidenceID" type="hmis:iDIndex"><xsd:annotation><xsd:documentation xml:lang="en">Establishes a unique ID for the Prior Residence element sequence.</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="PriorResidenceCode" type="hmis:residence" minOccurs="0"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 3.9" xml:lang="en">To identify the type of residence and length of stay at that residence just prior to (i.e., the night before) program admission.</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="PriorResidenceOther" type="hmis:string50" minOccurs="0"/></xsd:sequence></xsd:complexType>
Residence Type1 = Emergency shelter, including hotel or motel paid for with emergency shelter voucher*2 = Transitional housing for homeless persons (including homeless youth)*3 = Permanent supportive housing for formerly homeless persons (such as SHP, S+C, or SRO Mod Rehab)4 = Psychiatric hospital or other psychiatric facility5 = Substance abuse treatment facility or detox center6 = Hospital (non-psychiatric)7 = Jail, prison or juvenile detention facility12 = Staying or living in a family member’s room, apartment or house13 = Staying or living in a friend’s room, apartment or house14 = Hotel or motel paid for without emergency shelter voucher15 = Foster care home or foster care group home16 = Place not meant for habitation (e.g., a vehicle, an abandoned building, bus/train/subway station/airport or anywhere outside); inclusive of “non-housing service site (outreach programs only)”17 = Other18 = Safe Haven19 = Rental by client, with VASH housing subsidy 20 = Rental by client, with other (non-VASH) ongoing housing subsidy21 = Owned by client, with ongoing housing subsidy:22 = Rental by client, no ongoing housing subsidy 23 = Owned by client, no ongoing housing subsidy8 = Don’t Know9 = Refused
Diagram
Type
restriction of xsd:unsignedInt
Facets
enumeration
1
Emergency shelter, including hotel or motel paid for with emergency shelter voucher*
enumeration
2
Transitional housing for homeless persons (including homeless youth)*
enumeration
3
Permanent housing for formerly homeless persons (such as SHP, S+C, or SRO Mod Rehab)
enumeration
4
Psychiatric hospital or other psychiatric facility
enumeration
5
Substance abuse treatment facility or detox center
enumeration
6
Hospital (non-psychiatric)
enumeration
7
Jail, prison or juvenile detention facility
enumeration
8
Don’t Know
enumeration
9
Refused
enumeration
12
Staying or living in a family member’s room, apartment or house
enumeration
13
Staying or living in a friend’s room, apartment or house
enumeration
14
Hotel or motel paid for without emergency shelter voucher
enumeration
15
Foster care home or foster care group home
enumeration
16
Place not meant for habitation (e.g., a vehicle, an abandoned building, bus/train/subway station/airport or anywhere outside); inclusive of “non-housing service site (outreach programs only)
enumeration
17
Other
enumeration
18
Safe Haven
enumeration
19
Rental by client, with VASH housing subsidy
enumeration
20
Rental by client, with other (non-VASH) ongoing housing subsidy
<xsd:simpleType name="residenceBase"><xsd:annotation><xsd:documentation xml:lang="en">Residence Type
1 = Emergency shelter, including hotel or motel paid for with emergency shelter voucher*
2 = Transitional housing for homeless persons (including homeless youth)*
3 = Permanent supportive housing for formerly homeless persons (such as SHP, S+C, or SRO Mod Rehab)
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
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 (e.g., a vehicle, an abandoned building, bus/train/subway station/airport or anywhere outside); inclusive of “non-housing service site (outreach programs only)”
17 = Other
18 = Safe Haven
19 = Rental by client, with VASH housing subsidy
20 = Rental by client, with other (non-VASH) ongoing housing subsidy
21 = Owned by client, with ongoing housing subsidy:
22 = Rental by client, no ongoing housing subsidy
23 = Owned by client, no ongoing housing subsidy
8 = Don’t Know
9 = Refused</xsd:documentation></xsd:annotation><xsd:restriction base="xsd:unsignedInt"><xsd:enumeration value="1"><xsd:annotation><xsd:documentation xml:lang="en">Emergency shelter, including hotel or motel paid for with emergency shelter voucher*</xsd:documentation></xsd:annotation></xsd:enumeration><xsd:enumeration value="2"><xsd:annotation><xsd:documentation xml:lang="en">Transitional housing for homeless persons (including homeless youth)*</xsd:documentation></xsd:annotation></xsd:enumeration><xsd:enumeration value="3"><xsd:annotation><xsd:documentation xml:lang="en">Permanent housing for formerly homeless persons (such as SHP, S+C, or SRO Mod Rehab)</xsd:documentation></xsd:annotation></xsd:enumeration><xsd:enumeration value="4"><xsd:annotation><xsd:documentation xml:lang="en">Psychiatric hospital or other psychiatric facility</xsd:documentation></xsd:annotation></xsd:enumeration><xsd:enumeration value="5"><xsd:annotation><xsd:documentation xml:lang="en">Substance abuse treatment facility or detox center</xsd:documentation></xsd:annotation></xsd:enumeration><xsd:enumeration value="6"><xsd:annotation><xsd:documentation xml:lang="en">Hospital (non-psychiatric)</xsd:documentation></xsd:annotation></xsd:enumeration><xsd:enumeration value="7"><xsd:annotation><xsd:documentation xml:lang="en">Jail, prison or juvenile detention facility</xsd:documentation></xsd:annotation></xsd:enumeration><xsd:enumeration value="8"><xsd:annotation><xsd:documentation xml:lang="en">Don’t Know</xsd:documentation></xsd:annotation></xsd:enumeration><xsd:enumeration value="9"><xsd:annotation><xsd:documentation xml:lang="en">Refused</xsd:documentation></xsd:annotation></xsd:enumeration><xsd:enumeration value="12"><xsd:annotation><xsd:documentation xml:lang="en">Staying or living in a family member’s room, apartment or house</xsd:documentation></xsd:annotation></xsd:enumeration><xsd:enumeration value="13"><xsd:annotation><xsd:documentation xml:lang="en">Staying or living in a friend’s room, apartment or house</xsd:documentation></xsd:annotation></xsd:enumeration><xsd:enumeration value="14"><xsd:annotation><xsd:documentation xml:lang="en">Hotel or motel paid for without emergency shelter voucher</xsd:documentation></xsd:annotation></xsd:enumeration><xsd:enumeration value="15"><xsd:annotation><xsd:documentation xml:lang="en">Foster care home or foster care group home</xsd:documentation></xsd:annotation></xsd:enumeration><xsd:enumeration value="16"><xsd:annotation><xsd:documentation xml:lang="en">Place not meant for habitation (e.g., a vehicle, an abandoned building, bus/train/subway station/airport or anywhere outside); inclusive of “non-housing service site (outreach programs only)</xsd:documentation></xsd:annotation></xsd:enumeration><xsd:enumeration value="17"><xsd:annotation><xsd:documentation xml:lang="en">Other</xsd:documentation></xsd:annotation></xsd:enumeration><xsd:enumeration value="18"><xsd:annotation><xsd:documentation xml:lang="en">Safe Haven</xsd:documentation></xsd:annotation></xsd:enumeration><xsd:enumeration value="19"><xsd:annotation><xsd:documentation xml:lang="en">Rental by client, with VASH housing subsidy</xsd:documentation></xsd:annotation></xsd:enumeration><xsd:enumeration value="20"><xsd:annotation><xsd:documentation xml:lang="en">Rental by client, with other (non-VASH) ongoing housing subsidy</xsd:documentation></xsd:annotation></xsd:enumeration><xsd:enumeration value="21"><xsd:annotation><xsd:documentation xml:lang="en">Owned by client, with ongoing housing subsidy:</xsd:documentation></xsd:annotation></xsd:enumeration><xsd:enumeration value="22"><xsd:annotation><xsd:documentation xml:lang="en">Rental by client, no ongoing housing subsidy</xsd:documentation></xsd:annotation></xsd:enumeration><xsd:enumeration value="23"><xsd:annotation><xsd:documentation xml:lang="en">Owned by client, no ongoing housing subsidy</xsd:documentation></xsd:annotation></xsd:enumeration></xsd:restriction></xsd:simpleType>
<xsd:complexType name="substanceAbuseProblem"><xsd:sequence><xsd:element name="HasSubstanceAbuseProblem" type="hmis:sixValDKRefused"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.8" xml:lang="en">"...determine (a) if the client has an alcohol or drug abuse problem or both,..."</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="SubstanceAbuseIndefinite" type="hmis:fourValDKRefused" minOccurs="0"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.8" xml:lang="en">"(If client has a substance abuse problem) Expected to be of long-continued and indefinite duration and substantially impairs ability to live independently"</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="ReceiveSubstanceAbuseServices" type="hmis:fourValDKRefused" minOccurs="0"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.8" xml:lang="en">"(If client has a substance abuse problem) Currently receiving services or treatment for this condition or received services/treatment prior to exiting the program?</xsd:documentation></xsd:annotation></xsd:element></xsd:sequence></xsd:complexType>
<xsd:complexType name="veteran"><xsd:sequence><xsd:element name="MilitaryBranches" type="hmis:militaryBranches" minOccurs="0" maxOccurs="unbounded"><xsd:annotation><xsd:documentation xml:lang="en">Establishes a sequence for MilitaryBranch and MilitaryBranchOther Responses</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="MilitaryServiceDuration" type="hmis:nonNegativeInteger" minOccurs="0" maxOccurs="unbounded"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.15E" xml:lang="en">"Duration of active duty"</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="ServedInWarZone" type="hmis:fourValDKRefused" minOccurs="0" maxOccurs="unbounded"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.15E" xml:lang="en">"Served in a war zone"</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="ServiceEra" type="hmis:serviceEra" minOccurs="0" maxOccurs="unbounded"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.15E" xml:lang="en">"...determine: 1) which military service era did the client serve..."</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="VeteranStatus" type="hmis:fourValDKRefused" minOccurs="0" maxOccurs="unbounded"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 3.7" xml:lang="en">To determine the number of homeless veterans.</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="WarZonesServed" type="hmis:warZoneServed" minOccurs="0" maxOccurs="unbounded"><xsd:annotation><xsd:documentation xml:lang="en">Establishes a sequence of War Zone related elements.</xsd:documentation></xsd:annotation></xsd:element></xsd:sequence></xsd:complexType>
<xsd:complexType name="militaryBranches"><xsd:sequence><xsd:element name="MilitaryBranchID" type="hmis:iDIndex"><xsd:annotation><xsd:documentation xml:lang="en">Establishes a unique ID for the Military Branches sequence.</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="DischargeStatus" type="hmis:dischargeStatus" minOccurs="0"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.15E" xml:lang="en">Discharge status</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="DischargeStatusOther" type="hmis:string50" minOccurs="0"><xsd:annotation><xsd:documentation xml:lang="en"/></xsd:annotation></xsd:element><xsd:element name="MilitaryBranch" type="hmis:sevenValDKRefused2" minOccurs="0"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.15E" xml:lang="en">"Branch of the military"</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="MilitaryBranchOther" type="hmis:string50" minOccurs="0"><xsd:annotation><xsd:documentation xml:lang="en"/></xsd:annotation></xsd:element></xsd:sequence></xsd:complexType>
Service Era List1= Persian Gulf Era (August 1991 – September 10, 2001) 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= Don’t know9= Refused10= Post September 11, 2001 (September 11, 2001 -Present)
Diagram
Type
restriction of xsd:unsignedInt
Facets
enumeration
1
Persian Gulf Era (August 1991 – September 10, 2001)
enumeration
2
Post Vietnam (May 1975 – July 1991)
enumeration
3
Vietnam Era (August 1964 – April 1975)
enumeration
4
Between Korean and Vietnam War (February 1955– July 1964)
enumeration
5
Korean War (June 1950 – January 1955)
enumeration
6
Between WWII and Korean War (August 1947 – May 1950)
enumeration
7
World War II (September 1940 – July 1947)
enumeration
8
Don’t know
enumeration
9
Refused
enumeration
10
Post September 11, 2001 (September 11, 2001 -Present)
<xsd:simpleType name="serviceEraBase"><xsd:annotation><xsd:documentation xml:lang="en">Service Era List
1= Persian Gulf Era (August 1991 – September 10, 2001)
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= Don’t know
9= Refused
10= Post September 11, 2001 (September 11, 2001 -Present)</xsd:documentation></xsd:annotation><xsd:restriction base="xsd:unsignedInt"><xsd:enumeration value="1"><xsd:annotation><xsd:documentation xml:lang="en">Persian Gulf Era (August 1991 – September 10, 2001)</xsd:documentation></xsd:annotation></xsd:enumeration><xsd:enumeration value="2"><xsd:annotation><xsd:documentation xml:lang="en">Post Vietnam (May 1975 – July 1991)</xsd:documentation></xsd:annotation></xsd:enumeration><xsd:enumeration value="3"><xsd:annotation><xsd:documentation xml:lang="en">Vietnam Era (August 1964 – April 1975)</xsd:documentation></xsd:annotation></xsd:enumeration><xsd:enumeration value="4"><xsd:annotation><xsd:documentation xml:lang="en">Between Korean and Vietnam War (February 1955– July 1964)</xsd:documentation></xsd:annotation></xsd:enumeration><xsd:enumeration value="5"><xsd:annotation><xsd:documentation xml:lang="en">Korean War (June 1950 – January 1955)</xsd:documentation></xsd:annotation></xsd:enumeration><xsd:enumeration value="6"><xsd:annotation><xsd:documentation xml:lang="en">Between WWII and Korean War (August 1947 – May 1950)</xsd:documentation></xsd:annotation></xsd:enumeration><xsd:enumeration value="7"><xsd:annotation><xsd:documentation xml:lang="en">World War II (September 1940 – July 1947)</xsd:documentation></xsd:annotation></xsd:enumeration><xsd:enumeration value="8"><xsd:annotation><xsd:documentation xml:lang="en">Don’t know</xsd:documentation></xsd:annotation></xsd:enumeration><xsd:enumeration value="9"><xsd:annotation><xsd:documentation xml:lang="en">Refused</xsd:documentation></xsd:annotation></xsd:enumeration><xsd:enumeration value="10"><xsd:annotation><xsd:documentation xml:lang="en">Post September 11, 2001 (September 11, 2001 -Present)</xsd:documentation></xsd:annotation></xsd:enumeration></xsd:restriction></xsd:simpleType>
<xsd:complexType name="warZoneServed"><xsd:sequence><xsd:element name="WarZoneID" type="hmis:iDIndex"><xsd:annotation><xsd:documentation xml:lang="en">Establishes a unique ID for the War Zone sequence.</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="MonthsInWarZone" type="hmis:nonNegativeInteger" minOccurs="0"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.15E" xml:lang="en">"If yes [to ServedInWarZone], number of months in war zone"</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="ReceivedFire" type="hmis:fourValDKRefused" minOccurs="0"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.15E" xml:lang="en">If yes, [to ServedInWarZone] received hostile or friendly fire"</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="WarZone" type="hmis:warZone" minOccurs="0"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.15E" xml:lang="en">"If yes[to ServedInWarZone], name of war zone"</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="WarZoneOther" type="hmis:string50" minOccurs="0"><xsd:annotation><xsd:documentation xml:lang="en">If yes [to ServedInWarZone] See also Section 5.1.3 for treatment of "other" elements.</xsd:documentation></xsd:annotation></xsd:element></xsd:sequence></xsd:complexType>
<xsd:complexType name="serviceEvent"><xsd:sequence><xsd:element name="ServiceEventID" type="hmis:iDIndex"><xsd:annotation><xsd:documentation xml:lang="en">See HMIS XML Version 3.0 Cumulative Package Overview, IV.B.3.d..</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="SiteServiceID" type="xsd:nonNegativeInteger"><xsd:annotation><xsd:documentation xml:lang="en">Links the ServiceEvent to a particular SiteService</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="HouseholdID" type="hmis:id" minOccurs="0"><xsd:annotation><xsd:documentation xml:lang="en">If the person's entire household is also receiving the service, insert the ID of the household receiving this same ServiceEvent.</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="FundingSources" type="hmis:fundingSourcesServiceEvent" minOccurs="0"><xsd:annotation><xsd:documentation xml:lang="en">Tracks the fund that paid for the service event.</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="IsReferral" type="hmis:twoValBase" minOccurs="0"><xsd:annotation><xsd:documentation xml:lang="en">See HMIS XML Version 3.0 Cumulative Package Overview, Section 3: VI.11.</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="QuantityOfServiceEvent" type="xsd:nonNegativeInteger" minOccurs="0"><xsd:annotation><xsd:documentation xml:lang="en">See HMIS XML Version 3.0 Cumulative Package Overview, Section 3: VI.11.</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="QuantityOfServiceEventUnit" type="hmis:unit" minOccurs="0"><xsd:annotation><xsd:documentation xml:lang="en">See HMIS XML Version 3.0 Cumulative Package Overview, Section 3: VI.11.</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="ServiceEventAIRSCode" type="hmis:string50Base" minOccurs="0"><xsd:annotation><xsd:documentation xml:lang="en">See HMIS XML Version 3.0 Cumulative Package Overview, Section 3: VI.11.</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="ServiceEventEffectivePeriod" type="hmis:dateRangeOpen" minOccurs="0"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.15H" xml:lang="en">"Record “date of service” as the two-digit month, two-digit day and four-digit year."</xsd:documentation><xsd:documentation xml:lang="en">This data element allows a period of time for the service, instead of just a single date, which is also valid.</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="ServiceEventProvisionDate" type="xsd:date" minOccurs="0"><xsd:annotation><xsd:documentation source="" xml:lang="en">"Record “date of service” as the two-digit month, two-digit day and four-digit year."</xsd:documentation><xsd:documentation xml:lang="en">This data element tracks the date the service was given out. This can be used for tracking date arrearage payments made.</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="ServiceEventRecordedDate" type="xsd:dateTime" minOccurs="0"><xsd:annotation><xsd:documentation xml:lang="en">This is simply the date the ServiceEvent was recorded in the HMIS system.</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="ServiceEventNotes" type="hmis:notes" minOccurs="0"><xsd:annotation><xsd:documentation xml:lang="en">Any case manager or other notes regarding the service event.</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="ServiceEventIndFam" type="hmis:twoValBase" minOccurs="0"><xsd:annotation><xsd:documentation xml:lang="en">See HMIS XML Version 3.0 Cumulative Package Overview, Section 3: VI.11.</xsd:documentation></xsd:annotation></xsd:element><xsd:choice><xsd:element name="HMISServiceEventCode" type="hmis:hMISServiceEvent"><xsd:annotation><xsd:documentation xml:lang="en">Groups HMIS Service Type with free text other response.</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="HPRPFinancialAssistanceServiceEventCode" type="hmis:sixValBase" minOccurs="0"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.13" xml:lang="en">To determine the type of financial assistance (including rental assistance,security deposits, utility deposits, utility payments, moving cost assistance, and motel and hotel vouchers) and amount provided during program participation.</xsd:documentation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.13" xml:lang="en">Response categories for the types of financial assistance are consistent with the requirements of the HPRP Notice (FR-5307-N-01).</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="HPRPRelocationStabilizationServiceEventCode" type="hmis:fiveValBase"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.14" xml:lang="en">To determine the housing relocation and stabilization services provided during program participation. This data element is required for HPRP-funded programs in order to complete the QPR and APR.</xsd:documentation></xsd:annotation></xsd:element></xsd:choice></xsd:sequence></xsd:complexType>
<xsd:complexType name="fundingSourceServiceEvent"><xsd:complexContent><xsd:extension base="fundingSourceBase"><xsd:sequence><xsd:element name="AdvanceOrArrears" type="hmis:twoValBase" minOccurs="0"><xsd:annotation><xsd:documentation xml:lang="en">Optional way to indicate if the service event is for a past expenses</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="FinancialAssistanceAmount" type="hmis:currency" minOccurs="0"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.13">Programs must record the amount of HPRP financial assistance provided for each instance of one-time or ongoing financial assistance, as described above. Programs may also choose to record information on financial assistance provided through other sources. However, this should be recorded as a separate transaction in order to distinctly record and track HPRP financial assistance payments.</xsd:documentation><xsd:documentation xml:lang="en">Also used for HPRP Financial Assistance</xsd:documentation></xsd:annotation></xsd:element></xsd:sequence></xsd:extension></xsd:complexContent></xsd:complexType>
<xsd:complexType name="hMISServiceEvent"><xsd:sequence><xsd:element name="TypeOfService" type="hmis:typeOfService" minOccurs="0"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.15H" xml:lang="en">"To determine the services provided to clients during program participation."</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="TypeOfServiceOther" type="hmis:string50Base" minOccurs="0"/></xsd:sequence></xsd:complexType>
Type of Service1 = Food2 = Housing placement 3 = Material goods4 = Temporary housing and other financial aid5 = Transportation6 = Consumer assistance and protection7 = Criminal justice/legal services10 = Education11 = HIV/AIDS-related services12 = Mental health care/counseling13 = Other health care14 = Substance abuse services15 = Employment16 = Case/care management17 = Day care18 = Personal enrichment19 = Referral to other service(s) 20 = Outreach21 = Other
fiveval: Applicable to: Length of Stay at Prior Residence1 = One week or less2 = More than a week, but less than a month3 = One to three months4 = More than three months, but less than one year5 = One year or longerMilitary Branch1 = Army2 = Air Force3 = Navy4 = Marines5 = OtherHousing Relocation and Stabilization Services Provided1 = Case management2 = Outreach and engagement3 = Housing search and placement4 = Legal services5 = Credit repair
<xsd:simpleType name="fiveValBase"><xsd:annotation><xsd:documentation xml:lang="en">fiveval: Applicable to:
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
Military Branch
1 = Army
2 = Air Force
3 = Navy
4 = Marines
5 = Other
Housing Relocation and Stabilization Services Provided
1 = Case management
2 = Outreach and engagement
3 = Housing search and placement
4 = Legal services
5 = Credit repair</xsd:documentation></xsd:annotation><xsd:restriction base="xsd:unsignedInt"><xsd:minInclusive value="1"/><xsd:maxInclusive value="5"/></xsd:restriction></xsd:simpleType>
<xsd:complexType name="siteServiceParticipation"><xsd:sequence><xsd:element name="SiteServiceParticipationID" type="hmis:iDIndex"><xsd:annotation><xsd:documentation xml:lang="en">See HMIS XML Version 3.0 Cumulative Package Overview, IV.B.3.e..</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="SiteServiceID" type="xsd:nonNegativeInteger"><xsd:annotation><xsd:documentation xml:lang="en">See HMIS XML Version 3.0 Cumulative Package Overview, IV.B.3.e..</xsd:documentation><xsd:documentation xml:lang="en">Links to airs:tSiteService.Key</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="HouseholdID" type="hmis:id" minOccurs="0"><xsd:annotation><xsd:documentation xml:lang="en">See HMIS XML Version 3.0 Cumulative Package Overview, IV.B.3.e..</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="Need" type="hmis:need" minOccurs="0" maxOccurs="unbounded"><xsd:annotation><xsd:documentation xml:lang="en">See HMIS XML Version 3.0 Cumulative Package Overview, IV.B.3.e.i..</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="ParticipationDates" type="hmis:dateRangeOpen"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 3.12 and 3.13" xml:lang="en">This data element is needed for reporting purposes for all programs and to measure lengths of stay for residential programs.</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="PersonHistorical" type="hmis:personHistorical" minOccurs="0" maxOccurs="unbounded"><xsd:annotation><xsd:documentation xml:lang="en">See HMIS XML Version 3.0 Cumulative Package Overview, IV.B.3.b..</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="ReasonsForLeaving" type="hmis:reasonForLeaving" minOccurs="0" maxOccurs="unbounded"><xsd:annotation><xsd:documentation xml:lang="en">Groups ReasonForLeavingCode with ReasonForLeavingOther responses.</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="ServiceEvent" type="hmis:serviceEvent" minOccurs="0" maxOccurs="unbounded"><xsd:annotation><xsd:documentation xml:lang="en">See HMIS XML Version 3.0 Cumulative Package Overview, IV.B.3.d..</xsd:documentation></xsd:annotation></xsd:element></xsd:sequence></xsd:complexType>
<xsd:complexType name="reasonForLeaving"><xsd:sequence><xsd:element name="ReasonForLeavingID" type="hmis:iDIndex"><xsd:annotation><xsd:documentation xml:lang="en">Establishes a unique ID for the ReasonForLeaving element sequence.</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="ReasonForLeaving" type="hmis:elevenVal" minOccurs="0"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.15G" xml:lang="en">Identify the reason why the client left the program. If a client left for multiple reasons, record only the primary reason.</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="ReasonForLeavingOther" type="hmis:string50" minOccurs="0"><xsd:annotation><xsd:documentation xml:lang="en">Free text field used when "Other" is selected in ReasonForLeaving.</xsd:documentation></xsd:annotation></xsd:element></xsd:sequence></xsd:complexType>
elevenVal: Applicable to: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 program 5 = Criminal activity/destruction of property/violence 6 = Reached maximum time allowed by project 7 = Needs could not be met by program 8 = Disagreement with rules/persons 9 = Death 10 = Unknown/disappeared 11 = Other Target Population Type A 1 = SM Single Males (18 years and older) 2 = SF Single Females (18 years and older) 3 = SMF Single Males and Females (18 years and older) 4 = CO Couples Only, No Children 5 = SM+HC Single Males and Households with Children 6 = SF+HC Single Females and Households with Children 7 = HC Households with Children 8 = YM Unaccompanied Young Males (under 18) 9 = YF Unaccompanied Young Females (under 18) 10 = YMF Unaccompanied Young Males and Females (under 18) 11 = SMF+HC Single Male and Female and Households with Children
<xsd:simpleType name="elevenValBase"><xsd:annotation><xsd:documentation xml:lang="en">elevenVal: Applicable to:
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 program
5 = Criminal activity/destruction of property/violence
6 = Reached maximum time allowed by project
7 = Needs could not be met by program
8 = Disagreement with rules/persons
9 = Death
10 = Unknown/disappeared
11 = Other
Target Population Type A
1 = SM Single Males (18 years and older)
2 = SF Single Females (18 years and older)
3 = SMF Single Males and Females (18 years and older)
4 = CO Couples Only, No Children
5 = SM+HC Single Males and Households with Children
6 = SF+HC Single Females and Households with Children
7 = HC Households with Children
8 = YM Unaccompanied Young Males (under 18)
9 = YF Unaccompanied Young Females (under 18)
10 = YMF Unaccompanied Young Males and Females (under 18)
11 = SMF+HC Single Male and Female and Households with Children</xsd:documentation></xsd:annotation><xsd:restriction base="xsd:unsignedInt"><xsd:minInclusive value="1"/><xsd:maxInclusive value="11"/></xsd:restriction></xsd:simpleType>
<xsd:complexType name="sSNHashingChoice"><xsd:sequence><xsd:choice><xsd:element name="Unhashed" type="hmis:sSNumber" minOccurs="0"/><xsd:element name="Hashed" type="hmis:string50" minOccurs="0"/></xsd:choice><xsd:element name="SocialSecNumberQualityCode" type="hmis:fourValDKRefused2"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 3.2" xml:lang="en">"In another field, record the appropriate SSN type (data quality code)."</xsd:documentation></xsd:annotation></xsd:element></xsd:sequence></xsd:complexType>
<xsd:complexType name="service"><xsd:complexContent><xsd:extension base="airs:tService"><xsd:sequence><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 2.3" xml:lang="en">To uniquely identify each CoC Program within the CoC.</xsd:documentation><xsd:documentation xml:lang="en">Program Identifier is mapped to airs:tService.Key</xsd:documentation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 2.4" xml:lang="en">To identify the name of each CoC Program within the CoC.</xsd:documentation><xsd:documentation xml:lang="en">Program Name is mapped to airs:tService.Name</xsd:documentation></xsd:annotation><xsd:element name="COCCode" type="hmis:string5Base" minOccurs="0"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 2.7" xml:lang="en">To associate each CoC Program with a CoC for HUD reporting purposes.</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="Configuration" minOccurs="0" type="hmis:threeValBase"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 2.6A" xml:lang="en">"...record the site configuration type as follows: 1. Single site, single building. Housing units (or service encounters) are at one site, in a single structure. 2. Single site, multiple buildings. Housing units (or service encounters) are at one site, in multiple structures (e.g., single apartment complex with multiple buildings and program units in two or more buildings). 3. Multiple sites. Housing units (or service encounters) are at multiple sites (e.g., scattered-site housing, outreach)."</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="DirectServiceCode" type="hmis:twoValBase" minOccurs="0"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 2.5" xml:lang="en">To differentiate CoC Programs in the HMIS that provide direct services from organizations that do not provide direct services (such as HMIS Lead Agencies, organizations that oversee or support CoC Programs, or software solution providers).</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="FundingSources" type="hmis:fundingSourcesService" minOccurs="0"><xsd:annotation><xsd:documentation xml:lang="en">Provides a place to assign a set of Federal funding sources to the Service.</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="GranteeIdentifier" type="hmis:string10Base" minOccurs="0"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 2.13" xml:lang="en">"All subgrantees of a federal HPRP grantee must identify their projects with the original state or local grantee identifier as assigned by HUD."</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="IndividualFamilyCode" type="hmis:fourValBase" minOccurs="0"><xsd:annotation><xsd:documentation xml:lang="en">See HMIS XML Version 3.0 Cumulative Package Overview, IV.B.4.</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="Inventory" type="hmis:inventory" minOccurs="0" maxOccurs="unbounded"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 2.9" xml:lang="en">To record inventory information for each residential CoC Program in order to produce Housing Inventory data for the CoC application and the AHAR.</xsd:documentation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 2.9" xml:lang="en">The revised data standards also state: "These data may also be collected separately for distinct sites within a program, as long as they can be aggregated to the program level.". So, inventory is also included as a subelement of SiteService, so that site-based inventories can be conveyed, though site-based inventory tracking is not required.</xsd:documentation><xsd:documentation xml:lang="en">Alternatively, each bed can be individually reported using an asset.</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="ResidentialTrackingMethod" type="hmis:threeValBase" minOccurs="0"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 2.12">Record the method used to track the actual nights that a client stays in a program.</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="ServiceType" type="hmis:serviceType" minOccurs="0"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 2.8" xml:lang="en">To associate each CoC Program with the specific type of service offered.</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="ServiceEffectivePeriod" type="hmis:dateRangeOpen" minOccurs="0"><xsd:annotation><xsd:documentation xml:lang="en">Period of time during which this service is in existence.</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="ServiceRecordedDate" type="xsd:dateTime"><xsd:annotation><xsd:documentation xml:lang="en">Simply the date when this Service data was added to the system for synchronization purposes. Required.</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="TargetPopulationA" type="hmis:elevenValBase" minOccurs="0"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 2.10" xml:lang="en">"This information may be used to track bed utilization and service gaps."</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="TargetPopulationB" type="hmis:fourValBase" minOccurs="0"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 2.11" xml:lang="en">"To allow HMIS to produce the Housing Inventory data for the for the annual CoC application to HUD."</xsd:documentation></xsd:annotation></xsd:element></xsd:sequence><xsd:attributeGroup ref="hmis:deleteStampGroup"/></xsd:extension></xsd:complexContent></xsd:complexType>
<xsd:complexType name="inventory"><xsd:annotation><xsd:documentation xml:lang="en">Based on 1/15/2010 "2010 Housing Inventory and 2010 Point-in-Time Homeless Persons Counts Data Collection Guidance"</xsd:documentation></xsd:annotation><xsd:complexContent><xsd:extension base="hmis:bedAndUnitInfo"><xsd:sequence><xsd:element name="InventoryID" type="hmis:iDIndex"><xsd:annotation><xsd:documentation xml:lang="en">Unique ID to track each inventory.</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="BedInventory" type="hmis:bedCountBase" minOccurs="0"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 2.9D" xml:lang="en">"The bed inventory data element is an integer that tracks the total number of beds available for occupancy as of the inventory start date..."</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="HMISParticipatingBeds" type="xsd:nonNegativeInteger" minOccurs="0"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 2.9I" xml:lang="en">"This data element is an integer that tracks the total number of beds participating in HMIS as of the HMIS participation start date recorded in 2.9J."</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="InventoryEffectivePeriod" type="hmis:dateRangeOpen" minOccurs="0"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 2.9G" xml:lang="en">"The inventory effective period constrains when the bed and unit inventory information applies."</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="InventoryRecordedDate" type="xsd:dateTime"><xsd:annotation><xsd:documentation xml:lang="en">Used for synchronization purposes to differentiate two sets of inventory for the same period.</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="UnitInventory" type="xsd:nonNegativeInteger" minOccurs="0"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 2.9F" xml:lang="en">"The unit inventory data element is an integer that tracks the total number of units available for occupancy as of the inventory start date recorded in 2.1.9G."</xsd:documentation></xsd:annotation></xsd:element></xsd:sequence></xsd:extension></xsd:complexContent></xsd:complexType>
"Describes the availability of beds based on whether beds are available on a planned basis year-round or seasonally (during a defined period of high demand), or on an ad hoc or temporary basis as demand indicates."
This data element arises from HIC requirements. The Service also indicates whether it primarily serves individuals or families, but this is more specific for inventory counts for the HIC.
"describes the type of program beds based on whether beds are: located in a residential homeless assistance program facility (including cots or mats); provided through a voucher with a hotel or motel; other types of beds"
"(Permanent Supportive Housing Programs Only). The chronic homeless bed status data element is an yes/no flag that tracks whether the beds are available for occupancy for chronically homeless persons as of the inventory start date recorded in 2.1.9G."
To arrive at chronic homelessness inventory from the alternate asset tracking method, one would have to look at the asset assignment's person id, then look for any chronic homeless episodes in their person historical data that overlap the bed stay.
<xsd:simpleType name="twoVal2Base"><xsd:annotation><xsd:documentation xml:lang="en">Applicable to:
Household Type
1 = Households without children
2 = Households with children</xsd:documentation></xsd:annotation><xsd:restriction base="xsd:unsignedInt"><xsd:enumeration value="1"/><xsd:enumeration value="2"/></xsd:restriction></xsd:simpleType>
<xsd:complexType name="site"><xsd:complexContent><xsd:extension base="airs:tSite"><xsd:sequence><xsd:element name="AgencyKey" type="xsd:nonNegativeInteger" minOccurs="0"><xsd:annotation><xsd:documentation>This represents ID of parent Agency.</xsd:documentation></xsd:annotation></xsd:element></xsd:sequence><xsd:attributeGroup ref="hmis:deleteStampGroup"><xsd:annotation><xsd:documentation xml:lang="en">Allows for the deletion of a Site. Provide only the airs:tSite.Key when this is used.</xsd:documentation></xsd:annotation></xsd:attributeGroup></xsd:extension></xsd:complexContent></xsd:complexType>
<xsd:complexType name="siteService"><xsd:complexContent><xsd:extension base="airs:tSiteService"><xsd:sequence><xsd:element name="ServiceID" type="xsd:nonNegativeInteger"/><xsd:element name="SiteID" type="xsd:nonNegativeInteger"><xsd:annotation><xsd:documentation xml:lang="en">A "Site" is, in AIRS XML parlance, the parent of a SiteService; a physical location. This ID links back up to the parent Site.Key.</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="GeographicCode" type="hmis:geographicCode" minOccurs="0"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 2.6C" xml:lang="en">For the principal program service site, record the geocode associated with the geographic location of the site.</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="HMISAsset" type="hmis:hMISAsset" minOccurs="0" maxOccurs="unbounded"><xsd:annotation><xsd:documentation xml:lang="en">A physical item that can be assigned to an individual. The two types of assets currently covered by the HMIS Revised Data Standard are housing units and shelter beds, so the generic asset type is extended to make the hMISAsset, which has HMIS-specific asset information. The aggregate counts of these can serve as a proxy for an Inventory, found in Service.</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="HousingType" type="hmis:sevenVal" minOccurs="0"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 2.6E" xml:lang="en">For the principal program service site, record the appropriate housing type.</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="Inventory" type="hmis:inventory" minOccurs="0" maxOccurs="unbounded"><xsd:annotation><xsd:documentation xml:lang="en" source="2010 HUD HMIS Data and Technical Standards, Section 2.9">Inventory counts aggregate bed and unit info for HUD HMIS reporting. SiteService.Inventory is used for Housing Inventory Chart (HIC) reporting. Alternatively, each bed can be individually reported using an asset.</xsd:documentation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 2.9" xml:lang="en">The revised data stnadards also state: "These data may also be collected separately for distinct sites within a program, as long as they can be aggregated to the program level.". The placement of Inventory, here within SiteService, accomodates conveying site-based inventories. However, this is not required, and Inventory is also included as a subelement of Service, so that non-site-based inventories can be conveyed.</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="Principal" type="hmis:twoValBase" minOccurs="0"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 2.6B" xml:lang="en">This yes/no element designates whether this SiteService is the "principal program service site".</xsd:documentation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 2.6B" xml:lang="en">The data standards also track the address of this principal site service. That is located by completing information for the parent Site (referenced by SiteService.SiteID) of the principal Site Service at airs:tSite.PhysicalAddress.</xsd:documentation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 2.6B" xml:lang="en">In the data standards, it mentions that "Programs without a principal program service site (e.g., mobile programs such as street outreach and scattered-site housing programs) should record the address of their administrative office." The administrative office location is located at airs:tAgency.AgencyLocation.tSite.PhysicalAddress.</xsd:documentation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 2.6" xml:lang="en">In the data standards, it mentions that "Programs may choose to record the Site Information data element for each site or facility operated by the program.", so even if a Site Service is not the principal SiteService, information in section 2.6 can still be tracked.</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="PITCountSet" type="hmis:pITCountSet" minOccurs="0" maxOccurs="unbounded"><xsd:annotation><xsd:documentation xml:lang="en">Holds a set of PIT Count data collected at the program site level.</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="SiteServiceEffectivePeriod" type="hmis:dateRangeOpen" minOccurs="0"><xsd:annotation><xsd:documentation xml:lang="en">When this SiteService was entered into the system, for synchronization purposes.</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="SiteServiceRecordedDate" type="xsd:dateTime" minOccurs="0"><xsd:annotation><xsd:documentation xml:lang="en">When this SiteService was entered into the system, for synchronization purposes.</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="SiteServiceType" type="hmis:threeValBase" minOccurs="0"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 2.6D" xml:lang="en">For the principal program service site, record the site type as follows: 1. Non-residential: services only. The program only provides supportive services and does not provide overnight accommodations. 2. Residential: special needs and non-special needs. Residential housing (i.e., site that provides overnight accommodation) is located within a building or complex that houses both persons with special needs—e.g., homeless or formerly homeless persons, persons with substance abuseproblems, persons with mental illness, or persons with HIV/AIDS—andpersons without any special needs. 3. Residential: special needs only. Residential housing is located within a building or complex that houses only persons with special needs—e.g., homeless or formerly homeless persons, persons with substance abuse problems, persons with mental illness, persons with HIV/AIDS, persons with a physical disability, and/or elderly persons.</xsd:documentation></xsd:annotation></xsd:element></xsd:sequence><xsd:attributeGroup ref="deleteStampGroup"/></xsd:extension></xsd:complexContent></xsd:complexType>
<xsd:complexType name="asset"><xsd:sequence><xsd:element name="AssetID" type="hmis:iDIndex"><xsd:annotation><xsd:documentation xml:lang="en">Assigns a unique identifier to the particular asset.</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="AssetCount" type="hmis:bedCountBase"><xsd:annotation><xsd:documentation xml:lang="en">Quantity of asset tracked. Usually, this will be "1", if assigned to an individual.</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="AssetType" type="hmis:twoValBase"><xsd:annotation><xsd:documentation xml:lang="en">Currently, the only asset types are beds or units. If it is not one of these, HUD will not need this asset reported.</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="AssetEffectivePeriod" type="hmis:dateRangeOpen" minOccurs="0"><xsd:annotation><xsd:documentation xml:lang="en">Similar to the Inventory Start and End Dates in 2.9G and 2.9H, except this only pertains to one bed/unit.</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="AssetRecordedDate" type="xsd:dateTime"><xsd:annotation><xsd:documentation xml:lang="en">Simply tracks the date and time the asset was entered into the system for synchronization purposes.</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="Assignment" type="hmis:assignment" minOccurs="0" maxOccurs="unbounded"><xsd:annotation><xsd:documentation xml:lang="en">Assigns an asset to a person.</xsd:documentation></xsd:annotation></xsd:element></xsd:sequence></xsd:complexType>
<xsd:complexType name="assignment"><xsd:sequence><xsd:element name="AssignmentID" type="hmis:iDIndex"><xsd:annotation><xsd:documentation xml:lang="en">Assigns a unique identifier to the assignment of the asset to the person.</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="PersonID" type="hmis:id"><xsd:annotation><xsd:documentation xml:lang="en">ID of the Person linked to this asset assignment.</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="HouseholdID" type="hmis:id" minOccurs="0" maxOccurs="1"><xsd:annotation><xsd:documentation xml:lang="en">Optional unique identifier of a household associated with this asset assignment. The Assignment.PersonID should identify a member of this household.</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="AssignmentPeriod" type="hmis:dateRangeCapped" minOccurs="0" maxOccurs="unbounded"><xsd:annotation><xsd:documentation xml:lang="en">Period of time during which the assignment to the Person/Household is in effect.</xsd:documentation></xsd:annotation></xsd:element></xsd:sequence></xsd:complexType>
<xsd:simpleType name="sevenValBase"><xsd:restriction base="xsd:integer"><xsd:annotation><xsd:documentation xml:lang="en">Applicable to:
Housing Type
1 = Mass shelter/barracks
2 = Dormitory/hotel/motel
3 = Shared housing
4 = Single Room Occupancy (SRO) units
5 = Single apartment (non-SRO) units
6 = Single homes/townhouses/duplexes
7 = Not applicable: non-residential program</xsd:documentation></xsd:annotation><xsd:minInclusive value="1"/><xsd:maxInclusive value="7"/></xsd:restriction></xsd:simpleType>
<xsd:complexType name="pITCountSet"><xsd:annotation><xsd:documentation xml:lang="en">Based on 1/15/2010 "2010 Housing Inventory and 2010 Point-in-Time Homeless Persons Counts Data Collection Guidance"</xsd:documentation></xsd:annotation><xsd:sequence><xsd:element name="PITCountSetID" type="hmis:iDIndex"><xsd:annotation><xsd:documentation xml:lang="en">Establishes a unique ID for the Pregnancy element sequence.</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="HUDWaiverReceived" type="hmis:twoValBase" minOccurs="0"><xsd:annotation><xsd:documentation xml:lang="en">for Point In Time Chart, whether HUD granted a waiver for PIT reporting</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="HUDWaiverDate" type="xsd:date" minOccurs="0"><xsd:annotation><xsd:documentation xml:lang="en">for Point In Time Chart, date HUD granted a waiver for PIT reporting</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="HUDWaiverEffectivePeriod" type="dateRangeOpen" minOccurs="0"><xsd:annotation><xsd:documentation xml:lang="en">for Point In Time Chart, date range during which HUD granted waiver for PIT reporting is effective.</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="LastPITShelteredCountDate" type="xsd:date" minOccurs="0"><xsd:annotation><xsd:documentation xml:lang="en">for Housing Inventory Chart and Point In Time Chart</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="LastPITUnshelteredCountDate" type="xsd:date" minOccurs="0"><xsd:annotation><xsd:documentation xml:lang="en">for Housing Inventory Chart and Point In Time Chart</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="PITCounts" type="hmis:pITCounts" minOccurs="0"><xsd:annotation><xsd:documentation xml:lang="en">Holds a series of Pit Count data elements.</xsd:documentation></xsd:annotation></xsd:element></xsd:sequence></xsd:complexType>
<xsd:complexType name="pITCounts"><xsd:sequence minOccurs="0" maxOccurs="unbounded"><xsd:element name="PITCount" type="hmis:pITCount"><xsd:annotation><xsd:documentation xml:lang="en">for Point In Time Chart</xsd:documentation></xsd:annotation></xsd:element></xsd:sequence></xsd:complexType>
Within each sheltered and unsheltered category, PIT homeless person counts will be recorded in the following household types:a. Number of persons in households without children;b. Number of persons in households with at least one adult and one child; andc. Number of persons in households with only children. This includes only personsage 17 or under, including unaccompanied youth, adolescent parents and theirchildren, adolescent siblings, or other household configurations composed onlyof children.
Source
<xsd:complexType name="pITCount"><xsd:sequence><xsd:element name="PITCountValue" type="xsd:nonNegativeInteger"/><xsd:element name="PITCountEffectivePeriod" type="hmis:dateRangeCapped" minOccurs="0"><xsd:annotation><xsd:documentation xml:lang="en">Date range for which the PIT Counts apply.</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="PITCountRecordedDate" type="xsd:date"><xsd:annotation><xsd:documentation xml:lang="en">The date this PIT Count is recorded in the originating system, for synchronization purposes.</xsd:documentation></xsd:annotation></xsd:element></xsd:sequence><xsd:attribute name="pITHouseholdType" type="threeValBase" use="required"><xsd:annotation><xsd:documentation source="'2010 Housing Inventory and 2010 Point-in-Time Homeless Persons Counts Data Collection Guidance', 1/15/2010" xml:lang="en">Within each sheltered and unsheltered category, PIT homeless person counts will be recorded in the following household types:
a. Number of persons in households without children;
b. Number of persons in households with at least one adult and one child; and
c. Number of persons in households with only children. This includes only persons
age 17 or under, including unaccompanied youth, adolescent parents and their
children, adolescent siblings, or other household configurations composed only
of children.</xsd:documentation></xsd:annotation></xsd:attribute></xsd:complexType>
Number of persons in households with only children. This includes only persons age 17 or under, including unaccompanied youth, adolescent parents and their children, adolescent siblings, or other household configurations composed only of children.
Source
<xsd:simpleType name="bedStatusEnum"><xsd:restriction base="xsd:string"><xsd:enumeration value="householdNoChildren"><xsd:annotation><xsd:documentation source="'2010 Housing Inventory and 2010 Point-in-Time Homeless Persons Counts Data Collection Guidance', 1/15/2010 " xml:lang="en">Number of persons in households without children</xsd:documentation></xsd:annotation></xsd:enumeration><xsd:enumeration value="householdOneAdultOneChild"><xsd:annotation><xsd:documentation source="'2010 Housing Inventory and 2010 Point-in-Time Homeless Persons Counts Data Collection Guidance', 1/15/2010 " xml:lang="en">Number of persons in households with at least one adult and one child</xsd:documentation></xsd:annotation></xsd:enumeration><xsd:enumeration value="householdOnlyChildren"><xsd:annotation><xsd:documentation source="'2010 Housing Inventory and 2010 Point-in-Time Homeless Persons Counts Data Collection Guidance', 1/15/2010 " xml:lang="en">Number of persons in households with only children. This includes only persons age 17 or under, including unaccompanied youth, adolescent parents and their children, adolescent siblings, or other household configurations composed only of children.</xsd:documentation></xsd:annotation></xsd:enumeration></xsd:restriction></xsd:simpleType>
Optionally allows specification of a deleted record. If record is to be added, do not append this attribute, since "add" is the default, understood behavior.
<xsd:attribute name="delete" type="hmis:twoValBase" fixed="1" use="optional"><xsd:annotation><xsd:documentation xml:lang="en">Optionally allows specification of a deleted record. If record is to be added, do not append this attribute, since "add" is the default, understood behavior.</xsd:documentation></xsd:annotation></xsd:attribute>
"Describes the availability of beds based on whether beds are available on a planned basis year-round or seasonally (during a defined period of high demand), or on an ad hoc or temporary basis as demand indicates."
<xsd:attribute name="bedAvailability" type="hmis:threeValBase"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 2.9C" xml:lang="en">"Describes the availability of beds based on whether beds are available on a planned basis year-round or seasonally (during a defined period of high demand), or on an ad hoc or temporary basis as demand indicates."</xsd:documentation></xsd:annotation></xsd:attribute>
<xsd:attribute name="bedStatus" type="hmis:threeValBase"><xsd:annotation><xsd:documentation xml:lang="en">For HIC reporting, identifies if the beds are current/new/under development.</xsd:documentation></xsd:annotation></xsd:attribute>
"describes the type of program beds based on whether beds are: located in a residential homeless assistance program facility (including cots or mats); provided through a voucher with a hotel or motel; other types of beds"
<xsd:attribute name="bedType" type="hmis:threeValBase"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 2.9B" xml:lang="en">"describes the type of program beds based on whether beds are: located in a residential homeless assistance program facility (including cots or mats); provided through a voucher with a hotel or motel; other types of beds"</xsd:documentation></xsd:annotation></xsd:attribute>
This data element arises from HIC requirements. The Service also indicates whether it primarily serves individuals or families, but this is more specific for inventory counts for the HIC.
<xsd:attribute name="bedIndividualFamilyType" type="hmis:twoValBase"><xsd:annotation><xsd:documentation>This data element arises from HIC requirements. The Service also indicates whether it primarily serves individuals or families, but this is more specific for inventory counts for the HIC.</xsd:documentation></xsd:annotation></xsd:attribute>
"(Permanent Supportive Housing Programs Only). The chronic homeless bed status data element is an yes/no flag that tracks whether the beds are available for occupancy for chronically homeless persons as of the inventory start date recorded in 2.1.9G."
To arrive at chronic homelessness inventory from the alternate asset tracking method, one would have to look at the asset assignment's person id, then look for any chronic homeless episodes in their person historical data that overlap the bed stay.
<xsd:attribute name="chronicHomelessBed" type="hmis:twoValBase"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 2.9E" xml:lang="en">"(Permanent Supportive Housing Programs Only). The chronic homeless bed status data element is an yes/no flag that tracks whether the beds are available for occupancy for chronically homeless persons as of the inventory start date recorded in 2.1.9G."</xsd:documentation><xsd:documentation xml:lang="en">To arrive at chronic homelessness inventory from the alternate asset tracking method, one would have to look at the asset assignment's person id, then look for any chronic homeless episodes in their person historical data that overlap the bed stay.</xsd:documentation></xsd:annotation></xsd:attribute>
<xsd:attribute name="householdType" type="hmis:twoVal2Base"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 2.9A" xml:lang="en">"describes the household type served by beds and units counted in the Bed and Unit Inventory Information data elements"</xsd:documentation></xsd:annotation></xsd:attribute>
Within each sheltered and unsheltered category, PIT homeless person counts will be recorded in the following household types:a. Number of persons in households without children;b. Number of persons in households with at least one adult and one child; andc. Number of persons in households with only children. This includes only personsage 17 or under, including unaccompanied youth, adolescent parents and theirchildren, adolescent siblings, or other household configurations composed onlyof children.
<xsd:attribute name="pITHouseholdType" type="threeValBase" use="required"><xsd:annotation><xsd:documentation source="'2010 Housing Inventory and 2010 Point-in-Time Homeless Persons Counts Data Collection Guidance', 1/15/2010" xml:lang="en">Within each sheltered and unsheltered category, PIT homeless person counts will be recorded in the following household types:
a. Number of persons in households without children;
b. Number of persons in households with at least one adult and one child; and
c. Number of persons in households with only children. This includes only persons
age 17 or under, including unaccompanied youth, adolescent parents and their
children, adolescent siblings, or other household configurations composed only
of children.</xsd:documentation></xsd:annotation></xsd:attribute>
<xsd:attribute name="version" type="hmis:version"><xsd:annotation><xsd:documentation xml:lang="en">The version number of HMIS XML Schema the XML instance document conforms to (e.g. 3.0).</xsd:documentation></xsd:annotation></xsd:attribute>
<xsd:group name="childEnrolledYes"><xsd:sequence><xsd:element name="ChildSchoolName" type="hmis:string50" minOccurs="0"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.15F" xml:lang="en">If yes [to ChildCurrentlyEnrolledInSchool], name of child’s school.</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="ChildMcKinneyVentoLiaison" type="hmis:fourValDKRefused" minOccurs="0"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.15F" xml:lang="en">"If yes [to ChildCurrentlyEnrolledInSchool], was/is the child connected to the McKinney-Vento Homeless Assistance Act school liaison?"</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="ChildSchoolType" type="hmis:fourValDKRefused2" minOccurs="0"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.15F" xml:lang="en">"If yes [to ChildCurrentlyEnrolledInSchool], type of school."</xsd:documentation></xsd:annotation></xsd:element></xsd:sequence></xsd:group>
<xsd:group name="childEnrolledNo"><xsd:sequence><xsd:element name="ChildEnrollmentBarrier" type="hmis:barrier" minOccurs="0" maxOccurs="unbounded"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.15F" xml:lang="en">"If not enrolled, identify problems in enrolling child"</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="ChildSchoolLastEnrolledDate" type="hmis:date" minOccurs="0"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 4.15F" xml:lang="en">"If not enrolled, last date of enrollment"</xsd:documentation><xsd:documentation xml:lang="en">If day not known, use "01" for day.</xsd:documentation></xsd:annotation></xsd:element></xsd:sequence></xsd:group>
<xsd:group name="bedAndUnitInfo"><xsd:sequence><xsd:element name="HMISParticipationPeriod" type="hmis:dateRangeOpen" minOccurs="0"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 2.9J" xml:lang="en">"This is the date when the HMIS participating bed information first applies (i.e., the date when a change in the number of HMIS participating beds occurs for a program’s Bed and Unit Inventory Record)."</xsd:documentation></xsd:annotation></xsd:element></xsd:sequence></xsd:group>
Optionally allows specification of a deleted record. If record is to be added, do not append this attribute, since "add" is the default, understood behavior.
<xsd:attributeGroup name="deleteStampGroup"><xsd:attribute name="delete" type="hmis:twoValBase" fixed="1" use="optional"><xsd:annotation><xsd:documentation xml:lang="en">Optionally allows specification of a deleted record. If record is to be added, do not append this attribute, since "add" is the default, understood behavior.</xsd:documentation></xsd:annotation></xsd:attribute><xsd:attribute name="deleteOccurredDate" type="xsd:dateTime" use="optional"><xsd:annotation><xsd:documentation xml:lang="en">Date deletion occured.</xsd:documentation></xsd:annotation></xsd:attribute><xsd:attribute name="deleteEffective" type="xsd:dateTime" use="optional"><xsd:annotation><xsd:documentation xml:lang="en">Date deletion effective.</xsd:documentation></xsd:annotation></xsd:attribute></xsd:attributeGroup>
"Describes the availability of beds based on whether beds are available on a planned basis year-round or seasonally (during a defined period of high demand), or on an ad hoc or temporary basis as demand indicates."
This data element arises from HIC requirements. The Service also indicates whether it primarily serves individuals or families, but this is more specific for inventory counts for the HIC.
"describes the type of program beds based on whether beds are: located in a residential homeless assistance program facility (including cots or mats); provided through a voucher with a hotel or motel; other types of beds"
"(Permanent Supportive Housing Programs Only). The chronic homeless bed status data element is an yes/no flag that tracks whether the beds are available for occupancy for chronically homeless persons as of the inventory start date recorded in 2.1.9G."
To arrive at chronic homelessness inventory from the alternate asset tracking method, one would have to look at the asset assignment's person id, then look for any chronic homeless episodes in their person historical data that overlap the bed stay.
"describes the household type served by beds and units counted in the Bed and Unit Inventory Information data elements"
Source
<xsd:attributeGroup name="bedAndUnitInfo"><xsd:attribute name="bedAvailability" type="hmis:threeValBase"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 2.9C" xml:lang="en">"Describes the availability of beds based on whether beds are available on a planned basis year-round or seasonally (during a defined period of high demand), or on an ad hoc or temporary basis as demand indicates."</xsd:documentation></xsd:annotation></xsd:attribute><xsd:attribute name="bedStatus" type="hmis:threeValBase"><xsd:annotation><xsd:documentation xml:lang="en">For HIC reporting, identifies if the beds are current/new/under development.</xsd:documentation></xsd:annotation></xsd:attribute><xsd:attribute name="bedType" type="hmis:threeValBase"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 2.9B" xml:lang="en">"describes the type of program beds based on whether beds are: located in a residential homeless assistance program facility (including cots or mats); provided through a voucher with a hotel or motel; other types of beds"</xsd:documentation></xsd:annotation></xsd:attribute><xsd:attribute name="bedIndividualFamilyType" type="hmis:twoValBase"><xsd:annotation><xsd:documentation>This data element arises from HIC requirements. The Service also indicates whether it primarily serves individuals or families, but this is more specific for inventory counts for the HIC.</xsd:documentation></xsd:annotation></xsd:attribute><xsd:attribute name="chronicHomelessBed" type="hmis:twoValBase"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 2.9E" xml:lang="en">"(Permanent Supportive Housing Programs Only). The chronic homeless bed status data element is an yes/no flag that tracks whether the beds are available for occupancy for chronically homeless persons as of the inventory start date recorded in 2.1.9G."</xsd:documentation><xsd:documentation xml:lang="en">To arrive at chronic homelessness inventory from the alternate asset tracking method, one would have to look at the asset assignment's person id, then look for any chronic homeless episodes in their person historical data that overlap the bed stay.</xsd:documentation></xsd:annotation></xsd:attribute><xsd:attribute name="domesticViolenceShelterBed" type="hmis:twoValBase"><xsd:annotation><xsd:documentation xml:lang="en">For HIC reporting of domestic violence shelter beds</xsd:documentation></xsd:annotation></xsd:attribute><xsd:attribute name="householdType" type="hmis:twoVal2Base"><xsd:annotation><xsd:documentation source="2010 HUD HMIS Data and Technical Standards, Section 2.9A" xml:lang="en">"describes the household type served by beds and units counted in the Bed and Unit Inventory Information data elements"</xsd:documentation></xsd:annotation></xsd:attribute></xsd:attributeGroup>