Live grading streams on a native workflow protocol, and a new burna.ai

The live grading stream moves to a native protocol

In Week 18 of 2026, the Burna AI live grading stream, the step-by-step progress a clinician watches while a note is graded, moved onto the agent framework's native workflow protocol. The screens on top did not change. Underneath, three workflows now stream through one transport, each request carries its organization, and the duplicated parsing behind the display is gone.

The week also brought the first version of a new burna.ai and support for a staging environment where changes can be checked before production. Protocol ingestion merged at the end of the week.

How the live grading stream works now

Three workflows report progress while they run: CTCAE grading, drug attribution and drug interaction analysis. Until this week, each wrote its progress into a database-backed text stream that the provider app polled and reshaped, and three display components (web, a second web layout, and mobile) each carried their own copy of the step names.

This week each workflow got its own streaming route that emits step events in a standard format: running, completed or failed. A single transport hook in the app maps those events onto the shape the display components already used, so none of the screens had to change, and sign-in headers now travel explicitly with each request.

Aspect	Before Week 18	From Week 18
Transport	Database-backed text stream, polled	Native workflow protocol, one route per workflow
Parsing	Repeated in three display components	One transport hook; step names in one shared file
Organization scope	Not passed into workflow steps	Carried from the app into the workflow steps

Two smaller changes rode along. The model behind clinical reasoning moved to a newer version, and a follow-up fix made sure each step's ID is read from the right level of the stream event, so step tracking stays correct.

Why organization scope matters during grading

Grading draws on more than the note. Knowledge search over an organization's own documents, comorbidity lookups and drug attribution all query stored material, and one platform serves many organizations. Each request now carries its organization from the app through to the individual workflow step, so those searches can be filtered to that organization's own data. For how the steps fit together, see how the engine works.

The first version of a new burna.ai website

The first version of a new burna.ai marketing site merged on 27 April. It gave each audience its own pages:

• Audiences: healthcare providers, life sciences, clinical research and patients
• Company: about, careers, press, contact and a request-a-demo page
• Trust: a trust center, a security page and a technology page

A staging environment before production

The list of web addresses allowed to call the API, the trusted origins, lived in a shared package that several services imported, so changing it meant touching shared code. It now lives in the API layer as the single source of truth for origin checks. Staging addresses for the provider and patient apps were added to it, so both apps can run in a pre-production environment under the same sign-in and cross-origin rules as production.

Grading screens still in development were hidden from production navigation in the same change, and a follow-up on 3 May removed a retired address from the list.

Protocol ingestion lands at the end of the week

The protocol ingestion workflow merged on 1 May. Upload a trial protocol and the platform reads it into structured fields and makes its text searchable during grading. Week 19 explains how protocol passages reach each CTCAE grade.

Also in Week 18

• More than a hundred dependencies were updated, including the libraries the platform uses to call AI models.
• TypeScript tooling and React were brought to current patch versions, and unnecessary button roles were removed from the encounters page so screen readers announce it correctly.
• Duplicate dependency entries were cleaned out of the monorepo.
• A filtering bug in the provider web app was fixed, along with the filter status on mobile.
• The provider mobile app received a round of fixes.
• The provider mobile app's settings screen was fixed for iPad, and patient token sign-in on the server now reuses an existing account with the same email instead of creating a duplicate.
• Token sign-in on the server gained explicit types and a check that refuses a missing user.
• A symptom management fix landed, and routine logs moved to debug level.

What changed after Week 18

• Week 19 (May 2026): the second web grading layout was removed together with the database-backed streaming path, leaving one workflow pattern in which grading runs on the server and saves its results. The three streaming routes added this week, for grading, attribution and drug interaction analysis, remain in the platform's API.
• May 2026 and August 2026: burna.ai was rebuilt twice. The current site describes what the platform does today, checked against the code.
• July 2026: the provider web app was retired in favor of app.burna.ai.
• September 2026: protocol reading for research sites became Protocol Studio, a Burna AI product line, which starts with a free protocol conformance report.

AI suggests, clinicians decide. Human-in-the-loop, always.

Book a 15-minute conversation to see a note graded on your own workflow.