Transactions search & detail

Outcome

You can find any inbound or outbound transaction in seconds — by ISA13, by correlation ID, by source claim, by partner — and the detail page gives you the full segment trace and the full ack chain in one view.

Prerequisites

Scope	What it lets you do
edi.transaction.read	View list / detail

The list page

/transactions filters:

Filter	Default
Date range	Last 24h
Direction	All
Transaction type	All
Partner	All
Status	All
Test indicator	All
Correlation ID	(free text)
Source claim ID	(free text)
ISA13	(free text — exact)

The default sort is created_at descending.

Common columns:

Column	Notes
Direction	outbound / inbound
Tx type	837P, 837I, 270, 271, 277CA, 999, TA1, 835, 278, 276, 277, 834
Partner	Display name
ISA13	Interchange control number
Status	submitted, acknowledged, accepted, rejected, failed, received, parsed, dispatched
Correlation	What this transaction relates to (claim, auth, sweep, …)
Created at	Server timestamp

The detail page

/transactions/:id opens with five tabs:

Tab	Content
Overview	Header — type, direction, partner, status, control numbers, correlation.
Segment trace	The full envelope rendered as a hierarchy: ISA → GS → ST → loops → segments. Click any segment to expand to per-element detail.
Parsed result	The structured object the parser produced (for inbound) or the source object the generator consumed (for outbound).
Ack chain	Outbound only — every related ack inbound (TA1, 999, 277CA) with status. Click any to navigate.
Activity	Replay attempts, status changes, operator notes.

Segment trace

The trace is the most-used tab. It renders the envelope as a tree:

ISA*00*..*00*..*ZZ*ACME*ZZ*PARTNER*250131*1234*^*00501*000000123*1*P*:~
└── GS*HC*ACME*PARTNER*20250131*1234*1*X*005010X222A1~
    └── ST*837*0001~
        └── BHT*0019*00*REF*20250131*1234*CH~
            └── 1000A — Submitter
                └── NM1*41*2*ACME BILLING*****46*1234567890~
            └── 1000B — Receiver
                └── NM1*40*2*PARTNER*****46*0617003~
            └── 2000A — Billing Provider Hierarchy
                ...

Click any node to expand. Per-element view shows position, qualifier, value, and (for outbound) which companion guide rule produced it.

Parsed result

For inbound, this is the structured output of the parser — e.g. for 835, the ParsedRemittance object with claims, services, adjustments. JSON-shaped; copy-able.

For outbound, this is the source-object snapshot the generator consumed — useful for confirming whether a missing field was due to source data or a generator bug.

Ack chain

Outbound transactions display a graph of acks:

Click any ack node to navigate to its detail page.

Steps to find a transaction by claim

The most common operator query: "what happened to this claim's submission?"

1. Note the claim's ID in the rcm-app.

2. Open /transactions in the edi-app, paste the claim ID into the Source claim ID filter.

3. The list shows every transaction that touched this claim — outbound 837 + every related ack. The most recent is the freshest acknowledgment status.

4. Open the outbound 837 (the originating row). The Ack chain tab shows the full acknowledgment history.

Steps to find a transaction by ISA13

When a partner cites a specific interchange:

1. Paste the ISA13 into the ISA13 filter. The list shows the one matching transaction (ISA13 is unique per partner per direction).

2. Open the detail. Confirm direction and partner match what the partner is citing.

Steps to find a transaction by correlation

Useful when troubleshooting an event flow — e.g., "an auth request was queued at 10:32; what came of it?":

1. Look up the correlation ID in the source system (rcm-core authorization_request.auth_request_id, claim build event ID, etc.).

2. Paste into the Correlation ID filter. Every transaction emitted from this event is listed.

Validation

Check	Expected
Filter changes update the list immediately	Yes.
Segment trace renders the full envelope	Yes.
Parsed result is JSON-copyable	Yes.
Ack chain shows all related acks	Yes.

Troubleshooting

Symptom	Cause	Fix
Search by claim ID returns nothing	The claim was never built into a transaction (still CREATED in rcm-core)	Confirm in rcm-app's claim detail.
Search by ISA13 returns nothing	Wrong ISA13, or transaction was cleaned from active storage	Old transactions move to cold storage at >90d retention; ask a platform admin.
Segment trace shows fewer segments than the raw EDI	The renderer collapses repeated empty segments by default	Toggle "Show all segments" in the trace view.
Ack chain missing 999	Partner does not produce 999, or 999 has not yet arrived	Check capability (2.4).

Next

8.4 — Batches view