Laserfiche WebLink
Attachment C <br />7.3.2 Timeliness <br />Participant data should be entered into HMIS as close to the date of collection as possible. Entering <br />data as soon as possible supports data quality by avoiding backlogs of pending data and allowing near <br />real time analysis and reporting. <br />Shelter Programs must enter/update project participant data in HMIS within 14 calendar days <br />following the date of project enrollment/exit. <br />Counties not using the State HMIS (data integration counties), must work with the HMIS Manager to <br />provide full CSV exports every six months. When Commerce is able to accept monthly imports, <br />Counties must upload data to the State's HMIS using XML or CSV schema compliant with current HUD <br />HMIS Data Standards. Uploads must occur no later than the 30th calendar day following the end of <br />each month. Counties not able to export and upload data to the State HMIS using an approved format <br />must use the State HMIS for direct data entry. <br />7.3.9 Accuracy <br />Data entered into HMIS must reflect the real situation of the participant as closely as possible. <br />Accurate data is necessary to ensure any project reporting fairly represents the work of the project and <br />each participant's story. <br />Exomples of ddto accurocy: <br />Elements of Data Accuracy <br />Project Start Date <br />Date of Birth and , Ensure the two are not the same dates <br />Ensure responses for Prior living situation, Length of stay in prior living situation, <br />Situation data Approximate date homelessness started, Numbe <br />Prior Living <br />elements <br />Disabling Condition <br />homelessness in the last 3 years, and Number of <br />the last 3 ye91s do not conflict with each other <br />Ensure the Yes/No answer does not conflict with <br />conditions <br />Ensure the Yes/No answer does not conflict with <br />Ensure the Yes/No answer does not conflict with <br />income. <br />r of times the client has experienced <br />'months experiencing homelessness in <br />trre speciric ivp"j ot aiiinrine i <br />: <br />the spec,ific types of f'"iftf' l1irfinc", . <br />the specific sources of monthly j <br />Health lnsurance <br />Monthly lncome <br />, rvon-i"irt eenetiti <br />Relationship to <br />Head of Household <br />. <br />i' <br />r Veteran Status <br />i, Project Population <br />Specifics <br />Ensure the <br />benefits. <br />' Ensure there is only one Head of Household for any given household (including clients <br />served individually) and that this element is entered and accurate for all household <br />members. <br />Ensure individuals under L8 years of qge 9re n9t ldentified as veterans. <br />Ensure that projects only serving individuals only enroll individuals and not multi- <br />, person households. <br />Ensure that projects only serving families with children only enroll families with <br />children. <br />Ensure that projects only serving clients of a specific age range only enroll clients of <br />Yes/No "nr*"r. Jo"i not .onif iii with the specific sources of non-cash <br />that age range. <br />Page 043 <br />26