CareTend Release Notes - 10/19/2026-10/30/2026
about 8 hours ago by Josh Grimes
Release Availability: Staging/Production 11/18/2026
| Issue # | Jira # | Description | Area | Version |
|---|---|---|---|---|
| HCSI-5800 | A new V4 API is now available to retrieve eRx transaction data directly from the eRx Hub. It includes a token endpoint (POST api/v4/erx/token) for authentication and a transaction search endpoint (POST api/v4/erx/transactions/search) that returns stored eRx transaction data in JSON. *Relient on other development. | eRx | V4 | |
| HCSI-6210 | Searching patient order items was taking about 3.7 seconds on every call, however small the request. The search now does work proportional to the page returned, not the full fill history. In load testing on a large dataset, a typical request dropped from about 11.7 seconds to about 11 milliseconds. Responses are identical to before, and no API contract changes. | Patient Orders | V4 | |
| HCSI-6211 | Persons search had a 95th-percentile response time of about 5.4 seconds. We removed a count query whose result was never used, and the search no longer re-runs the full filter for each related-data load. This means fewer database round trips and faster responses. Responses and TotalCount behavior are unchanged. | Persons | V4 | |
| HCSI-6215 | One sync client was making about 570 database calls per request. That drove about 88% of the slow calls and the recurring IntegrationApi slow-transaction alert. Database calls now scale with the page size, not with the number of patients or child records returned. Responses are unchanged. | Patients | V4 | |
| HCSI-6241 | Every database save in the V4 Integration API ran an extra lookup query even when it had nothing to look up. That lookup is now skipped when there is nothing to check, which saves one database round trip per save across the API. There is no change to HIPAA log output or API responses. | API Performance | V4 |