Skip to content
Model infoModelsSnapshot: 15 Oct 2026

Nabla / Clinical AI

Nabla Note Fact Verification

Managed internal check of note claims against encounter transcripts and patient context.

restrictedClosed-source managed componentText analysis
Official documentation (opens in a new tab)Reviewed 16 Oct 2026
3 of 16 specification fields collected
Context windowNot collectedAwaiting source review
Maximum outputNot collectedAwaiting source review
Input billingNot collectedNabla clinical documentation platform
Output billingNot collectedNo inferred price

Specifications

Provider-documented facts. “Not collected” means we have not verified that field yet, not that the feature is unsupported.

Context / input limit
Not collected

No exact model-level contract established. Unknown does not mean unsupported.

Maximum input tokens
Not collected

No exact model-level contract established. Unknown does not mean unsupported.

Maximum output
Not collected

No exact model-level contract established. Unknown does not mean unsupported.

Parameters
Not collected

No exact model-level contract established. Unknown does not mean unsupported.

Release date
Not collected

No exact model-level contract established. Unknown does not mean unsupported.

Knowledge cutoff
Not collected

No exact model-level contract established. Unknown does not mean unsupported.

Tool calling
Not collected

No exact model-level contract established. Unknown does not mean unsupported.

Structured output
Not collected

No exact model-level contract established. Unknown does not mean unsupported.

Streaming
Not collected

No exact model-level contract established. Unknown does not mean unsupported.

Batch processing
Not collected

No exact model-level contract established. Unknown does not mean unsupported.

Fine-tuning
Not collected

No exact model-level contract established. Unknown does not mean unsupported.

Reasoning
Not collected

No exact model-level contract established. Unknown does not mean unsupported.

Context caching
Not collected

No exact model-level contract established. Unknown does not mean unsupported.

API version mapping
Core API 2026-10-05; versioning covers the API contract, not immutable weights.Source for API version mapping (opens in a new tab)
Output modalities
Claim validationSource for Output modalities (opens in a new tab)

Access & pricing

Prices belong to an endpoint and billing tier. A provider listing does not guarantee access for every account or region.

Nabla clinical documentation platform

Provider source (opens in a new tab)
API model ID
Not collected

No standalone model selector or API route established.

Access
Integrated note quality process; separately callable access is not established.
Regions
Exact verifier processing location is not established.

Endpoint pricing has not been collected. Check the provider for applicable rates.

Data & enterprise terms

Public terms include de-identified-data use for internal AI training; no blanket no-training guarantee is inferred. The product help article describes configurable patient-data retention, normally 14 days, and no retained audio. API WebSocket and async-result lifecycles are separately documented and must not be replaced with that product default. Applicable enterprise agreement and region-specific policy remain controlling.

Read the service policy (opens in a new tab)

Caching

Caching can reuse earlier input processing. Availability, lifetime and billing depend on the endpoint. A cache hit still generates a new response.

01 / INITIAL INPUTProcess & retain

The system processes eligible input and retains reusable state.

02 / LATER REQUESTCheck available state

Reuse depends on matching input, session state and the cache policy.

03 / CACHE HITReuse & generate

Reusing state can reduce repeated work. Any charges follow the billing rules below.

Nabla clinical documentation platform

Not verified

No published inference-cache contract established. Async result retention, client history and session recovery are not prompt caching.

How it works
Not collected

No published inference-cache contract established. Async result retention, client history and session recovery are not prompt caching.

Minimum reusable input
Not collected

No published inference-cache contract established. Async result retention, client history and session recovery are not prompt caching.

Lifetime & refresh
Not collected

No published inference-cache contract established. Async result retention, client history and session recovery are not prompt caching.

How to enable it
Not collected

No published inference-cache contract established. Async result retention, client history and session recovery are not prompt caching.

Usage fields
Not collected

No published inference-cache contract established. Async result retention, client history and session recovery are not prompt caching.

Billing rules
Not collected

No published inference-cache contract established. Async result retention, client history and session recovery are not prompt caching.

Limits & data boundaries
Not collected

No published inference-cache contract established. Async result retention, client history and session recovery are not prompt caching.

No verified cache rate for this endpoint. An empty rate is not a zero charge.

Caching reviewed 16 Oct 2026

What the measurements say

No benchmark observations have been added for this model. We do not turn a vendor description into a performance score.

Latency and throughput depend on the host, request size, reasoning settings and load. There is no measured speed or global usage figure in this record.

The record behind the model

Why it is included

Provider-operated clinical component under service terms. Underlying private, third-party and shared checkpoint mappings are not established; this record is not counted as an independent private base model.

Classification evidence (opens in a new tab)

Sources reviewed