Important Dates
Stay up to date on the latest important dates for the Canvas platform.
| Description | Type | What You Need To Know | Release Date | End of Life |
|---|---|---|---|---|
| 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 | |
| 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. | TBD | |
| 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. | TBD | |
| FHIR API: Patient deceasedBoolean field | Breaking Change | USCDIv3 requirements dictate that FHIR APIs support the deceasedDateTime field of the Patient resource.Starting on the release date of this change, Canvas by default will provide the deceasedDateTime value for any given patient, if it is available. If it is not, the API will continue providing the deceasedBoolean value. Please note that the FHIR standard only allows one, not both, of these values to be returned.Client code will need to be adjusted to consume either value. | 08/22/2025 |