Changelog

N/A

HCSI-3170

Added a new V4 POST /v4/patients/discharge endpoint that allows external systems to create a patient discharge record in CareTend programmatically. The endpoint accepts the patient's medical record number, discharge date, last visit date, progress during therapy, services and care provided, reason for discharge, discharge status, acuity at discharge, prescriber notification flag, discharge instructions, and patient clinical history. On success, CareTend creates the patient discharge record, enabling external systems to initiate the discharge process without requiring manual entry in the CareTend Desktop.

Patients

V4

Staging: 5/6/2026

Production: 5/6/2026

N/A

HCSI-3171

Added a new V4 PATCH /v4/patients/discharge endpoint for updating an existing patient discharge record in CareTend. The endpoint accepts the same fields as the create discharge endpoint — including patient MRN, discharge date, last visit date, therapy progress, services provided, discharge reason, discharge status, acuity, prescriber notification, discharge instructions, and clinical history — allowing external systems to correct or update discharge records without requiring access to the CareTend Desktop.

Patients

V4

Staging:
5/6/2026

Production:
5/6/2026

N/A

HCSI-4000

Added a new V4 POST /v4/billingauthorizations/search endpoint that allows external systems to search for billing authorization records in CareTend using structured search criteria. On success, the API returns matching billing authorization records, providing integration partners with a V4-compatible method to query authorization data for downstream billing and claims workflows.

Billing
Auths

V4

Staging:
5/6/2026

Production:
5/6/2026

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:
5/6/2026

Production:
5/6/2026

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:
5/6/2026

Production:
5/6/2026

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:
5/6/2026

Production:
5/6/2026

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:
5/6/2026

Production:
5/6/2026

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:
5/6/2026

Production:
5/6/2026

N/A

HCSI-5512

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:
5/6/2026

Production:
5/6/2026

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:
5/6/2026

Production:
5/6/2026

N/A

HCSI-5514

Added a new PATCH /v4/userdefinedfields/patients/"MRN" endpoint that updates patient user-defined field values in a single API call using field names and group names rather than numeric IDs. The endpoint resolves groupName and fieldName to the correct container and field IDs internally and auto-creates a ContainerGroupAssociation if one does not yet exist for the patient, eliminating the need for a prior GET call to retrieve record IDs before updating.

UDF

V4

Staging:
5/6/2026

Production:
5/6/2026

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:
5/6/2026

Production:
5/6/2026

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

WSI-66548

HCSI-4953

Updated the POST /v4/deliverytickets/items endpoint to accept LocationId as an optional input parameter alongside required fields such as InventoryItemId, allowing clients to specify the inventory location when adding items to a delivery ticket. Previously, the endpoint did not add the Location_Id to the database. The endpoint now correctly stores and returns the LocationId for delivery ticket items in the response.

Deivery Tickets

V4

Staging: 4/22/2026

Production: 4/22/2026

N/A

HCSI-4954

Enhanced the PATCH /v4/deliverytickets/items/{id} endpoint to accept an optional LocationId field, allowing external systems to update the inventory location on a delivery ticket item without requiring manual entry in CareTend. On success, the API returns the updated ticket item with the correct location assignment.

Delivery
Tickets

V4

Staging:
4/22/2026

Production:
4/22/2026

N/A

HCSI-5459

Added a POST /v4/supporting-documents endpoint to create Statement of Medical Necessity (SMN) documents for patients, accepting document date, certification type, expiration date, diagnoses, clinical notes, modifiers, and field values with sensible defaults applied when optional fields are omitted. A companion GET /v4/supporting-documents/{id} endpoint retrieves the full SMN document by ID, enabling external systems to create and retrieve complete medical necessity documentation without manual CareTend Desktop entry.

Supporting Documents

V4

Staging:
4/22/2026

Production:
4/22/2026

N/A

HCSI-5429

Resolved an issue where the PATCH /v4/prescriptions/transfer endpoint returned 400 "Central Pharmacy must be enabled in order to transfer prescriptions" for all tenants regardless of their actual configuration, making prescription transfers impossible through the V4 API. The endpoint now correctly reads each tenant's Central Pharmacy configuration and completes transfers for tenants where the feature is enabled.

Prescriptions

V4

Staging:
4/22/2026

Production:
4/22/2026

N/A

HCSI-5433

Resolved an issue where the PATCH /v4/clinicianvisits/{id} endpoint accepted empty strings for mandatory fields TherapyType, EmployeeUserName, PatientMRN, and InventoryItemId and returned HTTP 200 without validation errors, allowing incomplete records to be saved in violation of CareTend business rules. The endpoint now returns 400 Bad Request with field-specific error messages when mandatory fields are submitted as empty.

Clinician
Visits

V4

Staging:
4/22/2026

Production:
4/22/2026

N/A

HCSI-5435

Resolved an issue where the PATCH /v4/billingauthorizations/{id} endpoint returned 404 when attempting to reactivate a discontinued billing authorization, even though CareTend Desktop permitted this workflow. Added an includeInactive=true query parameter that allows discontinued authorizations to be located and updated, enabling full authorization lifecycle management through the API.

Billing
Auths

V4

Staging:
4/22/2026

Production:
4/22/2026

N/A

HCSI-5436

Resolved an issue where the PATCH /v4/patients/mrn/{mrn}/patientalerts endpoint returned 500 Internal Server Error instead of 404 when no alert record existed for a patient, and corrected the related GET endpoint which returned 400 instead of 404. Both endpoints now return 404 with consistent error messages, allowing external systems to reliably distinguish between missing patients and missing alert records.

Patients

V4

Staging:
4/22/2026

Production:
4/22/2026

N/A

HCSI-5438

Resolved an issue where the PATCH /v4/deliverytickets/{id} endpoint silently cleared the TrackingURL and Delivery Manager (IsVirtueScriptEnabled) settings whenever the shipping method was changed, despite returning a 200 OK response. On success, shipping method updates preserve all associated configuration including Tracking URL and Delivery Manager settings.

Delivery
Tickets

V4

Staging:
4/22/2026

Production:
4/22/2026

N/A

HCSI-5459

Added a POST /v4/patients/assessments/custom endpoint to create custom assessment instances for patients in CareTend, accepting MedicalRecordNumber and ContainerGroupId (template ID) as required fields along with optional clinician, date, status, location, and assessment type. On success, the API returns the CustomAssessmentId and PatientAssessmentId needed to complete the assessment via the field update endpoint, enabling end-to-end custom assessment workflows without CareTend Desktop interaction.

Custom
Assessments

V4

Staging:
4/22/2026

Production:
4/22/2026

N/A

HCSI-5460

Enhanced the POST /v4/customassessments/template endpoint to return ContainerId and FieldId values for all created groups and fields in the creation response, eliminating the need for a separate lookup call to discover these identifiers after template creation. External systems can now immediately use the returned identifiers to populate assessment instances without additional API calls.

Custom
Assessments

V4

Staging:
4/22/2026

Production:
4/22/2026

N/A

HCSI-5466

Resolved an issue where the POST /v4/inventory/items/quantity/deduct endpoint drew vial-based deductions from quantity-based inventory records instead of the correct vial-sized records, causing inaccurate inventory totals and erroneous "Insufficient quantity" errors. On success, the API deducts from the correct vial-size record, ensuring accurate inventory totals for pharmaceutical dispensing operations.

Inventory

V4

Staging:
4/22/2026

Production:
4/22/2026

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