The Availity clearinghouse vendor ID for OpenEMR is V07432 (Victor-Zero-Seven-Four-Three-Two).
This was assigned by Availity for general use by users of OpenEMR. The Availity representative (Availity case #01005710) I contacted after receiving the e-mail notice that a number was assigned was not able to verify what agency actually assigned the number (Availity or someone else), but assured me that it would be good for anyone using OpenEMR 4.1+ submitting 5010 format claims.
This value is entered in your x-12 partner configuration PER06 value. It is verified good for Availity, but for other x12 partners you need to check for the appropriate value. If they do not give you a number, and say that you should use your Vendor’s ID, then this is the value you may use.
Sorry, I’ve been busy doing a couple of things on my own as much as I can but I am out of lead. Below is the error message I got
Error Initiator: HIPAA Loop: 1000B
Segment ID: NM1 Element #: 8
Version #: 5010A1 Error Message If either of
NM108, NM109 is present, then all must be present. The syntax rule P0809 of Segment NM1
is violated. Segment NM1 is defined in the guideline at position 0200. Invalid data: 46
Error Initiator: HIPAA Loop: 1000B
Segment ID: NM1 Element #: 9
Version #: 5010A1 Error Message Element NM10
9 (Identification Code) is missing. This Element’s user option is ‘Must Use’. Segment NM
1 is defined in the guideline at position 0200.
Error Initiator: HIPAA Loop: 1000B
Segment ID: NM1 Element #: 9
Version #: 5010A1 Error Message If either of
NM108, NM109 is present, then all must be present. The syntax rule P0809 of Segment NM1
is violated. Segment NM1 is defined in the guideline at position 0200.
This is the latest error message I got from Availity. Why are they so particular?
Your batch failed due to invalid data in your interchange:
“Invalid control number in ISA13: 0. Element ISA13 (Interchange Control Number) includes non-numeric characters. The Element has a data type of ‘Numeric with implied decimal’ (N0).”
Your ISA13 cannot be ‘0’. These settings are often not set by the user. I advise contacting your software vendor for help with correcting interchange data settings.