Open Tickets With Wellsky
Issue |
Details(If App.) |
Dates Ticket Was Started |
Who This Impacts |
Status |
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 |
CoC APR; PATH Outreach clients w/out date of engagement are appearing in Q6 |
One of our providers has noticed their PATH Outreach clients are appearing in Q6 on the CoC APR even when there is no Date of Engagement. 5/13/25: Yes, the question is why they are appearing in Q6 when they do not have a date of engagement. 5/13/25: I reviewed the CoC APR specifications and the Reporting Glossary and did not see where either document states that the client must have a DOE to be included. Based on the documentation it seems as though the only requirement for a client to be included in Q6 is that they are active. 5/19/25: Thanks for checking before closing this case! My understanding is that Street Outreach / PATH Services projects should not have clients included in Q6 unless they have a Date of Engagement. 5/19/25: We are going to further discuss this case with the team and I will keep you posted as I have updates to provide. |
05/13/2025 |
HMIS Users/Sys Admins |
Accepted for Development |
FE: Save & Verify on Calls |
We have seen some issues where data is imported into a Calls record, but because that data has a timestamp prior to the ROI created at the time of this new call, it is not visible to other providers. Is there a way to add the "Save & Verify" feature to the calls module to fix this? 6/17/25: I can bring your question to our meeting with Development, but even if they entertain it, it won't be a quick feature addition due to the amount of items already in our development queue. But, I can let you know. |
06/17/2025 |
HMIS Users/Sys Admins |
Accepted for Development |
Last Updated: Friday, October 31st, 2025
