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 |
