130 likes | 136 Views
KYHMIS BOS Quarterly Meeting. November 15, 2017 2:30 p.m. Housekeeping. Purpose: To keep all KYHMIS BOS users informed with the same timely information Quarterly Webinars with mandatory attendance Recording sent out afterwards and must be watched within 1 week of webinar if missed
E N D
KYHMIS BOS Quarterly Meeting November 15, 2017 2:30 p.m.
Housekeeping • Purpose: • To keep all KYHMIS BOS users informed with the same timely information • Quarterly Webinars with mandatory attendance • Recording sent out afterwards and must be watched within 1 week of webinar if missed • License will remain inactive until requirement is met • Suggestion for topics can be made through the HelpDesk
Help Desk Etiquette • Must fill out all fields or it will not submit the ticket • Agency name must be populated • If requesting assistance with errors on a report, or a report question, please attach the report in question to the HelpDesk ticket • HelpDesk guarantees quickest response rate
Agency Admin Role • Agency Admin is the liaison between HMIS Lead Agency (BOS-KHC) and other HMIS users within the agency • Assist In: • Report Development • System Testing • Updating, correcting, and maintaining the participating agency information in the KYHMIS • Requesting all agency have Agency Admin assigned by 1/1/18
Previous Data Quality Approach • CoC projects will be contacted prior to their APR being due to help with any errors • Worked with ESG Projects for CAPER submission • Quarterly review of all KYHMIS agencies • Data Quality Plan located on the Helpdesk under KYHMIS Administrative Documentation
New Data Quality Submissions • Data Quality calendar will be provided by January 1st 2018 to show which projects have a report submission due in each month • Submissions of report will be required to be submitted to assigned System Admin by 15th of report submission month • Feedback will be sent by end of month
New Data Quality Submissions • Scorecard will be provided to show acceptable missing/don’t know limits • If data quality threshold not met, action plan and/or explanation will be required with submission • Data Quality Framework Report will be used for report submission
ROI Workflow • ROI must be entered before Entry into a program • If you happen to not enter ROI prior to Entry the client record will need to be unlocked by System Admin • If you are using back date mode – TIME MATTERS
Running Reports in EDA vs. Regular • There shouldn’t be a reason why there is a difference, therefore, if the workflow is followed appropriately (using EDA) when you run the report in EDA or out of EDA – you should get the same results