Laserfiche WebLink
Exam les of data accuracy <br />Date of Birth and <br />Project Start Date <br />Prior Living <br />Situation data <br />elements <br />Disabling Condition <br />, Health lnsurance <br />Monthly lncome <br />I Non-Cash Benefits <br />Relationship to <br />Head of Household <br />, Veteran Status <br />Proiect 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 />Rpproximate date homelessness started, Number of times the client has experienced <br />i 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 />i Ensure the yes/No answer does not conflict with the specific types of health insurance <br />Ensure the yes/lrto answer does not conflict with the specific sources of monthly <br />income. <br />Ensure the 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 />, Ensure individuals under 18 years of age are not identified 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 />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 />Alldata will be collected, entered, and stored in accordance with the Agencv PartnerAgreement. <br />All data elements and responseswill 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 <br />7.2.2 Consent for Entry of Personally ldentifying Information <br />7 .2.2.Lldentified Records <br />rt merce G <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 the Client Releose of lnformotion <br />ond lnformed Consent Form in the ctient file. lf electronic consent has been received, a copy <br />does not need to be printed for the client file 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 />pe rson. See HMIS reem <br />11 pll includes name, social security number, birthdate, address, phone number, email, and photo. <br />Page | 35 <br />Elements of Data AccuracY