Introduction

Avara Express is how integration partners sell AutoScribe and/or Viewer as a service to their own customers, inside their own product. You keep one Avara organization. Each of your customers is an Express customer (cus_…) with its own users and studies.

That is a deep integration. Fitting Express into your data model takes a real API implementation: you create and label tenants, attach studies, and map your users onto Express customers so isolation holds. Plan for that work before you enable it.

It is built for:

• PACS companies embedding AutoScribe or Viewer in their product
• Distributors with their own software platform reselling AutoScribe or Viewer to sites they serve
  • Distributors who only do support and resale — without a software platform of their own — should use a separate Avara organization per customer, not Express
• EHR/RIS companies adding dictation and viewing as a deep integration, not a bolt-on login

Your customers never need their own Avara org. You host them; isolation is membership-based, with no leakage across tenants. Read Isolation before you attach studies.

Billing

Avara bills your platform. You charge your customers whatever you want — usage, seats, or your own service fees.

Avara does not charge setup or service fees — not to get Express running, and not to get your platform, PACS, or integration off the ground. There is no onboarding invoice for help standing up AutoScribe, Viewer, or Express.

Enable Express

1. In Settings, open Avara Express.
2. Click Enable Avara Express and confirm.

Enabling Express is permanent for the organization. It cannot be turned off.

After enable, an Express Customers tab appears in the sidebar. Study create accepts expressCustomerId. Your API key needs Express customer access — set that when you create the key in AutoScribe API Config or Viewer API Config.

Integration steps

1. Enable Express — Settings, as above. Irreversible.

2. Create customers — One Express customer per tenant you sell to. Customers.

3. Add users after they accept invites — Invite from AutoScribe or Viewer. They must accept before you can add them to a customer. Users.

4. Attach expressCustomerId on study create — Members only see studies tagged with a customer they belong to. Studies.

Do not make end-customer users admins. Admins see every study in the org.

For every Express operation the SDKs expose, see the API Reference.