bugfix

• Fixed several command-related issues:
  • Commands added to a note from a chart button could occasionally disappear from the note body.
  • Deleting a command no longer leaves the note out of date until refresh.
  • When post-processing events after a command was committed or marked enter-in-error failed, the command appeared committed/EIE in the UI but related records could end up out of sync. The status change is now rolled back if any post-processing records fails.
  • Commands could move to “in review” even when required fields were missing or invalid; the move is now blocked until the validation errors are resolved.
  • Prescribers who already had an SPI number on file were still being prompted to add one before reviewing an adjust-prescription command.
  • Questionnaire comments can be opened on locked or signed notes for multiple-choice fields that accept comments.
  • Goals could not be updated when the start date field had been cleared.
• The schedule view was not honoring the configured order of providers; providers now appear in their assigned schedule-column order.
• Fixed crashes in the Day and Week views in the schedule that could occur when an appointment was created, edited, or canceled in real time — most commonly right after switching dates or location filters.
• The Letter author dropdown now searches the full staff directory as you type, so customers with more than 350 active staff members can find and select any provider (previously the dropdown showed only the first set of providers).
• CCDA exports for patients without an assigned team lead now return a clear error explaining the missing team lead, instead of a generic server error, so integrations know to correct the patient record rather than retry the export.
• Resolved a source of app-wide slowness during Health Gorilla lab report ingestion that was tying up the database while Canvas waits on it.
• Fixed a bug related to Timed out after 60s waiting for namespace '<namespace>' to be created by the schema manager errors during plugin install, which would leave the plugin disabled and require a manual re-enable to recover.

ui

• Redesigned the diagnostic imaging requisition: provider name, license, and NPI now appear in a dedicated Ordering Provider block at the top; a medical-necessity certification, an electronically-signed attestation with a timezone-stamped date, and an order-validity statement now appear at the bottom.

sdk

Data

• Added a LabTest relationship to LabValue in the SDK data module, enabling plugins to associate lab values with their corresponding tests. See the LabTest reference and Ordered vs. result tests.
• Staff member signatures are now accessible via the SDK data module. Read more.

Events

• Plugins can now respond to a new SDK event, PATIENT_PAYMENT_PROCESSED, triggered when a patient payment is processed. Read more.

Config

• Plugins can now read the instance’s configured time zone via self.environment["INSTALLATION_TIME_ZONE"] (an IANA name like America/Los_Angeles), enabling accurate local-time rendering in plugin output. Read more.
• Added a --disable flag to canvas install so plugins can be installed in a disabled state via the CLI (defaults to enabled). (requires Canvas CLI 0.143.0 or newer) Read more.
• New variables schema for plugin configuration declared in CANVAS_MANIFEST.json. (requires Canvas CLI 0.147.0 or newer)
  • Manifest schema: CANVAS_MANIFEST.json now accepts a variables array of {name, sensitive} objects in place of the flat secrets string array, distinguishing sensitive secrets (such as API tokens) from non-sensitive configuration values (such as log levels or feature flags). The legacy secrets field still works but emits a deprecation warning during canvas validate-manifest, and is internally mapped to variables entries with sensitive: false. Read more.
  • CLI: A canvas install --variable KEY=value flag is available alongside --secret for non-sensitive values. canvas config list now renders each variable as [set] or [not set], with a (sensitive) annotation for sensitive variables — values themselves are never displayed. Read more.
  • Settings UI: Sensitive variables display as SENSITIVE in Settings — leave the field blank to keep the existing value, or submit a new value to overwrite. Non-sensitive variables remain editable inline with their current value visible.
  • Plugin runtime: Handler code reading values via self.secrets["KEY"] is unchanged — sensitive and non-sensitive values land in the same dictionary. Migrating a plugin from secrets: to variables: requires no handler code changes.
  • ⚠️ Migration caveat: Existing plugin secrets and any values configured via the legacy secrets: array default to non-sensitive in this release — they will appear in plain text in the Admin UI until the owning plugin is migrated to the variables schema with sensitive: true and re-installed.

bugfix

• Fixed an issue where SDK commands (prescribe, refill, adjust prescription) could be moved to “in review” even when schema validation errors were present.
• Fixed a bug preventing CCDA documents from being ingested when a section uses an OID that differs from what Canvas considers standard for that section.
• Fixed printing of plugin-defined additional fields on command printouts so that all configured fields now appear correctly in the printed output.

sdk

• The ClaimQueue SDK data model now exposes the id field, enabling plugins to look up claim queues using the queue IDs provided in CLAIM_QUEUE_MOVED event context.
• Plugins can now make outbound HTTP requests using the new HTTPRequest effect, with support for both synchronous and asynchronous execution. Read more.
• The event DOCUMENT_REVIEWED now kicks off when the Referral and Uncategorized Document review commands are committed, enabling workflows that respond to these document types. Read more.

• Questionnaire commands can now be originated with pre-filled responses — when creating a questionnaire command via a plugin, responses set before calling .originate() are applied immediately on creation, removing the need for a separate .edit() call. Read more.
• Fixed note headers not sticking to the top of the page when scrolling on the patient chart.

sdk

• Plugins can now use delay/async functionality with SDK effects, enabling deferred or asynchronous execution of effect handlers. Read more.
• Plugins can now define and attach custom fields to commands/sdk/commands/, allowing practices to capture additional structured data beyond the built-in command fields. Read more.

• Fixed a bug that showed irrelevant refill requests when a staff member is not on any team but the “Me or My Teams” filter is selected.
• Fixed the After Visit Summary not showing the Diagnosed section when it was the only content under Today’s Visit.

api

• Added user-level and system-level scopes for FHIR Questionnaire and QuestionnaireResponse as options when creating credentials.

sdk

• Added LabPartnerTestQuestion and LabPartnerTestQuestionChoice to the SDK data module for querying ask-at-order-entry (AOE) questions and choices on lab tests. Read more.
• A mobile-friendly Canvas interface is now available at https://<instance-name>.canvasmedical.com/companion/. This is a space for mobile-optimized plugins to be launched from. Companion applications can be scoped to a note, a patient, or global. See Provider Companion for more details.

• Fixed a race condition where concurrent updates to the same command could silently overwrite each other, potentially causing data loss during rapid edits.

sdk

• Plugins can now add custom sections to the patient chart summary, enabling practices to surface domain-specific data alongside the built-in clinical sections. Read more.

ui

• [Gradual roll out] Improved the patient chart timeline to enforce that only one note can be open at a time, preventing conflicting edits across multiple open notes.
• Improved page load performance for practices with large staff rosters. Pages that previously slowed down with hundreds of staff members now load significantly faster.

bugfix

• Fixed a bug where FHIR Encounter resources did not have Provenance records created for them.
• Fixed Structured Assessment commands using expired ICD-10 descriptions when creating billing line item diagnoses. The lookup now filters by the note’s date of service, ensuring the current ICD-10-CM text is used.

sdk

• Added a commit parameter to the originate() command method, allowing plugins to originate and commit a command in a single effect without manually managing UUIDs.
• Added a new CLAIM_QUEUE_MOVED SDK event, which emits when a claim moves to a queue. Read more.
• Added the rendering provider address fields (addr1, addr2, city, state, zip) to the ClaimProvider data model and the claim effect payload.
• The patient chart header now has room to render more action buttons at once, so plugins using the CHART_PATIENT_HEADER button location will display reliably even when many are registered.
• The upsert_metadata method on commands can now be chained with originate() in the same handler response, allowing metadata to be attached to commands at creation time. Read more.
• Granted the reporting database user read access to custom data tables, enabling reporting queries against custom data via read replicas.
• Expanded the plugin sandbox allow list with many additions across django.db.models, several standard library modules, and new modules including html, traceback, django.db.transaction, django.db.models.functions, and django.contrib.postgres.indexes. A new extract_exc_frames() builtin is also available for safely extracting frame info from exception tracebacks.
• We are deprecating the requests module in the plugin sandbox. Plugins should use the Canvas SDK’s Http helper instead.

api

• FHIR Questionnaire read and search endpoints now support nested item objects under the item attribute.
• FHIR QuestionnaireResponse read and search endpoints now support nested item objects under both the item and answer attributes, population of the identifier attribute and questionnaireDisplay extension, a url extension for responses to non-FHIR questionnaires, and valueDecimal answers.
• FHIR QuestionnaireResponse create and update endpoints now support creating resources that respond to non-FHIR questionnaires (i.e., a questionnaire at an external URL rather than a FHIR Questionnaire resource).

bugfix

• Improved the accuracy and resiliency of cron scheduling for plugins in the Canvas SDK. Cron tasks should now fire much closer to the minute boundary, and cases where tasks scheduled every minute could rarely fire twice or not at all have been addressed.
• Fixed an issue where original claims were incorrectly sent with a prior payer claim reference number, which could cause the clearinghouse to misinterpret them as resubmissions.
• Fixed an issue where the DEA schedule label for a medication would disappear from the UI once a pharmacy was selected if the DrFirst lookup was unavailable. The system now falls back to the FDB national schedule when the state-specific lookup cannot be completed.
• Fixed a race condition where saving data on a patient chart (e.g., committing a command or updating vitals) could briefly show stale values or fail to refresh until the page was manually reloaded.
• Fixed an issue where enabling or disabling plugins with multiple registered commands via the Canvas CLI would fail. Re-enabling a plugin via CLI also now correctly restores its command availability.
• The patient search results dropdown was not scrollable, making it difficult to navigate when there were many results (for a common last name, for example). This has been addressed by making the results scrollable.

bugfix

• Fixed duplicate ServiceProvider records being created every time a Refer, Imaging Order, External Care Team Member, or Inbound Fax was saved. ServiceProviders are now deduplicated by science contact ID (when available) or by name, specialty, and address.
• Fixed ServiceProviders selected via Refer, Imaging Order, or inbound fax not appearing in FHIR /Organization search results. All ServiceProviders now have an associated OrganizationalEntity.
• Fixed issue where external care team members were not searchable by name in FHIR Organization.
• Expands the length of the QuestionnaireResult.code field to 100 characters.

api

• FHIR Organization search now supports the type parameter, mapping to the http://hl7.org/fhir/organization-type value set: prov (Healthcare Provider) for ServiceProviders and Business Entities, pay (Payer) for Transactors, and other (Other) for Vendors.

sdk

• Adds an optional description field to ClinicalQuantity to allow narrowing the type to dispense when multiple clinical quantity options are available for the same NDC and qualifier code.

bugfix

• Added the FAX_EVENT_HISTORY item to the PatientNoteHeaderDropdownConfiguration effect, allowing plugins to include fax event history in the note header dropdown menu.

sdk

• The ImagingOrderCommand and ReferCommand now support delegate() and sign() methods, enabling plugins to programmatically delegate and sign these commands as part of automated workflows.

bugfix

• The practice location “full name” field is now sent in the PracticeLocation.BusinessName field for electronic prescriptions.
• Fixed an issue where fax submission failed with an error when the cover sheet subject, comments, or recipient name contained special characters such as #, &, =, or non-ASCII characters. These fields now properly handle all characters.
• The Axes “AccessLog” settings view could fail to load due to the volume of records it contained. This has been fixed.

sdk

• A new PatientNoteHeaderDropdownConfiguration effect allows plugins to configure which items appear in the note header dropdown menu.

bugfix

• Ensures “Interaction checks cannot be performed for free text compound medications” now displays when initiating a Refill or Adjust Prescription for a compound medication from the chart medication list.

sdk

• Adds 6 new SDK events for the Data Integration document lifecycle: DOCUMENT_RECEIVED, DOCUMENT_LINKED_TO_PATIENT, DOCUMENT_CATEGORIZED, DOCUMENT_REVIEWER_ASSIGNED, DOCUMENT_REVIEWED, and DOCUMENT_DELETED. Plugins can now react to documents arriving, being linked to patients, categorized, assigned to reviewers, being reviewed, or deleted.
• Adds a new CanvasFhir client for interacting with the Canvas FHIR API from within plugins. Supports create, read, update, and search operations with automatic credential management and caching. Requires client_id and client_secret to be configured in plugin secrets.

sdk

• Adds a new NOTE_HEADER_DROPDOWN action button placement, allowing plugins to add custom entries to the note header triple-dot menu.
• Adds ClaimLineItemModifier to the SDK data module, enabling read access to modifiers added to claim line items in revenue. Accessible via claim_line_item.modifiers.all() on a ClaimLineItem.
• Adds actor to NOTE_STATE_CHANGE_EVENT_PRE_CREATE events, allowing plugins to identify which user initiated a note state change (e.g., lock, push charges) and conditionally block it based on role.
• Action buttons with the CHART_PATIENT_HEADER location now appear on both the chart and profile pages. The PROFILE_PATIENT_HEADER location has been removed — plugins using it should switch to CHART_PATIENT_HEADER.
• The Canvas CLI now notifies you when a newer version is available on PyPI. This can be disabled with CANVAS_NO_UPDATE_CHECK=1.

ui

• The note header triple-dot menu now includes plugin-provided action buttons below the existing options.
• Fixed the note header triple-dot menu being cut off on small screens, making some options inaccessible.

bugfix

• Fixed an error when attaching documents with long labels (over 500 characters) to a Letter. Document labels that include comments are now truncated to fit the database field limit.
• Fixed an error in real-time command update notifications that occurred when a task linked to a command was closed or completed. This prevented the UI from receiving the update and could require a page refresh to see the latest command state.
• Fixed a GraphQL resolver error ('Command' object is not subscriptable) that could cause UI errors during command operations.
• Fixed an error where note subscription updates could fail for certain note types, requiring a page refresh to see the latest state.
• Fixed an error where custom command lifecycle events (origination, commit) could fail with a LookupError for standalone command schema keys.

sdk

• Adds plugin integration to validate appointment scheduling. Plugins responding to the APPOINTMENT__FORM__UPDATED event can return an EventValidationError effect to disable the Book button and display validation errors as a tooltip.
• Standardizes key and value attributes for all metadata models (ClaimMetadata, AppointmentMetadata, TaskMetadata, PatientMetadata, NoteMetadata, CommandMetadata), including an increase in allowed key length to 256 characters.
• Adds the ability for the Canvas SDK to convert from Coverage to Snapshot and vice-versa.

ui

• Adds the option to mark a document in review as Unassigned in both the document review panel and patient chart documents.
• Prevents sending Lab Order to Health Gorilla unless your patient has a phone number configured.
• Several setting pages (Patient, Role Group, Task, Transactor) could cause excessive memory consumption under heavy use. These pages now load related records on demand via search, resulting in more stable memory usage.

sdk

• Today Canvas Medical is releasing the Custom Data SDK feature. Plugins now have two techniques available to store information within the Canvas EMR durably and securely with minimal setup.

  1. Fully normalized relational database schemas via CustomModels, with or without integration to core SDK models.
  2. Zero configuration key/value and document storage via AttributeHubs

  To start experimenting, see the Quick Start guide, and update the canvas CLI tool for latest functionality.

• Various Note Application improvements: Read more.
  • Adds support for Note Applications to open automatically when a note is viewed, via the new open_by_default() method. Read more.
  • The handle() method is now deprecated in favor of on_open(), which can return a single Effect or a list[Effect]. Existing plugins using handle() will continue to work.
  • Tabs now support a PRIORITY class attribute to control tab ordering — lower values appear first. Read more.
  • The context now includes a note key containing the note’s external UUID.
  • The “Note” tab can now be relabeled via the NOTE_BODY_TAB_LABEL Constance Config setting in the UI to avoid duplication when a charting application is also named “Note”.
  • Tabs have moved from the note body into the sticky note header, keeping them visible while scrolling through long notes.
• Expanded the plugin sandbox allowed imports to include re.findall, requests.Session, functools.wraps, typing.Callable, typing.ClassVar, typing.Pattern, and django.db.IntegrityError. Read more.

ui

• The assessed/diagnosed conditions summary that previously appeared in the note header has been removed.
• Fixed an issue where uploading fillable PDFs with invalid form field references caused a 500 error when previewing, printing, or faxing documents.

bugfix

• Fixed an issue where the Refer command would fail to commit when attached documents had labels exceeding 500 characters.
• For customers using Candid without Claim.MD, the payer list will now update on a weekly basis as expected.
• Fixed intermittent “Save Failed” errors during charting caused by a race condition between command commit and note autosave. When committing or entering-in-error commands that update the note, a checksum mismatch could cause 409 conflicts resulting in “Save Failed” errors. This also resolves the note body flash and scroll position jump that occurred during these actions.
• Fixed an issue where protocol recommendations without associated commands could cause the Protocols tab to crash instead of rendering correctly.
• Fixed a bug where the DiagnosticReport and Observations created from a Lab Report were missing LOINC codes.
• C-CDA files sent via direct messaging (DataMotion integration) that contain non-ASCII characters are now handled correctly.
• Fixed an error that could prevent EPCS signing for refill prescriptions.
• Concurrent write requests to the CareTeam FHIR endpoint could result in a 500 error. This has been resolved.

sdk

• Adds note foreign key to the LabReview, ReferralReview, and ImagingReview SDK data models, allowing plugins to access the note associated with a review. This also allows plugins to navigate from a Note to its associated review commands.
• Adds a new ButtonLocation option for plugin action buttons: CHART_PATIENT_HEADER, allowing plugins to display action buttons on the patient header. Read more.
• Action buttons now support custom styling via BUTTON_TEXT_COLOR and BUTTON_BACKGROUND_COLOR class constants. Read more.
• Adds SDK support for patient groups, enabling plugins to manage group membership programmatically:
  • New PatientGroup and PatientGroupMember data models for querying groups and their members. Read more.
  • New PatientGroupEffect with add_member() and deactivate_member() methods for managing group membership.
  • New events: PATIENT_GROUP_CREATED, PATIENT_GROUP_UPDATED, PATIENT_GROUP_MEMBERSHIP_CREATED, PATIENT_GROUP_MEMBERSHIP_UPDATED, and PATIENT_GROUP_MEMBERSHIP_DELETED.
  • Patient groups are also accessible from a Patient object via patient.patient_groups.

config

• Instances no longer require Google Calendar to be configured in order to function without errors. Previously users would see an error "Provider availability calendars have not yet been configured. When you’re ready to connect them, contact Support and we’ll help get you squared away.", forcing them to connect to google calendar.

ui

• Print templates now use a serif font instead of monospace for a more polished appearance.
• Failed prescriptions now show more detail regarding the reason for failure. Additionally, non-ASCII characters in patient addresses are now transliterated to the nearest ASCII equivalent, preventing a class of Surescripts transmission errors.

sdk

• Adds new CommandMetadata model to the SDK Data models. Read more
• Adds new COMMAND_METADATA_CREATED and COMMAND_METADATA_UPDATED events. Read more
• Adds new UPSERT_COMMAND_METADATA effect used to create or update metadata values in a command. Read more
• Recently we added some new Document-related models to the Canvas SDK. The pre-signed keys generated for the files related to those objects were incorrect; this has now been addressed.
• Adds new pharmacy search parameters in search_pharmacies Read more :
  • specialty — Filter by pharmacy specialty type
  • zip_code_prefix — Filter by zip code
  • state — Filter by state code
  • ncpdp_id — Look up a specific pharmacy by its NCPDP identifier

ui

• Removed note header colored bar

api

• Allow updating CareTeams with external members via FHIR. Read more

sdk

• File upload related models have been added to the Canvas SDK: DocumentReference, Snapshot/SnapshotImage, PatientIdentificationCard, and MessageAttachment.file_url
• Fixed an issue where the note body could display stale content after another user committed changes.
• Fixed an issue where note application tabs where not returning to the note view on close.
• For plugins that handle events where an actor is set — such as action button clicks, application context changes, patient portal interactions, etc — command module methods (originate, commit, edit, delete, review, send, enter-in-error) are now attributed to that user instead of the system bot. Events without an actor continue to be attributed to the system bot.
• Adds the CREATE_CCDA_EXPORT effect that allows creation of CCDA documents for patients. Read more

config

• Staff images, background images, and logos can now be uploaded directly in Settings.

bugfix

• Fixes bug where it was not defaulting the practice location when scheduling an appointment from the patient’s chart to be the current logged-in user’s primary practice location.
• A rare condition could arise when an Adjust Medication command existed in an error state without an associated medication and resulted in our medication state synchronization inferring the incorrect state for a medication. This would manifest as a medication showing as inactive when it should have shown as active. Affected customers have been informed directly.
• Inbound faxes will try to find an existing service provider contact before creating a new contact to prevent duplicate entries.
• We’ve addressed several performance issues in the Canvas admin pages, specifically around the patient, lab order, condition, device, refill request, prescription change request, and prescription alert pages.
• Fixed bug that attempted to maintain references to specific coding gaps when coding gap related commands were used in automations.

sdk

• Adds a new PDF generator utility that enables plugins to generate PDFs either from a hosted HTML page or from raw HTML content. Read more
• Adds Python 3.13 support to the SDK.
• Adds a new claim effect for updating provider information on a claim. Read more

bugfix

• Questionnaires with long question names could become corrupted if used within the Questionnaire Builder. This corruption will no longer happen.
• The unsupported browser warning was hidden on Safari; it is now visible. Safari is not a supported browser for Canvas, you must use Chrome.

api

• Fixes Facility addresses not including country on FHIR’s Patient read/search

sdk

• Adds Prescription to the SDK data module. Read more
• Adds the following SDK events for Prescription status changes: PRESCRIPTION_OPENED, PRESCRIPTION_PENDING, PRESCRIPTION_ACCEPTED, PRESCRIPTION_ERRORED, PRESCRIPTION_CANCEL_REQUESTED, PRESCRIPTION_CANCELED, PRESCRIPTION_CANCEL_DENIED. PRESCRIPTION_RECEIVED, PRESCRIPTION_SIGNED, PRESCRIPTION_INQUEUE, PRESCRIPTION_TRANSMITTED, PRESCRIPTION_DELIVERED. Read more