Go to App ↗

Chrome Extension

Access selected Assurlytics research tools in the browser: Codes, Denials, Policies, Scrubber, and Payers.

Last updated: 2026-10-31 · 3 min read · Status: draft
Documentation draft — not a verified product specification. This page is based on an existing extension UI evidenced by a product screenshot. Installation and distribution links, permission scope and whether the extension reads page content still require verification.

Overview

The Assurlytics Chrome Extension provides a compact way to access selected Assurlytics research tools while working in the browser. It aims to reduce context switching between reference websites and the main web application.

Who should use it

Coders, billers and RCM staff who want quick access to Code Lookup, Denial Help, Policy Q&A, Claim Scrubber and Payer Intelligence without opening the full web app for every question.

Prerequisites

A browser with the extension installed, and an Assurlytics account if the current authentication flow requires sign-in. Use non-PHI information only.

The supplied extension screenshot shows five navigation tabs:

  1. Codes — Code Lookup.
  2. Denials — Denial Help.
  3. Policies — Policy Q&A.
  4. Scrubber — Claim Scrubber.
  5. Payers — Payer Intelligence.

The screenshot also shows an AI Language selector, monthly usage status, Manage Plan, recent items, a connected status indicator and an Open Web App action.

Step-by-step instructions

  1. Open the installed extension using the browser's extension control.
  2. Sign in if required by the current authentication flow.
  3. Select one of the available tool tabs.
  4. Enter a non-PHI search or structured example.
  5. Review the result and verify official guidance.
  6. Open the web app for the full workspace when needed, using Open Web App where available.

The extension has been discussed in both regular popup and a separate window opened from an application-side icon. Document the actual available opening modes and window controls before treating either as confirmed. The standalone-window layout should expand to its window width and remain responsive; this is a UI implementation requirement, not a new product capability.

Language preference

A screenshot shows an English language selector and a possible error: "AI language preference could not load." Document actual supported languages and persistence behaviour only after verifying the settings service. Spanish support has been discussed for the wider platform, but per-feature availability must be checked. Do not claim all tools are fully localised merely because a language selector exists.

Usage and plan display

The extension may show monthly usage, reset date and a Manage Plan link. If data is unavailable, it should show a clear retry/error state rather than implying zero usage or unlimited credits. No prices, credit allowances or billing cycles are published here — see Plans and Usage.

Payer Intelligence in the extension

The extension's Payer Intelligence view shows a Payer Name or ID field (example placeholder Aetna or 00540), an optional State field defaulting to "Any state", a Find Payer action, a Recent section and a Ctrl + Enter shortcut, plus a warning not to enter member IDs, dates of birth, patient names or other patient identifiers. See Payer Intelligence.

Privacy and permissions — verification required

Before publication, document the actual Chrome Web Store listing, permission scope, data handling, authentication behaviour and whether the extension reads page content. Do not claim automatic extraction from EHRs, payer portals or patient records. Do not claim the extension reads page content until verified.

Limitations

  • Not all Chrome extension features are necessarily identical to the web app. Document actual feature differences after comparing the released versions.
  • Installation and distribution links require verification and are not published on this page.
  • AI language preference behaviour, including the error state above, requires verification against the settings service.

Troubleshooting

  • Language preference cannot load: retry, check the settings service, and do not assume a language has been applied.
  • Usage unavailable: retry using the current UI; do not infer a zero balance.
  • A tool result is unclear: open the web app for the full workspace and verify against official guidance.