835 file parsing and Payer ID

Day-to-Day Users
#1

Good Evening all.

I have received my first few 835 response files through office Ally and I’m trying to read them into OpenEMR with mixed result.

One problem I see is that the payer_id is not being identified. The value is not showing up in TRN04 in any of the 835 files I have and it appears this is the only way that OpenEMR recognizes the payer.

Anyone else see this problem and have a solution?

Thanks,
Kyle

#2

I was specifically looking at the ar_session table which does not have the payer_id.

Apparently somewhere down stream it can correlate as the invoice shows the correct payer… is payer_id in ar_session still used?

#3

hi @KyleNave, payer id can have different contexts, the most common which you’re probably familiar with is the electronic payer id which helps route claims to the correct payers through clearinghouses. TRN04 is seldom used and maybe only in institutional cases.

In this case the payer id in ar_session is the openemr payer id from the insurance_data table which is sourced from insurance_companies.id but this might not be used in the era posting routine.