ty, state and zip. You might be wondering why this would be different from the address in fields 7 - 11. The answer is simple. In some cases, the person receiving payment is not the same person as the one sending the claims. In this case, the address of the person where the check needs to go has to be sent.

BA1 field 18, positions 227 - 236, is the pay to provider phone number. This is required in case there is a problem with the check and the carrier needs to call the person who will be

In the field of medical billing, the BA1 record, for the electronic transmission of claims, sends additional provider data to the carrier. If you're wondering why this record needs to exist when we already have a BA0 record sending provider data, a short explanation, before actually reviewing the record itself, is in order.

NSF specifications are very clear. Each record can only be 320 characters long. Because of this, there wasn't enough room to send all the provider data in one record. So the provider information was broken up into two records, the BA0 and the BA1.

BA1 field 1, positions 1 - 3, is the record type, which in this case is the BA1 record and must be filled in as such.

BA1 field 2, positions 4 - 18, is the provider ID. Even though this was transmitted in record BA0, it must be transmitted again to identify the provider. Government and their regulations.

BA1 fields 3, 4 and 5, positions 19 - 31, identify the batch itself, which includes the batch type, batch number and batch ID. This info must match the info sent in BA0.

BA1 field 6, positions 32 - 34, is the provider's type of organization. This is another code that the provider can find from a list of codes. There are many organization types and it is critical that the right type be entered or the claim will most certainly be denied.

BA1 fields 7 - 11, are the provider's address fields, which include city, state zip as well as the actual street address. The fields are large enough so that abbreviations are usually not necessary. However, should a provider have a street address that is too long, they are allowed to abbreviate things like St. for street, Rd for road and so on.

BA1 field 12, positions 126 - 135, is the provider's phone number. Again, this is a required field and must be included in case the carrier needs to call the provider for any reason.

BA1 fields 13 - 17, positions 136 - 226, is the provider's pay to address, which includes street name, city, state and zip. You might be wondering why this would be different from the address in fields 7 - 11. The answer is simple. In some cases, the person receiving payment is not the same person as the one sending the claims. In this case, the address of the person where the check needs to go has to be sent.

BA1 field 18, positions 227 - 236, is the pay to provider phone number. This is required in case there is a problem with the check and the carrier needs to call the person who will be

o the provider information was broken up into two records, the BA0 and the BA1.

BA1 field 1, positions 1 - 3, is the record type, which in this case is the BA1 record and must be filled in as such.

BA1 field 2, positions 4 - 18, is the provider ID. Even though this was transmitted in record BA0, it must be transmitted again to identify the provider. Government and their regulations.

BA1 fields 3, 4 and 5, positions 19 - 31, identify the batch itself, which includes the batch type, batch number and batch ID. This info must match the info sent in BA0.

BA1 field 6, positions 32 - 34, is the provider's type of organization. This is another code that the provider can find from a list of codes. There are many organization types and it is critical that the right type be entered or the claim will most certainly be denied.

BA1 fields 7 - 11, are the provider's address fields, which include city, state zip as well as the actual street address. The fields are large enough so that abbreviations are usually not necessary. However, should a provider have a street address that is too long, they are allowed to abbreviate things like St. for street, Rd for road and so on.

BA1 field 12, positions 126 - 135, is the provider's phone number. Again, this is a required field and must be included in case the carrier needs to call the provider for any reason.

BA1 fields 13 - 17, positions 136 - 226, is the provider's pay to address, which includes street name, city, state and zip. You might be wondering why this would be different from the address in fields 7 - 11. The answer is simple. In some cases, the person receiving payment is not the same person as the one sending the claims. In this case, the address of the person where the check needs to go has to be sent.

BA1 field 18, positions 227 - 236, is the pay to provider phone number. This is required in case there is a problem with the check and the carrier needs to call the person who will be

, batch number and batch ID. This info must match the info sent in BA0.

BA1 field 6, positions 32 - 34, is the provider's type of organization. This is another code that the provider can find from a list of codes. There are many organization types and it is critical that the right type be entered or the claim will most certainly be denied.

BA1 fields 7 - 11, are the provider's address fields, which include city, state zip as well as the actual street address. The fields are large enough so that abbreviations are usually not necessary. However, should a provider have a street address that is too long, they are allowed to abbreviate things like St. for street, Rd for road and so on.

BA1 field 12, positions 126 - 135, is the provider's phone number. Again, this is a required field and must be included in case the carrier needs to call the provider for any reason.

BA1 fields 13 - 17, positions 136 - 226, is the provider's pay to address, which includes street name, city, state and zip. You might be wondering why this would be different from the address in fields 7 - 11. The answer is simple. In some cases, the person receiving payment is not the same person as the one sending the claims. In this case, the address of the person where the check needs to go has to be sent.

BA1 field 18, positions 227 - 236, is the pay to provider phone number. This is required in case there is a problem with the check and the carrier needs to call the person who will be

ugh so that abbreviations are usually not necessary. However, should a provider have a street address that is too long, they are allowed to abbreviate things like St. for street, Rd for road and so on.

BA1 field 12, positions 126 - 135, is the provider's phone number. Again, this is a required field and must be included in case the carrier needs to call the provider for any reason.

BA1 fields 13 - 17, positions 136 - 226, is the provider's pay to address, which includes street name, city, state and zip. You might be wondering why this would be different from the address in fields 7 - 11. The answer is simple. In some cases, the person receiving payment is not the same person as the one sending the claims. In this case, the address of the person where the check needs to go has to be sent.

BA1 field 18, positions 227 - 236, is the pay to provider phone number. This is required in case there is a problem with the check and the carrier needs to call the person who will be

ty, state and zip. You might be wondering why this would be different from the address in fields 7 - 11. The answer is simple. In some cases, the person receiving payment is not the same person as the one sending the claims. In this case, the address of the person where the check needs to go has to be sent.

BA1 field 18, positions 227 - 236, is the pay to provider phone number. This is required in case there is a problem with the check and the carrier needs to call the person who will be receiving it.

BA1 field 19, positions 237 - 320, is national filler and must be left blank or the claims will be denied without question.

This concludes the specs for the provider record. In our next article, we'll be moving on to the CA0 record, which is the patient data. This is where things really get interesting.