CareTend API Release Notes - 4/20/2026 - 5/1/2026
Issue Number | Jira Number | Release Note | Collection | API Version | Availability |
|---|---|---|---|---|---|
N/A | HCSI-3170 | Added a new V4 POST | Patients | V4 | Staging: Production: |
N/A | HCSI-3171 | Added a new V4 PATCH | Patients | V4 | Staging: Production: |
N/A | HCSI-4000 | Added a new V4 POST | Billing | V4 | Staging: Production: |
N/A | HCSI-5475 | Resolved multiple issues with the POST /commands/v4/userdefinedfields/template endpoint that caused user-defined fields created via the API to be invisible in the CareTend Desktop User Defined tab. Added a validation requiring groupName to be provided when defining fields within a group, preventing fields from being silently assigned to an unassigned container that the Desktop filters out. Also corrected the CreatedBy field to use a valid system user ID and added automatic SortOrder calculation to prevent overlapping sort values when not explicitly provided. | UDF | V4 | Staging: Production: |
N/A | HCSI-5479 | Resolved an issue where the POST /commands/v4/inventory/items/quantity/update-on-hand endpoint accepted and persisted LOT information (lotNumber, lotExpirationDate) for inventory items that do not track lots (LogLots = false), inconsistent with the ADD and DEDUCT endpoints which correctly reject LOT data for non-lot-tracked items. The update-on-hand endpoint now validates and rejects LOT information for non-lot-tracked inventory items, ensuring consistent LOT data integrity across all inventory quantity operations. | Inventory | V4 | Staging: Production: |
N/A | HCSI-5485 | Resolved an issue where the Provider Contact Address sub-resource endpoint expected providerContactId to be PartyContact.Id (the relationship record's primary key), while the Create Provider Contact response only returns PersonId. This mismatch made the address endpoint impossible to use with the ID returned by the create response. The address endpoint now accepts PersonId as the contact identifier, consistent with the Phone Number and Email Address sub-resource endpoints, so all provider contact sub-resources work with the same ID returned by the Create Provider Contact response. | Providers | V4 | Staging: Production: |
N/A | HCSI-5486 | Added new endpoints that allow creating and initializing user-defined fields for a patient or prescriber in a single API call, replacing the need for multiple sequential calls. Each endpoint accepts group names, field names, field types, and initial field values, and creates and initializes UDF records in CareTend in a single operation. On success, the API returns the created UDF field information, allowing external systems to efficiently set up and populate user-defined data without a multi-step workflow. | UDF | V4 | Staging: Production: |
N/A | HCSI-5489 | Updated the V4 inventory search and retrieval endpoints to include a TrackLotNumbers (boolean) field in response payloads. The field is now returned in InventoryItemResponseV4 from POST /v4/inventory/items/search and in InventorySummaryResponseV3 from POST /v4/inventory/search, mapping to the LogLots database column. External systems can now determine lot tracking eligibility for inventory items without additional queries. | Inventory | V4 | Staging: Production: |
N/A | HCSI-5512 | Resolved a production error where the PATCH | UDF | V4 | Staging: Production: |
N/A | HCSI-5513 | Added a new endpoint that allows to programmatically remove user-defined field definitions from UDF templates. The endpoint performs a soft-delete by setting RecStatus = 0 on the associated Field, ContainerField, and FieldValue records, maintaining referential integrity with existing field value data. The endpoint validates that the specified field exists and belongs to a user-defined fields container group before processing the deletion. | UDF | V4 | Staging: Production: |
N/A | HCSI-5514 | Added a new PATCH | UDF | V4 | Staging: Production: |
N/A | HCSI-5515 | Resolved a production error where the PATCH /v4/userdefinedfields/patients endpoint threw System.InvalidOperationException: Nullable object must have a value during query materialization when a ContainerGroupAssociationFieldValue record referenced a Field_Id with no corresponding ContainerField join record in the database. The repository now handles orphaned field value records gracefully, ensuring patient UDF updates complete reliably without nullable exceptions. | UDF | V4 | Staging: Production: |