bradymiller wrote on Friday, November 08, 2013:
Hi Kevin,
Although it took awhile, I just committed your two commits (temp path fix and new codes fix to official codebase.
thanks,
-brady
OpenEMR
bradymiller wrote on Friday, November 08, 2013:
Hi Kevin,
Although it took awhile, I just committed your two commits (temp path fix and new codes fix to official codebase.
thanks,
-brady
OpenEMR
macula wrote on Thursday, February 06, 2014:
verification failed for 20140204_172375245_.edi
Received 1 files, accepted 0
ibr_era_html_page: failed verification for
kevmccor wrote on Sunday, February 09, 2014:
My code does not deal with the .edi extension. There are at least two possibilities: 1) your file is actually an 835 (era), 277 (status), or 999 (initial response) type; or 2) OfficeAlly mixes the edi types in a single file, which is a situation I did not anticipate. Since uploading files offers such an opportunity for bad stuff, there is a somewhat elaborate analysis before a file is “accepted.” If the file is one of the types accepted, change the extension from .edi to that type, e.g. .835; but if it is mixed types, then you will have to copy the ISA-IEA segment blocks into separate files. They could also be grouped by GS-GE segment blocks. The names should be the "20140204_{ISA[or GS] control number}.{835/277/999}. The ISA control number is field/element 13 in the ISA segment, I believe.