Skip to main content
The Prior Authorizations screen (/pm/authorizations) lists all prior authorization requests for the current organization and lets users with the appropriate permission create new ones.

​
Overview

The screen displays prior authorization requests scoped to the current organization, ordered by creation date (newest first). Each row shows the patient name, authorization number, service type, payer name, requested date range, unit usage (used_units / approved_units), and a status badge. Users can filter the list by status (Draft, Submitted, Pending, Approved, Denied, Appealed, Expired, Cancelled) or search by patient name or authorization number. Clicking any row navigates to the authorization detail page at /pm/authorizations/:id.

​
Who it’s for

Requires the pm.prior_auth.view permission. Creating a new authorization additionally requires pm.prior_auth.create.

​
Before you start

  • The pm.prior_auth.view permission must be granted for the user’s role.
  • An organization must be selected (the hook returns an error state when no organization is active).

​
Steps

1

Filter the list

Use the search input to find authorizations by patient name or authorization number. Use the status dropdown to narrow to a specific status (All Statuses, Draft, Submitted, Pending, Approved, Denied, Appealed, Expired, or Cancelled). Filters are combined client-side after the server returns the status-filtered results.
2

Review an authorization

Click any card in the list to navigate to the authorization detail page (/pm/authorizations/:id).
3

Create a new authorization

Users with pm.prior_auth.create will see the “New Authorization” button in the page header. Clicking it opens the PriorAuthorizationFormDialog. When no authorizations exist, the empty state also offers a “New Authorization” action.

​
Key concepts

When no authorizations match the current filters, an empty state is shown with the message “No prior authorizations” and a “New Authorization” action (subject to the pm.prior_auth.create gate). If the data fetch fails, the card displays “Failed to load authorizations. Please try again.”

​
Viewing a prior authorization

The Authorization Details screen displays a single prior authorization record at route /pm/authorizations/:id (permission: pm.prior_auth.view). Additional permissions:
  • pm.prior_auth.submit — Submit button (draft status)
  • pm.prior_auth.appeal — Appeal button (denied status)
  • pm.prior_auth.edit — Edit button (draft/submitted/pending)
The page loads a prior authorization via usePriorAuthorizationDetail. It shows a two-column grid with Authorization Details (auth number, service type, urgency, payer, requested and approved date ranges, units, diagnosis codes, procedure codes) and Patient details (name, MRN, date of birth). A Units Used progress bar appears when approved units are set. If a determination date or denial reason is recorded, a Determination card shows those values. Clinical Justification text is displayed when present. The page also renders an AuthReviewSection for concurrent reviews. Note: urgency of urgent combined with a BHRF service type shows an Exempt badge.
  1. Navigate from the Prior Authorizations list (/pm/authorizations) and click a row to open the detail page.
  2. The left card shows all authorization fields including service type, urgency, payer, date ranges, unit counts, and codes.
  3. The right card shows patient name, MRN, and date of birth joined from pm_patients.
  4. Depending on current status, click Submit (draft), Appeal (denied), or Edit to update the record.
  5. The AuthReviewSection below the main grid shows linked concurrent review entries.

Practice Management

Overview of the Practice Management core.

Governance & parity

Documentation coverage and governance.
This page documents shipped product behavior. It is not medical, legal, or billing advice. Verify against your organization’s policies and applicable regulations before using it for clinical, compliance, or billing decisions. Protected health information (PHI) shown in the product is governed by your tenant’s access controls and is never exposed in this documentation.
  • src/routes/pm.tsx
  • src/cores/pm/pages/PriorAuthorizationListPage.tsx
  • src/cores/pm/hooks/usePriorAuthorizationList.ts
  • src/cores/pm/pages/PriorAuthorizationDetailPage.tsx
  • src/cores/pm/hooks/usePriorAuthorizationDetail.ts
  • src/cores/pm/hooks/usePriorAuthorizationMutation.ts