ProviderAlly

ProviderAlly — by Attenti LLC

ProviderAlly: practice management for behavioral-health clinics, built on the tools you already use.

ProviderAlly is a HIPAA-aware practice-management platform for behavioral-health clinics. It installs as an embedded add-on inside your existing practice CRM and gives clinic owners and clinicians a single workspace for intake forms with e-signature, telehealth sessions via Google Meet, clinical notes and treatment plans, and EHR-style reporting — all under one signed Business Associate Agreement.

By creating an account or using the service, you agree to our Privacy Policy and Terms of Service.

Schedule a demoSign in

What ProviderAlly does

ProviderAlly is workflow software for the people running a behavioral-health practice. It is not an EHR replacement and not a clinical decision-support system — clinical judgment stays with the licensed clinician.

Clinic owners install ProviderAlly into their practice CRM at the agency or sub-account level, sign a Business Associate Agreement, and provision clinician accounts. From inside the embedded app, staff use FormAlly to publish intake, consent, and assessment forms with conditional logic, calculated fields, and e-signature; deliver them to patients by link or email; and route the completed responses into the patient chart with version history.

Clinicians schedule telehealth sessionsfrom the chart. ProviderAlly creates a Google Meet link on the clinician’s calendar through the Google Calendar API and shares only a short check-in URL with the patient — personal video URLs are never published. An opt-in public provider directory lets clinics list accepting clinicians without exposing those URLs either.

The unified clinical record covers treatment plans, clinician notes, intake and discharge summaries, consent records, and inbound or outbound fax. EHR-style reportingaggregates census, productivity, and outcomes data so administrators don’t need to export PHI into spreadsheets.

What’s included

Tightly-integrated modules under one practice account. Each ships with audit logging, role-based access controls, and BAA coverage.

  • Practice CRM add-on

    ProviderAlly installs into your existing CRM as an embedded app. Practice owners manage sub-accounts, track signed Business Associate Agreements, and provision clinician users from one place.

  • FormAlly form engine

    Build intake, consent, and assessment forms with conditional logic, calculated fields, and legally-binding e-signatures. Forms route into the patient chart with full versioning and audit history; multi-step workflows can branch by response.

  • Telehealth via Google Meet

    Schedule a session and ProviderAlly creates the Google Meet link on the clinician's calendar through the Google Calendar API. Patients check in from a single short link; an opt-in public provider directory lets clinics list accepting clinicians without ever exposing personal video URLs.

  • Clinical record

    A unified chart across intake, treatment plans, clinician notes, consent records, discharge summaries, and inbound or outbound fax — searchable, exportable, and access-controlled per role.

  • EHR-derived reporting

    Census, productivity, and outcomes reports drawn from data already in ProviderAlly and connected systems — without exporting PHI into spreadsheets.

  • Audit, access, and BAA

    Every read and write is logged with user, action, and timestamp. Role-based access controls, encrypted storage, and a Business Associate Agreement available at signup.

Connecting your Google Calendar

If your clinic uses ProviderAlly’s telehealth module, each clinician is asked to connect their Google account so the app can create the Google Meet link for a session on the clinician’s calendar. We are transparent about exactly what this access is used for:

  • Scope requested: https://www.googleapis.com/auth/calendar.events — the minimum scope needed to create, update, and delete the calendar event for a telehealth session.
  • What we do with it: create the Meet conference for an appointment scheduled inside ProviderAlly, attach the clinician and patient as invitees, and update or cancel the event when the appointment changes.
  • What we do not do:we do not read, store, or display events on your calendar that ProviderAlly didn’t create; we do not request Gmail, Drive, or Contacts scopes; we do not share Google user data with advertisers; and we do not use Google user data to train AI or machine-learning models.
  • Disconnecting: you can revoke ProviderAlly at any time inside the app or from your Google Account permissions page. The OAuth refresh token we hold is deleted when you do.

ProviderAlly’s use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. The full disclosure is in our Privacy Policy.

Built for HIPAA

Compliance is structural, not a checkbox. We sign BAAs with every clinic and pass them through to the cloud providers handling protected health information on our behalf.

BAA available on signup
A signed Business Associate Agreement is required before any PHI enters the system. We do not process PHI without one.
Audited access
Every read and write against a clinical record is logged with user, action, and timestamp. Logs are retained per HIPAA.
Encrypted at rest
Cloud SQL and Cloud Storage encryption-at-rest, TLS 1.2+ in transit. OAuth tokens stored encrypted with envelope keys.
No AI on PHI without BAA scope
PHI is never sent to a third-party model provider unless that provider is on your BAA and the feature is explicitly enabled.

Privacy and terms

Before you use ProviderAlly, please review how we handle your data and the agreement that governs the service. Both documents are available below and are incorporated into every account.