06.29.2026
Today’s release includes the following updates: bugfix
- Fixed an issue where questionnaire result narratives generated by a plugin did not appear in the committed questionnaire command until the page was manually refreshed. They now appear immediately.
- Fixed an issue where refilling or re-prescribing a medication left it incorrectly marked as Inactive. The medication’s status is now reconciled when the prescription is created, so previously-refilled medications correctly show as Active.
- Fixed an issue where signing a Lab, Imaging, Consult Report, or Uncategorized Document review from a report panel could intermittently fail silently — the review wouldn’t complete (it stayed flagged as review-required) and the typed annotation was discarded. Signing these reviews now completes reliably and preserves the annotation.
ui
- A note can now record a supervising provider, selectable from a new dropdown in the note header. Locking the note or pushing its charges propagates the supervising provider onto the resulting claim. Claims can be billed incident-to using the new supervising-provider section and incident-to toggle in the claim’s provider details. When a claim is billed incident-to, the supervising provider becomes the rendering provider across the CMS-1500 (paper), 837P (EDI), and Candid billing outputs.
sdk
- The Patient SDK effect gains several new capabilities:
- Plugins can now supply their own patient key when creating a patient via CREATE_PATIENT; the supplied key becomes the new patient’s identifier, so the plugin can reference that patient in follow-up effects within the same execution. When no key is supplied, the server generates one as before.
- Plugins can now set a patient’s biological race and cultural ethnicity codes via the
biological_race_codesandcultural_ethnicity_codesfields. Previously these values were silently dropped by the effect interpreter. - Plugins can now mark a patient as inactive or deceased, including the date, cause, and comment for deceased patients.
- Plugins can now read and write supervising-provider data on notes and claims through the SDK:
- Effects: the Note effect accepts a
supervising_provider_id— which propagates onto the resulting claim when the note is locked or its charges are pushed — and Claim effects set the supervising provider (by staff link or free-text) and toggleincident_to. - Data: the
Note.supervising_provider,Claim.incident_to,ClaimSupervisingProvider, andStaff.default_supervising_providerdata models are now queryable. - Events: new
NOTE_SUPERVISING_PROVIDER_CHANGED,CLAIM_INCIDENT_TO_CHANGED, andCLAIM_SUPERVISING_PROVIDER_CHANGEDevents fire when these values change.
- Effects: the Note effect accepts a