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.

This page is the Transaction Log — a read-only audit trail of all clearinghouse transactions — accessible at /pm/clearinghouse/transactions.

​
Overview

The Clearinghouse Transactions page presents an append-only (pm_transaction_log) of individual clearinghouse transactions. Records are created server-side by edge functions or a service client; no mutation actions are available from the UI. Each entry shows the transaction type, status, optional trace number, the associated batch file name (from pm_transaction_batches), claim number (from pm_claims), and the creation timestamp. Error codes, when present, are displayed inline. The list is capped at the 500 most recent records per query. This page is a sub-route within the Clearinghouse area (/pm/clearinghouse/...).

​
Who it’s for

Requires permission pm.claims.view (route guard: PM_PERMISSIONS.CLAIMS_VIEW). This page is read-only for all users.

​
Before you start

  • Transaction log entries are created automatically when clearinghouse batches are processed; no manual creation is available.
  • You must hold pm.claims.view to access this page.

​
Steps

1

Open the Transaction Log

Navigate to /pm/clearinghouse/transactions. The page loads the 500 most recent transaction log entries for your organization, newest first.
2

Filter by status

Use the status dropdown to filter entries to: Pending, Accepted, Rejected, Error, or Warning.
3

Filter by transaction type

Use the transaction type dropdown to filter to a specific X12 type (e.g., 837P — Professional Claim, 835 — ERA/EOB, 270 — Eligibility Inquiry).
4

Investigate errors

Entries with a status of Rejected or Error display the raw error_codes value below the metadata row. Use the trace number and batch file name to correlate with the batch record at /pm/clearinghouse/batches.

​
Key concepts

The pm_transaction_log table is immutable. RLS enforces USING(false) deny policies for UPDATE and DELETE. All entries are written server-side; the UI provides read access only.
Log entries carry the same X12 transaction type identifiers as batches: , , , , , , , , , .
Status values are pending, accepted, rejected, error, and warning. These reflect the clearinghouse’s response to the individual transaction, which may differ from the parent batch status.
When no entries exist, the page shows “Transaction log entries are created automatically when batches are processed.”

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/TransactionLogListPage.tsx
  • src/cores/pm/hooks/useTransactionLog.ts
  • src/cores/pm/types/clearinghouse.ts
  • src/platform/permissions/constants.ts