Assistant update: TXA recognition and clearer follow-up context

By Conor Early, CRNA, creator of GlottaVue Anesthesia.

Published October 28, 2026. This retrospective covers Assistant service changes developed and deployed October 27, with a follow-up reliability check on October 28.

A short medication question should lead to relevant references or a useful request for clarification. Some TXA questions instead encountered long waits and failed answers. This update corrects two reference-lookup problems and changes how the Assistant handles a narrowly defined request that lacks context.

What changed in the online Assistant

The abbreviation TXA now resolves to tranexamic acid when the service looks up medication labeling. Previously, the local library recognized the abbreviation but the label lookup could miss it. A related correction helps a dose follow-up retain the medication you named earlier when the follow-up contains general workflow words.

For a brief TXA dose request containing only a weight, the Assistant now asks for the indication or procedure, age group, renal function and any TXA already given before attempting a generated answer. This clarification does not provide a regimen or claim that a source has already been verified.

How to use the change

These service changes are live and do not require an app update. Open the Assistant with an internet connection, name the medication and state the educational question. If it asks for missing context, continue in the same conversation. Keep identifying patient details out of questions, and make a new case or topic explicit rather than relying on earlier context.

Open the references attached to a generated answer and check their applicability. Finding a label or matching a medication name does not establish that an answer is appropriate for a particular situation. The Assistant overview explains the broader workflow, and our earlier reference-matching update describes another recent correction.

What this update does not promise

Generated responses can still be slow or fail. A follow-up check on October 28 found a delayed response that completed more quickly when repeated; this is not a guarantee of consistent response times. Software checks verify selected behavior, not clinical accuracy. Continue to verify clinical information independently.

New in-app progress messages and timeout handling are prepared in development, but have not been released through the app stores. Those screen changes require a later app release. While waiting for an online answer, the offline reference library remains another way to browse material. For a persistent technical problem, contact support with your app version and reproduction steps, without patient information.

This article describes the app and availability at its publication date. Check your store listing for the current release.