# Changelog — 2025

This page lists all Welkin platform releases for 2025, newest first. For earlier releases see the [2024 Changelog](/release-notes/changelog-2024.md).

***

## Version 2025.68.0

**Release Date:** December 11, 2025 – 1:00 AM PST

### New Functionality

**FT-2396: Smart Inbox: Added Search Functionality.** This release introduces a new search feature in the Smart Inbox. Users can now quickly find communications by phone number (to/from), email address (to/from), patient or contact name, as well as by any text contained within the communication. This enhancement adds convenience and makes it easier to locate the needed information without manual scrolling.

**FT-2039: Outlook Calendar Integration.** Outlook Calendar Integration is now available, providing both one-way and two-way synchronization options. One-way sync allows Welkin events to be pulled into Outlook, while two-way sync keeps updates aligned in both systems. This feature is optional and can be enabled individually. To request activation, please reach out to your Account Manager.

\*\*FT-2163: Support for Not Applicable and New Scaled Average Formula. \*\* For Scored Assessments, we’ve added the ability to mark individual assessment items as Not Applicable (N/A) so they are excluded from both the calculated score and the total possible points, ensuring results reflect only relevant inputs. Additionally, a new Scaled Average formula option is now available for groups. This allows the average score to be multiplied by a configurable λ (lambda) factor, providing greater flexibility in score calculations.

**FT-2299: New Encounter Date-Only Variable for Message Templates.** A new variable, {{ENCOUNTER.\*.startDate}}, has been added to the Message Template section of the Designer when the context type is set to Encounter. This variable allows templates to reference the encounter date only, without including the time, providing more flexibility for communication formatting.

**FT-2318: New “Not Contains” and “Not Contains All” Conditions for Automations.** This release adds two new condition options — Not Contains and Not Contains All — for automations that use the Data Type entity. These options allow automations to run when specific values are absent from a list. Not Contains checks whether at least one of the specified values is not present in the field. If any value is missing, the condition is satisfied, and the automation can run. Not Contains All requires all specified values to be missing. If even one of them is present, the condition is not met. These new options offer greater flexibility when building logic based on values that should not appear in a Data Type field.

### Improvements and Bug Fixes

**FT-1936: PDF Title Display Issue Resolved.** Fixed an issue where PDF titles in patient records could display the wrong patient name, often showing the name of the first patient whose form was opened. This incorrect caching display behavior has been corrected, and PDFs now consistently show the proper title for each patient.

**FT-2230: Fixed Issue With Completed Tasks on the New Homepage.** Resolved a problem where completed tasks continued to appear in the widget on the new homepage. Tasks now fall off the list correctly based on the widget’s configuration.

**FT-2368: Improved Encounter Creation During Time Changes.** Enhanced the handling of encounter creation during both the transition into and out of daylight saving time. The system now prevents unintended one-hour shifts, ensuring consistent and predictable appointment times throughout seasonal time changes.

## Version 2025.67.0

**Release Date:** Oct 30, 2025 – 1:00 AM PDT

### New Functionality

**FT-1504: Smart Inbox (BETA) – Unified Communication Center for Patient-Centered Care.** This release introduces the Welkin Smart Inbox (Beta) – a foundational step toward a fully unified communication experience and the first feature built with Welkin’s new design language system, showcasing a modern, intuitive interface that improves usability and consistency across the platform. The Smart Inbox centralizes all patient conversations across Secure Email, SMS, In-App Chat, Unrecognized messages, and WhatsApp in a single workspace, empowering care teams to collaborate seamlessly, respond faster, and reduce unanswered or delayed communications. The Smart Inbox includes role-based views (My Inbox, Team Inbox, All Patients Inbox), real-time collaboration, and patient context displayed alongside each conversation to reduce tab-switching and improve response accuracy. The handling of unrecognized communications has also been reworked for greater efficiency to improve triage and routing of inbound messages. The new Communication Center is fully compatible with the previous version and should not disrupt any existing workflows or automations. This release establishes the foundation for future capabilities like internal provider chat, @tag mentions, advanced routing, analytics, and expanded channel support – all designed to enhance communication, accountability, and care coordination. If you’d like early access or assistance with enabling Smart Inbox and migrating existing communication data, please reach out to your Welkin account manager.

## Version 2025.66.0

**Release Date:** Oct 2, 2025 – 1:00 AM PDT

### New Functionality

**FT-2118: HIN Secure Email Integration. We’re excited to announce a new integration with HIN (Health Info Net), Switzerland’s trusted healthcare communication network. This feature enables secure, compliant email communication directly through the Welkin Care Portal, ensuring that all sensitive communications meet Swiss healthcare data protection standards (DSG & GDPR).**

**FT-2037: Google Calendar Synchronization Enhancements. We’ve improved our Google Calendar integration to now allow for one-way or two-way synchronization.** With two-way sync, updates in Google Calendar automatically appear in Welkin, and changes in Welkin are reflected in Google Calendar — helping you save time and keep schedules aligned. This optional feature is enabled separately. To request activation, please contact your Account Manager.

**FT-2104: Improved Task Comments via API. We’ve enhanced how comments work when creating tasks through the API. In addition to comments from the API client, you can now add a comment on behalf of the patient when the task is created. This provides better context for customers adding patient comments from their apps to Tasks via API.**

### Improvements and Bug Fixes

\*\*FT-1861: Improved Call Notifications. We’ve enhanced the reliability and timing of call notifications, ensuring they arrive more promptly so users can stay informed and respond without delays. \*\*

**FT-2156: Task Comments Ordering Fix. We’ve resolved an issue where task comments were not always displayed in the correct order. Comments are now consistently sorted, with the most recent ones shown at the top for easier visibility.**

**FT-2171: Improved File Upload Notifications. We’ve updated toast notifications in the Document Center for a smoother experience. When uploading files, notifications now disappear automatically and no longer require an extra click to dismiss.**

## Version 2025.65.0

**Release Date:** Aug 21, 2025 – 1:00 AM PDT

### New Functionality

**FT-1807: Use Patient Profile Fields in Assessments.** This release introduces the ability to include Patient Profile fields directly within assessments. These fields can be pre-filled with existing profile data, giving respondents the opportunity to confirm, update, or complete missing information during the assessment process. Use this feature to improve data accuracy, reduce duplication, and streamline patient information management by integrating profile verification seamlessly into your assessment workflow.

**FT-1760: Create Encounter Automation - “Today”.** Previously, encounter creation via automation was only possible for future dates. With this release, automations can now be set to create an encounter on the same day by specifying 0 in the Days field. This improvement is especially useful for handling urgent cases or same-day scheduling without manual intervention. If the specified time is in the past, the automation will not run, and details will be recorded in the Automation Audit for review.

**FT-1966: Enhanced Data Views Settings.** As part of this release, the Data Views settings have been expanded to provide more control and flexibility. HTML field settings now support variables, enabling the display of additional dynamic information for more convenient and informative Data View usage. In addition, new Required and Read-only options have been added to field settings, helping ensure data is filled out accurately and consistently according to your workflow requirements.

### Improvements and Bug Fixes

**FT-2012: Patient List Display Issue Fixed.** Resolved an issue where the full list of patients was not displayed when reassigning communications, ensuring all eligible patients are now visible for selection.

**FT-2103: Fixed Time Selection in Assessments.** Resolved an issue where the time picker in assessments was not functioning correctly, ensuring it is now fully usable for selecting time values.

**FT-2124: Fixed Formatting Issues in PFA Templates.** Resolved several formatting problems in Patient-Facing Assessment (PFA) templates to improve readability and overall user experience.

**FT-2131: Fixed Variable Resolution in Assessments Within Encounters.** Fixed an issue where variables in assessments were not being resolved when the assessment was initiated within an encounter.

**FT-2120: Improved Acuity Integration.** Enhanced integration with Acuity and fixed an issue where a patient might not be created in Welkin when scheduling an event through Acuity.

## Version 2025.64.0

**Release Date:** July 17, 2025 – 1:30 AM PDT

### New Functionality

* FT-1942: Enhanced “Bulk Update for Patients” Endpoint. With this release, the “Bulk Update for Patients” API endpoint has been expanded. It now supports partial updates to the care team, allowing the addition, removal, or replacement of specific care team members, rather than modifying the entire team. The API can perform these updates even if the user and patients have a region or territory mismatch.\
  The Postman public collection will be refreshed after the release to include documentation on these new capabilities.
* FT-1941: Task Commenting via API on Behalf of a Patient. This release introduces the ability to add comments to tasks on behalf of a patient through the API. If patient information is not provided, the comment will be attributed to the API client by default. The Postman public collection will be updated after the release. The "Add comment to Task" request will include support for commenting on behalf of a patient.
* FT-1943: New Automation Event: Task Comment Added. The automation system now includes a new event: Task Comment Added. This enables automations to be triggered when a comment is posted to a task, supporting more dynamic workflows and enhancing task management.
* FT-1656: ‘Is Completed’ Condition for Assessment Entity Type. A new condition, ‘Is Completed,’ has been added for the Assessment entity type in automations. This condition verifies whether the most recent assessment with a specific name has been completed. If the latest assessment is not completed (e.g., it has an In Progress status), the condition will not be satisfied.
* FT-1962: Compact View Setting in Widget Columns. This release introduces a Compact View setting in the Columns section of Widgets. When enabled, CDT data is consolidated into a single row per patient. Multiple text, datetime, and integer values from different CDTs are displayed as comma-separated entries. This improves the data display, making it easier to review patients with multiple CDT records.
* FT-1942: Resolve Message Templates via API. With this release, a new endpoint called "Resolve Template" has been added. It allows the API client to resolve message templates, including those that contain PFA variables or other supported variables. This enables more dynamic and personalized content generation through the API.

### Improvements and Bug Fixes

* FT-1936: User-Friendly Labels for System-Generated Actions. In the Care Portal, system-generated actions now feature user-friendly labels such as System, Automation, and API Client, making activity logs easier to understand. An information icon has also been added, hovering over it reveals which internal service performed the action.
* FT-1768: Date of Birth Field in Patient Profile. Resolved an issue affecting the Date of Birth field when editing patient information in the profile. The field now functions correctly during updates.
* FT-1752: Variable Display in Assessments. Fixed an issue where variables were not displaying correctly within assessments. All variables now appear as expected during form completion and review.
* FT-1843: File Preview for Duplicate File Names. Resolved an issue where uploading files with the same name caused the preview of one file to appear for both. Each file now displays its correct individual preview, even if filenames are identical.
* FT-2036: Resolved Delay When Viewing Incoming Notifications. Resolved an issue that caused a delay when clicking the notification bell to view incoming alerts. Notifications now load promptly, improving the responsiveness of the alert system.

## Version 2025.63.0

**Release Date:** June 20, 2025 – 1:00 AM PDT

### New Functionality

* FT-1885: Video Uploads in Document Center: We’ve added the ability to upload video files directly to the Document Center, making it easier to share and store rich media content as part of internal patient documentation. This feature supports the .mp4 format, with a maximum file size of 200 MB per video, and allows users to upload up to 10 video files per document, totaling up to 2GB. Whether it's a recorded consultation, a rehabilitation exercise demo, or a clinical reference clip, this feature enhances collaboration and documentation accuracy among care team members.

### Improvements and Bug Fixes

* FT-1937: Improved Look & Feel of PFAs: We’ve updated the design of PFAs to improve clarity and alignment across all assessment elements. These changes enhance the overall experience for users on both mobile and desktop.
* FT-1974: Improved Error Messaging on the HomePage: We’ve added more clear and readable error messages in the HomePage to better inform users when data is unavailable.

## Version 2025.62.0

**Release Date:** May 16, 2025 – 1:00 AM PDT

### New Functionality

* FT-1771: Automation Support for Tracking Candid Claim Failures: As part of this release, a new automation trigger, “Candid Claims Failed,” has been introduced. This trigger is designed to work exclusively with the “Webhook” action. It enables users to monitor failed claim submissions and take timely corrective action. In addition, when a claim fails to be created, a detailed error message will now be displayed in the upper right corner of the Care Portal, providing the maximum available information about the issue to facilitate quick troubleshooting. All executions of this automation are now logged and can be reviewed in the Automation Audit of Admin.
* FT-1814: Widget Preview Option in the Designer Portal: To enhance the user experience when configuring Homepage Widgets, a Preview option has been added to the Designer Portal. This functionality allows users to view a visual representation of the widget before publishing, ensuring accuracy in layout and content presentation. To maintain data privacy, any inaccessible or sensitive information within the preview will be obscured with star symbols.

### Improvements and Bug Fixes

* FT-1784: Enhanced Readability of Profile-Type Fields in Reports and Templates: The display of information from Profile-type fields has been improved in both Superbill and Invoice reports. This enhancement ensures that the data is now presented in a more readable and structured format. The same improvement has also been applied to message templates where the Context Type is set to "Encounter".
* FT-1850: Improved API Response for “Get Available Schedules”: A fix has been made to the “Get Available Schedules” API request to ensure accurate data retrieval. With this update, the API now returns information for all participants associated with the event, providing a complete and reliable schedule view.
* FT-1855: Corrected Event Order in Month View: An issue has been resolved in the Month View of the Calendar, where day events were displayed based on their creation order rather than their scheduled start time. The events will now be ordered by their start time ensuring a more intuitive and accurate chronological display.
* FT-1862: Updated Behavior for Numeric Fields: The system behavior for fields with numeric types has been updated. These fields will now remain empty by default, unless a specific default value is configured in the Designer Portal.

## Version 2025.61.0

**Release Date:** Apr 25, 2025 – 1:00 AM PST

### New Functionality

* FT-1003: Automation to Update and Create CDT records. In this release, we’re excited to introduce a new type of automation — the creation and updating of CDTs. This functionality currently supports a limited set of CDT categories, including Data Types and Custom Field Types, with field types such as Float, Integer, Text, TextArea, Boolean, and List. A few important details: for a single record CDT, only updating is supported, and for Multiple record CDTs, only creation is available. We look forward to your feedback on this new functionality, as well as your suggestions for future enhancements!
* FT-1801: “Pre-authorize Payment” automation. We’ve introduced a new automation — Pre-authorize Payment, which allows to define the settings that determine for which encounters a payment will be pre-authorized. This automation supports two event types: “Encounter Created” and “Encounter Disposition Updated”. Please note, if this automation is not configured, pre-authorization will not be triggered automatically.
* FT-1696: Default secure email settings. A new Secure Email setting has been added to the Admin Portal under the Integrations, Communication section. This allows system administrators to define the default state (enabled or disabled) of the Secure toggle for all outgoing emails at the environment level. It’s important to note that while this sets the default, Care Portal users can still manually change the Secure toggle when composing individual messages.
* FT-1812: Support for Task Entity in Widgets on the New Homepage (Beta). The Task entity is now available as a Core Entity in the widget creation dropdown on the New Homepage. This enables users to build widgets based on their tasks and associated attributes.

### Improvements and Bug Fixes

* CT-1147: Google Calendar Synchronization. We’ve enhanced the behavior when enabling Google Calendar synchronization. Now, upon activation, the system will automatically synchronize calendar events from 30 days before the current date and up to 365 days into the future. This synchronization occurs immediately at the moment the feature is enabled.
* FT-1779: Welkin encounter updates do not sync to Google Calendar. We’ve resolved an issue affecting calendar synchronization when two users work on the same event. Now, changes made by multiple users are correctly synchronized.
* FT-1832: Call misrouted despite recognized number. We’ve fixed an issue where, in some cases, calls from known clients were incorrectly routed to the Unrecognized communications.
* FT-1289: Call recording stability. We’ve improved overall system performance to help prevent the potential loss of call recordings, ensuring more reliable data capture and call history integrity.
* FT-1485: Assessment order in PFA. Resolved an issue where the order of assessments in the PFA did not match the sequence set in Designer.
* FT-1747: Calendar navigation in month view. We’ve fixed an issue that prevented users from navigating to the next month when the Month View was selected in the calendar.
* FT-1778: Document info display in the Communication Center. Resolved an issue where incorrect information about attached documents was shown in the Communication Center.
* FT-1841: MRN Formatting on Homepage (Beta). Fixed an issue where the Medical Record Number (MRN) was displayed in an incorrect format on the Homepage.

## Version 2025.60.0

**Release Date:** Apr 4, 2025 – 1:00 AM PST

### New Functionality

* FT-1553: The New Homepage (Beta). The New Homepage elevates daily workflows by serving as a personalized command center that turns patient data into actionable insights. It features configurable Widgets grouped into role-based Dashboards, enabling each user to focus on what matters most. Powered by the analytics engine, the Homepage supports flexible, real-time querying to keep information current and relevant. Note: An expression builder is available in Designer to help business users construct custom queries. Users should be familiar with Welkin entities, their relationships, and XOR logic to build effective queries. Customers are responsible for building, testing, and maintaining their own Widgets. Support is available through Welkin Professional Services (PSE) if needed. As this feature is currently in Beta, please contact your Customer Success representative or Account Manager to enable it.
* FT-1439: Link to Documents. A “Copy Link” button has been added to the document drawer, making it easier to reference documents in tasks or messages. Copied links include the document ID for sharing or bookmarking. If a user follows a link while not logged in, they will be redirected to the correct document after login.

### Improvements and Bug Fixes

Additional items which have been released for customers due to specified improvements or bug fixes

* FT-1735: Email Drafts Scheduled via API. Scheduled email drafts created via the API will now be sent as expected. The system automatically uses the patient’s point of contact as the sender if not manually specified. If the sender is missing and no contact point exists, an error is returned through the API and in the Automations log. Additional metadata fields (created\_by, updated\_by, etc.) are now recorded for better logging and traceability.
* CT-1145: Enhanced Webhook Payload with Initial Trigger Event Context. Webhook payloads now include additional fields to provide context about the initial event that triggered a sequence of events. This helps track the origin of chained events more effectively. New fields added: initiatedBy (ID) initiatedByName initiatedByObjectId initiatedByObjectType initiatedTime These fields capture details from the original triggering event in the initiatedBy object.
* FT-1743: Patient Deletion No Longer Fails with CDT Pre-Populated Values. Resolved an issue where attempting to delete a patient caused an “Unknown error” if a CDT text field value was used as a pre-populated value in an assessment. The deletion process now correctly handles these references, ensuring the patient record can be removed without error.
* FT-578: “Assessment Field is Required” Error When Using Saved Addresses. Resolved an issue where using a browser-saved full address to auto-fill assessment fields caused a false “Assessment field is required” error during submission. The form now correctly recognizes auto-filled values across multiple fields, eliminating the need for incognito mode or manual re-entry.
* FT-1152: Rich Text Formatting Now Preserved in Email Drafts. Fixed an issue where HTML-formatted email templates appeared distorted or difficult to edit when loaded into the message draft sidebar. The draft view now accurately reflects the original template formatting, so users can confidently review and edit content before sending.
* FT-1717: Environment Access Scope Now Respected in Data Audit API. The Data Audit API now correctly enforces environment restrictions set on API clients. Clients will only receive audit records for environments they are explicitly granted access to.
* FT-1719: Multiple Prescription IDs for Same Medication ID. Welkin now lists multiple Prescription IDs separated by commas when more than one Prescription ID is received for the same Rcopia Medication ID. Previously, only the latest Prescription ID was shown.

## Version 2025.59.0

**Release Date:** Feb 27, 2025 – 1:00 AM PST

### New Functionality

* FT-1206: Pre-authorize payments. Pre-authorization allows funds to be held on a patient’s account prior to an Encounter, ensuring sufficient coverage for the expected costs. The pre-authorized amount is determined by the billing type and services added to the Encounter before the process is triggered.
* An automation can be configured to handle specific actions upon the completion or cancellation of an Encounter - either charging the blocked funds or releasing them based on predefined settings. This ensures seamless financial workflows tailored to each Encounter’s outcome. More details found in Knowledge Base Content (<https://welkinhealth.com/kb/pre-authorization/>)
* Users also have advanced options at the Encounter level to manage pre-authorizations manually. This includes adjusting the pre-authorized amount, rescheduling or retrying a failed pre-authorization, canceling it, and either releasing or charging the held funds as needed. This combined approach provides flexible, seamless financial workflows tailored to each Encounter’s outcome.
* FT-1191: Encounter: Amount Due. We have replaced the “Outstanding Balance” value for Encounters with a new Amount Due value, precisely reflecting what the patient currently owes for that specific Encounter. This value factors in all prior payments, adjustments, and charges.
* FT-1193: Encounter: Billing Statuses and Grid changes. We have updated the Encounter grid (on the Encounters page) to help billing managers easily view and manage essential billing details in one place. New Encounter Billing Statuses were introduced to accurately reflect the patient’s current payment situation. These enhancements provide a comprehensive view of each Encounter’s billing information, streamlining the workflow for billing managers and enabling more effective payment tracking and management.
* FT-1195: Encounter: Renaming “Encounter Balance” to “Patient Payments”. We have renamed the “Encounter Balance” field to “Patient Payments” to provide a clearer view of how much the patient has already paid toward the Encounter. The old Encounter Balance value has been deprecated, and all payment amounts made by the patient are now reflected under this updated Patient Payments value. This change ensures billing managers can quickly assess the patient’s contributions and track remaining financial responsibilities.
* FT-1316: Expanded Payment Method Support for Subscriptions. We have introduced additional payment methods - Google Pay, Apple Pay, Link by Stripe, and Cash App - for subscription services in Welkin. When a Stripe payment link is sent to a patient, they choose their preferred method, pay, and are automatically charged according to the billing schedule. Once a payment method is used, it appears as the “Current Payment Method,” and any invoices generated for the subscription are tied to that method.

### Improvements and Bug Fixes

Additional items which have been released for customers due to specified improvements or bug fixes

* FT-1669: Changed the logic of selecting NPI for the Rendering Provider. When creating claims in Candid, the user's NPI from user attributes will always be taken as the NPI for the Rendering Provider, regardless of the Billing Type (responsible party).
* FT-1594: Automation Audit Export API. We have introduced a new security policy in the Designer under Data Export → Automation Audit, allowing you to export and monitor automation audits. A status filter (failure, success, conditions\_check\_failed) has been added exclusively to this new export endpoint, providing enhanced monitoring and alerting capabilities for automated workflows, including those that fail.
* FT-1595: API Access - Invoices endpoints. The invoice API endpoints are now open, allowing read-only access to invoice data. For reference, visit the Postman Collection of Open Endpoints <https://www.postman.com/welikan/public-welkinhealth-api/folder/9413ql0/invoices>
* FT-1662: Open API for downloading recognized calls. Requests to view call information, as well as to download a recording of a recognized call are now open to the API client. To work with these requests, the client must have the “Voice Calls None Care Team” policy. For reference, visit the Postman Collection of Open Endpoints <https://www.postman.com/welikan/public-welkinhealth-api/folder/dkc1vgh/calls>
* FT-1695: Open API for downloading email and sms attachments. Added ability to retrieve email and sms attachments via API. For reference, visit the Postman Collection of Open Endpoints for [emails](https://www.postman.com/welikan/public-welkinhealth-api/request/r87050q/download-email-attachment) and [sms](https://www.postman.com/welikan/public-welkinhealth-api/request/fwi9pbv/download-sms-attachment).
* FT-1254: Data Audit: Subscriptions. New functionality has been added to log actions performed on subscriptions. Events categorized as "Subscription" will now appear in the Data Audit log. Actions such as creation, update, cancellation, etc. will be recorded for enhanced traceability.
* FT-1194: Enhanced Transaction View for Payment History in Invoices. We have improved the payment history to provide a concise, expandable view of all transactions related to each payment. These grouped transactions - covering refunds, pre-authorizations, and cancellation fees - show their respective amounts, timestamps, and statuses in one place.
* FT-1491 - Preview in Documents Center Increased to 100 Documents. Removed the system limitation on the number of documents displayed in the pop-up when sending files.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.welkinhealth.com/release-notes/changelog-2025.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
