A claim can carry the correct procedure code and the correct ICD-10-CM code and still deny, because the payer never saw them connected. The diagnosis pointer is the field that ties one service line to the diagnoses that justify it. Point it at the wrong code, or at one the payer does not cover for that procedure, and the line reads as medically unnecessary.
What this covers
- On the CMS-1500 (02/12), Item 21 holds up to 12 ICD-10-CM codes lettered A through L, and Item 24E holds up to four letters per service line.
- On the 837P, the claim-level HI segment carries the diagnoses and SV107 on each service line carries up to four pointers, with SV107-1 naming the primary diagnosis for that line.
- Pointer values are positions, not codes: 1 points at HI01, 2 at HI02, and so on. X12 states that the number of pointers cannot exceed the number of diagnoses on the claim.
- A linkage failure is paid as CARC 11, the diagnosis is inconsistent with the procedure, or CARC 50, not deemed a medical necessity. Both are active on the current X12 list.
- Nevada Medicaid requires ABA claims to carry F84.0 or Q86.0, so an ABA line pointed at a symptom code fails a linkage edit rather than a documentation review.
The pointer does not repeat the diagnosis. It tells the payer which diagnosis to judge this line against.the link that decides medical necessity one service line at a time
A professional claim splits one story across two levels. Diagnoses sit at the claim level, in Item 21 of the CMS-1500 or the HI segment of the 837P. Procedures sit at the line level. The pointer is the only thing connecting them, and it is written by whoever builds the claim rather than by the clinician who documented the visit.
Where the diagnosis link lives on a claim
On the CMS-1500 (02/12), Item 21 holds the diagnosis codes, up to 12 of them, lettered A through L. Item 24E is the diagnosis pointer. The NUCC instruction manual says to enter the reference letter from Item 21 to relate the service line to the primary diagnosis, with the primary reference letter for each service listed first. The field holds four characters, so one line can point at four diagnoses, entered left justified with no commas between the letters.
The 837P carries the same structure in different clothes. The claim-level HI segment holds the diagnosis codes, with HI01 first, and each service line in loop 2400 carries an SV107 composite with four pointer positions. In X12’s own interpretation of that data element, request 2776, SV107-1 designates the primary diagnosis for the service line, the remaining pointers indicate declining importance, and acceptable values are 1 through 12, corresponding to HI01 through HI12. The same interpretation states that it is not compliant for the number of pointers to exceed the number of diagnoses on the claim.
NUCC instructions require the diagnosis codes on the first page of a multi-page CMS-1500 to be repeated on later pages, because only the first page’s codes may be used. A claim needing more than 12 diagnoses, or more than 50 service lines, has to be split.
The pointer is a position, not a code. Nothing in Item 24E or SV107 repeats the ICD-10-CM code; the value says which slot in the diagnosis list applies to that line. Both codes can be correct and the connection still wrong.
Getting the diagnosis list right is a medical coding task. Getting the pointer right is a claim-building task, and it fails on its own.
How a payer turns the pointer into a payment decision
Medical necessity edits work line by line. For each line, the payer reads the diagnosis positions the pointer names and asks whether those diagnoses support the procedure billed there. The answer comes from a written coverage policy rather than a reviewer’s judgment.
For Medicare, that policy is a local coverage determination with a companion billing and coding article. CMS describes the articles this way: they typically include procedure codes and ICD-10-CM diagnosis codes, and the code lists explain which services the policy applies to, the diagnosis codes for which the service is covered, and the codes for which it is not considered reasonable and necessary. A diagnosis absent from that list denies the line, whatever the note says.
Coding rules set the other half of the test. The ICD-10-CM Official Guidelines for Coding and Reporting put outpatient diagnosis selection in Section IV: list first the code for the condition chiefly responsible for the services provided, then codes for coexisting conditions that affected care. A claim built by copying the problem list gives the pointer a symptom code, a history code, or a code for a condition the visit did not address.
NCCI is a different family of edits. Procedure-to-procedure edits and medically unlikely edits test code pairs and units of service, not the diagnosis pointer. A clean NCCI report says nothing about linkage.
The linking errors that deny claims
Most pointer denials fall into a few patterns. The table maps each to what the payer’s edit sees and the adjustment that follows.
| Pointer pattern | What the payer’s edit reads | Adjustment you will see |
|---|---|---|
| No pointer on the line | No diagnosis is attached to this service | Rejection before adjudication, or CARC 16 with a remark such as M76 |
| Pointer names a symptom code | The line is billed for a sign rather than the condition treated | CARC 11, the diagnosis is inconsistent with the procedure |
| Pointer names a code outside the covered list | The procedure is not covered for that diagnosis under the policy | CARC 50, not deemed a medical necessity by the payer |
| Every line defaults to the first diagnoses | Unrelated services are linked to unrelated conditions | CARC 11, or a records request the note cannot answer |
| More pointers than diagnoses | SV107 references positions that do not exist in HI | Rejection as non-compliant before adjudication |
The default-pointer pattern costs the most because it is invisible. Software that fills Item 24E or SV107 with the first diagnoses on the claim produces claims that pass every code-level check. The error surfaces only at adjudication.
Specificity failures sit in the same family. Item 21 instructions say to use the greatest level of specificity, and RARC M81 says the same thing to the practice. An unspecified code behaves like a missing diagnosis when the covered list is built from specific codes.
CARC 11 and CARC 50 look alike on a remittance and mean different things. CARC 11 says the diagnosis and the procedure do not match. CARC 50 says the payer accepts the pairing but does not consider the service medically necessary.
The diagnosis a behavioral health line has to carry
Behavioral health and ABA claims concentrate this risk, because one condition drives coverage for a whole set of procedures. Nevada Medicaid states the rule in its Provider Type 85 billing guide: claims must be submitted with diagnosis code F84.0 (Autism Spectrum Disorder), Q86.0 (Fetal alcohol syndrome), or another condition for which ABA is recognized as medically necessary.
That is a claim-level requirement, and it still interacts with the line-level pointer. When ABA codes are on the claim, each line has to point at a diagnosis that supports it. A 97153 line pointed at a symptom code or an unrelated behavioral health diagnosis is judged against that code, and the authorization does not rescue it.
An approved authorization number in Item 23 or the 837P REF segment does not satisfy a diagnosis linkage edit, and Nevada Medicaid states that authorization does not guarantee payment of a claim. The payer still reads the pointer on every line, so an approved case can deny line by line.
The edits that catch pointer errors before submission
Pointer logic is testable before a claim leaves the building. Four moves cover most of the failures.
Derive Item 24E and SV107 from the note and the order that produced the service. If the software defaults the pointer, turn the default off and require a selection at charge entry.
For each payer and procedure, store the ICD-10-CM codes the policy covers, and refresh it when the payer revises the article.
Every line has at least one pointer. Every pointer value is less than or equal to the number of diagnoses on the claim. The first pointer on each line carries medical necessity. No pointer references a position with no diagnosis behind it.
Pull 20 to 30 lines per provider and compare the pointer against the note. Report the error rate as a percentage so you can tell whether a fix held.
- Every service line carries at least one pointer.
- The first pointer on each line is the diagnosis that supports medical necessity for that procedure.
- No pointer value exceeds the number of diagnoses on the claim.
- Each pointed-to diagnosis is on the payer’s covered list for that procedure.
- Codes are at the highest level of specificity the record supports.
- Coexisting conditions that affected the visit are on the claim alongside the first-listed code.
Pointer logic belongs inside the medical coding and billing workflow, not in a spreadsheet updated after a denial batch.
When a pointer denial arrives
The 835 reports the adjustment reason in the CAS segment with a group code that assigns responsibility. A CO group with CARC 11 tells you the payer treats this as a coding matter rather than a patient matter, so the amount is not billable to the patient.
Read the submitted 837P. If the pointer named the wrong diagnosis, the fix is a corrected claim, not an appeal.
Open the payer’s billing and coding article for the procedure and find the code. If it is listed and the record supports it, correct the claim.
NUCC Item 22 carries the frequency code and the payer’s original reference number. Code 7 replaces a prior claim, and code 8 voids one.
Cite the policy section and attach the documentation it asks for. A linkage error appealed without a coding argument reads as a request to override the policy.
Track outcomes by pattern rather than by claim. If CARC 11 concentrates in one provider’s lines, the problem is how that provider’s services are coded or linked. If it concentrates in one procedure, the problem is the covered list. Denial management turns that pattern into a fix.
Diagnosis linking questions billing teams ask
It is the field that ties one service line to the diagnoses on the claim. On the CMS-1500 it is Item 24E, where you enter the letters A through L that match Item 21. On the 837P it is the SV107 composite, where values 1 through 12 point at the positions of the codes in the claim-level HI segment.
Four. Item 24E holds four characters on the CMS-1500, and the SV107 composite carries four pointer positions. The limit is not a target. X12 states that the number of diagnosis pointers cannot exceed the number of diagnosis codes on the claim, so a line with four pointers on a two-diagnosis claim is non-compliant.
CARC 11, the diagnosis is inconsistent with the procedure. It has been active since January 1, 1995 on the X12 list, last modified July 1, 2017. It usually means the diagnosis is not on the payer’s covered list, the code is not specific enough, or the pointer named the wrong diagnosis.
No. NUCC instructions say the primary reference letter for each service should be listed first in Item 24E for that line, and different lines can point at different diagnoses. A common failure is a system that defaults every line to the first diagnoses on the claim, linking unrelated services to unrelated conditions.
Nevada Medicaid requires ABA claims to carry F84.0 (Autism Spectrum Disorder), Q86.0 (Fetal alcohol syndrome), or another condition for which ABA is recognized as medically necessary. When a 97153 line points at a symptom code or an unrelated behavioral health diagnosis, the line is judged against that code and fails medical necessity.
Correct it when the record contains a covered diagnosis that was not coded or not linked. Send a replacement claim with frequency code 7 and the original reference number in Item 22. Appeal when the billed diagnosis is correct and the payer’s policy excludes it, citing the coverage article’s own code list.
The bottom line
A claim denies on linkage when the payer cannot connect the service to a reason. The pointer is that connection, and it is set by whoever builds the claim. Get it right and the medical necessity argument never has to be made.
Is your claim scrubbing catching pointer errors before adjudication?
We read your 837P output line by line, map each procedure to the covered diagnosis list in your payers’ billing and coding articles, and show you which pointer errors are reaching the payer.
Request a free coding and denial auditThis article describes claim submission and coding practice as of September 2026 and is not a coverage guarantee; confirm the current policy for each payer and jurisdiction before changing your billing rules.
