Important Dates

Last updated: 19 Dec 2025

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
FHIR API: QuestionnaireResponse questionnaire attribute changing from reference string to absolute URL	Breaking Change	On the release date, Canvas will change the way the QuestionnaireResponse `questionnaire` attribute is presented. We are making this change to meet USCDI v3 requirements. The `questionnaire` attribute is currently presented as a reference string, e.g. `Questionnaire/b357ddc9-c6fc-4a99-a79b-1d0b933afd7a`. USCDI v3 requires that this attribute be presented as a full URL, e.g. `https://fumage-.canvasmedical.com/Questionnaire/b357ddc9-c6fc-4a99-a79b-1d0b933afd7a` This will affect all QuestionnaireResponse endpoints. What you need to do to avoid disruption: The create and update endpoints currently accept either a reference string or an absolute URL for the `questionnaire` attribute. Client code needs to be adjusted to start sending the absolute URL of the Questionnaire for this attribute in request bodies. Use the example above as a reference, and be sure to replace the customer ID in the example so that the base URL matches what you normally use for FHIR requests. Read and search endpoints will start returning the absolute URL for this attribute on the release date. Client code needs to be adjusted so that it can accept and handle either a reference string or an absolute URL for this attribute in response bodies. Making these two changes before the release date will ensure that your use of the QuestionnaireResponse endpoints will be unaffected by this change.	02/02/26
FHIR API: Condition category handling	Breaking Change	On the release date, Canvas will handle the `category` attribute on the FHIR Condition resource differently in order to meet USCDI v3 requirements. Currently, the `category` attribute for all Conditions is required to be `encounter-diagnosis`. On the release date, the following changes will take effect: The Condition create and update endpoints will accept `encounter-diagnosis`, `problem-list-item`, or `health-concern` for the `code` attribute of the category coding. The Condition read and search-type endpoints will return `encounter-diagnosis`, `problem-list-item`, or `health-concern` for the `code` attribute of the category coding, based on what is stored in the database for the Condition. Conditions created by the Diagnose command will have `category` set to `problem-list-item`. The Diagnose command will be enhanced in the future to enable use of the other value options for `category`. The `category` for all existing Conditions in the database will be set to `problem-list-item`. What you need to do: All client code that makes use of the Condition create or update endpoints must be updated before the release date so that `problem-list-item` is sent instead of `encounter-diagnosis`. Please note that until we make the breaking change, even if you send `problem-list-item`, we will continue returning you `encounter-diagnosis` from read and search endpoints until we make the breaking change. All client code that makes use of the read or search endpoints must be updated if they reference the `category` attribute to flexibly handle either `encounter-diagnosis` or `problem-list-item`. Making these two changes before the release date will ensure that your use of the endpoint will be unaffected by this change.	12/08/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