Skip to main content

Page tour of the edi-app

A two-minute walk through every page in the operator UI, with pointers to the chapter that covers each in depth.

Layout

The left nav groups by what kind of work you do, not by transaction type:

GroupPages
MonitoringDashboard · Transactions · Batches
ConfigurationTrading Partners · Companion Guides · Routing
OperationsResponse processing · Replay & retry

Monitoring pages

/dashboard

The morning-coffee page. Outbound volume, ack latency, stuck transactions, rejection rates, response queue depth, partner probe health, companion guide validation failures. Drill-through on any chart.

Covered in 8.1 — Daily monitoring.

/transactions

The most-used page. Every inbound and outbound transaction the gateway has ever produced or received, filterable by direction, type, partner, status, date range, ISA13, source claim ID, correlation ID.

Click any row for /transactions/:id — five tabs: Overview, Segment trace, Parsed result, Ack chain, Activity.

Covered in 8.3 — Transactions search & detail.

/batches

Outbound batches — one per cron tick per partner. Useful for spotting oversized batches and partner-rejected envelopes that affected many claims at once.

Covered in 8.4 — Batches view.

Configuration pages

/trading-partners

The partner list and detail. Tabs on the detail page: Overview, Connection, Capabilities, Credentials, Companion Guides, Routing, Activity.

Covered across the Trading Partners category — 2.1 through 2.5.

/companion-guides

The guide list and detail. The detail page hosts the X12 transaction tree, the rule list, and the live preview pane.

Covered in the Companion Guides category — 7.1 through 7.4.

/routing

Routing rules across all transaction types, with a precedence simulator backed by the live resolver.

Covered in 3.3 — Submission routing rules and 8.5 — Routing simulator.

Operations pages

/responses

The response-processing queue — inbound files awaiting parse, plus quarantined files that failed parsing.

Covered in 8.2 — Replay & retry.

/replay

The replay control surface. Three operations: re-parse inbound, re-submit outbound, re-build & resubmit. Bulk filter and execute.

Covered in 8.2 — Replay & retry.

Cross-cutting affordances

Global search (Cmd/Ctrl + K)

Jumps to any transaction by ISA13, any partner by name, any companion guide by name, any source claim by ID.

Profile menu (top-right)

ItemNotes
Sign out
Theme toggleLight / dark; persists across sessions on this browser.
My rolesShows your current scopes — useful for confirming why a button is greyed.
Audit accessLast 7 days of your own actions in the EDI surface.

Notification bell

Unread issues in your tenant's queue tagged EDI. Click for a dropdown; click an issue for /issues/:id (cross-app).

What lives in rcm-app instead

A few EDI-adjacent surfaces live in the tenant app rather than edi-app, because they belong to the billing / clinical workflow:

SurfaceLives inWhy
/issues (queue)rcm-appIssues span EDI and non-EDI categories.
/eligibility (one-off check)rcm-appTriggered by clinical staff, not EDI.
/eligibility/sweepsrcm-appSame — clinical / ops trigger.
/authorizationsrcm-appClinician-driven; EDI is the implementation detail.
/receivables (835 workspace)rcm-appBilling-side reconciliation.

You can navigate from edi-app to rcm-app and back via the Other Manuals dropdown in the top bar.

Next

1.4 — Authentication and your scopes