Laserfiche WebLink
Exam les of data accura <br />Date of Eirth and <br />Prolect Start Date' Prior Living <br />Situation data <br />, elements <br />Disabling Condition <br />, Health lnsurance <br />Monthly lncome <br />Non-Cash Benefits <br />Relationship to <br />Head of Household <br />Veteran Status <br />Project Population <br />Specifics <br />Ensure the two are not the same dates <br />' Ensure responses for Prior living situation, Length of stay in prior living situation, <br />Approximate date homelessness started, Number of times the client has experienced <br />homelessness in the last 3 years, and Number of months experiencing homelessness in <br />, the last 3 years do not conflict with each other. <br />Ensure the Yes/No answer does not conflict with the specific types of disabling <br />conditions. <br />Ensure the Yes/No answer do_es not conflict with the specific types of health insurance. <br />Ensure the YeslNo answer does not conflict with the specific sources of monthly <br />'i;1t",ff;r. Yes/No answer does not conflict with the specific sources of non-cash <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 />not identified as veterans.Ensure individuals under 18 years of age are <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 />that age range. <br />7.2.L.4 Consistency <br />Consistent data helps ensure that any reporting generated by a project is understood. Data consistency <br />is important for effectively communicating the processes and outcomes of a project. <br />All data will be collected, entered, and stored in accordance with the Asencv Partn r Asreement <br />All data elements and responses will be entered perthe HUD Data Standards Manual. To avoid <br />inconsistency, agencies should use language on intake forms that closely matches the elements and <br />responses in HMIS. <br />Clients who refuse consent must be made anonymous per Department of Commerce Guidance. <br />7.2.2 Consent for Entry of Personally ldentifying lnformation <br />7 .2.2.tldentified Records <br />./ Personally identifying information (Pll)11must not be entered into HMIS unless all adult <br />household members have provided informed consent. <br />./ lnformed consent must be documented with a signed copy of lhe Client Releose of lnformotion <br />ond tnformed Consent Form in the client file. lf electronic consent has been received, a copy <br />does not need to be printed forthe clientfile but must be available in HMIS. lf telephonic <br />consent has been received, complete the consent form the first time the household is seen in <br />person. See HMIS Asencv Pa ner Asreement <br />11 Pll includes name, social security number, birthdate, address, phone number, email, and photo. <br />Page | 35 <br />Elernents of Data