Patient identity handoffs that keep the patient attached at every step

A patient identity handoff is any point where a patient's record passes from one system or step to the next: from the EHR into the grading platform, from a participant's report into a clinician's review queue, and from one workspace to the people allowed to read it. Burna AI's late July 2026 work, built on a development branch and live on the platform since 10 August 2026, keeps the patient attached at each of those points, along with a record of who acted on it.

It serves the coordinators who import and review patients, and the administrators who bring a site team onto the platform.

Where a patient identity handoff happens

Handoff	What now travels with it
EHR encounter into the platform	The encounter's note, filed as a visit for that patient
EHR read inside an organization	The clinician's organization, checked before the request leaves
Participant report into review	A review status of its own for every submission
Person into a workspace	The right active workspace at sign-in, on accepting an invitation and on removal
Administrative change	An audit entry naming who made it, written first

EHR encounter import brings the note with the patient

Import encounter on the EHR sync screen fetches the selected encounter's note from the connected EHR, creates a visit for that patient, and opens it, where grading starts. The patient and the note arrive together, so the grade is made against the record the EHR holds for that encounter. When the EHR returns the patient but no retrievable note, the screen says which half arrived.

EHR connections that belong to one organization

• An administrator picks the organization's EHR endpoint from a directory instead of typing an address, and the EHR sign-in is addressed to that organization's own server.
• Changing the endpoint disconnects the members' existing connections, so nobody keeps reading from the previous server.
• A patient read from the EHR is checked against the clinician's organization and refused before any request leaves the platform.
• Every EHR read, whether it succeeds or fails, is recorded in the audit trail.
• A Burna AI account comes from signing in to Burna AI; an EHR identity on its own no longer creates one.

For the full picture of how patient data is separated and protected, see the architecture a security review asks about.

Each patient-reported submission keeps its own review status

The review queue for patient-reported submissions now gives every submission its own review. A participant with three unreviewed submissions shows three entries, and a clinician can open, review and sign each one, oldest included.

Since then (August 2026): the participant app that collects these submissions is Healthnotes, the participant app sponsors deploy through sites.

Invitations and organization provisioning that land on the right team

• Every sign-in carries the person's active workspace: the one they were last active in, or else their first membership.
• A new account receives a workspace of its own, with the new user as owner, so every account has a workspace from its first sign-in.
• Accepting an invitation makes the inviting workspace the active one.
• Removal from the workspace a person is active in moves them to one they still belong to, preferring a workspace they own, and never back to the one they were removed from.
• An invitation that cannot be accepted says why, with separate screens for a visitor who is not signed in, an invitation addressed to a different account, and an invitation that has expired or was already used.

Since then (28 August 2026): people who belong to more than one workspace switch between them from the account menu.

Every administrative change records who made it

Every change made through the platform's administration layer, including organization changes, EHR connections, API keys and consents, now writes its audit entry before the change runs. The entry names the person who made the change and then records whether it succeeded. If that entry cannot be written, the change is refused, so a governed action and its record of who made it happen together or not at all.

Where this runs today

The 10 August release also retired the earlier provider web app; the platform runs at app.burna.ai. What Burna AI does today lists every live capability.

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

If your site imports patients from an EHR or is bringing a team onto the platform, book a 15-minute conversation.