Laserfiche WebLink
<br />Page | 35 <br /> <br /> Examples of data accuracy: <br />Elements of Data Accuracy <br />Date of Birth and <br />Project Start Date <br />Ensure the two are not the same dates. <br />Prior Living <br />Situation data <br />elements <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 />Disabling Condition Ensure the Yes/No answer does not conflict with the specific types of disabling <br />conditions. <br />Health Insurance Ensure the Yes/No answer does not conflict with the specific types of health insurance. <br />Monthly Income Ensure the Yes/No answer does not conflict with the specific sources of monthly <br />income. <br />Non-Cash Benefits Ensure the Yes/No answer does not conflict with the specific sources of non-cash <br />benefits. <br />Relationship to <br />Head of Household <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 />Veteran Status Ensure individuals under 18 years of age are not identified as veterans. <br />Project Population <br />Specifics <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 /> 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 /> <br /> All data will be collected, entered, and stored in accordance with the Agency Partner Agreement. <br /> <br />All data elements and responses will be entered per the 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 /> <br />Clients who refuse consent must be made anonymous per Department of Commerce Guidance. <br /> Consent for Entry of Personally Identifying Information <br /> Identified Records <br /> Personally identifying information (PII)11 must not be entered into HMIS unless all adult <br />household members have provided informed consent. <br /> Informed consent must be documented with a signed copy of the Client Release of Information <br />and Informed Consent Form in the client file. If electronic consent has been received, a copy <br />does not need to be printed for the client file but must be available in HMIS. If telephonic <br />consent has been received, complete the consent form the first time the household is seen in <br />person. See HMIS Agency Partner Agreement. <br /> <br />11 PII includes name, social security number, birthdate, address, phone number, email, and photo.