-
Notifications
You must be signed in to change notification settings - Fork 208
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
VAOS vets-api Log clinic stop codes returned for Direct scheduling. #71272
Comments
I have attached the raw data from the clinic's stop code logging. clinic_stop_codes.xlsx |
None of the Primary Secondary pairs showed up in the collected logs. Below is the Secondary Stop code's that showed up in the logs.
@ldelacosta The data collected should be reviewed, and logging should be removed if it is no longer necessary. |
^^ I referenced the wrong GH ticket in the "VAOS Remove Missing ICN Logging" PR. The Stop code logging is still in place. |
@ajmagdub - could we get the latest logging for this work. Please let us know when it's ready for review. |
@ldelacosta here's the latest logging |
^^ miss-reference this ticket in the above PR. Stop code logging still in place. |
Merged changes to stop logging, will go into production on 02/28 Vets API deployment. |
Changes to remove stop code logging are in production with no issues. |
No issues to report. Closing out the ticket. cc: @JRRoof |
Description
When the vets-api endpoint
vaos/v2/locations/{id}/clinics?clinical_service={typeOfCare}
is called, we want to log the clinic primary and secondary stop codes pairs returned.The text was updated successfully, but these errors were encountered: