SMART launch from the EHR, with the account linked and the workspace ready

Week 27 of 2026 (29 June to 5 July) connected the SMART launch from the EHR to a Burna AI account and workspace. A practitioner starts Burna AI from inside the EHR, the launch links their account using the EHR's own practitioner record, and everyone from the same EHR organization lands in one shared workspace, with no separate sign-up. A new EHR callback page shows each step as it runs.

The week also moved the choice of model behind grading into configuration and tightened date-of-birth entry on patient forms. It serves the clinicians who grade from inside the chart, and the IT teams who approve how they get there.

What is a SMART launch from the EHR?

A SMART launch from the EHR starts a clinical application from inside the EHR, which passes it the address of its FHIR server and a launch token. SMART on FHIR is the standard way a clinical application authenticates with an EHR and reads its FHIR resources, and the EHR launch is the flow it defines for starting from inside the chart. The application exchanges an authorization code for access tokens with the EHR's authorization server, then reads the resources it is allowed to see.

EHR launch account linking, step by step

1. The practitioner launches from inside the EHR, and a session opens with no sign-up or sign-in screen in the way.
2. The launch exchanges the authorization code for tokens with the EHR's authorization server.
3. It reads the practitioner's Practitioner record from the EHR's FHIR server.
4. It upgrades the session to a named account, taking the email from that record on the server, never from the browser.
5. It resolves the practitioner's Organization, joins or creates the workspace keyed to that organization's FHIR identifier, and stores the EHR tokens against that workspace.

Tests cover a practitioner re-linking the same account, several practitioners from one organization joining a single workspace, and launches that create no duplicate workspaces.

Why identity comes from the EHR, not the browser

An email supplied by a browser can be forged. An identity read from the EHR's own practitioner record comes from the system that already knows the clinician.

That matters for every signature that follows. 21 CFR Part 11 requires each electronic signature to be unique to one individual, and requires an organization to verify a person's identity before it sanctions that person's electronic signature (21 CFR 11.100). How Burna AI approaches 21 CFR Part 11 covers signatures and the audit trail, and the architecture a security review asks about, SMART on FHIR included, is set out on one page.

Shared workspace provisioning for each EHR organization

Every practitioner launching from the same EHR Organization resolves to one Burna AI workspace, keyed to that organization's FHIR identifier. A team from one site lands together on its first launch, and nobody provisions the workspace by hand.

An EHR callback page that shows each step

Connecting to an EHR now runs through a dedicated callback page with a step timeline: authentication, then the workspace, then data import. When a step fails, the page shows a message the user can act on, alongside a feedback form that files the report against the EHR connection.

Configurable model routing

The choice of model behind grading moved from an on/off switch for one self-hosted route to a configured default model. Operators change the model through configuration rather than a code change, and the self-hosted route's credentials moved into a managed secret.

Date-of-birth entry with month and year menus

Six patient date-of-birth fields gained month and year menus, so an older patient's date takes two selections rather than paging back month by month. The six are creating a patient, adding a patient, patient details, encounter import, SAE reporting and EHR patient search. Each field also enforces a range: no date in the future, and none before a set earliest date.

Trend charts on the patient check-in screens

Work on the patient app's check-in screens continued. Symptom trend cards now draw as line charts from a charting library.

Since then: The check-in screens now ship in Healthnotes, the participant app sponsors deploy through their sites. In September 2026 the SMART launch was restructured: workspace membership is resolved on the server from the launch token's practitioner-to-organization binding, and a launch whose organization cannot be resolved creates no workspace. The web provider app was retired in July 2026; the platform is app.burna.ai.

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

If you are planning a SMART launch from your EHR, book a 15-minute conversation.