Review an Import Row

A row stops at import review when ClaimPod cannot decide something on its own. Until you resolve it, nothing from that row reaches your live data.

Before You Start

You need the User role and an import review queue with open items. Queues are named after the file they came from.

Resolve the Row

1. Open the import review queue.
2. Select an item in the Work Items rail. The workspace groups the row into Patient, Visit and Services, with the file name and row number above it.
3. Read the problem on the section that carries one. It names what could not be decided, such as an imported record matching an existing patient closely but not exactly.
4. Set the decision on each part that needs one. The choices are Link to Existing, Create New and Reject Row…, and The Queue Processor says what each does.
5. Correct any field the file got wrong.
6. Select Complete.

Result: the row promotes into patients, visits and services as though it had imported cleanly.

Caution

Rejecting is final for this run. The row is skipped and does not enter your data. If the file itself was wrong, fix the file and re-run the import rather than rejecting row by row.

Why a Row Stops at All

ClaimPod stages every row and promotes only what it can resolve alone, so a row you have not seen never becomes a silent bad record. That is the trade the claim loop makes: fewer records to trust blindly, some rows to decide. If a source suddenly stops every row, see An Import or Queue Is Stuck.

Related: The Queue Processor · Imports · Work a Queue Item · The Claim Loop