Changelog

N/A

HCSI-3713

Enhanced the GET v4/patients/{mrn}/policies/{policyId} endpoint to retrieve comprehensive patient insurance policy information for complete coverage and billing details for claims processing.

Employees

V4

Staging: 4/8/2026

Production: 4/8/2026

N/A

HCSI-3714

Enhanced the POST /v4/patients/{mrn}/policies endpoint to support creation of patient insurance policy records for comprehensive coverage and billing validation.

Patients

V4

Staging:
4/8/2026

Production:
4/8/2026

N/A

HCSI-3715

Enhanced the DELETE /v4/patients/{mrn}/policies/{policyId} endpoint to support removal of patient insurance policy records for dependency validation and for data integrity.

Patients

V4

Staging:
4/8/2026

Production:
4/8/2026

N/A

HCSI-3716

Enhanced the PUT /v4/patients/{mrn}/policies/{policyId} endpoint to support comprehensive patient insurance policy updates for maintaining accurate coverage information for billing operations.

Patients

V4

Staging:
4/8/2026

Production:
4/8/2026

N/A

HCSI-4293

Added a POST /v4/patients/{mrn}/progressnotes
endpoint to create patient progress note records. This endpoint documents patient care encounters with clinical assessments and treatment outcomes for regulatory compliance.

Patients

V4

Staging:
4/8/2026

Production:
4/8/2026

N/A

HCSI-4294

Added a PATCH /v4/patients/{mrn}/progressnotes/{noteId} endpoint to update patient progress note records. This endpoint modifies clinical documentation while maintaining note history and audit trail for care record accuracy.

Patients

V4

Staging:
4/8/2026

Production:
4/8/2026

N/A

HCSI-4295

Added a POST /v4/patients/progressnotes/search endpoint to search for patient progress notes using flexible filter criteria. This endpoint returns clinical documentation for care review and quality audit workflows.

Patients

V4

Staging:
4/8/2026

Production:
4/8/2026

N/A

HCSI-4307

Added a GET /v4/patients/{mrn}/diagnoses endpoint to retrieve patient diagnosis records with optional ICD-9 or ICD-10 code filtering. This endpoint returns diagnosis information with clinical coding detail for documentation and billing workflows.

Patients

V4

Staging:
4/8/2026

Production:
4/8/2026

N/A

HCSI-4319

Added a POST /v4/patients/{mrn}/providers endpoint to create patient-provider relationships in CareTend. This endpoint establishes care team associations with provider role and relationship type for coordinated care delivery.

Patients

V4

Staging:
4/8/2026

Production:
4/8/2026

N/A

HCSI-4344

Added a POST /v4/patients/{mrn}/notes endpoint to create patient note records in CareTend. This endpoint accepts note type, content, and clinical context, creating timestamped notes with audit trail for comprehensive patient documentation.

Patients

V4

Staging:
4/8/2026

Production:
4/8/2026

N/A

HCSI-4345

Added a GET v4/patients/{mrn}/notes/{noteId}
endpoint to retrieve specific patient note
records by medical record number and note identifier. This endpoint returns complete note content with author information and clinical context for care documentation review.

Patients

V4

Staging:
4/8/2026

Production:
4/8/2026

N/A

HCSI-4346

Added a GET
/v4/patients/notes/templates
endpoint to retrieve patient note templates filtered by note type in CareTend. This endpoint returns template definitions that external systems can use to present standardized note entry forms for consistent clinical documentation.

Patients

V4

Staging:
4/8/2026

Production:
4/8/2026

N/A

HCSI-5418

Added a GET endpoint to retrieve quantity information for a specific lot number at a specific location for a given inventory item in CareTend. This endpoint validates the inventory item exists and has lot tracking enabled, then returns lot-specific quantity data including available quantity, requested quantity, lot expiration date, and current stock levels. On success, the API returns detailed lot quantity information that external systems can use for inventory allocation decisions, FIFO dispensing workflows, and expiration management operations, enabling precise inventory tracking at the lot level for pharmaceutical operations and regulatory compliance.

Inventory

V4

Staging:
4/8/2026

Production:
4/8/2026

N/A

HCSI-5328

Added a GET /v4/patients/userdefinedfields/definitions endpoint to retrieve user-defined field metadata and container definitions configured for patient records in CareTend. This endpoint returns the complete schema of custom patient attributes including container names, field labels, data types, validation rules, and allowable values configured by healthcare administrators. On success, the API returns user-defined field definitions that external systems can use to build dynamic forms, validate custom patient data before submission, and maintain synchronized custom attribute schemas for program enrollment, social determinants of health tracking, and facility-specific patient attributes without manual CareTend Desktop reference.

Patients

V4

Staging:
4/8/2026

Production:
4/8/2026

N/A

HCSI-5393

Added a GET /v4/inventory/items/{id}/audittrail endpoint that retrieves the complete audit history for a specific inventory item, including all quantity changes, lot additions, transfers, adjustments, and dispensing transactions. This endpoint accepts an inventory item ID and optional date range parameters, returning a chronological collection of audit records with transaction types, quantities, user information, timestamps, and change reasons. On success, the API returns the full audit trail with sufficient detail for regulatory compliance reviews, inventory discrepancy investigations, and financial reconciliation workflows, allowing external systems to track complete inventory lifecycle history for pharmaceutical accountability and healthcare compliance reporting requirements.

Inventory

V4

Staging:
4/8/2026

Production:
4/8/2026

N/A

HCSI-5394

Enhanced the POST /v4/inventory/lots/search endpoint to support filtering lot records by supplier identifier and expiration date range, allowing external systems to identify inventory lots from specific suppliers that will expire within a specified timeframe for proactive inventory management. This enhancement adds supplier-based filtering criteria to the existing lot search capabilities and validates expiration date range parameters to return lots approaching their expiration dates. On success, the API returns a collection of lot records with expiration dates, quantities, and supplier information, enabling external systems to generate expiration alerts, prioritize FIFO dispensing workflows, and minimize medication waste for pharmacy operations and regulatory compliance.

Inventory

V4

Staging:
4/8/2026

Production:
4/8/2026

WSI-75154

HCSI-5399

Resolved a data interoperability issue where the POST /v4/inventory/suppliers/search
endpoint returned supplier information for inventory items but did not include the inventoryItemSupplierId field required by the PATCH and DELETE supplier endpoints, breaking the request/response data chain and making it impossible for external systems to update or remove suppliers that were created outside the API. This occurred because the response model only returned the SupplierId (the supplier entity's ID) and supplier details, but not the InventoryItemSupplier join table's primary key that serves as the route parameter for modification endpoints. Added the inventoryItemSupplierId field to the search response DTO and repository query, enabling external systems to retrieve the identifier and use it for subsequent PATCH and DELETE operations.

Inventory

V4

Staging:
4/8/2026

Production:
4/8/2026

N/A

HCSI-5420

Resolved an issue where the POST /v4/inventory/items/quantity/add endpoint created duplicate aggregate quantity rows when adding inventory to an existing lot at a location, causing GET requests for lot quantities to return incomplete results by selecting only the first duplicate row via FirstOrDefaultAsync, making added quantities appear lost. This occurred because the repository always inserted new InventoryItemLocationQuantity records without checking for existing rows with the same location and lot combination, while the LotInformation table correctly used find-or-create logic. Updated the repository to check for existing aggregate quantity records before inserting, incrementing Quantity and AvailableQuantity fields when found, or creating new records when not found. On success, the API now maintains a single aggregate quantity record per location-lot combination and returns accurate total quantities via GET endpoints, allowing external systems to track inventory levels correctly for procurement and dispensing workflows.

Inventory

V4

Staging:
4/8/2026

Production:
4/8/2026

N/A

HCSI-5421

Resolved an issue where the POST /v4/inventory/items/quantity/update-on-hand endpoint incorrectly set InventoryQuantityAvailability to 'Pending' (ID=1) instead of 'Available' (ID=2) when creating inventory received records, causing the V3 location quantities search endpoint to permanently display incorrect availability status for inventory added via the V4 API. This occurred because the repository hardcoded the wrong lookup ID with a misleading comment, and because the availability field is immutable once set, the records remained stuck in Pending status with no transition mechanism. Changed the repository to use the correct 'Available' lookup ID, matching the behavior of all other inventory entry points in the CareTend Desktop UI and API. On success, inventory added via the Update On Hand endpoint now appears with the correct 'Available' status in search results, enabling external systems to accurately track usable inventory quantities for clinical operations and supply chain management.

Inventory

V4

Staging:
4/8/2026

Production:
4/8/2026

N/A

HCSI-5422

Resolved an issue where the POST /v4/inventory/items/quantity/add endpoint matched inventory location quantity records on location and lot only, without including UnitsPerVial in the match key, causing the system to update the same aggregate record when adding inventory with different vial sizes to the same lot. This created a data mismatch where subsequent deduct-by-vials operations failed with the error "Cannot deduct by vials because UnitsPerVial is not set for this inventory item location and lot combination" even after vials were added to the lot. Updated the repository logic to include UnitsPerVial in the inventory location quantity lookup, matching the CareTend Desktop stored procedure behavior that creates separate aggregate records for each vial size. The deduct-by-vials flow now filters for records with UnitsPerVial greater than zero, ensuring the API can successfully deduct vials after adding inventory, allowing external systems to manage pharmaceutical inventory with mixed vial sizes per lot for accurate dispensing workflows.

Inventory

V4

Staging:
4/8/2026

Production:
4/8/2026

N/A

HCSI-5423

Resolved an issue where the POST /v4/inventory/items/quantity/deduct endpoint arbitrarily selected the first available UnitsPerVial value when multiple vial sizes existed for the same lot number at a location, resulting in incorrect deduction amounts. This occurred because the API did not accept a UnitsPerVial parameter, forcing the system to use FirstOrDefaultAsync() logic that picked whichever inventory record the database returned first rather than the specific vial size the caller intended to deduct. Added an optional UnitsPerVial field to the deduct request model, allowing external systems to specify which vial size to deduct from when multiple sizes exist, and providing clear error messages when the field is required but not provided. On success, the API now deducts the correct quantity from the specified vial size and returns accurate remaining inventory totals, ensuring external systems maintain proper inventory tracking for pharmaceutical dispensing operations.

V4

Staging:
4/8/2026

Production:
4/8/2026

N/A

HCSI-4142

Added a POST /v4/patients/{mrn}/userdefinedfields endpoint to create user-defined field values for patient records in CareTend. This endpoint validates the patient exists, accepts container-based user-defined field data, and creates custom patient attributes configured by healthcare administrators. On success, the API returns the newly created user-defined field container with values, allowing external systems to capture custom patient data such as program enrollment, social determinants, or facility-specific attributes without manual CareTend Desktop entry.

Employees

V4

Staging: 3/25/2026

Production: 3/25/2026

N/A

HCSI-4317

Added a POST /v4/patients/{mrn}/ancillaryproviders endpoint to create new patient-to-ancillary provider relationships in CareTend. This endpoint validates the provider exists, verifies the relationship type, and ensures the patient record is valid before creating the association. On success, the API returns the newly created relationship record with a unique identifier, enabling external systems to manage care team coordination.

Patients

V4

Staging:
3/25/2026

Production:
3/25/2026

N/A

HCSI-4318

Added a DELETE /v4/patients/{mrn}/ancillaryproviders/ endpoint to remove patient-to-ancillary provider relationships from CareTend. This endpoint validates the relationship exists and checks for dependencies before allowing deletion. On success, the API returns a 204 No Content response confirming the relationship has been removed, allowing external systems to maintain accurate care team associations.

Patients

V4

Staging:
3/25/2026

Production:
3/25/2026

N/A

HCSI-4320

Added a DELETE /v4/patients/{mrn}/providers/ endpoint to remove patient-to-provider relationships by provider ID from CareTend. This endpoint validates the relationship exists and checks for dependencies before allowing deletion. On success, the API returns a 204 No Content response confirming the relationship has been removed, allowing external systems to maintain accurate provider assignments.

Patients

V4

Staging:
3/25/2026

Production:
3/25/2026

N/A

HCSI-4321

Added a GET /v4/patients/{mrn}/ancillaryproviders endpoint to retrieve all ancillary provider relationships for a patient identified by medical record number. This endpoint accepts search parameters and returns a collection of ancillary provider associations including provider details, relationship type, and effective dates. On success, the API returns ancillary provider records, allowing external systems to maintain coordinated care team information.

Patients

V4

Staging:
3/25/2026

Production:
3/25/2026

N/A

HCSI-4327

Added a
PATCH /v4/patients/{mrn}/policies/
endpoint to update existing patient insurance policies in CareTend. This endpoint validates policy information including payer plan, policy number, coverage dates, and authorization details, applying updates to the existing policy record while maintaining referential integrity. On success, the API returns the updated policy record, enabling external systems to keep insurance information synchronized for accurate billing operations.

Patients

V4

Staging:
3/25/2026

Production:
3/25/2026

N/A

HCSI-4328

Added a GET /v4/patients/{mrn}/policies endpoint to retrieve all insurance policies for a patient identified by medical record number. This endpoint accepts search parameters including policy status, payer type, and coverage dates, returning matching insurance policy records from CareTend. On success, the API returns a collection of policy records with payer information, coverage details, and authorization data, supporting billing and insurance verification workflows.

Patients

V4

Staging:
3/25/2026

Production:
3/25/2026

N/A

HCSI-5246

Added a
GET /v4/patients/{mrn}/assessments
endpoint to retrieve patient assessment records based on assessment type and date range criteria. This endpoint accepts patient medical record number, assessment type filters, and date range parameters to return matching clinical assessment records from CareTend. On success, the API returns a collection of patient assessment documents with assessment dates, types, scores, and clinical findings, supporting clinical decision support, quality reporting, and care coordination workflows for patient care management.

Patients

V4

Staging:
3/25/2026

Production:
3/25/2026

N/A

HCSI-5312

Added a POST /v4/providers/{providerId}/userdefinedfields endpoint to initialize empty user-defined field containers for provider records in CareTend. This endpoint accepts a provider ID and creates the base container structure for custom provider attributes without requiring initial values. On success, the API returns the newly created container with empty field values and unique identifiers, allowing external systems to prepare provider records for subsequent user-defined field updates through other API operations.

Providers

V4

Staging:
3/25/2026

Production:
3/25/2026

N/A

HCSI-5313

Added a GET /v4/providers/{providerId}/userdefinedfields endpoint to retrieve user-defined field values for provider records in CareTend. This endpoint accepts a provider ID and returns all configured user-defined field containers including container IDs, names, and field values. On success, the API returns the complete set of custom provider attributes, allowing external systems to display, validate, or synchronize user-defined provider data for credentialing, provider directory management, and regulatory compliance workflows. | Providers

Providers

V4

Staging:
3/25/2026

Production:
3/25/2026

N/A

HCSI-5314

Added a PATCH /v4/providers/{providerId}/userdefinedfields endpoint to update user-defined field values for provider records in CareTend. This endpoint validates the provider exists, accepts container-based user-defined field data, and applies updates to custom provider attributes configured by healthcare administrators. On success, the API returns the updated user-defined field container with current values, allowing external systems to synchronize custom provider data such as credentials, specialties, or organizational attributes without manual CareTend Desktop entry.

Providers

V4

Staging:
3/25/2026

Production:
3/25/2026

N/A

HCSI-5315

Enhanced the
PATCH /v4/clinicianvisits/{id}
endpoint to enforce comprehensive validation rules matching CareTend Desktop UI business logic. This enhancement adds field-level validation for clinician visit updates including visit date, visit type, clinician assignment, service codes, and documentation requirements. On success, the endpoint rejects invalid updates with clear validation messages matching UI error handling, preventing external systems from creating dirty data or bypassing business rules when updating clinician visit records for patient care documentation.

Clinician Visits

V4

Staging:
3/25/2026

Production:
3/25/2026

N/A

HCSI-5316

Enhanced the PATCH /v4/billingauthorizations/{id}
endpoint to support updating Auth Type and DC Authorization fields on billing authorizations. This enhancement adds these fields as updateable parameters in the V4 authorization update endpoint, with validation to ensure values match allowable authorization types and DC authorization status codes. On success, the API returns the updated authorization record with Auth Type and DC Authorization values, allowing external systems to manage complete authorization details for patient billing and insurance claims processing.

Billing
Auths

V4

Staging:
3/25/2026

Production:
3/25/2026

N/A

HCSI-5317

Enhanced the PATCH /v4/billingauthorizations/{id} endpoint to properly handle blank and null values for authorization fields based on CareTend business rules. This enhancement adds explicit validation to distinguish between intentionally cleared fields (blank/null) versus omitted fields (preserve existing), and returns clear validation messages when fields cannot be set to blank. On success, external systems can selectively clear authorization data or receive actionable error messages, allowing patient coordinators to update billing authorizations from external systems without creating data integrity issues. | Billingauthorizations

Billing Auths

V4

Staging:
3/25/2026

Production:
3/25/2026

N/A

HCSI-5342

Added a POST /v4/suppliers/{supplierId}/addresses endpoint to create new addresses for suppliers in CareTend. This endpoint validates the address components including street, city, state, postal code, and ensures the supplier exists before creating the new address record. On success, the API returns the newly created address record with a unique identifier, allowing external systems to manage supplier location information.

Suppliers

V4

Staging:
3/25/2026

Production:
3/25/2026

N/A

HCSI-5343

Added a PATCH /v4/suppliers/{supplierId}/addresses/ endpoint to update existing supplier addresses in CareTend. This endpoint validates address components and applies changes to the existing record while maintaining data integrity and standardization requirements. On success, the API returns the updated address record, enabling external systems to keep supplier location information current and accurate.

Suppliers

V4

Staging:
3/25/2026

Production:
3/25/2026

N/A

HCSI-5344

Added a DELETE /v4/suppliers/{supplierId}/addresses/ endpoint to remove addresses from supplier records in CareTend. This endpoint validates that the address exists and checks for dependencies before allowing deletion. On success, the API returns a 204 No Content response confirming the address has been removed, allowing external systems to maintain clean and accurate supplier location data.

Suppliers

V4

Staging:
3/25/2026

Production:
3/25/2026

N/A

HCSI-5345

Added a GET /v4/suppliers/{supplierId}/addresses endpoint to retrieve all addresses associated with a specific supplier in CareTend. This endpoint accepts a supplier ID and returns a collection of address records including address type, street, city, state, postal code, and country information. On success, the API returns the complete list of supplier addresses, allowing external systems to maintain synchronized location data for shipping and procurement workflows.

Suppliers

V4

Staging:
3/25/2026

Production:
3/25/2026

N/A

HCSI-5346

Added a POST /v4/suppliers/{supplierId}/phones endpoint to create new phone numbers for suppliers in CareTend. This endpoint validates the phone number format, phone type, and ensures the supplier exists before creating the new contact record. On success, the API returns the newly created phone record with a unique identifier, allowing external systems to track and manage supplier contact information.

Suppliers

V4

Staging:
3/25/2026

Production:
3/25/2026

N/A

HCSI-5347

Added a PATCH /v4/suppliers/{supplierId}/phones/ endpoint to update existing supplier phone numbers in CareTend. This endpoint validates the phone number format and type, applying changes to the existing contact record while maintaining referential integrity. On success, the API returns the updated phone record, enabling external systems to keep supplier contact information current and accurate.

Suppliers

V4

Staging:
3/25/2026

Production:
3/25/2026

N/A

HCSI-5348

Added a DELETE /v4/suppliers/{supplierId}/phones/ endpoint to remove phone numbers from supplier records in CareTend. This endpoint validates that the phone record exists and checks for dependencies before allowing deletion. On success, the API returns a 204 No Content response confirming the phone number has been removed, allowing external systems to maintain clean and accurate supplier contact data.

Suppliers

V4

Staging:
3/25/2026

Production:
3/25/2026

N/A

HCSI-5349

Added a GET /v4/suppliers/{supplierId}/phones endpoint to retrieve all phone numbers associated with a specific supplier in CareTend. This endpoint accepts a supplier ID and returns a collection of phone records including phone type, number, extension, and status information. On success, the API returns the complete list of supplier phone numbers, allowing external systems to maintain synchronized contact information for procurement operations.

Suppliers

V4

Staging:
3/25/2026

Production:
3/25/2026

N/A

HCSI-5350

Added a POST /v4/suppliers/{supplierId}/emails endpoint to create new email addresses for suppliers in CareTend. This endpoint validates the email address format, email type, and ensures the supplier exists before creating the new contact record. On success, the API returns the newly created email address record with a unique identifier, allowing external systems to track and manage supplier contact information.

Suppliers

V4

Staging:
3/25/2026

Production:
3/25/2026

N/A

HCSI-5351

Added a PATCH /v4/suppliers/{supplierId}/emails/
endpoint to update existing supplier email addresses in CareTend. This endpoint validates the email address format and type, applying changes to the existing contact record while maintaining data integrity. On success, the API returns the updated email address record, enabling external systems to keep supplier contact information current and accurate.

Suppliers

V4

Staging:
3/25/2026

Production:
3/25/2026

N/A

HCSI-5352

Added a DELETE /v4/suppliers/{supplierId}/emails/
endpoint to remove email addresses
from supplier records in CareTend. This
endpoint validates that the email address exists and checks for dependencies before allowing deletion. On success, the API returns a 204 No Content response confirming the email address has been removed, allowing external systems to maintain clean and accurate supplier contact data.

Suppliers

V4

Staging:
3/25/2026

Production:
3/25/2026

N/A

HCSI-5353

Added a GET /v4/suppliers/{supplierId}/emails endpoint to retrieve all email addresses associated with a specific supplier in CareTend. This endpoint accepts a supplier ID and returns a collection of email address records including email type, address, and status information. On success, the API returns the complete list of supplier email addresses, allowing external systems to maintain synchronized contact information for procurement and supplier communication workflows.

Suppliers

V4

Staging:
3/25/2026

Production:
3/25/2026

N/A

HCSI-5373

Enhanced the GET /v4/inventoryunits
endpoint to retrieve unit of measure data including mg, ml, and other standard pharmaceutical units. This enhancement allows external systems to query and display available units of measure for medication ordering, inventory management, and clinical documentation workflows. On success, the API returns a collection of unit records with unit codes, descriptions, and active status, enabling integration partners to maintain synchronized unit of measure reference data for accurate medication dosing and inventory tracking.

Inventory
Units

V4

Staging:
3/25/2026

Production:
3/25/2026

N/A

HCSI-5375

Enhanced the PUT /v4/prescriptions/transfer
endpoint to enable prescription
transfers between companies in
CareTend using external system data. This endpoint validates that the prescription
exists in the source company, verifies the
target company is valid, and executes the
transfer using the Prescription.Prescription
Transfer stored procedure. On success, the API returns confirmation of the prescription transfer with updated company ownership, allowing external systems to automate prescription transfers between branches, locations,
or acquired entities for continuity of
patient care.

Prescriptions

V4

Staging:
3/25/2026

Production:
3/25/2026

N/A

HCSI-5378

Resolved an issue where the PATCH /v4/patientorders/drug/injpo endpoint allowed updating all fields on Active or Discontinued patient orders regardless of prescription print status, bypassing the field-level editability restrictions enforced in CareTend Desktop UI. Added validation logic to prevent modification of restricted fields (Frequency, Route, Order Date, Stop Date, Dispense Item, Order Type) when orders are in Active or Discontinued status, ensuring API behavior aligns with UI business rules. On success, the endpoint now prevents unintended changes to locked prescription orders, maintaining data integrity for printed prescriptions and active medication orders.

Patient
Orders

V4

Staging:
3/25/2026

Production:
3/25/2026

N/A

HCSI-5379

Resolved an issue where the PATCH /v4/patients/medicationprofiles endpoint could not clear date fields (StartDate, StopDate, DiscontinuedDate) to null when explicitly requested, and incorrectly accepted blank empty strings for the required Name field. Updated the service layer to distinguish between omitted fields (preserve existing value) and explicitly cleared fields (set to null), and added validation to reject empty Name values consistent with UI requirements. On success, the endpoint now allows proper date field clearing and enforces mandatory Name validation, ensuring medication profile data integrity matches CareTend Desktop UI business rules.

Patients

V4

Staging:
3/25/2026

Production:
3/25/2026

WSI-74892

HCSI-5384

Resolved an issue where the PATCH /commands/v4/inventory
endpoint returned a confusing error message "UnitofMeasure found by Name CN must be active" even when CN was already marked as active in the system. This occurred due to a table join mismatch in the validation logic. The fix corrects the validation query to properly check the active status of units of measure, providing clear and accurate error messages when patching drug inventory items, enabling external systems to troubleshoot data issues more effectively.

Inventory

V4

Staging:
3/25/2026

Production:
3/25/2026

WSI-74895

HCSI-5385

Resolved an issue where the
GET /commands/v4/inventoryunits API returned an x12UnitCodeId field as a numeric value without clear documentation of its meaning. Clarified that the x12UnitCodeId represents the EDI (Electronic Data Interchange) code identifier for the inventory unit, allowing external systems to correctly map and interpret unit codes when synchronizing inventory data with CareTend for procurement and supply chain operations.

Inventory
Units

V4

Staging:
3/25/2026

Production:
3/25/2026

N/A

HCSI-4629

Updated the CareTend Integration API with a V4 GET /v4/employees/search/roles endpoint that returns a paged list of employees who match one or more requested role names (for example, Biller/Collector), so clients can directly retrieve the staff assigned to specific responsibilities. The endpoint validates the requested role names and pagination parameters, ensures that each role type is recognized, and returns the union of all matching employees while preventing duplicate people from appearing more than once in the response. On success, the API returns a paginated result set containing each employee’s core identity and role information, allowing external systems to reliably see which users currently hold the specified roles.

Employees

V4

Staging: 3/11/2026

Production: 3/11/2026

N/A

HCSI-5244

Updated the CareTend Integration API with a V4 POST /v4/progressnotes/search endpoint that adds server-side pagination support when searching patient progress notes, improving performance and usability when large note histories exist. This endpoint validates the search filters carried over from V3 (such as MRN, entered-by, date ranges, subjects, follow-up flags, company IDs, and other existing criteria) along with 0-based pageNumber and pageSize parameters, enforcing allowed ranges and returning clear 400 Bad Request errors when pagination values are out of bounds. On success, the API returns a paged response using the standard Atlas PagedResponse<T> model—including pageNumber, pageSize, totalCount, totalPages, hasNextPage, hasPreviousPage, and a list of notes whose structure matches the V3 response—so clients can easily migrate by updating the URL and adding pagination parameters.

Progress Notes

V4

Staging:
3/11/2026

Production:
3/11/2026

N/A

HCSI-5266

Updated the CareTend Integration API V4 PATCH /v4/userdefinedfields/patients endpoint so clients can clear DateTime (type 4) and Single Choice Popup (type 6) patient user defined fields by sending either null or an empty string as the fieldValue, matching the behavior supported in the CareTend Desktop UI. The endpoint now treats empty or null values for these field types as valid “clear” operations, skipping type-specific parsing and choice validation while still enforcing the usual patient, container, and field identity checks in the request payload. On success, the API updates the underlying UDF records so the DateTime or Single Choice values are removed (with Value/FieldValue_Id cleared accordingly), and the response reflects the patient’s current user defined field values for confirmation.

User Defined Fields

V4

Staging:
3/11/2026

Production:
3/11/2026

WSI-72772

HCSI-5268

Resolved a issue in the CareTend Integration API PATCH /v4/patients endpoint where endpoint returned HTTP 400 errors even when clients supplied a valid medicalRecordNumber and collectorId as documented. The endpoint now correctly validates the MRN and collector ID along with other core patient fields (such as name fields) without requiring undocumented properties, so well‑formed PATCH requests are accepted instead of failing validation. On success, users will experience consistent system behavior and accurate data processing without errors.

Patients

V4

Staging:
3/11/2026

Production:
3/11/2026

N/A

HCSI-5299

Updated the CareTend Integration API with a V4 POST /v4/parties/{partyId}/addresses endpoint that allows ReferencePoint and other intake systems to create addresses for provider contacts programmatically, eliminating follow-up manual entry in CareTend. The endpoint validates the target party/provider contact and key address details—including address type, required address lines, city, state, postal code, county/country, and primary shipping flag—as well as ensuring address type and geographic values are valid for the tenant before saving. On success, the API returns the newly created address record for the specified provider contact, including its identifiers and stored address metadata, so external systems can confirm the address that will be used in CareTend.

Parties

V4

Staging:
3/11/2026

Production:
3/11/2026

N/A

HCSI-5300

Updated the CareTend Integration API with a V4 PATCH /v4/parties/{partyId}/addresses/ endpoint that allows ReferencePoint and other intake systems to update address information for provider contacts without logging into CareTend. The endpoint validates the target party and address identifiers along with key address fields—such as address type, address lines, city, state, postal/zip code, country/county, phone, place of service, directions, and the primary shipping flag—and returns clear errors when required inputs are missing or invalid. On success, the API returns the updated address record for the provider contact, including its identifiers and current address details, so external systems can confirm exactly what is stored and used in CareTend.

Parties

V4

Staging:
3/11/2026

Production:
3/11/2026

N/A

HCSI-5301

Updated the CareTend Integration API with a V4 GET /v4/parties/{partyId}/addresses endpoint that allows intake and ReferencePoint workflows to retrieve address details for a specific provider contact directly from CareTend. The endpoint validates the input provider (partyId), provider contact, and optional addressType filter, returning clear errors if identifiers are missing or invalid. On success, it returns the provider and provider contact IDs along with address type, address lines, city, state, zip code, county, place of service, directions, phone, and primary shipping flag so external systems can reliably use the same address information shown in CareTend.

Parties

V4

Staging:
3/11/2026

Production:
3/11/2026

N/A

HCSI-5302

Updated the CareTend Integration API with a V4 DELETE /v4/parties/{partyId}/addresses/ endpoint that allows intake and ReferencePoint workflows to remove an address from a provider contact without logging into CareTend. The endpoint validates the provider (partyId), provider contact address (partyAddressId), and related primary‑address rules to prevent deletion when it would violate required primary address constraints, returning clear errors if inputs are missing or invalid. On success, the API removes the specified address and returns a standard success response so external systems can confirm that the provider contact’s address list in CareTend has been updated accordingly.

Parties

V4

Staging:
3/11/2026

Production:
3/11/2026

N/A

HCSI-5303

Updated the CareTend Integration API with a V4 POST /v4/providers/{providerId}/contacts/ endpoint that allows intake and ReferencePoint workflows to create phone numbers for provider contacts directly from external systems instead of manually entering them in CareTend. The endpoint validates the provider and provider contact identifiers along with key phone details—including phone type, phone number value, and whether the number is primary—and returns clear errors when required fields are missing or invalid. On success, the API creates and returns the new phone number record tied to the specified provider contact, including its identifiers and stored phone metadata, so external systems can confirm exactly what will be used in CareTend.

Providers

V4

Staging:
3/11/2026

Production:
3/11/2026

N/A

HCSI-5304

Updated the CareTend Integration API with a V4 PATCH /v4/providers/{providerId}/contacts endpoint that allows intake and ReferencePoint workflows to update phone numbers for provider contacts directly from external systems instead of editing them in CareTend. The endpoint validates the provider, provider contact, and phone number identifiers along with key phone fields—such as phone type, phone number value, and whether the number is primary—and returns clear errors when required inputs are missing or invalid. On success, the API updates and returns the provider contact phone record, including its identifiers and current phone metadata, so external systems can confirm exactly what is stored and used in CareTend.

Providers

V4

Staging:
3/11/2026

Production:
3/11/2026

N/A

HCSI-5305

Updated the CareTend Integration API with a V4 GET /v4/providers/{providerId}/contacts endpoint that lets intake and ReferencePoint workflows retrieve specific phone numbers for a provider contact directly from CareTend. The endpoint validates the provider ID, provider contact ID, and provider contact phone ID, returning clear errors if any identifiers are missing or invalid. On success, the API returns the provider ID, provider contact ID, provider contact phone ID, phone number type, and phone number so external systems can reliably use the same contact details shown in CareTend.

Providers

V4

Staging:
3/11/2026

Production:
3/11/2026

N/A

HCSI-5306

Updated the CareTend Integration API with a V4 DELETE /v4/providers/{providerId}/contacts endpoint that lets intake and ReferencePoint workflows remove a specific phone number from a provider contact directly from external systems. The endpoint validates the provider, provider contact, and phone number identifiers (including phone number type) and will return clear errors if required IDs are missing or invalid, ensuring only the intended phone record is removed. On success, the API deletes the targeted provider contact phone record and returns a standard success response so external systems can confirm the number is no longer present for that contact in CareTend.

Providers

V4

Staging:
3/11/2026

Production:
3/11/2026

N/A

HCSI-5307

Updated the CareTend Integration API with a V4 POST /v4/providers/{providerId}/contacts endpoint that allows intake and ReferencePoint workflows to create email addresses for provider contacts programmatically instead of entering them manually in CareTend. The endpoint validates the provider and provider contact identifiers along with key email details— including email address type, email address value, and whether the email is primary—returning clear errors if required fields are missing or invalid. On success, the API creates and returns the new email address record tied to the specified provider contact, including its identifiers and stored email metadata, so external systems can confirm exactly what will be used in CareTend.

Providers

V4

Staging:
3/11/2026

Production:
3/11/2026

N/A

HCSI-5309

Updated the CareTend Integration API with a V4 GET /v4/providers/{providerId}/contacts endpoint that allows intake and ReferencePoint workflows to retrieve a specific email address for a provider contact directly from CareTend. The endpoint validates the provider ID, provider contact ID, and provider contact email address ID, returning clear errors if any identifiers are missing or invalid. On success, the API returns the provider ID, provider contact ID, provider contact email address ID, email address type, and email address so external systems can reliably use the same contact information shown in CareTend.

Providers

V4

Staging:
3/11/2026

Production:
3/11/2026

N/A

HCSI-5310

Updated the CareTend Integration API with a V4 DELETE /v4/providers/{providerId}/contacts endpoint that lets intake and ReferencePoint workflows remove an email address from a provider contact directly from external systems instead of doing it manually in CareTend. The endpoint validates the provider, provider contact, email address identifiers, and email address type, returning clear errors if required IDs are missing or invalid to ensure only the intended email record is removed. On success, the API deletes the targeted provider contact email address and returns a standard success response so external systems can confirm that the contact’s email list in CareTend has been updated accordingly.

Providers

V4

Staging:
3/11/2026

Production:
3/11/2026

N/A

HCSI-5311

Updated the CareTend Integration API with a V4 POST /v4/partycontacts endpoint that lets intake and ReferencePoint workflows associate an existing contact (person) to an existing party—such as Provider, Carrier, Facility, or Supplier—mirroring the “Search to Add Contact” activity in CareTend. The endpoint validates the partyId, personId, partyType (for example Provider, Carrier, Facility, Supplier), and contact details such as contactType (for example Primary, Responsible Party, Emergency, Other) and relationshipType, returning clear errors if required fields are missing or invalid for the specified party type. On success, the API creates and returns the new party-contact association record with its identifiers and stored relationship metadata so external systems can confirm how the contact is linked to the provider, insurance company, facility, or supplier in CareTend.

Party Contacts

V4

Staging:
3/11/2026

Production:
3/11/2026

N/A

HCSI-5318

Updated the CareTend Integration API V4 POST /v4/inventory/search endpoint to support an optional isFactor field in the request body so external systems like ProfitPoint can filter inventory results by factor status when needed. The endpoint now validates the isFactor flag (true/false) along with existing search and paging inputs, ensuring that including or omitting this optional field does not impact other inventory searches. On success, the API returns the usual paged inventory search results enriched with the isFactor value for each matching item so clients can see and act on factor information alongside other inventory details.

Inventory

V4

Staging:
3/11/2026

Production:
3/11/2026

N/A

HCSI-5319

Updated the CareTend Integration API V4 POST /v4/inventory/items/search endpoint so external systems like ProfitPoint can both send and receive an isFactor value when searching inventory items by location. The endpoint now validates the optional isFactor flag in the request along with required inputs such as LocationId, SiteId, and paging parameters, ensuring that including isFactor (true/false) does not break existing searches. On success, the API returns the usual paged inventory items for the specified location, with each item’s response now including its IsFactor value so clients can filter and act on factor status as part of their downstream workflows.

Inventory

V4

Staging:
3/11/2026

Production:
3/11/2026

N/A

HCSI-5217

Updated the POST V3 Delivery Ticket Items search endpoint /v3/deliverytickets/items/search so Workday’s ExternalRefKey (WorkdayId) is returned for each matching delivery ticket item, supporting Intermountain’s Workday–CareTend integration.Updated input handling to validate required search criteria (such as medical record number and delivery ticket ID) and ensure they correspond to existing delivery tickets before results are returned. Updated the response payload to include the ExternalRefKey alongside existing delivery ticket item details, enabling consumers to reliably tie CareTend delivery ticket items back to the originating Workday records.

Delivery Tickets

V3

Staging: Week of 3/02/2026

Production: Week of 3/16/2026

N/A

HCSI-5255

Updated the CareTend Integration API to add a V4 POST /commands/v4/suppliers endpoint that allows external systems to create new suppliers and keep data in sync with CareTend. This endpoint validates structured supplier details including name, addresses, phone numbers, email addresses, return information, special instructions, integration vendor, EDI support, and active status. On success, the API returns the newly created supplier record so you can confirm the stored contact and address information in CareTend.

Suppliers

V4

Staging: 2/25/2026

Production: 2/25/2026

N/A

HCSI-5256

Updated the CareTend Integration API with a V4 DELETE /commands/v4/suppliers/{supplierId} endpoint that allows external systems to remove suppliers from CareTend to keep both systems in sync and reduce manual data entry errors. This endpoint validates the supplied supplierId to ensure it is present, correctly formatted, and corresponds to an existing supplier before performing the delete. On success, the API confirms the deletion by making the supplier no longer available via supplier queries, allowing you to verify that the record has been removed from CareTend in alignment with your source system.

Suppliers

V4

Staging:
2/25/2026

Production:
2/25/2026

N/A

HCSI-5257

Updated the CareTend Integration API V4 POST create provider contact endpoint to allow external systems to set the Referral Source and Allow Web Access properties at the time of contact creation, reducing the need to log into CareTend for follow-up configuration. This endpoint validates standard provider contact details along with the optional Referral Source and Allow Web Access flags to ensure data is well-formed and consistent with your CareTend configuration before the contact is created. On success, the API returns the newly created provider contact record, including its CareTend identifiers and the configured Referral Source and Allow Web Access values, so you can confirm the contact setup directly from your integration.

Providers

V4

Staging:
2/25/2026

Production:
2/25/2026

N/A

HCSi-5354

Updated the ReferencePoint V4 PATCH patient documents endpoint in the CareTend Integration API to enforce that requests use form data when updating patient document information.

Patient Documents

V4

Staging:
2/25/2026

Production:
2/25/2026

N/A

HCSI-5247

Updated the POST /commands/v4/inventoryunits endpoint to allow external systems to create new Inventory Unit picklist entries, eliminating the need for manual setup in CareTend. The endpoint validates that Name is required, unique, and within length limits, IsActive is required, the X12 Unit Code is provided from the list of valid codes when supplied, and prevents duplicates for business-critical values while leaving other fields (such as Description) optional. On success, the endpoint returns the newly created Inventory Unit record, including its key attributes so clients can confirm and align values between CareTend and their source systems.

InventoryUnits

V4

Staging: 2/11/2026

Production: 2/11/2026

N/A

HCSI-5248

Updated the PATCH /commands/v4/inventoryunits endpoint so external systems can update existing Inventory Unit picklist entries (non‑system records only) instead of requiring manual changes in CareTend. The endpoint requires a valid Inventory Unit ID and at least one updatable field (Name, X12UnitCodeId, or IsActive), enforces that system records (IDs < 500001) cannot be modified, validates Name for uniqueness and length, validates X12UnitCodeId against allowed values when provided, treats unspecified fields as unchanged, and does not allow Description to be updated. On success, the endpoint returns the updated Inventory Unit record, including its key values (such as ID, Name, X12 Unit Code, and Active status) so client systems can verify that the change was applied correctly.

InventoryUnits

V4

Staging:
2/11/2026

Production:
2/11/2026

N/A

HCSI-5249

Updated the DELETE /commands/v4/inventoryunits endpoint so external systems can soft-delete Inventory Unit picklist entries, eliminating the need to manually remove them in CareTend. The endpoint requires that either Id or Name be provided (optionally both, but they must reference the same record), enforces that only non-system records (IDs ≥ 500001) can be deleted, and returns appropriate errors if inputs are missing, inconsistent, or refer to protected system entries. On success, the endpoint performs a soft delete (sets the record to inactive) and returns a confirmation message including key details of the deleted Inventory Unit so clients can verify the correct entry was removed.

InventoryUnits

V4

Staging:
2/11/2026

Production:
2/11/2026

N/A

HCSI-5250

Updated the GET /commands/v4/inventoryunits endpoint to let external systems retrieve Inventory Unit picklist data directly from CareTend, reducing manual re-entry and helping keep inventory data in sync across systems. The endpoint accepts optional Id or Name filters (but not both together), returns all Inventory Units when no filter is provided, uses case-insensitive matching on Name, only returns active records, and returns standard validation errors when inputs are missing, conflicting, or invalid. On success, the response includes each matching Inventory Unit’s Id, Name, Description, X12 Unit Code, Active indicator, record status, record status date, and record status modified-by so client systems have full, reliable detail for downstream use.

InventoryUnits

V4

Staging:
2/11/2026

Production:
2/11/2026

N/A

HCSI-5251

Updated the POST /commands/v4/manufacturers endpoint in the v4 CareTend API so external systems (such as Intermountain’s) can create new Manufacturer picklist entries and keep the CareTend manufacturer list synchronized across systems. The endpoint requires Name and Active indicator, accepts an optional Description, and validates inputs for required fields, data types, and business rules, returning clear error messages when data is missing or invalid. On success, the API returns the newly created manufacturer record (including its identifier, name, description, and active status) so clients can confirm the entry and align it with their source system.

Manufacturers

V4

Staging:
2/11/2026

Production:
2/11/2026

N/A

HCSI-5253

Updated the DELETE /commands/v4/manufacturers v4 endpoint so external systems (such as Intermountain’s) can remove entries from the CareTend manufacturer picklist and keep the list synchronized across systems. The endpoint accepts Name, Id, or both as input, validates that at least one is provided and that when both are passed they reference the same record, and returns clear validation errors when inputs are missing or inconsistent. On successful deletion, the API returns a confirmation response with key details of the affected manufacturer so clients can verify that the correct entry was removed in CareTend.

Manufacturers

V4

Staging:
2/11/2026

Production:
2/11/2026

N/A

HCSI-3217

Added a new V4 POST endpoint (/commands/v4/inventory/items/quantity/update-on-hand) that updates on-hand quantities in CareTend for Drug and Supply items (lot and non-lot), driven by data from external systems, with Equipment to be handled in a future enhancement. Added validations to ensure the inventory item and location, external reference key, new on-hand quantity, quantity change reason, optional lot details (lot number and expiration), and cost per unit are all present and valid before the update is applied. Added a response that reflects the updated inventory quantities for the specified item and location, recalculating available quantities based on existing commitments so users see accurate counts on the Quantity and Locations tab.

Inventory

V4

1/28/2026

1/28/2026

N/A

HCSI-5219

Updated the V4 POST endpoint } (/commands/v4/inventory/dispensable-units) that lets external systems such as Workday retrieve one or more matching dispensable units for an inventory item using InventoryItemId, ExternalRefKey, or both, with optional InventoryUnitId filtering. Updated input validation to ensure required identifiers are present, correctly formatted, and refer to the same inventory item (rejecting invalid, unrelated, or duplicate combinations with clear error messages). Updated the response to return a collection of matching dispensable units including IDs, names, EDI code, quantity, inventory item and external reference IDs, plus full audit details (created/modified and record status fields) so downstream systems can accurately sync and audit inventory data.

Inventory

V4

1/28/2026

1/28/2026

N/A

HCSI-5221

Updated the CareTend Integration API with a v4 POST endpoint that allows external systems such as Workday to create one or more new dispensable unit entries for an inventory item in bulk, reducing manual data entry and errors. Updated input validation so each requested dispensable unit is checked for required identifiers (InventoryItemId or ExternalRefKey, InventoryUnitId, Quantity), rejects combinations where InventoryItemId and ExternalRefKey do not belong to the same item, blocks duplicates for the same inventory unit and quantity, enforces system rules for the default “Each” unit, and caps the list at 25 dispensable units per inventory item. Updated the response to return the successfully created dispensable units and their key identifiers for each item in the request, along with clear validation errors for any records that cannot be created, so external systems can reliably track which units were added in CareTend.

Inventory

V4

1/28/2026

1/28/2026

N/A

HCSI-5222

Updated the v4 PATCH endpoint (/commands/v4/inventory/items/dispensable-units/{dispensableUnitId}) that allows external systems such as Workday to update an individual dispensable unit on an inventory item, reducing duplicate data entry and keeping systems in sync. Updated input validation to require a valid combination of inventoryItemId or externalRefKey with the target dispensable unit and inventory unit, enforce that the Inventory Item and External Ref Key refer to the same item, ensure quantity is greater than zero, block updates to the system-managed “Each” unit, and reject duplicate unit/quantity combinations. Updated the response to return the updated dispensable unit, including its identifiers, quantity, inventory item and external reference details, and audit information so calling systems can clearly see and track the changes applied in CareTend.

Inventory

V4

1/28/2026

1/28/2026

N/A

HCSI-5223

Updated the V4 DELETE endpoint (/commands/v4/inventory/items/dispensable-units/{dispensableUnitId}) that allows external systems such as Workday to remove dispensable unit entries for an inventory item, helping purchasing managers avoid duplicate data entry and errors. Updated input validation to require a valid dispensable unit ID, prevent deletion of the system-managed “Each” unit and any default dispensable unit, and block removal of units that are referenced in transactions like inventory purchase orders or inventory transfers. Updated the response to return a clear success status and key identifiers when a dispensable unit is soft-deleted, and to surface detailed validation errors when a requested unit cannot be deleted so calling systems can accurately track which units remain active.

Inventory

V4

1/28/2026

1/28/2026

N/A

HCSI-5225

Updated the V4 POST search endpoint (/commands/v4/inventory/suppliers/search) that lets external systems such as Workday retrieve a list of suppliers defined for an inventory item using inventoryItemId, externalRefKey, or both, with an optional supplierId filter to support data consistency checks between systems. Updated input validation to require at least one valid inventory identifier, ensure that inventoryItemId and externalRefKey refer to the same inventory record when both are provided, and confirm that any supplied supplierId is correctly associated with that item. Updated the response to return each matching supplier with its supplierId, supplier name, package unit, eaches per package, reorder number, cost per package unit, cost per each, and primary indicator so downstream systems can accurately compare and reconcile supplier data.

Inventory

V4

1/28/2026

1/28/2026

N/A

HCSI-5226

Updated the V4 POST bulk endpoint (/commands/v4/inventory/items/suppliers/bulk) that lets external systems such as Workday create multiple supplier entries at once for a single inventory item using either inventoryItemId or ExternalRefKey, improving cross-system data consistency. Updated input validation to require a valid inventory identifier, ensure inventoryItemId and externalRefKey (when both are provided) reference the same item, validate each supplier entry (supplierId, packageUnit, eaches, reorderNumber, costPerUnit, isPrimary), enforce that there is only one primary supplier, and cap the suppliers list at 25 per inventory item. Updated the response to return the successfully created suppliers and their key identifiers for the item, along with clear validation errors for any supplier records that cannot be created so calling systems can easily confirm which suppliers were added in CareTend.

Inventory

V4

1/28/2026

1/28/2026

N/A

HCSI-5227

Updated the V4 PATCH endpoint (/commands/v4/inventory/items/suppliers/{inventoryItemSupplierId}) that allows external systems such as Workday to update an existing supplier entry for an inventory item, supporting cross-system data consistency checks. Updated input validation to require a valid inventory item supplier ID and supplierId, accept inventoryItemId and/or externalRefKey (which must reference the same inventory record when both are provided), and verify that packageUnit, eaches, reorderNumber, costPerUnit, and isPrimary are all valid for that item. Updated the response to return the updated supplier entry and its key identifiers—including inventory item and external reference details, supplier, package unit, quantities, cost, and primary flag—so calling systems can clearly confirm which supplier details were changed in CareTend.

Inventory

V4

1/28/2026

1/28/2026

N/A

HCSI-5228

Updated the V4 DELETE endpoint (/commands/v4/inventory/items/suppliers/{inventoryItemSupplierId}) that allows external systems such as Workday to remove an existing supplier entry for an inventory item, supporting consistency of supplier data across systems. Updated input validation to require a valid inventory item supplier ID and supplierId, optionally accept inventoryItemId and/or externalRefKey that must reference the same inventory record, and prevent deletion when the supplier is still referenced on purchase orders or dispensable units. Updated the response to return a clear success status and key identifiers for the deleted supplier—including indication when a primary supplier has been removed—or detailed validation errors when the supplier cannot be deleted, so calling systems can accurately track which suppliers remain active in CareTend.

Inventory

V4

1/28/2026

1/28/2026

WSI-72439

HCSI-5258

Resolved an issue where the v4 PATCH /commands/v4/patientorders/drug/injpo was defaulting the primaryPayerPolicyNumber to the patient (self-pay) whenever the field was omitted from the request, effectively making this optional field behave as if it were required. Now the input handling distinguishes between a missing primaryPayerPolicyNumber (no change to the existing primary payer) versus an explicitly provided empty string or null (treated as a request to clear the primary payer per the documented rules), preventing unintended payer changes. The response accurately returns the patient order with the correct primary payer policy number—either preserved or cleared as requested—so downstream systems see consistent and expected payer information after updates.

Patientorders

V4

1/28/2026

1/28/2026

N/A

HCSI-4933

Added a new POST v4/scheduletasks endpoint that lets AlayaCare create CareTend schedule tasks with subject, task type, start/end or duration, employee/department assignees, optional patient MRN, notes, and reminder minutes. Added validation and error handling for required fields (e.g., subject, task type, start date/time, department, entered by/on) and common edge cases, including support for clearing optional fields by sending null or no value. Added a structured response that returns the created task details (subject, type, start date/time, department, patient, duration, notes, assignees, reminder minutes) so calling systems can confirm the schedule entry that was created in CareTend.

ScheduleTasks

V4

Staging: 1/14/2026

Production: 1/14/2026

N/A

HCSI-5028

Added a POST /v4/patients/search endpoint that removes use of database views in the underlying stored procedure so Integration V4 patient search works with the latest build pipeline. Added input validation to require well-formed patient search criteria and to reject invalid or incomplete request payloads before the query executes. Added an optimized query that returns patient search results directly from the underlying tables, with all previously ignored E2E and unit tests reinstated and functionality verified in QA (see attached Postman QA check)

Patients

V4

Staging:
1/14/2026

Production:
1/14/2026

WSI-71574

HCSI-5216

Updated the v4 GET /commands/v4/deliverytickets endpoint used by Workday–CareTend integrations so that delivery ticket responses now include the ExternalRefKey (WorkdayId) when retrieving a ticket by id or number. The endpoint validates that a valid delivery ticket id or number query parameter is provided and that the caller is authorized, returning standard error responses if the input is missing, invalid, or the ticket is not found. Responses continue to return the full delivery ticket payload and now also include the ExternalRefKey field, enabling Intermountain and other clients to reliably correlate CareTend tickets with their Workday records.

Deliverytickets

V4

Staging:
1/14/2026

Production:
1/14/2026

N/A

HCSI-5231

Resolved an issue where the v4 PATCH /commands/v4/inventory endpoint returned a 500 error instead of a 400 when updating Drug or Supply inventory items with mismatched inventoryItemId and externalRefKey. Input validation has been enhanced so that mismatched identifiers or mismatched item types (for example, attempting to update a Drug inventory item as a Supply, or vice versa) now return a clear 400 error explaining that the values or types do not match the target inventory item. The endpoint continues to return standard success responses when the inventoryItemId, externalRefKey, and item type (Drug or Supply) are valid and consistent.

Inventory

V4

Staging:
1/14/2026

Production:
1/14/2026

N/A

HCSI-5232

Added a POST v4/documents/newfax and v4/documents/newscan workflow integration so that newly created fax and scanned documents now appear correctly in the Document Manager and the Incoming Documents queue in the CareTend UI. Input validation ensures that only supported document types (New Fax, New Scanned) with valid workflow group settings create corresponding workflow instances required by the UI. The endpoint returns a standard 200 response with the created document, and now also creates the necessary workflow tracking records so these documents are immediately visible and editable in the UI

Documents

V4

Staging:
1/14/2026

Production:
1/14/2026

N/A

HCSI-3455

Resolved an issue where the POST /v3/deliverytickets/shipmentupdates/search returned no results when shipment updates existed. The endpoint now requires a correctly structured JSON body (TeamIds, CompanyIds, ShipmentStatuses like ["shipped","return","transfer"], valid StartDate/EndDate, and paging: PageNumber, PageSize) and returns a paged list of matching shipment updates when validations and data conditions are met.

Deliverytickets

V3

Staging: **Week **of 1/5/2026

Production: Week of 1/19/2026

N/A

HCSI-3859

Added a POST /v3/patientorders/hme/recurringrental/item Recurring Rentals endpoint to create a recurring rental item and link it to an existing recurring rental, with automatic promotion to primary when it’s the only item and recalculation of billing options, authorizations, and taxes.

Patientorders

V3

Staging:
Week of 1/5/2026

Production:
Week of 1/19/2026

N/A

HCSI-3860

Added a PATCH /v3/patientorders/hme/recurringrental/item endpoint that allows updating a recurring rental item and adding it to an existing recurring rental. Supports modifying details such as serial number, price, quantity, and tax status for equipment or non-inventory items, with billing and taxes recalculated as needed.

Patientorders

V3

Staging:
Week of 1/5/2026

Production:
Week of 1/19/2026

N/A

HCSI-3862

Added a GET /v3/patientorders/hme/recurringrental/item endpoint to retrieve recurring rental items by Recurring Rental ID. Returns details such as serial number, billed and expected price, quantity, HCPC code, modifiers, billing narrative, taxable status, item description, and equipment asset information, and validates IDs for appropriate responses.

Patientorders

V3

Staging:
Week of 1/5/2026

Production:
Week of 1/19/2026

WSI-65354

HCSI-4933

Updated Patient Orders CareTend API Endpoint where it will now automatically set the primary payer to “Patient” if none is provided.

Patientorders

V3

Staging:
Week of 1/5/2026

Production:
Week of 1/19/2026

N/A

HCSI-4136

Updated the PUT IV patient drug order endpoint validation to prevent editing IV orders once a prescription is filled or labels have been printed.

Patientorders

V3

Staging:
Week of 1/5/2026

Production:
Week of 1/19/2026

N/A

HCSI-4945

Updated Prescriptions CareTend API Endpoint where the Rx Description for Factor drug orders was not displaying in the UI response despite being passed via the Create or Update Prescription API, ensuring accurate rendering of prescription details for drugs like Eloctate Intravenous Solution Reconstituted 2000 UNIT.

Prescriptions

V3

Staging:
Week of 1/5/2026

Production:
Week of 1/19/2026

N/A

HCSI-4947

Updated Documents CareTend API Endpoint validation to clarify that the Received Date field cannot be set during creation of a "Patient Document" type, aligning with system constraints that restrict date fields to update operations only.

Documents

V3

Staging:
Week of 1/5/2026

Production:
Week of 1/19/2026

N/A

HCSI-4963

Fixed an issue in the POST Documents
CareTend API endpoint where updating
the activeDate field caused the Date
Active value to be removed in CareTend UI,
ensuring the updated date displays
correctly instead of reverting to
“Select a date.”

Documents

V3

Staging:
Week of 1/5/2026

Production:
Week of 1/19/2026

N/A

HCSI-4977

Fixed an issue with the POST Prescriptions API Endpoint where you received an error when trying to create a prescription for a Drug or HME order.

Prescriptions

V3

Staging:
Week of 1/5/2026

Production:
Week of 1/19/2026

N/A

HCSI-4978

Updated the POST Persons CareTend API endpoint by adding support for the ‘Associated Organization’ field group (Prescriber, Facility, Insurance Company, Supplier) in the Create Person endpoint, aligning API functionality with UI capabilities for contact management workflows.

Persons

V3

Staging:
Week of 1/5/2026

Production:
Week of 1/19/2026

WSI-66291

HCSI-4979

Updated the POST Delivery Ticket Items CareTend API endpoints to allow updates on non-working Delivery Tickets, resolving previous errors and enabling full support for programmatically created tickets in purchase order workflows.

Deliverytickets

V3

Staging:
Week of 1/5/2026

Production:
Week of 1/19/2026

N/A

HCSI-5015

Updated the POST Providers CareTend API endpoint to support creating provider contacts and user-defined fields, aligning API functionality with UI capabilities for comprehensive provider data management.

Providers

V3

Staging:
Week of 1/5/2026

Production:
Week of 1/19/2026

N/A

HCSI-5021

Updated the POST Patients CareTend API endpoint to allow creating and updating patients without requiring a date of birth, aligning API behavior with UI functionality.

Patients

V3

Staging:
Week of 1/5/2026

Production:
Week of 1/19/2026

N/A

HCSI-5023

Updated the /v3/patients/contacts CareTend API endpoint to allow specifying an Active status when creating a patient contact, eliminating the need for a subsequent update call and aligning API behavior with UI functionality.

Patients

V3

Staging:
Week of 1/5/2026

Production:
Week of 1/19/2026

N/A

HCSI-5024

Updated the PATCH employees endpoint to allow clearing employee fields such as address, phone, DOB, and supervisor when information is incorrect and not yet available.

Employees

V3

Staging:
Week of 1/5/2026

Production:
Week of 1/19/2026

N/A

HCSI-5025

Fixed an issue with the POST /v3/documents/serach endpoint to return the appropriate Workflow Id based on the specified workflowGroupName (e.g., HME, SPRx), ensuring accurate document retrieval.

Documents

V3

Staging:
Week of 1/5/2026

Production:
Week of 1/19/2026

N/A

HCSI-5049

Updated POST /v3/deliverytickets/shippingresponses endpoint by fixing a bug for a missing
mapping to ensure successful API calls now
return accurate shipping data instead of empty responses.

Deliverytickets

V3

Staging:
Week of 1/5/2026

Production:
Week of 1/19/2026

WSI-69238

HCSI-5065

Fixed a bug where the POST /v3/patients/assessments/custom
endpoint required a customAssessmentId
without clear guidance. Validation now
ensures a valid ID is provided or generated,
and documentation clarifies requirements.

Patients

V3

Staging:
Week of 1/5/2026

Production:
Week of 1/19/2026

WSI-69445

HCSI-5068

Updated the POST
/v3/patientorders/search endpoint to include Created Date and Modified Date in responses. Requires valid patient MRN or patientOrderId in request body.

Patientorders

V3

Staging:
Week of 1/5/2026

Production:
Week of 1/19/2026

N/A

HCSI-5081

Updated the GET /v3/deliverytickets/shippingresponses
to allow Delivery Ticket ID as a
query parameter, require either
Delivery Ticket Number or Delivery
Ticket ID, and validate both
when provided to ensure they reference
the same ticket.

Deliverytickets

V3

Staging:
Week of 1/5/2026

Production:
Week of 1/19/2026

WSI-68347

HCSI-5189

Added a PUT /v3/prescriptions/sprx/discontinue endpoint to discontinue specialty pharmacy prescriptions, requiring prescription ID, stop date, and discontinuation reason. Supports reactivation and high-volume calls for bulk processing.

Prescriptions

V3

Staging:
Week of 1/5/2026

Production:
Week of 1/19/2026

WSI-662067

HCSI-5192

Resolved an issue where PUT /v3/entity/lastevent updated Last Event Name but did not refresh Last Event History and Workflow History details (LastEvent By, LastEvent Updated Date, Transition Date, Modified User, Modified Date). Validation ensures required entity and user context; updates now consistently use current UTC timestamp and calling user, and return accurate history.

Entity

V3

Staging:
Week of 1/5/2026

Production:
Week of 1/19/2026

N/A

HCSI-5196

Resolved an issue where POST /v3/deliverytickets ignored fromDate and toDate per ticket item and overwrote with targetDeliveryDate. The endpoint now uses item-level dates when provided, falling back to targetDeliveryDate only if absent, ensuring correct service date ranges for billing and scheduling.

Deliverytickets

V3

Staging:
Week of 1/5/2026

Production:
Week of 1/19/2026