08.04.2026

Today’s release includes the following updates:

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.

ui

  • 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.