Swarna Shivansh for athenahealth

Review requests triggered by completed athenahealth visits, for urgent care and medical groups. athenahealth remains your system of record; Swarna Shivansh reads only the events it needs.

How the connection works. Connector access depends on your athenahealth edition and the API or export options your account has. We confirm what is available for your locations during onboarding, before any data moves.

Appointment events

  • Encounter closed
  • Patient checked out
  • Telehealth visit completed
  • New patient visit completed

BAA configuration

A business associate agreement is signed before the connector is switched on. Contact details are used to send requests and are not stored with clinical identifiers. Sensitive visit types are excluded by default.

Setup timeline

Connected at the practice level, then filtered by department so each clinic sends its own requests.

athenahealth questions

Does Swarna Shivansh store clinical data from athenahealth?
No. The connector reads only what a review request needs: that an encounter was closed, the location, the provider and a contact channel the patient agreed to. Contact details are used to send the request and are not kept with clinical identifiers.
Can we choose which appointment types trigger a request?
Yes. You pick the appointment types, providers and locations that send requests, and the delay after the visit. Emergency, end of life and sensitive visit types are off by default.
Who signs the business associate agreement?
Swarna Shivansh signs a BAA with your organization before the connector is switched on. A BAA is available on request for every plan.

Other medical ehr connectors