# Errors on X12, submission to Medicaid

**URL:** <https://community.open-emr.org/t/errors-on-x12-submission-to-medicaid/11949>\
**Category:** OpenEMR Development\
**Tags:** x12\
**Created:** [April 11, 2019, 1:51pm UTC](https://community.open-emr.org/t/errors-on-x12-submission-to-medicaid/11949 "2019-04-11T13:51:54Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![jjchawla](https://community.open-emr.org/letter_avatar_proxy/v4/letter/j/6bbea6/32.png) [@jjchawla](https://community.open-emr.org/u/jjchawla)\
**Post date:** [April 11, 2019, 1:51pm UTC](https://community.open-emr.org/t/errors-on-x12-submission-to-medicaid/11949/1 "2019-04-11T13:51:54Z")

</div>

Hello,

I’ve got to submit 837P Claims to NC Medicaid and get the following errors on a validation tool. Using 5.02 dev version and filled out the x12 parameters under Admin/Practice/X12 per the specifications guide. I understand there is some previous discussion on X12 topics but the posts are so long not sure if/where corrected code has been submitted. Note, this is all test data so no worry about PHI. Whoever can help, greatly appreciated. Thanks!

> 1 Element ISA03 (Security Information Qualifier) does not contain a valid identification code: ‘7D’ is not allowed. Segment ISA is defined in the guideline at position N/A.
> 
> This error was detected at:  
> Segment Count: 1  
> Element Count: 3  
> Characters: 18 through 20
> 
> **SNIP Type** : 2  
> **Severity** : Normal ISA_00_ _7D_ _ZZ_7DCD _ZZ_N CTRACKSBAT _190411_0113\*^_00501_ 025915754_0_T\*: Element: 03
> 
> * * *
> 
> Name: Security Information Qualifier  
> ID:  
> Standard Option: Mandatory  
> Type: Identifier  
> Min Length: 2  
> Max Length: 2  
> Must Use  
> 2 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 error was detected at:  
> Segment Count: 5  
> Element Count: 8  
> Characters: 263 through 265
> 
> **SNIP Type** : 1  
> **Severity** : Normal NM1_41_2\*YOUR CLINIC NAME HERE\*\*\*\*\*46 Element: 08
> 
> * * *
> 
> Name: Identification Code Qualifier  
> ID:  
> Standard Option: Relational  
> Type: Identifier  
> Min Length: 1  
> Max Length: 2  
> Must Use  
> 3 Element NM109 (Identification Code) is missing. This Element’s user option is ‘Must Use’. Segment NM1 is defined in the guideline at position 0200.
> 
> This Element was expected in:  
> Segment Count: 5  
> Element Count: 9  
> Character: 265
> 
> **SNIP Type** : 2  
> **Severity** : Normal NM1_41_2\*YOUR CLINIC NAME HERE\*\*\*\*\* 46M Element: 09
> 
> * * *
> 
> Name: Identification Code  
> ID:  
> Standard Option: Relational  
> Type: Alphanumeric  
> Min Length: 2  
> Max Length: 80  
> Must Use  
> 4 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 error was detected at:  
> Segment Count: 5  
> Element Count: 9  
> Characters: 265 through 265
> 
> **SNIP Type** : 1  
> **Severity** : Normal NM1_41_2\*YOUR CLINIC NAME HERE\*\*\*\*\* 46M Element: 09
> 
> * * *
> 
> Name: Identification Code  
> ID:  
> Standard Option: Relational  
> Type: Alphanumeric  
> Min Length: 2  
> Max Length: 80  
> Must Use  
> 5 If either of PER03, PER04 is present, then all must be present. The syntax rule P0304 of Segment PER is violated. Segment PER is defined in the guideline at position 0450.
> 
> This error was detected at:  
> Segment Count: 6  
> Element Count: 3  
> Characters: 274 through 276
> 
> **SNIP Type** : 1  
> **Severity** : Normal PER\*IC **TE** EM Element: 03
> 
> * * *
> 
> Name: Communication Number Qualifier  
> ID:  
> Standard Option: Relational  
> Type: Identifier  
> Min Length: 2  
> Max Length: 2  
> Must Use  
> 6 Element PER04 (Communication Number) is missing. This Element’s user option is ‘Must Use’. Segment PER is defined in the guideline at position 0450.
> 
> This Element was expected in:  
> Segment Count: 6  
> Element Count: 4  
> Character: 277
> 
> **SNIP Type** : 2  
> **Severity** : Normal PER_IC\*\*TE_M\*EM Element: 04
> 
> * * *
> 
> Name: Communication Number  
> ID:  
> Standard Option: Relational  
> Type: Alphanumeric  
> Min Length: 1  
> Max Length: 256  
> Must Use  
> 7 Value of element PER04 is incorrect. Expected value is Telephone Number (format is ‘10 digits’) when PER03=‘TE’. Segment PER is defined in the guideline at position 0450.
> 
> This error was detected at:  
> Segment Count: 6  
> Element Count: 4  
> Character: 277 through 277
> 
> **SNIP Type** : 2  
> **Severity** : Warning PER_IC\*\*TE_M\*EM Element: 04
> 
> * * *
> 
> Name: Communication Number  
> ID:  
> Standard Option: Relational  
> Type: Alphanumeric  
> Min Length: 1  
> Max Length: 256  
> Must Use  
> 8 If either of PER03, PER04 is present, then all must be present. The syntax rule P0304 of Segment PER is violated. Segment PER is defined in the guideline at position 0450.
> 
> This error was detected at:  
> Segment Count: 6  
> Element Count: 4  
> Characters: 277 through 277
> 
> **SNIP Type** : 1  
> **Severity** : Normal PER_IC\*\*TE_M\*EM Element: 04
> 
> * * *
> 
> Name: Communication Number  
> ID:  
> Standard Option: Relational  
> Type: Alphanumeric  
> Min Length: 1  
> Max Length: 256  
> Must Use  
> 9 If either of PER05, PER06 is present, then all must be present. The syntax rule P0506 of Segment PER is violated. Segment PER is defined in the guideline at position 0450.
> 
> This error was detected at:  
> Segment Count: 6  
> Element Count: 5  
> Characters: 278 through 280
> 
> **SNIP Type** : 1  
> **Severity** : Normal PER\*IC **TE** EM Element: 05
> 
> * * *
> 
> Name: Communication Number Qualifier  
> ID:  
> Standard Option: Relational  
> Type: Identifier  
> Min Length: 2  
> Max Length: 2  
> Used  
> 10 Value of element PER06 is incorrect. Expected value is E-mail address when PER05=‘EM’. Segment PER is defined in the guideline at position 0450.
> 
> This error was detected at:  
> Segment Count: 6  
> Element Count: 6  
> Character: 280 through 280
> 
> **SNIP Type** : 2  
> **Severity** : Warning PER\*IC **TE** EMM Element: 06
> 
> * * *
> 
> Name: Communication Number  
> ID:  
> Standard Option: Relational  
> Type: Alphanumeric  
> Min Length: 1  
> Max Length: 256  
> Used  
> 11 If either of PER05, PER06 is present, then all must be present. The syntax rule P0506 of Segment PER is violated. Segment PER is defined in the guideline at position 0450.
> 
> This error was detected at:  
> Segment Count: 6  
> Element Count: 6  
> Characters: 280 through 280
> 
> **SNIP Type** : 1  
> **Severity** : Normal PER\*IC **TE** EMM Element: 06
> 
> * * *
> 
> Name: Communication Number  
> ID:  
> Standard Option: Relational  
> Type: Alphanumeric  
> Min Length: 1  
> Max Length: 256  
> Used  
> 12 PRV segment is missing. Billing Provider Taxonomy is required for NCTracks
> 
> **SNIP Type** : 7  
> **Severity** : Normal HL_1\*\*20_1M Name: Billing Provider Specialty Information  
> 13 Value of element NM108 is incorrect. Expected value is ‘XX’ for covered providers when National Provider ID is mandated for use. Segment NM1 is defined in the guideline at position 0150.
> 
> This error was detected at:  
> Segment Count: 9  
> Element Count: 8  
> Character: 358 through 358
> 
> **SNIP Type** : 4  
> **Severity** : Warning NM1_85_2\*YOUR CLINIC NAME HEREM Element: 08
> 
> * * *
> 
> Name: Identification Code Qualifier  
> ID:  
> Standard Option: Relational  
> Type: Identifier  
> Min Length: 1  
> Max Length: 2  
> Used  
> 14 Unrecognized data was found in the data file as part of Loop 2010AA. The last known Segment was NM1 at guideline position 0150.
> 
> This error was detected at:  
> Segment Count: 10  
> Characters: 359 through 361
> 
> **SNIP Type** : 1  
> **Severity** : Normal N3 Name: Billing Provider Name  
> 15 Unrecognized data was found in the data file as part of Loop 2010AA. The last known Segment was NM1 at guideline position 0150.
> 
> This error was detected at:  
> Segment Count: 11  
> Characters: 362 through 364
> 
> **SNIP Type** : 1  
> **Severity** : Normal N4 Name: Billing Provider Name  
> 16 Segment N3 (Billing Provider Address) at guideline position 0250 is missing. This Segment’s user option is ‘Must Use’.
> 
> This Segment was expected after:  
> Segment Count: 11  
> Character: 364
> 
> **SNIP Type** : 2  
> **Severity** : Normal N4M Name: Billing Provider Address  
> 17 Segment N4 (Billing Provider City, State, ZIP Code) at guideline position 0300 is missing. This Segment’s user option is ‘Must Use’.
> 
> This Segment was expected after:  
> Segment Count: 11  
> Character: 364
> 
> **SNIP Type** : 2  
> **Severity** : Normal N4M Name: Billing Provider City, State, ZIP Code  
> 18 Segment REF (Billing Provider Tax Identification) at guideline position 0350 is missing. This Segment’s user option is ‘Must Use’.
> 
> This Segment was expected after:  
> Segment Count: 11  
> Character: 364
> 
> **SNIP Type** : 2  
> **Severity** : Normal N4M Name: Billing Provider Tax Identification  
> 19 Unrecognized data was found in the data file as part of Loop 2000B. The last known Segment was HL at guideline position 0010.
> 
> This error was detected at:  
> Segment Count: 13  
> Characters: 377 through 380
> 
> **SNIP Type** : 1  
> **Severity** : Normal SBR Name: Subscriber Hierarchical Level  
> 20 Segment SBR (Subscriber Information) at guideline position 0050 is missing. This Segment’s user option is ‘Must Use’.
> 
> This Segment was expected after:  
> Segment Count: 13  
> Character: 380
> 
> **SNIP Type** : 2  
> **Severity** : Normal SBRM Name: Subscriber Information  
> 21 Element NM103 (Name Last or Organization Name) is missing. This Element’s user option is ‘Must Use’. Segment NM1 is defined in the guideline at position 0150.
> 
> This Element was expected in:  
> Segment Count: 14  
> Element Count: 3  
> Character: 390
> 
> **SNIP Type** : 2  
> **Severity** : Normal NM1_IL_1_M_\*\*\*MI Element: 03
> 
> * * *
> 
> Name: Name Last or Organization Name  
> ID:  
> Standard Option: Relational  
> Type: Alphanumeric  
> Min Length: 1  
> Max Length: 60  
> Must Use  
> 22 Element NM104 is missing. It is recommended to be used when Subscriber is a person (NM102=‘1’). Segment NM1 is defined in the guideline at position 0150.
> 
> This element was expected in:  
> Segment Count: 14  
> Character: 391
> 
> **SNIP Type** : 2  
> **Severity** : Warning NM1_IL_1 **M** \*MI Element: 04
> 
> * * *
> 
> Name: Name First  
> ID:  
> Standard Option: Optional  
> Type: Alphanumeric  
> Min Length: 1  
> Max Length: 35  
> Used  
> 23 Element NM108 is missing. It is required when NM102 is ‘1’. Segment NM1 is defined in the guideline at position 0150.
> 
> This element was expected in:  
> Segment Count: 14  
> Character: 396
> 
> **SNIP Type** : 2  
> **Severity** : Normal NM1_IL_1\*\*\*\*\*MIM Element: 08
> 
> * * *
> 
> Name: Identification Code Qualifier  
> ID:  
> Standard Option: Relational  
> Type: Identifier  
> Min Length: 1  
> Max Length: 2  
> Used  
> 24 Element NM109 is missing. It is required when NM102 is ‘1’. Segment NM1 is defined in the guideline at position 0150.
> 
> This element was expected in:  
> Segment Count: 14  
> Character: 396
> 
> **SNIP Type** : 2  
> **Severity** : Normal NM1_IL_1\*\*\*\*\*MIM Element: 09
> 
> * * *
> 
> Name: Identification Code  
> ID:  
> Standard Option: Relational  
> Type: Alphanumeric  
> Min Length: 2  
> Max Length: 80  
> Used  
> 25 Element NM103 (Name Last or Organization Name) is missing. This Element’s user option is ‘Must Use’. Segment NM1 is defined in the guideline at position 0150.
> 
> This Element was expected in:  
> Segment Count: 15  
> Element Count: 3  
> Character: 406
> 
> **SNIP Type** : 2  
> **Severity** : Normal NM1_PR_2\*M\*\*\*\*\*PI Element: 03
> 
> * * *
> 
> Name: Name Last or Organization Name  
> ID:  
> Standard Option: Relational  
> Type: Alphanumeric  
> Min Length: 1  
> Max Length: 60  
> Must Use  
> 26 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 0150.
> 
> This error was detected at:  
> Segment Count: 15  
> Element Count: 8  
> Characters: 411 through 413
> 
> **SNIP Type** : 1  
> **Severity** : Normal NM1_PR_2\*\*\*\*\*\*PI Element: 08
> 
> * * *
> 
> Name: Identification Code Qualifier  
> ID:  
> Standard Option: Relational  
> Type: Identifier  
> Min Length: 1  
> Max Length: 2  
> Must Use  
> 27 Element NM109 (Identification Code) is missing. This Element’s user option is ‘Must Use’. Segment NM1 is defined in the guideline at position 0150.
> 
> This Element was expected in:  
> Segment Count: 15  
> Element Count: 9  
> Character: 413
> 
> **SNIP Type** : 2  
> **Severity** : Normal NM1_PR_2\*\*\*\*\*\*PIM Element: 09
> 
> * * *
> 
> Name: Identification Code  
> ID:  
> Standard Option: Relational  
> Type: Alphanumeric  
> Min Length: 2  
> Max Length: 80  
> Must Use  
> 28 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 0150.
> 
> This error was detected at:  
> Segment Count: 15  
> Element Count: 9  
> Characters: 413 through 413
> 
> **SNIP Type** : 1  
> **Severity** : Normal NM1_PR_2\*\*\*\*\*\*PIM Element: 09
> 
> * * *
> 
> Name: Identification Code  
> ID:  
> Standard Option: Relational  
> Type: Alphanumeric  
> Min Length: 2  
> Max Length: 80  
> Must Use  
> 29 Unrecognized data was found in the data file as part of Loop 2010BB. The last known Segment was NM1 at guideline position 0150.
> 
> This error was detected at:  
> Segment Count: 16  
> Characters: 414 through 416
> 
> **SNIP Type** : 1  
> **Severity** : Normal N3 Name: Payer Name  
> 30 Unrecognized data was found in the data file as part of Loop 2010BB. The last known Segment was NM1 at guideline position 0150.
> 
> This error was detected at:  
> Segment Count: 17  
> Characters: 417 through 419
> 
> **SNIP Type** : 1  
> **Severity** : Normal N4 Name: Payer Name  
> 31 Unrecognized data was found in the data file as part of Loop 2000C. The last known Segment was HL at guideline position 0010.
> 
> This error was detected at:  
> Segment Count: 19  
> Characters: 432 through 435
> 
> **SNIP Type** : 1  
> **Severity** : Normal PAT Name: Patient Hierarchical Level  
> 32 Segment PAT (Patient Information) at guideline position 0070 is missing. This Segment’s user option is ‘Must Use’.
> 
> This Segment was expected after:  
> Segment Count: 19  
> Character: 435
> 
> **SNIP Type** : 2  
> **Severity** : Normal PATM Name: Patient Information  
> 33 Element NM104 is missing. It is recommended to be used when Patient is a person (NM102=‘1’). Segment NM1 is defined in the guideline at position 0150.
> 
> This element was expected in:  
> Segment Count: 20  
> Character: 452
> 
> **SNIP Type** : 2  
> **Severity** : Warning NM1_QC_1\*PATIENTM Element: 04
> 
> * * *
> 
> Name: Name First  
> ID:  
> Standard Option: Optional  
> Type: Alphanumeric  
> Min Length: 1  
> Max Length: 35  
> Used  
> 34 Unrecognized data was found in the data file as part of Loop 2010CA. The last known Segment was NM1 at guideline position 0150.
> 
> This error was detected at:  
> Segment Count: 21  
> Characters: 453 through 455
> 
> **SNIP Type** : 1  
> **Severity** : Normal N3 Name: Patient Name  
> 35 Unrecognized data was found in the data file as part of Loop 2010CA. The last known Segment was NM1 at guideline position 0150.
> 
> This error was detected at:  
> Segment Count: 22  
> Characters: 456 through 458
> 
> **SNIP Type** : 1  
> **Severity** : Normal N4 Name: Patient Name  
> 36 Segment N3 (Patient Address) at guideline position 0250 is missing. This Segment’s user option is ‘Must Use’.
> 
> This Segment was expected after:  
> Segment Count: 22  
> Character: 458
> 
> **SNIP Type** : 2  
> **Severity** : Normal N4M Name: Patient Address  
> 37 Segment N4 (Patient City, State, ZIP Code) at guideline position 0300 is missing. This Segment’s user option is ‘Must Use’.
> 
> This Segment was expected after:  
> Segment Count: 22  
> Character: 458
> 
> **SNIP Type** : 2  
> **Severity** : Normal N4M Name: Patient City, State, ZIP Code  
> 38 Element CLM02 (Monetary Amount) has a data type of ‘Numeric’ (R). Leading zeros are not allowed. Segment CLM is defined in the guideline at position 1300.
> 
> This error was detected at:  
> Segment Count: 24  
> Element Count: 2  
> Characters: 485 through 489
> 
> **SNIP Type** : 1  
> **Severity** : Normal CLM_1-2_0.00_00:B:1YA_N\*Y Element: 02
> 
> * * *
> 
> Name: Monetary Amount  
> ID:  
> Standard Option: Optional  
> Type: Numeric  
> Min Length: 1  
> Max Length: 18  
> Must Use  
> 39 Value of sub-element CLM05-01 is incorrect. Expected value is from external code list - Place of Service (237). Segment CLM is defined in the guideline at position 1300.
> 
> This error was detected at:  
> Segment Count: 24  
> Composite Count: 5  
> Sub-Element Count: 1  
> Character: 492 through 494
> 
> **SNIP Type** : 5  
> **Severity** : Warning CLM_1-2_0.00_00:B:1YA_N\*Y Element: 01
> 
> * * *
> 
> Name: Facility Code Value  
> ID:  
> Standard Option: Mandatory  
> Type: Alphanumeric  
> Min Length: 1  
> Max Length: 2  
> Must Use  
> 40 Value of sub-element HI01-02 cannot be verified because there were no pointers to this code. Segment HI is defined in the guideline at position 2310.
> 
> This error was detected at:  
> Segment Count: 25  
> Composite Count: 1  
> Sub-Element Count: 2  
> Character: 514 through 521
> 
> **SNIP Type** : 4  
> **Severity** : Warning HI\*ABK:E083219 Element: 02
> 
> * * *
> 
> Name: Industry Code  
> ID:  
> Standard Option: Mandatory  
> Type: Alphanumeric  
> Min Length: 1  
> Max Length: 30  
> Must Use  
> 41 Unrecognized data was found in the data file as part of Loop 2310C. The last known Segment was NM1 at guideline position 2500.
> 
> This error was detected at:  
> Segment Count: 27  
> Characters: 553 through 555
> 
> **SNIP Type** : 1  
> **Severity** : Normal N4 Name: Service Facility Location Name  
> 42 Segment N3 (Service Facility Location Address) at guideline position 2650 is missing. This Segment’s user option is ‘Must Use’.
> 
> This Segment was expected after:  
> Segment Count: 27  
> Character: 555
> 
> **SNIP Type** : 2  
> **Severity** : Normal N4M Name: Service Facility Location Address  
> 43 Segment N4 (Service Facility Location City, State, ZIP Code) at guideline position 2700 is missing. This Segment’s user option is ‘Must Use’.
> 
> This Segment was expected after:  
> Segment Count: 27  
> Character: 555
> 
> **SNIP Type** : 2  
> **Severity** : Normal N4M Name: Service Facility Location City, State, ZIP Code  
> 44 Element SV102 (Monetary Amount) has a data type of ‘Numeric’ (R). Leading zeros are not allowed. Segment SV1 is defined in the guideline at position 3700.
> 
> This error was detected at:  
> Segment Count: 29  
> Element Count: 2  
> Characters: 574 through 578
> 
> **SNIP Type** : 1  
> **Severity** : Normal SV1_HC:99212_0.00_UN_1 Element: 02
> 
> * * *
> 
> Name: Monetary Amount  
> ID:  
> Standard Option: Optional  
> Type: Numeric  
> Min Length: 1  
> Max Length: 18  
> Must Use  
> 45 Composite SV107 (Composite Diagnosis Code Pointer) is missing. This Composite’s user option is ‘Must Use’. Segment SV1 is defined in the guideline at position 3700.
> 
> This Composite was expected in:  
> Segment Count: 29  
> Composite Count: 7  
> Character: 583
> 
> **SNIP Type** : 2  
> **Severity** : Normal

---

<div class="post-metadata">

**Author:** ![stephenwaite](https://community.open-emr.org/user_avatar/community.open-emr.org/stephenwaite/32/15754_2.png) [@stephenwaite](https://community.open-emr.org/u/stephenwaite)\
**Post date:** [April 11, 2019, 4:15pm UTC](https://community.open-emr.org/t/errors-on-x12-submission-to-medicaid/11949/2 "2019-04-11T16:15:24Z")

</div>

alot of these errors are easily understood, like the last one, there’s no charge $ on the 99212