Important Dates

Last updated: 26 Sep 2025

Stay up to date on the latest important dates for the Canvas platform.

</tr> </tbody> </table>

Description	Type	What You Need To Know	Release Date	End of Life
FHIR API: Task note field append/replace behavior phase 1	Breaking Change	The FHIR Task update endpoint currently operates in a non-RESTful manner with respect to task notes (i.e. task comments in Canvas nomenclature). A FHIR Task update request will append all notes in the request body to the resource, rather than replacing all notes in the resource with the notes in the request body. To make the endpoint behave in a RESTful manner, we will be changing the behavior of this endpoint in multiple phases to allow for a gradual migration. To facilitate this change, the Task update endpoint now recognizes a Prefer header that will accept one of two values: note-append or note-replace. The current default value, if this header is not provided, is Prefer: note-append. On the release date, the default behavior will change from Prefer: note-append to Prefer: note-replace. Users are advised to update their client code to send Prefer: note-replace before the release date. Sending Prefer: note-replace will also require updating client code to send all notes for a Task in a update request body, rather than just new notes. Without this update to client code, there is a risk of deletion of Task notes during update requests. If you wish to temporarily retain the old default behavior to allow more time to update client code, you can send Prefer: note-append, but please note that this behavior is deprecated, and support for it will be removed in the near future.	09/16/25
FHIR API: Task note field append/replace behavior phase 2	Breaking Change	On the release date, the FHIR Task update endpoint will no longer support the Prefer: note-append header.	09/30/25
UI & FHIR API: Patient Contact Relationship	Breaking Change	On the release date, the following will be updated: Prefer: note-append header. UI: Relationship field is being removed from contacts section of patient profile page Data migration: Data in Relationship field will be migrated to / appended to the Comments field FHIR Patient Support will be discontinued for free text contact[].relationship[].text field; Relationship will now be represented by expanded use of contact categories Support will be discontinued for emergency contact and authorized for release of information extensions	09/30/25
FHIR API: Coverage member identifier moving from subscriberId attribute to identifier attribute	Breaking Change	On the release date, several corrections will be made to the FHIR Coverage resource. The meaning of the subscriberId attribute in the resource is changing, resulting in the following updates: Insurance member ID will no longer be provided in the subscriberId attribute. The member ID will now be presented in the identifier attribute instead, and the subscriberId attribute will now represent the identifier for the subscriber, not the member. This will apply for create, read, update, and search endpoints. The subscriberid will represent a new optional field within Canvas The subscriberid search parameter will no longer search member IDs; it will now instead search subscriber IDs. The new identifier search parameter will now search member IDs. </ul> To facilitate this change, the following changes have already been made to FHIR Coverage resource and endpoints: The insurance member ID is being populated into and consumed from the identifier attribute. Member IDs can be searched using the new identifier search parameter. Examples and documentation for the identifier field are available in the FHIR Coverage API documentation. API client code must be updated by the release date to avoid disruption. </td>	10/14/25
Workflow SDK	New Version	The Workflow SDK has been deprecated, and will only receive fixes for defects or security issues. We are replacing its functionality with the Canvas SDK and its plugins, and will not set a date for the removal of the Workflow SDK until the Canvas SDK reaches feature parity. At that time we will present a migration plan to convert Workflow SDK Protocols into Canvas Plugins.		TBD (Not Soon)
FHIR API: Setting appointment location using the location integer value	Breaking Change	The FHIR Appointment endpoint now uses the reference from the Location Read/Search endpoint for the Location in supportingInformation. We plan to discontinue support of using the location integer.	TBD