Canvas Medical Release Notes

09.03.2026

2026-09-03T00:00:00-07:00

• Prescribers can now review and sign a prescription without an SPI (Surescripts Prescriber Identifier) number on file.

◦ SPI is only needed to transmit a prescription electronically through Surescripts, so it no longer blocks review and sign for prescribers who don’t transmit that way, such as direct-integration or compounding workflows.

◦ A prescription whose prescriber has no SPI still offers no send action. The same applies to Refill and Adjust Prescription.

◦ An NPI number is still required to sign, and controlled-substance prescribing is still gated by EPCS enrollment.

bugfix

• Fixed an issue in the appointment scheduling modal where free-text fields would grey out and lose the cursor mid-word while a scheduling plugin was installed, sometimes discarding characters. Reason for Visit, Comments, Event Title, and any text field a plugin adds now stay editable while the form refreshes.

sdk

• Plugins can now dock an application in a persistent pane on an edge of the screen: left, right, top, or bottom.

◦ The pane stays mounted as staff move around Canvas, so it keeps its state instead of being rebuilt on every page. on_context_change() hands it each new page’s context, and the pane reloads only if the plugin asks it to.

◦ A plugin decides who gets a pane. visible() is asked per staff member, so a dock can be scoped to a team or a role rather than appearing for everyone once the plugin is installed.

◦ Staff resize a pane by dragging its divider or with the arrow keys, and Canvas remembers the size each pane was left at. A plugin can resize its own pane too, collapse it to a thin rail, or remove it.

◦ Up to two panes can share an edge. Left and right panes together take at most half the window’s width, and top and bottom panes at most half its height.

• Plugins can now drive their own automations in a note, rather than clinicians having only the ones built into Canvas. A plugin adds an action button in the new NOTE_BODY_AUTOMATION location, and it appears in the note body’s / menu alongside the native commands, marked with a plug icon.

◦ It is an ordinary action button, so handle() can return any effects. What the location is meant for is a BatchOriginateCommandEffect with replace_line=True, which originates a set of commands onto the line the clinician typed the trigger on.

◦ visible() decides who sees an entry and where. Its context carries the signed-in staff member alongside the note and the patient, so an entry can be limited to particular staff as well as to particular notes or patients. PRIORITY orders it within the menu.

• Four more records are now readable through the SDK data module, covering the Surescripts change and cancel workflows:

◦ PrescriptionChangeResponse: the approve or deny recorded against a change request, with the response type, the status, and the response detail fields.

◦ PrescriptionChangeRequest: the pharmacy’s incoming change request, with its medication codings and the prescription it relates to.

◦ CancelPrescription: a request to cancel a patient’s prescription, with the prescription, the patient, the note, the message, and the status.

◦ CancelPrescriptionResponse: the response to a cancel request, linked one to one to the request that produced it.

• Fixed an issue where a self-pay coverage reported a stale Failed eligibility status to plugins. A self-pay coverage now reports NOT_APPLICABLE, and the stale response behind it is never surfaced.

• Fixed an issue where a field a plugin adds to the appointment scheduling modal with editable=False was still editable. The flag had never taken effect; it now makes the field read-only.

09.01.2026

2026-09-01T00:00:00-07:00

• Questionnaires now support a Date question type, alongside single select, multi select and free text.

◦ When building a questionnaire, choose Date for a question in the Questionnaire Builder, or set the question’s responses_type to DATE in the Google Sheets import.

◦ When filling one out in a note, the question renders as a date picker in the Questionnaire, Review of Systems, Structured Assessment and Physical Exam commands.

◦ The captured date carries through charting and carry-forward.

bugfix

• Fixed an issue in the Canvas Remote app where capturing insurance card images failed when adding a new coverage. The front and back capture steps now load for a coverage that has just been started.

• Discharging an inpatient note now records one discharge and one lock in the note’s state history, plus a signature for note types that require one. Previously the lock was written three times, so the state history showed duplicates and plugins subscribed to NOTE_STATE_CHANGE_EVENT_CREATED were notified of the same lock three times.

api

• The FHIR API now carries Date questions.

◦ A Questionnaire declares one as "type": "date".

◦ A QuestionnaireResponse answers it with a valueDate, an ISO 8601 calendar date, on both read and create.

sdk

• A questionnaire can declare a DATE question, and a plugin can answer one.

◦ Set responses_type: DATE on the question in the questionnaire’s YAML template, the one your plugin’s CANVAS_MANIFEST.json points at. See Questionnaires.

◦ Answer it from the Questionnaire command. An answers entry takes the date as an ISO 8601 YYYY-MM-DD string, while the question’s own add_response(date=...) also accepts a datetime.date.

• Five more records are now readable through the SDK data module, each of them the record behind a command:

◦ Plan: what the Plan command records, with its narrative.

◦ FollowUp: what the Follow Up command records, including the requested appointment date and type, the reason for the visit, and the comments to the patient and to staff.

◦ ReasonForVisit: what the Reason for Visit command records, with its narrative and codings, alongside the configured codings an instance offers.

◦ RemoveAllergyEvent: what the Remove Allergy command records, with the allergy removed, the patient, the note and the rationale.

◦ ResolveConditionEvent: what the Resolve Condition command records, with the condition resolved, the patient, the note and the rationale.

• Fixed an issue where calling find() with a value set on FamilyHistory or ImmunizationStatement records raised an error instead of returning results. These value-set lookups now work.

08.31.2026

2026-08-31T00:00:00-07:00

• Moving a batch of claims between queues — Batch actions → Move claims to queue on the Revenue worklist — has been reworked end to end. The action used to run behind a browser pop-up that showed no progress and reported no outcome, so a large or failed move looked the same as a successful one.

◦ Several performance improvements make the move itself considerably faster.

◦ A dialog replaces the browser pop-ups, and names how many claims match your current filters — every matching claim, not only the rows shown in the table. When nothing matches, it tells you there is nothing to move.

◦ A spinner runs while the claims are counted and again while they are moved, and the dialog can’t be dismissed part-way through a move.

◦ One run moves up to 2,000 claims by default, which an admin can change with the MAX_BATCH_CLAIM_QUEUE_MOVE setting in the config section below. When more than that match, the result says how many are left, so you can repeat the action to work through them.

◦ The outcome is reported when the move lands — including when it doesn’t finish — and the claim table refreshes as you close the dialog.

bugfix

• Fixed an issue where electronic remittances stopped posting automatically for insurers configured with two or more entries in their “Accept remittances from” list. The payment never posted and the claim was left commented “coverage with remit payer id not found in claim”, so staff only noticed when a balance looked wrong. Remittances for these insurers now post as expected.

• Imaging result codes are now normalized as results are ingested, so a code carrying stray or doubled spaces no longer makes FHIR Observation and DiagnosticReport reads and searches fail with a 500 error.

• Fixed an issue where the rendered report PDF that Health Gorilla delivers alongside a lab’s real results created an empty lab value and lab test on the patient’s chart. Only the exact name “PDF Report” was recognized as the attachment, so variants such as “Clinical PDF Report” or “Enhanced PDF Report” came through as results. The attachment is now recognized however it is named.

config

• Canvas can now keep a security audit trail of sign-ins, chart access, and clinical data changes, and stream it to your own SIEM. The trail is recorded in the OCSF standard, and its events carry opaque identifiers only — never patient or provider names, dates of birth, or clinical values. It can be read as a retained, read-only view inside Canvas, or exported to an HTTPS endpoint you nominate. Off by default; reach out to Canvas support to enable it for your instance and to set the retention period, the endpoint, and whether identifiers are sent directly or as a keyed hash. Read more.

• Admins can now set a new instance-wide Constance config setting, MAX_BATCH_CLAIM_QUEUE_MOVE, that caps how many claims one run of Batch actions → Move claims to queue will move. The cap is what keeps a very large move performant: instead of one action taking on an unbounded amount of work, a big queue is moved in batches. Defaults to 2,000; when more claims match your filters, the action reports how many remain and you run it again to move the next batch.

sdk

• Charting from your own application has always meant building the API yourself. Not anymore. CommandAPI turns any Canvas command into an HTTP endpoint in five lines — you declare the route and who may reach it, and Canvas handles reading the request, validating it against the command, and writing it to the chart. Writing Commands Over HTTP takes you from nothing to your first working endpoint.

• Eight more commands now carry additional validation on the record they point at: the id must name a record belonging to the same patient as the note_uuid you pass — or, when the command names no note, as the command_uuid you pass. A record on any other patient’s chart is refused, and the error names the id that failed:

◦ Lab Review, Imaging Review, Referral Review and Uncategorized Document Review — every id in report_ids must name a report that is still awaiting review and is on that patient’s chart. A single foreign report among otherwise valid ones rejects the whole command.

◦ Resolve Condition — condition_id.

◦ Stop Medication — medication_id.

◦ Remove Allergy — allergy_id.

◦ Update Goal — goal_id.

• The Remove Allergy command’s narrative now accepts up to 512 characters.

• Answering a questionnaire from a plugin no longer means fetching the questions and branching on each one’s type: pass an answers list and the command works out the rest. It works on the Questionnaire command and the three built on it — Review of Systems, Structured Assessment and Physical Exam. Read more.

08.27.2026

2026-08-27T00:00:00-07:00

bugfix

• Several improvements to the patient portal login workflow:

◦ Invite and password-reset links no longer show “Expired link” when the link is still good. A link stays usable for its full lifetime and is spent only when the password is actually set.

◦ When a different account is signed in on the same browser, an invite or reset link now names that as the reason and offers a one-click “Sign out and continue” that reopens the same link, rather than reporting the link as expired.

◦ Patients who open the portal at a URL without a trailing slash, such as /app, now reach the portal instead of a 403 Forbidden.

• Fixed an issue where signing in to the patient portal and then opening a page in Canvas gave a bare 403 error with nothing to act on — most often hit while testing the portal in a non-production environment. That page now explains that the portal session is in the way, and signs you out to the page you were headed for.

sdk

• Vital sign readings are now available in the SDK data module — the records behind the Vitals command. Plugins can read a patient’s readings along with each individual measurement — the sign, its LOINC code, the value and the units — through the reading’s signs.

• The Immunize command is now available in the SDK, so plugins can record a vaccine administered during a visit and the lot it came from. The instance’s vaccine catalog and its lot inventory are readable as Vaccine and VaccineLot, and supplying a lot fills in the manufacturer and expiration date for you.

• The Lab Order command’s comment is now limited to 128 characters.

08.26.2026

2026-08-26T00:00:00-07:00

bugfix

• Printouts, note headers and outbound lab and imaging orders now report the patient’s recorded sex at birth. Previously any value other than Male read as “female”, including Other, Unknown and blank.

• Coverages with the “Patient” payer now show “No eligibility check applies” rather than a failed eligibility check, and no longer send eligibility requests to the clearinghouse. A self-pay coverage that had already collected failed checks no longer reports them as failures.

• Requests to the Claim.MD clearinghouse now time out instead of waiting indefinitely when Claim.MD accepts a connection and then stops responding. An eligibility check that times out records “coverage verification timed out” rather than leaving the check unresolved, and claim submissions, remittance retrieval and payer list refreshes are bounded the same way.

• Fixed an issue where a signed lab review that used “Send via patient app” showed “Error loading command” in place of the review when the note was reopened. These reviews now reopen correctly.

• Admin CSV imports, such as Fee Schedule → Import, no longer fail with a 500 error when you confirm the upload.

sdk

• Four more records are now readable through the SDK data module, three of them the records behind commands:

◦ Procedure — what the Perform command records, with its CPT codings.

◦ FamilyHistory — what the Family History command records, one per relative, with the relative’s relation and its condition codings.

◦ HistoryOfPresentIllness — what the History of Present Illness command records.

◦ EligibilityRequest and EligibilityResponse — the coverage eligibility check sent to a payer and what came back, including the payer’s errors and the parsed response. Both are reachable from a Coverage, which also gains an eligibility_status.

• Plugins can now subscribe to coverage eligibility events:

◦ COVERAGE_ELIGIBILITY_RESPONSE_CREATED fires when a response is first recorded, and COVERAGE_ELIGIBILITY_RESPONSE_UPDATED when an existing one changes.

◦ One of COVERAGE_ELIGIBILITY_RESPONSE_ACTIVE, _INACTIVE or _FAILED fires alongside it, carrying the status the check resolved to.

◦ The event context carries the coverage, the patient, the status, and the payer’s errors on a failure.

• The SDK commands module enforces more validations, each reported when the command is written rather than failing later:

◦ The Prescribe, Refill and Adjust Prescription commands check four fields against what can be transmitted to a pharmacy:

◦ sig — up to 1000 characters.

◦ note_to_pharmacist — up to 210 characters.

◦ refills — from 0 to 99.

◦ quantity_to_dispense — greater than zero. Fractional quantities such as 0.5 — half a tablet, or 0.5 mL of a suspension — are still valid, so the bound is exclusive rather than a minimum of one.

◦ The Update Diagnosis command’s background and narrative accept up to 2048 characters.

◦ The Close Goal command validates goal_id, and fails when the goal doesn’t exist or belongs to another patient.

08.24.2026

2026-08-24T00:00:00-07:00

bugfix

• Fixed an issue where committing a Point of Care Lab Test did not add the CPT charge configured on the test’s template to the billing footer of the note, so the visit could be under-billed. The charge is now added when the command is committed, whether that happens in the chart or from a plugin.

sdk

• The SDK data module now reaches a patient’s signed consent documents, where previously only the blank template was available. PatientConsent gains:

◦ documents — the signed PatientAdministrativeDocument records.

◦ active_document — the current signed document.

◦ document_references — the DocumentReference records behind them.

• The SDK data module now reaches a goal’s update history alongside the goal itself. UpdateGoal is the record behind the Update Goal and Close Goal commands, and three accessors list them:

◦ goal.updates — the updates and closures recorded against a goal.

◦ patient.updategoals — those recorded for a Patient.

◦ note.updategoals — those recorded on a Note.

• canvas validate and canvas install now catch two more constructs the sandbox rejects. Both used to pass validation on your machine and then fail once the plugin reached the instance; the error now names the alternative that works. (requires Canvas CLI 0.198.1 or newer)

◦ Any call to type(), not just the three-argument form used for dynamic class creation — use isinstance(x, SomeClass) to test a type, or x.__class__.__name__ to read its name.

◦ Augmented assignment to an attribute (obj.attr += v), which is rejected even on classes your plugin defines itself — write obj.attr = obj.attr + v instead.

• The Change Medication command now validates medication_id when you edit an existing command, not only when you originate a new one. An id that isn’t a valid UUID, or that matches no active medication on the patient’s chart, fails validation.

• Some commands now validate their string fields against the maximum length the chart accepts, and raise a validation error when a value exceeds it. The error names the field, so an over-long value is caught in your plugin instead of being accepted and then rejected later, away from the plugin that sent it.

◦ The Allergy command’s narrative accepts up to 512 characters.

◦ The Family History command’s note accepts up to 512 characters.

◦ The Imaging Order command’s additional_details and comment accept up to 1024 characters.

◦ The Immunization Statement command’s comments accepts up to 255 characters.

◦ The Medication Statement command’s sig accepts up to 1000 characters.

08.19.2026

2026-08-19T00:00:00-07:00

bugfix

• Fixed an issue where choosing “Send via patient app” as the patient communication method left a report review stuck. Sign stayed greyed out with “Please select a report” even though a report was attached, the review never saved, and it could only be cleared by reloading the page. On a lab review the patient was still notified that their results were ready, even though nothing had been recorded in the chart. Reviews now sign and save normally.

• “Send via patient app” is now offered only on lab reviews, the one review type that supports it, so it no longer appears on imaging, referral, or uncategorized document reviews. It also now appears when reviewing a lab report from the panel, matching the patient chart.

• Providers on a touch screen can now act on a medication in the Medications section of the patient summary, on the left-hand side of the patient chart. Tapping a medication there opens its detail, where Stop, Adjust, and Refill are full-size buttons and the medication name stays readable. Tapping a medication before its details had finished loading no longer blanks the patient summary. On a mouse or trackpad, including an iPad with a keyboard attached, the buttons continue to appear on the row on hover.

sdk

• The Patient effect now allows you to manage your patient’s contacts — emergency contacts, next-of-kin, and other related persons. A contact either holds the person’s details inline, or points at another Canvas patient, which is how two patients are linked to each other. Contacts are added, modified, and removed one at a time: unlike the FHIR Patient API, where a contact left out of an update message is deleted, a contact you leave out here is untouched, and removing one is always explicit.

• The following were added to the SDK data module so plugins can read those contacts back:

◦ PatientContactPerson lists a patient’s contacts.

◦ PatientContactCategory links each contact to its relationship codings.

◦ ContactCategory lists the codings the instance defines.

08.17.2026

2026-08-17T00:00:00-07:00

• A controlled substance can no longer be sent for a patient whose sex at birth isn’t recorded as male or female. This covers the Prescribe, Refill and Adjust Prescription commands, both in Canvas — where the send action is no longer offered — and through the SDK, where send() reports “eRx unavailable, patient sex at birth must be male or female”. Previously the send failed downstream with nothing to point the prescriber at the cause.

• Imaging order, Lab Review, lab report and Referral printouts now accurately reflect the patient’s recorded sex at birth, including “Other” and “Unknown”.

sdk

• The PluginCommand data model now holds one row per custom command. Rows left over from the old content-versioned keys are consolidated when this release is deployed, and schema_key now always matches the command_key declared in the plugin’s manifest.

08.13.2026

2026-08-13T00:00:00-07:00

sdk

• Plugins can now get from a DocumentReference to the record it was generated from — the originating Lab Report, Invoice, Educational Material, and so on — and from any of those records back to the document reference that carries its file.

• The Assess command now checks that the condition it references belongs to the patient whose chart is being written to. Referencing a condition from another patient, or one that doesn’t exist, returns a clear validation error instead of being charted silently or failing with a generic error.

• The Assess command’s narrative and the Diagnose command’s today_assessment now accept up to 2048 characters.

• After a Canvas release is deployed, any tab that was already open now shows a banner across the top of the page: “An update is available for Canvas. Please click here to reload the page.” Previously that tab kept running the older build and could fail with unexplained errors.

08.12.2026

2026-08-12T00:00:00-07:00

sdk

• The following were added to the SDK data module:

◦ PatientAdministrativeDocument exposes the administrative documents on a patient’s chart, along with their document coding and a document_url for the file itself.

◦ UncategorizedClinicalDocument gains a code property, so plugins can read the document’s coding.

08.11.2026

2026-08-11T00:00:00-07:00

sdk

• Plugins can now restrict which note types the New Note button offers for a given patient, and hide the button entirely when none are permitted, using the new allowed_new_note_types attribute on the Patient Timeline effect. This affects note creation only — existing notes and the timeline’s note type filter still show every note type.

08.06.2026

2026-08-06T00:00:00-07:00

bugfix

• Fixed an issue where the patient chart’s Goals “Active/Closed” filter classified goals incorrectly. The filter now classifies each goal by its most recent update, so a goal that was updated while active and later closed no longer appears under “Active” or sorts by an outdated due date.

• Fixed an issue where installing, updating, or reinstalling a plugin could temporarily block a user’s IP address with a site-wide “403 Forbidden” while the plugin reloaded. Requests to plugin endpoints no longer count toward that block.

sdk

• The following were added to the SDK data module:

◦ ImagingReport gains a document_url property, so plugins can read the file attached to an imaging report.

◦ CareTeamMembership gains a service_provider property, so plugins can read a patient’s external care team members (e.g. an external PCP) and their contact info with membership.service_provider.business_fax. It resolves through the new organizational_entity relationship and the new OrganizationalEntity data module.

◦ EducationalMaterial exposes Educational Material command data — the article’s title and abstract, the language it was shared in, and the languages it is available in. The article PDF itself is reached through DocumentReference.

• Plugins can now control which items appear in the provider (hamburger) menu via the new ProviderMenuConfiguration effect. For example, a scheduling plugin can hide the native Schedule item so it no longer renders in the menu.

• Running canvas validate no longer reports library-owned handler classes in hidden directories (e.g. .venv/) as unreferenced, so plugin authors stop seeing spurious validation warnings. (requires Canvas CLI 0.191.1 or newer)

08.05.2026

2026-08-05T00:00:00-07:00

api

• When a FHIR request is inserting a command into a specific note by passing that note’s ID in the extension, Canvas now checks that the note is not in a deleted or cancelled state. If the note has been deleted or canceled, you get a clear 422 telling you which note it was, instead of the 502 you would have seen before.

sdk

• Plugins can now build and maintain your own directory of service providers — the external providers picked when referring a patient, ordering imaging, adding an external care team member, or sending a fax.

◦ Three new effects create, update, and deactivate providers: Service Provider effects.

◦ Four new events let you customize two contact searches that plugins could not reach before:

◦ FAX__RECIPIENT__PRE_SEARCH and FAX__RECIPIENT__POST_SEARCH — the fax recipient list.

◦ PATIENT_PROFILE__EXTERNAL_CARE_TEAM__PRE_SEARCH and PATIENT_PROFILE__EXTERNAL_CARE_TEAM__POST_SEARCH — a patient’s external care team.

◦ Providers you create are not searched automatically. To offer them in the Refer, Imaging Order, fax, or care team searches, handle that surface’s search event and return them yourself — the guide walks through Offering your own providers alongside the directory.

◦ The ServiceProvider data module gains five fields:

◦ npi — the provider’s NPI.

◦ direct_address — the provider’s Direct (secure messaging) address.

◦ is_active — False once a provider is deactivated; the record is kept, not deleted.

◦ is_customer_managed — True for providers created through the new effects.

◦ science_contact_id — the shared directory contact the provider came from, if any.

◦ It also gains two helpers, as_search_result() and as_search_contact(), which shape a provider for the search surfaces so you do not have to build those payloads yourself.

• The SDK Vitals command now supports the Supplemental Oxygen field added to the Vitals command in the previous release, so plugins can record whether a patient continuously depends on high-flow or low-flow oxygen, or uses oxygen intermittently.

08.04.2026

2026-08-04T00:00:00-07:00

bugfix

• Fixed several issues with snoozing protocol cards that come from plugins. Quality measure protocol cards now show the Snooze button when the plugin allows snoozing, snoozing from the card now applies to the protocol you snoozed instead of appearing to do nothing, and the patient’s protocol list refreshes with the updated state right away.

• Fixed an issue where a questionnaire launched by an automation kept carrying answers forward after carry-forward had been turned off for that questionnaire — including when a new version was uploaded with carry-forward disabled, or the questionnaire was archived. Automations now use the questionnaire’s current carry-forward setting instead of the setting that was in effect when the automation was created.

• The Vitals command now includes a “Supplemental Oxygen” field, so you can record a patient’s ongoing dependence on oxygen alongside the rest of their vitals.

◦ It’s a single-select with three options: “Continuously depending on high oxygen flow”, “Continuously depending on low oxygen flow”, and “Intermittent oxygen consumption”.

◦ Your selection is recorded as a coded LOINC value (question 88658-0, answer list LL4908-1) rather than as free text, and it appears on the committed command and in note printouts alongside the other vitals.

◦ The resulting observation can be read through the FHIR Observation endpoint, where it is returned as a valueCodeableConcept. Supplemental oxygen cannot be created through that endpoint.

◦ The SDK’s Vitals command does not support this field yet — plugin support is coming soon.

• For instances with the ENABLE_COLLAPSED_NOTES Constance config setting turned on, opening a patient’s chart no longer auto-expands a note. A note opens only when you click it, create it, or follow a direct link to it. Commands inserted from a quality protocol recommendation now open in a note you can see, instead of landing in a collapsed background note where they appeared to vanish. The setting is off by default and an admin can turn it on under General Configuration; charts on instances without it are unaffected.

• The “Submit a support ticket” link has been removed from the help menu. Support requests are now handled through either the in-app support chat bubble or the Help Center.

sdk

• Plugins can now subscribe to calendar and calendar-event lifecycle events — CALENDAR_CREATED, CALENDAR_UPDATED, CALENDAR_DELETED, CALENDAR_EVENT_CREATED, CALENDAR_EVENT_UPDATED, and CALENDAR_EVENT_DELETED — to react when a calendar or one of its events is created, changed, or removed.

08.03.2026

2026-08-03T00:00:00-07:00

bugfix

• Fixed an issue where delegating patient communication on a Review, Image, or Refer command could fail to create the follow-up task when no team was set up to own it. These commands now always create the delegated task and assign it using a clear fallback order: the responsible team when one exists, otherwise the patient’s care team lead, and if there is no care team lead, the staff member who signed the command.

◦ Review commands (lab, imaging, uncategorized document, and consult report review) assign the task to a team with the “Communicate diagnostic results to patient” responsibility.

◦ Image and Refer commands assign the task to a team with the “Coordinate referrals for a patient” responsibility.

• Fixed an issue where changing an uncategorized clinical document’s type to a Lab or Imaging Report — whether from the patient chart or in Data Integration — left the original document active in the review queue, creating a duplicate. The original document is now retired automatically, the reviewer’s “to review” badge count updates immediately, and the edit-report modal no longer gets stuck open after switching a document’s type.

• Fixed an issue where a patient’s Care Team summary appeared empty when all of the patient’s care team members were external. External care team members now show in the chart’s Care Team summary.

• The Refill Requests panel’s assignee filter has several improvements:

◦ It’s now multi-select, so you can combine options instead of choosing just one.

◦ Its individual staff options now list only prescribers — the staff members a refill request can actually be assigned to.

◦ Your care team is now its own filter option, split out from the “Me” and “Me and my teams” options. The refill requests badge count reflects this change.

• The Ignore action is now available on all refill requests, not just suspected duplicates.

• Labels applied to tasks — including the system-generated “Chart PDF” and “Batch Statements” labels and labels created through the FHIR API — are now scoped to the Tasks module, so they appear and are selectable in the Tasks label filter. Existing labels continue to work everywhere as before.

sdk

• Plugins can now show a notification badge — a count (capped at “99+”) with a bolded label — on a provider_menu_item scoped application’s item in the provider menu (the navigation sidebar, also called the hamburger menu), using the new Application Notification Badge effect or the compute_notification_badge hook on the Application handler.

• Plugins can now create, update, and mark lab reports as entered-in-error, and attach lab results (tests and values) to an existing report, through the new Lab Report effect — supporting workflows where a report is created first and its results arrive later, such as async OCR.

• Plugins can now redirect the user to an internal Canvas page or an approved external URL after an action such as signing a note, opening the destination in the same tab or a new tab, using the new Redirect effect.

• Marking an appointment as no-showed from the calendar appointment card’s status dropdown now fires the APPOINTMENT_NO_SHOWED plugin event, so plugins that respond to no-shows trigger as expected. Previously this only fired when marking the no-show from the patient chart.

07.29.2026

2026-07-29T00:00:00-07:00

bugfix

• Fixed an issue where opening a note whose type hadn’t finished loading could crash the entire patient chart. The affected note now shows a contained error message instead, and the rest of the chart keeps working.

• Commands marked “entered in error” no longer appear on a printed note or the generated full-chart PDF. They remain in the audit-trail PDF stamped to the note footer when the note is locked.

• Long entries in the “Reviewed:” sections of a printed or PDF note (for example medications, conditions, and allergies) now wrap to the next line instead of being cut off at the right edge of the page.

• Uncategorized clinical document / Medical Documents reviews can now be delegated to another staff member or team — with instructions and, optionally, consent to apply the original reviewer’s signature — and routed back to the original reviewer. Learn more.

• Long annotations in a command’s autocomplete dropdown are now shortened with an ellipsis and reveal their full text on hover.

sdk

• Plugins can now block the Create Coding Gap, Validate Coding Gap, Assess Coding Gap, Defer Coding Gap, and Change Medication commands at commit time by returning a validation error from a {COMMAND}__POST_VALIDATION handler. See Command Validation.

• Plugins can now read Change Medication records — to a medication’s directions (sig) — through the new ChangeMedication data model, queryable by a stable identifier and reachable from a patient’s or medication’s records.

• Plugins can now read document-review delegations through the new DocumentReviewDelegation data model and subscribe to the DOCUMENT_DELEGATED event, which fires when an uncategorized document review is delegated.

• Plugins reading a staff member’s top_clinical_role or top_role_abbreviation through the Staff data model now get the provider’s highest-ranking clinical role (and its credential abbreviation) when they hold more than one, instead of an arbitrarily chosen role.

07.27.2026

2026-07-27T00:00:00-07:00

bugfix

• Fixed an issue where recent edits to a letter or message in the patient’s timeline could be lost when you kept typing while an earlier edit was still saving. Edits now save reliably, and letters are always saved before being faxed or printed — so faxed or printed letters no longer go out with content missing or blank.

• Fixed an issue where opening or bookmarking the patient portal login URL directly could show a “This page isn’t working” error. The login page now loads correctly.

• Fixed an issue where scheduling availability could drop calendar holds and staff shift data when a connected Google Calendar’s cached events hadn’t been refreshed in about a month. Availability now refreshes the calendar automatically instead of falling back to incomplete data.

• Fixed an issue where a refill denial could fail to send back to the pharmacy when the original refill request had a missing or zero quantity. Denials now transmit reliably in this case.

• Fixed an issue where prescriptions the pharmacy had confirmed receiving could stay stuck showing as pending. Their status now reflects that the pharmacy accepted them.

• When e-prescribing a prescription fails unexpectedly, the error recorded on the prescription is now a short, readable message.

• Diagnosis text and ICD-10 codes are now shown in bold in the Assessment section of note printouts for the Assess, Diagnose, Change Diagnosis, Assess Coding Gap, and Resolve Condition commands.

sdk

• Plugins can now read incoming refill requests — including their medication codings and the prescriptions that respond to them — through the RefillRequest data model.

07.23.2026

2026-07-23T00:00:00-07:00

bugfix

• Fixed an issue where certain imported C-CDA documents could fail to display in the C-CDA viewer. Documents whose sections omit a display name — a pattern used by some external EHRs — now render correctly.

• Letters created through the Letter API now appear in the patient’s chart automatically, without requiring a page refresh — consistent with how notes created through the Note API already behave.

07.22.2026

2026-07-22T00:00:00-07:00

bugfix

• Fixed an issue where adding, removing, or switching a claim’s primary insurance could reprice line items to an outdated fee schedule rate, or to a single unit’s charge on line items with more than one unit. Line items now reprice to the rate in effect on each line item’s date of service — the payer-specific rate when insurance applies, or the self-pay rate when it doesn’t — multiplied by the billed units.

• Fixed an issue where plugin application drawer icons could appear as a broken-image placeholder instead of the icon after a chart had been open for several minutes. Icons now load reliably.

• The lab requisition form no longer displays the “Canvas Medical” header or the patient signature and payment-authorization section. It now presents a medical-necessity certification and an electronic signature block with the ordering provider and order date, consistent with the imaging requisition form.

sdk

• Fixed an issue where a patient’s default practice location and default provider set through the Patient effect were silently ignored — the effect returned success but the values were never saved. Both are now saved to the patient’s record whenever they’re included in a create or update.

07.21.2026

2026-07-21T00:00:00-07:00

bugfix

• Fixed an issue where assigning a task in a filtered queue reset the list to the first page. Assigning a task now keeps your place in the list.

api

• Preferred names (nicknames) received through integrations are now trimmed of surrounding whitespace, and a preferred name containing only whitespace (e.g. a single space) is stored as empty instead of a blank space.