aperezcrespo wrote on Wednesday, February 14, 2007:
Uploading ERA files creates files in era directory. These files however are named .edi. When I try to re upload the file it states that the file has not been processed. When and how does it get processed?
Thanks
Alfonso
sunsetsystems wrote on Wednesday, February 14, 2007:
After you upload the ERA file from the EOB Search page, a button "Process ERA File" appears at the bottom of that page. Clicking that button will then do the processing and produce a report.
Note that automated remittance processing is still experimental; it may or may not work for you.
aperezcrespo wrote on Wednesday, February 14, 2007:
Hi Rod
There is no “Process ERA File” button.
The ERA directory did not exist either, I had to create it and gave apache rw to it. I know its experimental but (as you may have noticed by all my postings) I’ve taken OEMR out for a real hard test drive.
My Live site wants to go for billing when NPI is required so we’re testing and training on billing. They also are setting up a bunch of new offices and the number of employees (providers, lab, and etc) will more than double by summer 08.
Thanks
Alfonso
sunsetsystems wrote on Wednesday, February 14, 2007:
So, the upload created the .edi file but you got no button and no error message? That’s very odd. Did you look at the very bottom of the page for the button? If so, it sounds like some debugging will be needed.
aperezcrespo wrote on Wednesday, February 14, 2007:
Not at all. In fact the only way I can get it to accept the file after using the browse button is by pressing enter while the cursor is in the File Text box.
Well clue me in as to where to look so I can begin debugging.
I’ll take a peek in the apache log files to start. Where else should I look?
Thanks
Alfonso
sunsetsystems wrote on Wednesday, February 14, 2007:
Aha. Try clicking the Search button instead of pressing Enter. I should probably rename that to "Submit".
Otherwise the relevant code is in interface/billing/sl_eob_search.php.
aperezcrespo wrote on Wednesday, February 14, 2007:
Ok got an error.
Now I get a "Unknown or unexpected Segment ID ISA*00* *00* *30*6606…"
Next?
Thanks
aperezcrespo wrote on Wednesday, February 14, 2007:
BTW the uploaded file ends up being named .EDI no name just ".edi" it this normal?
Thanks
Alfonso
sunsetsystems wrote on Wednesday, February 14, 2007:
The parser is expecting “|” instead of “*” as the separator between components within a segment. You’ll need to modify library/parse_era.inc.php for this (looks like line 50).
The ".edi" name is probably caused by the failure to parse the input.
aperezcrespo wrote on Thursday, February 15, 2007:
Rod
I made the change and I now get "SVC segment has unexpected qualifier", the file name is still ".edi". Wadayathink? And while on the subject: Couldnt there exist a 837 upload into OpenEMR? Wouldnt a utility of this type help users migrate from other systems that generate 837 file migrate to OpenEMR?
Alfonso
sunsetsystems wrote on Thursday, February 15, 2007:
This message suggests that some more work will be required to support the types of remittances that you receive. See the related comment in parse_era.inc.php where this message is generated.
Again, the ".edi" filename is a consequence of the parsing failure.
Re 837 upload, someone may find that useful but it would be quite a bit of work, and you’d still be missing all the chart notes and other things that are important to a practice but not for insurance billing.
aperezcrespo wrote on Thursday, February 15, 2007:
Arent 835s standard?
How can I debug the process to see where its hanging up and what changes need to be made? I couldnt locate anything in the apache logs.
Alfonso
sunsetsystems wrote on Thursday, February 15, 2007:
What’s in the SVC segment?
aperezcrespo wrote on Friday, February 16, 2007:
This is what it is.
SVC*HC:99205:::::OFFICE OUTPATIENT VISIT, NE*164.85*153.21**1
Alfonso
sunsetsystems wrote on Friday, February 16, 2007:
OK, I see. Another delimeter mismatch. Substitute ":" for "^" on line 287.
aperezcrespo wrote on Friday, February 16, 2007:
Hooray…
That seemed to be it…even the process button showed, files in the era folder have correct names and finally a EOB Posting report pops up.
We will begin testing with more data by next week (maybe tomorrow).
I will keep you posted.
You da man!
Thanks
Alfonso
xiaoanri wrote on Wednesday, February 18, 2009:
I am to start getting electronic ERA’s and will try to import to OpenEMR. On the Medicare electronic ERA set up form, it requests the info regarding what delimiters the software supports and seems give you choice, here is what I got from the form:
"The default delimiters returned on the electronic remittance advice are:
– * (2A hex value) for element delimiter
– > (3E hex value) for sub-element delimiter; and
– Line Feed (0A hex value) for segment delimiter.
If alternative values are required, please indicate below:
Element_________ Sub-element_________ Segment________"
Should I accept the default value for OpenEMR or need to put alternative values?
I am on version 2.9.1-dev
Thank you, any comments on importing ERA is appreciated!
Hui
jpmd wrote on Wednesday, February 18, 2009:
With some help from Rob we are currently able to upload ERA files from ZirMed without a problem for our clients. I am not sure about direct upload from Medicare. The files are generated on the ZirMed’s site and we then browse and upload them to OpenEMR from multiple payers seemlessly.
Jude A. Pierre, MD
www.phyaura.com
markleeds wrote on Wednesday, February 18, 2009:
Would preg_split instead of explode simplify the delimiter issue?
xiaoanri wrote on Monday, April 06, 2009:
I finally got the chance to try upload ERA function. The file i downloaded from United Healthcare is a .dat file. When I try to import it by first putting the link to the ERA file in the space and then do "search", it will pull ALL claims, and the payment info in the ERA file is not posted in the particular patient claim either. Would .DAT file appropriate to use here? and if so, what is wrong? Please help!
I am using Oemr2.9.1.