Open Tickets With WellSky

Open Tickets With Wellsky

Issue	Details(If App.)	Dates Ticket Was Started	Who This Impacts	Status
Mapping question	One of our providers recently noticed some clients who had been housed and subsequently exited prior to the Data Standards Update last year (10/1/23) and their exit destination was initally selected as "Permanent Housing (other than RRH) for formerly homeless persons" which as you know is no longer a response option for that data element. Apparently when the updates occured, those clients were now reflecting a response of "other" instead of the rental w/subsidy and corresponding rental subsidy type. The User has since updated the households reflecting this issue but I wanted to make you aware in the event that there is additional data impacted by this.	07/22/2024	HMIS USERS/ADMINS	Ongoing
CoC APR Q6e Data Timeliness	LATEST UPDATE REGARDING ACCURACY FROM WELLSKY: "CURRENTLY THE CODE FOR TABLE 6E IS BASED ON THE ENTRY/EXIT DATE UPDATED. IF THE ENTRY/EXIT IS UPDATED IT DOES AFFECT THE TIMELINESS REPORT. WE DO HAVE A DEVELOPMENT TICKET IN THE BACKLOG TO PULL FROM ENTRY DATE CREATED AND EXIT DATE CREATED INSTEAD. DEVELOPMENT HAS NOT BEEN ABLE TO PROVIDE ME WITH AN ESTIMATED TIMELINE FOR RESOLUTION. ONCE I DO RECEIVE AN UPDATE I WILL BE SURE TO NOTIFY YOU HERE." UPDATE(4/21/22) FROM WELLSKY: "DEVELOPMENT HAS NOT BEEN ABLE TO PROVIDE ME WITH AN ESTIMATED TIMELINE FOR RESOLUTION. ONCE I DO RECEIVE AN UPDATE I WILL BE SURE TO NOTIFY YOU HERE."	Re-opened Ticket on: 3/16/22	HMIS Users	Accepted for Development
Twins in HMIS	It appears that an error for Project Star Date (3.10) was traced back to a client who is a twin, so the system is flagging an error assuming it is a duplicate client (the twins have similar names and the same DOB, obviously). The guidance we received in that Case was to change one client's DOB by one day when needing to run the report, and then change it back so that it is accurate in the system outside of the time when a report needs to be run. It is never our preferred method to have providers inaccurately adjust data to get a report to work properly. We strive to have a product that works as intended, without manual manipulation (especially inaccurate manipulation) to yield accurate results. In pursuing guidance via a HUD AAQ on this matter, the response we got was: "This sounds like an error/issue on the part of your HMIS vendor and its mechanisms for identifying duplicate client records. Please note that the CoC Program interim rule gives CoCs authority over and responsibility for HMIS. HUD provides technical assistance to software vendors working on HMIS, but HUD does not regulate or certify vendors. You as the HMIS Lead should be able to negotiate with your vendor and determine a solution within the parameters of the contract between both parties. Additionally, your vendor is able to submit AAQs here as well as seek additional technical assistance support through the HUD NHDAP Data Lab." Is this issue something WellSky has logged for development work and/or could it be?	08/13/20204	HMIS Users	Accepted for Development

Last Updated: Wednesday, August 28th, 2024