Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.encoreos.io/llms.txt

Use this file to discover all available pages before exploring further.

The Batch History screen (/pm/batch-history) shows a chronological list of batch jobs run against charges, claims, and eligibility for the current organization.

​
Overview

The Batch History screen lists all batch jobs for the organization, ordered by start time (most recent first). Each row shows the job type, current status, total record count, processed count, error count, and start timestamp. Clicking any row opens a detail sheet with additional information. Users with the pm.batch.claim_generate permission also see a “Run batch operation” button that launches the Batch Operation Wizard for initiating new batch runs. When no batch jobs exist, the screen displays an empty state explaining that batch history appears when batch actions are run from the charges, claims, or appointments views.

​
Who it’s for

Requires the pm.batch.claim_generate permission. This permission gates both the route and the “Run batch operation” action button.

​
Before you start

  • You must hold the pm.batch.claim_generate permission.
  • Batch jobs are initiated from the Charge Capture (/pm/charges), claims, or appointments views. This screen is read-only history; new jobs are started elsewhere (or via the wizard launched from this page).

​
Steps

1

Open Batch History

Navigate to /pm/batch-history. The screen loads all batch jobs for your organization, newest first.
2

Review job status

Each job row shows: job type label, status badge (Pending, In Progress, Completed, Partial, Failed), total count, processed count, error count (shown in a destructive color when non-zero), and start timestamp.
3

Inspect a job

Click any row to open the Batch Job Detail Sheet, which provides further detail about the selected job.
4

Run a new batch operation (if permitted)

Click “Run batch operation” in the page header to open the Batch Operation Wizard. This button is only visible to users with the pm.batch.claim_generate permission.

​
Key concepts

— groups of charges, claims, or eligibility checks processed together. Job types visible in the list: Claim Generation, Claim Submission, Eligibility Check, Charge Approval. Status values: Pending, In Progress, Completed, Partial (some records failed), Failed.
When no batch jobs have been run, the screen shows “No batch jobs yet” with a note that history appears after running batch actions from charges, claims, or appointments views.
A job with status “Partial” means some records were processed successfully and some encountered errors. The error count column highlights the number of failures.

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/BatchHistoryPage.tsx
  • src/cores/pm/hooks/useBatchJobList.ts
  • src/cores/pm/types/batch.ts
  • src/platform/permissions/constants.ts