WSI-72761 | HCSI-5269 | Resolved an issue where the POST /v3/patients/contacts/search endpoint returned empty results or a generic error for patients with multiple phone numbers, email addresses, or mailing addresses. The endpoint now reliably returns all matching patient contact records regardless of how many contact details are associated with the patient. | Patients | V3 | Staging:
4/27/2026 Production:
5/11/2026 |
N/A | HCSI-5271 | Resolved an issue where the POST /v3/billingauthorizations/search endpoint excluded future-dated billing authorizations from results, causing valid scheduled coverage to appear missing. The endpoint now returns all authorizations matching the request criteria, including past, current, and future-dated records. | Billing
Auths | V3 | Staging:
4/27/2026* Production:
5/11/2026 |
WSI-73540 | HCSI-5322 | Resolved an issue where providing statOrderChangeReason without isStatOrder in a POST /v3/patientorders/drug/po request caused the progress note to be silently skipped while the order itself was saved successfully. The API now validates both fields together and ensures the progress note is created when expected. | Patient
Order | V3 | Staging:
4/27/2026 Production:
5/11/2026 |
WSI-74104 | HCSI-5361 | Resolved an issue where the POST /v3/patients/contacts/search endpoint returned an unexpected error when searching for certain patients by medical record number, even when additional filter parameters were included. The endpoint now reliably returns patient contact records for all patients. | Patients | V3 | Staging:
4/27/2026 Production:
5/11/2026 |
WSI-71886 | HCSI-5398 | Resolved an issue where the LocationId returned by POST /v3/inventory/locationsquantities/search was an internal identifier that could not be used directly as input to other API endpoints, requiring additional lookup calls to resolve a usable identifier. The LocationId value returned now matches the identifier accepted by downstream endpoints. | Inventory | V3 | Staging:
4/27/2026 Production:
5/11/2026 |
N/A | HCSI-5333 | Updated the POST /v3/prescriptions endpoint to return a clear 400 validation error when creating a prescription for a patient with no gender on record, replacing the previous generic 500 error. The error message now identifies the missing gender requirement so the patient record can be corrected before resubmitting. | Prescriptions | V3 | Staging:
4/27/2026 Production:
5/11/2026 |
