Open Tickets With WellSky

Open Tickets With Wellsky

Issue	Details	Date Ticket Opened	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.	03/16/2022	HMIS Users/ Sys. Admins	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.	05/13/2025	HMIS Users/ Sys. Admins	Resolved
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
DQF	I have a concern and I"m hoping you can help. We have been conducting data quality assessments and cleanup efforts in preparation for this year's reporting season. In doing so, I've found that the Data Quality Framework report is yielding higher error rates at the sys-admin level (the level we have to run it for inclusion in the SPMs) than when viewing the same data at the project level. For example, when running the DQF report, VA-XXX was showing me error rates for Income at Start, Annual, and Exit for the CoC's Emergency Shelter projects (date range 08/01/2022-07/31/2023). When viewing the project these errors were traced back to (Provider ID 1748), the errors do not appear at the provider level when running a CoC APR, for example. They only exist if I run that data at the sys-admin level. I'm worried about how this impacts CoC Data Quality reporting, as there is nothing the provider can do to "fix" these errors, since they aren't really errors at their level. Please advise.	09/09/2023	HMIS Users/ Sys. Admins	Accepted for Development

Last Updated: Monday, November 17th, 2025