10.13.2026

Today’s release includes the following updates:

bugfix

  • Fixed an issue where, when your Fee Schedule had more than one active entry for the same CPT code, a charge added from the note footer or a Perform command could bill a different entry’s amount. Charges now bill the entry you picked, and claim lines keep that amount when the claim is repriced, such as after a primary coverage change.
  • Fixed an issue where a questionnaire a patient completed in the portal before a visit, such as a PHQ-9, was dated with the upcoming appointment’s date in the patient chart’s Social Determinants section. It could also appear in place of a newer result for the same questionnaire. Each questionnaire is now dated by when it was completed, and the most recent result is shown.
  • Fixed an issue where entering a Perform command in error left its CPT code in the note’s billing footer. The CPT code is now removed.
  • Fixed an issue where a review queue failed to load when it contained a document with no clinical date. These documents now appear in the queue.
  • Fixed an issue where a billing line item in the note footer could reopen right after you clicked Done, if you then quickly clicked the CPT search or another line item. It now stays closed.
  • Fixed an issue where a custom panel or prefilled fields that a plugin adds to a new command could disappear until the page was refreshed. They now appear right away.
  • Fixed an issue where practice location names and other text in Settings could display as formatted content. They now always display as plain text.

portal

  • Plugins can now send patients to another portal page, a portal menu application, or an allowlisted external URL with RedirectEffect.

sdk

  • Private Notes commands are no longer returned by the Command data model, so only the provider who wrote a Private Note can see it.

api

  • Registering or managing an OAuth application at /auth/applications/ now requires the Administrative Developer or Clinical Developer role. Staff who set up API access by following Customer Authentication need one of these roles.
  • A FHIR Practitioner update can no longer change the practitioner’s sign-in email, the rank 1 email where password reset links are sent. Additional emails can still be added at rank 2 or higher.