Provider Claim Level File

InstaMed supports the ability to send payments (and denials) to providers (Explanation of Payment or EOP). These outbound payments consist of claims adjudicated by a health plan and owed to a provider.

In order to properly reflect the disposition of an adjudicated claim, issued via the InstaMed Disbursement Hub solution, InstaMed supports the generation of claim-level batch files.

For example, if a check payment, consisting of 5 claims, was issued for $1,000, each of these claims would be reported as an individual row in the batch file with a ‘Paid’ status. InstaMed will output another batch file in the future when the check is deposited to change the status of each of the claims from ‘Paid’ to ‘Settled’.

The specification below is used to report on the status of specific claims issued by InstaMed as part of a payment/835 transaction.

Files are output in a pipe delimited format and uploaded to client-specific SFTP directories.

Field #Field NameFormatMinMaxRequiredComment
1Record ID"IMCRA10"77Y
2ClaimIDAN118SInternal Claim ID REF*9A field
6ClaimPaymentDECSCLP04 - Available when transaction status is Paid
7PaymentDateAN88SYYYYMMDD, Available when transaction status is Paid
8DisbursementTraceNumberAN130STRN02 - Disbursed check/trace number to provider; Available when transaction status is Paid
9DisbursmentEntityAN1042STRN03:TRN04 - Available when transaction status is Paid
10FundingTraceNumberAN130SFrom original file -- TRN02
11FundingEntityAN1042SFrom original file -- TRN03:TRN04
12Payer NameAN135YN102 when N101 = PR
13Payee LastAN135YN102 when N101 = PE
14Payee FirstAN135S
15Payee Primary ID QualifierAN22YN103 when N101 = PE
16Payee Primary IDAN180YN104 when N101 = PE
17Patient Last NameAN135YNM103 when NM101 = QC
18Patient First NameAN135YNM104 when NM101 = QC
19Patient Middle NameAN125SNM105 when NM101 = QC
20Patient ID QualifierAN22YNM108 when NM101 = QC
21Patient IDAN180YNM109 when NM101 = QC
22StatusAN120YPAID: Payment was disbursed to provider
RETURNED: Returned payments
SETTLED: Settled payments
CANCELLED: Cancelled and Reissued card payments
PENDING APPROVAL: Payments that are available for approval in InstaMed Online
SUSPENDED: Suspended payments
PARTIALLY SETTLED: Partially settled payments
VOIDED: Payments were voided by client via their bank
EXPIRED: Expired claim payment card payments
STOPPED: Payments were stopped by client via their bank
REMOVED: Payments was removed from Pending Approval
24PaymentMethodAN130YACH, CHK, NON, Virtual Card
25Return CodeAN33SPopulated when Message Status = Returned
26Return ReasonAN1100SPopulated when Message Status = Returned
27Funding DateAN88SYYYYMMDD, Available with select funding models
28Funding StatusAN123SAvailable with select funding models
Notified: Email issued to Funding Entity (e.g. employer group) requesting funding
Ready for Funding: Transactions have been "settled" and funds are set to be collected (status is used with Presentment model)
Funded: NACHA Debit created to pull funding (funds to subaccount)
Ready for Replenishment: Transactions have been "settled" and funds are set to be collected (status is used with Issuance and Target Balance models)
Replenished: NACHA Debit created to pull funding (funds to disbursing account)
Date that print vendor placed item into mailstream; Always populated for CHK and VirtualCard
30Placeholder Field 6ANReserved for future use
31Placeholder Field 7ANReserved for future use
32Placeholder Field 8ANReserved for future use
33Placeholder Field 9ANReserved for future use
34Placeholder Field 10ANReserved for future use
35Placeholder Field 11DECReserved for future use
36Placeholder Field 12DECReserved for future use
37Placeholder Field 13DECReserved for future use
38Placeholder Field 14DECReserved for future use
39Placeholder Field 15DECReserved for future use