Nabla released version 2026-08-25 of its Core API. An optional specialty field was added to user management and note generation on the Server API, and an encounter date field was added to note generation on both the User and Server APIs, so a caller can now tell Nabla what kind of encounter it is transcribing instead of leaving the model to infer it. The release also introduces an audio chunk acknowledgement protocol and enforces strict endpoint path prefixes, which is a breaking change for anyone relying on loose paths.
Our readPassing specialty and encounter date at request time is the difference between a generic note and one shaped to the documentation conventions of the service producing it, which is usually where scribe output quality is won or lost. The audio acknowledgement protocol addresses silent data loss in streaming capture, a failure that is difficult to detect after the fact. Anyone with an existing Nabla integration should read the path prefix enforcement as required migration work rather than an optional improvement.