tsvas wrote on Sunday, March 27, 2011 : Can someone help me how to use “Report - Eligibility 270 Inquiry Batch”. I guess it automatically pulls insurance eligibility. When I used my clearing house as X12 partner, it is giving error in red “* Clearing house info required for EDI 270 batch creation”…

you mean goes from 000000001 to 000000002?

My apologies, I mean what is going to update the database table with a new number? The table is not auto-incremented. I am going to have to think this one out. i will look through the code to see how generate_id is used. [image] it looks like we would have to go into the sql.inc and create fun…

is it in library/encounter_events.inc.php?

It is used in that file but that is not where the class originates. I am looking for the public function GenID($table) { make and ID and store it in this table that was passed in }

Unsure why we need to track ISA13 anywhere but the generator. Isn’t that control increment only needed within the request? Can’t reference Office Ally real time because Office Ally doesn’t support batch request. I emulate batch by sending request one at a time.

genID comes from the AddoDB class In the codebase for MySQL it comes from vendor/adodb/adodb-php/drivers/adodb-mysqli.inc.php L452.

In case your unfamiliar with them, sequences are another way of doing auto-incremented ids, Oracle and other RDBMS engines use them heavily.

[image] sjpadgett: Unsure why we need to track ISA13 anywhere but the generator. Isn’t that control increment only needed within the request? I believe it’s the GS segment that has the control number that should be tracked. Say your submission fails and you have to find out what batch it was …

Okay but believe that’s in the response. I thought the problem is that they use the ISA13 control id within the batch request to delimit a new request so must be unique within the session. Simply increment in the generator. Anyway, I can’t read Sherwin screenshot of spec. If I could I’d have a bett…

Here is the guidebook edi_guide.pdf 2.09 MB The pages referenced are 56 -57 IEA02 and ISA13 must be the same number They suggested that there be one entry for claims and one entry in the x12 partners’ settings for eligibility. We should not be using the on…

OpenEMR Community

Report - Eligibility 270 Inquiry Batch

Management and Administration

show post in topic

Home
Categories
Guidelines
Terms of Service
Privacy Policy

Powered by Discourse, best viewed with JavaScript enabled