Product Updates

Product updates and release information

This page is Sarva’s home for product-change communication. It is being prepared as a structured release log: every published update will carry a real date, the affected workflow, and any action required. No updates are published yet — here is what will appear here, and how to confirm current capabilities in the meantime.

No dated releases are published yet

This is a deliberate choice, not an oversight.

Why the page is not padded

Publishing an unverified feature, date, or availability statement would make this page worse than useless — it would mislead evaluations. Until each release is verified for its date, scope, and limitations, this page explains the structure instead of filling it with marketing text.

What to do in the meantime

For any live evaluation, confirm current capabilities directly: describe the workflow, systems, permissions, inputs, outputs, and review requirements, and Sarva will confirm what is supported and what needs assessment. Start that conversation.

What every release note will include

The structure each published update follows, so you can scan for what matters and skip what does not.

Fields included in each Sarva release note
FieldWhat it covers
Release dateThe date the change became available, not the date it was written about.
What changedA concise description of the workflow, product area, or connector affected.
Who is affectedThe practices, billing companies, or workflows the change applies to — and which it does not.
Action requiredWhether customers need to do anything: confirm configuration, re-review a workflow, or nothing at all.
LimitationsKnown constraints, systems or plans out of scope, and what should be confirmed with Sarva before relying on the change.
Related pagesLinks to the product, connector, or documentation pages that describe the affected area.

Updates will also carry category labels — for example workflow capability, connector support, or security — so recurring readers can filter to what affects them.

How to confirm current capabilities

Release notes describe change over time. For a decision you are making now, confirm against the workflow in scope.

1

Describe the workflow

The tasks, systems, inputs, outputs, and the staff who review exceptions today.

2

Get a capability assessment

Sarva confirms what is supported, what needs configuration, and what requires further assessment — per your systems.

3

Verify in a pilot

Configured workflows are proven on real work with agreed measures before you rely on them. See the implementation approach.

Related pages: the AI agents for RCM, connector compatibility, how implementation works.

Need to know what is supported today?

Skip the release notes and ask directly — describe the workflow and Sarva will confirm current capabilities.