The ICD-10-CM code for an unspecified headache is R51.9, Headache unspecified. Use code R51.9 when a health care provider has documented a headache, but has not provided a more specific headache diagnosis. Code R51.0 is assigned when the health care provider documents a headache, with either an orthostatic or a positional component, and the headache is not classified elsewhere.
Do not assign code R51.9 when the documentation describes a headache syndrome that is more specific, such as migraine, a tension type headache, a cluster headache, a headache associated with a traumatic brain injury, or other medically diagnosed headaches. The Tabular List and the Alphabetic Index of ICD-10-CM should be consulted to assign the appropriate code.
Headache ICD 10 Codes at a Glance
The codes in the table below may be useful to you. Note that some of the codes shown are categories or groups. The final coding diagnosis is found in the ICD-10-CM Tabular Listing. It is important that the final code be determined prior to filing the claim.
| ICD-10-CM code/category | Description | Typical coding use |
|---|---|---|
| R51.9 | Headache, unspecified | Provider documents headache without a more specific type |
| R51.0 | Headache with orthostatic component, NEC | Positional/orthostatic headache not classified elsewhere |
| G43.- | Migraine | Provider establishes a migraine diagnosis |
| G43.009 | Migraine without aura, not intractable, without status migrainosus | Documentation supports all listed characteristics |
| G43.109 | Migraine with aura, not intractable, without status migrainosus | Migraine with documented aura and stated characteristics |
| G43.909 | Migraine, unspecified, not intractable, without status migrainosus | Migraine is diagnosed but type is not further specified |
| G44.0- | Cluster headache syndrome | Provider diagnoses a cluster headache syndrome; select the appropriate child code |
| G44.1 | Vascular headache, NEC | Documented vascular headache not classified elsewhere |
| G44.2- | Tension-type headache | Use the child code matching episodic/chronic, intractability and other documented details |
| G44.3- | Post-traumatic headache | Headache documented as resulting from trauma; further specificity may be required |
| G44.4- | Drug-induced headache | Provider links the headache to medication/drug use and documentation supports the applicable code |
| G44.81 | Hypnic headache | Provider specifically diagnoses hypnic headache |
| G44.83 | Primary cough headache | Provider specifically diagnoses primary cough headache |
| G44.86 | Cervicogenic headache | Provider diagnoses cervicogenic headache |
| G44.89 | Other specified headache syndrome | A specified headache syndrome not classified elsewhere |
This table shouldn’t replace the current ICD-10-CM Index and Tabular List. It is a quick reference for understanding where common headache diagnoses generally fall.
R51.9: The Main ICD 10 Code for Unspecified Headache
R51.9 indicates an unspecified headache.
When an individual asks what code to assign for a headache, this is the code they are most likely looking for.
However, the presence of the term “unspecified” is important and should be considered.
The assignment of this code indicates that a headache was documented, but no specific code for that headache is reported elsewhere.
For example, a provider may document the following:
“Patient reports a headache. Symptoms have been intermittent for the last 3 days and the provider is unable to determine the cause of the headache.”
In this instance, if this is an outpatient visit and no other headache diagnosis is made, it would be appropriate to assign code R51.9.
In contrast, if a diagnosis of migraine without aura and not intractable, and not status migrainosus, is made, then assigning code R51.9 would not be appropriate, since the migraine has been documented.
Coding headache related disorders is often complex and this is often the most difficult area of headache coding.
Is R51.9 billable?
R51.9 is an ICD-10-CM code that has replaced the old, nonspecific code R51.
Adding R51.9 to a service code doesn’t ensure that the service will be reimbursed. Several factors can contribute to service not being reimbursed. Some of these factors may include type of service, medical necessity, the rules set by the payer, the adequacy of documentation, benefits offered by the payer and other aspects.
It is important to understand the difference between the two.
Just because a service fails to be reimbursed does not invalidate the diagnosis code.
There may be sufficient clinical evidence for assigning a diagnosis code but a payer may not cover the associated service.
R51.9 vs R51.0: Don’t Treat Them as Interchangeable
The distinction is straightforward once you focus on the documentation.
R51.9 Headache, unspecified
This code is assigned when a provider documents a headache but is unable to determine the specific headache disorder, or if the orthostatic/positional feature of the headache is described by R51.0.
R51.0 Headache with orthostatic component, not elsewhere classified
This code is assigned when a headache is documented and the feature of orthostatic/positional nature is not attributed to other codes.
The nature of the documentation may state that the patient’s pain gets worse when he/she assumes the upright position and better when he/she assumes the lying down position.
The coder is not to assume that an orthostatic headache is documented if the provider does not state that the headache is positional or orthostatic.
Quick comparison
| Documentation | Likely direction |
|---|---|
| “Headache” | R51.9 |
| “Head pain, type undetermined” | R51.9 may be appropriate |
| “Positional headache, NEC” | Review R51.0 |
| “Orthostatic headache, NEC” | Review R51.0 |
| “Migraine with aura…” | Review G43.-, not simply R51.9 |
| “Tension-type headache…” | Review G44.2- |
| “Cervicogenic headache” | Review G44.86 |
The final code always depends on the full record and current code set.
R51 Changed: Why Older References Can Cause Confusion
Veteran coders that have worked with headache claims have likely encountered R51 as “Headache” and may not even recall the prior version of the code.
One of the reasons old articles may still show R51 as the final code is because of the older code structure.
R51 was revised to include the following codes:
- R51.0 Headache with an orthostatic component, NEC
- R51.9 Headache, NEC
So old articles may show R51 as the final code; however, headache documentation should be searching for one of the codes above for the most specific code.
When editing old templates or reference materials, be on the lookout for old, stale, and lone R51 codes and update or remove them. Old articles may have old, and outdated code structures that lead to erroneous coding.
Symptom Code or Definitive Headache Diagnosis?
This is the principal coding concern.
Migraines and other named headache syndromes are classified in other places, such as in codes G43 and G44.
In cases in which the provider has assigned a specific diagnosis, the coder must check the Alphabetic Index to see if that diagnosis has an entry in the Tabular List. If the diagnosis does have an entry in the Tabular List, then the symptom code does not need to be assigned.
R51.9 is a symptom code.
Example: Unspecified Headache
A patient is brought in for an evaluation for a new onset headache. The evaluating provider has not been able to determine if the headache is migraine, tension, or other type of headache syndrome.
Diagnosis: Headache
Coding Consideration: R51.9 may be appropriate.
Example: documented migraine
The provider has documented:
Migraine without aura, not intractable, without status migrainosus.
That documentation provides a level of detail about the migraine that is substantively more accurate than a code of R51.9.
Coders shouldn’t make diagnoses
The coder must not diagnose based on ambiguous information
There are several examples of coder traps regarding situations where a coder is presented with clinically relevant information but cannot make a clinical diagnosis.
The following information is provided:
- One sided pain
- Nausea
- Photophobia
- Throbbing pain
A provider may conclude that a patient is experiencing a migraine based on the information provided. However, a coder cannot assign a diagnosis of migraine based on symptoms and a provider’s documentation of a “headache.”
A diagnosis is only assigned based on positive rules of coding and the information provided by the Provider.
Documentation of a query by the Provider is dependent on the policies of the payer.
Migraine ICD-10-CM Codes: Specificity Matters
The G43 family of codes better represents the distinctions in clinical information than R51.9. Therefore, the description of migraine coding in this family is more detailed than in R51.9.
Clinicians should consider the following when assigning codes from the G43 family:
- Is there an aura?
- Is it an intractable migraine?
- Is it migrainosus?
- Are there other migraine variants?
These variants include migration without infarction, hemiplegic migraine, basilar migraine, migraine with brain stem aura, and other migraines of a listed site.
G43.009 indicates the presence of a migraine without aura that is not intractable and is not migrainosus.
Migraine with aura that is not intractable and is not migrainosus is coded as G43.109.
Aura
If the provider has documented the code G43.11 for migraine with aura, review the applicable branch.
Do not add “with aura” to the code, unless the patient has reported an isolated visual complaint and the diagnosis was migraine with aura by the provider.
Intractable versus not intractable
Code set determines intractable or non-intractable migraine.
Coders should refer to the terminology of ICD-10-CM and the documentation of the provider. It is not coders’ responsibility to evaluate if a headache is intractable.
Sometimes a patient may state their headache is “the worst headache of my life” or “most severe headache.” This does not justify assigning the code for intractable headache. It is imperative that the concept of intractability and the concept of severity should be differentiated.
Status migrainosus
Code selection in status migrainosus branches is also affected by status migrainosus.
Clinical records must support this condition. Code status migrainosus only when headache duration and severe nature of the headache are clearly documented, e.g., “headache of several days’ duration,” rather than vague, nonspecific comments such as “severe headache.”
Practical migraine documentation checklist
The specifics in migraine diagnosis that can be useful to a coder include:
- The type of migraine
- Whether or not auras are present
- Intractability
- The presence of migrainosus
- Frequency and chronicity
- Symptoms that co-occur and correlate
- How migraine is treated and how it responds to treatment
Coders try to understand as much as they can about the patient to interpret the ICD-10-CM code most accurately.
Tension-Type Headache Codes
Tension-type headaches are coded in this chapter as G44.2.
Using only the category number again will not always provide adequate code assignment. More specific codes identify if the condition is episodic or chronic and if the condition is intractable.
Pain which is described as pressure-like can also be coded as R51. The assigned code will ultimately be determined by the description provided by the doctor and the definition provided in the chapter.
Although a tentative diagnosis of tension-type headache would be appropriate based on the documentation in this example, this type of provider note may not always be sufficient for coding.
If documentation states the condition as “chronic tension-type headache, not intractable” then coding specificity is established.
Documentation worth capturing
Relevant elements for a documented tension-type headache may include, but are not limited to:
- Whether the headaches are episodic or chronic
- If the headaches are intractable
- How frequently the headaches occur
- The duration of the headaches
- Any other headache-related symptoms that occur at the same time (associated findings)
- If the headaches respond to treatment
The coder is not responsible for determining which headache phenotype the patient may have. The goal is to provide an accurate description of the headache diagnosis that was reported.
Cluster Headache Coding
Code syndromes of cluster headache within G44.0-.
Stopping at the parent category is not advisable if there is a more specific code for the condition, documented by additional information.
Pertinent information that may be documented includes, but is not limited to:
- The chronic or episodic nature of the cluster.
- Intractability of headaches.
- The nature of attacks.
- Other clinical findings.
Common errors in headache coding consist of stating that a category or code incomplete for cluster headaches does not allow for specific coding of cluster headache syndromes.
The condition is coded to the highest level of specificity allowed by the Index, and if a code is assigned, the Tabular List should be consulted for validation and instructions.
Cervicogenic Headache: G44.86
G44.86 Cervicogenic headache is a code for headache caused by issues in the upper neck. This code is more specific than the code for Unspecified headache (R51.9).
Use this code when a provider has indicated cervicogenic headache as the final diagnosis.
Coders should be familiar with the assessment provided by the provider and not make arbitrary assumptions while coding.
Cervicogenic headache is diagnosed by a provider and cannot be determined by a coder based on a description of neck pain and a headache.
Coders may refer to the assessment; however, if the assessment includes information about neck pain and a headache, the coder must not make the assumption that cervicogenic headache is present.
From the information available, it is clear that cervicogenic headache is diagnosed by a provider; it is not assignable by a coder.
Post-Traumatic Headache
Post-traumatic headaches are in the G44.3- group.
Coding this type of headache may require more than just the fact that the patient suffered a headache after suffering an injury.
Review the patient documentation for the specific post-traumatic headache condition and the requirements of the code in the current code set.
Example
patient suffered a head injury and is experiencing a headache.
If the provider assigns the diagnosis of post-traumatic headache, then the code in the G44.3- family should be assigned instead of assigning R51.9.
If the provider merely documents the two conditions, headache and injury, without providing the relationship, then the coder can not assume there is a relationship.
This is an important distinction that impacts compliance.
Drug-Induced and Medication-Related Headaches
Code headaches as G44.4-drug induced headache.
These cases require additional documentation to determine appropriate code assignment.
The record must demonstrate the relationship to the medication and the headache.
In other situations, a code for the headache may need to be assigned in addition to code assignment for the medication.
It may be appropriate to assign codes for complications of therapy, accidents, injuries and poisoning, and/or for the medication.
Although a medication may be documented on the patient’s medication list, this does not always signify the medication caused the headache.
It is the responsibility of the provider to document the relationship.
Other Specified Headache Syndromes
G44 encompasses a number of other headache disorders in addition to the more common ones.
These include:
- Vascular headache, etc.
- Hypnic headache
- Primary cough headache
- Cervicogenic headache
- Other specified headache disorders
Coders, typically, look only for R51.9. However, in this instance, the focus should be on the headache disorder documented. The Alphabetic Index should then be used to determine the appropriate code. The code should be validated in the Tabular List.
Primary Versus Secondary Headache: Why the Distinction Matters
In medicine, headaches are classified as primary or secondary.
Examples of primary headache disorders include migraine, tension and/or cluster headaches.
Headaches are considered secondary when they are associated with an underlying condition or situation.
There is a common coding convention to state that the cause of the headache, and not the headache itself, should be coded.
However, the headache code may be more appropriate in specific situations.
These situations are impacted by:
- the diagnoses that were given
- the place in which the service occurred
- the reason the service was requested
- relevant guidelines for the ICD-10-CM
- the order in which diagnoses are listed
- the notes in the Tabular List
- the policies of the payer or plan, if coverage is given
Coding conventions state that, in general, code the headache rather than the cause of the headache.
Example: Headache and Sinusitis
Imagine a patient comes to practice with a headache and facial pressure. The provider diagnoses this case of facial pressure and headache as sinusitis.
It would be incorrect to call this case a sinus headache and assign a headache syndrome code. Sinus headache is a subset of sinusitis and the code for sinusitis should be assigned based on the relevant coding guidelines.
If the sinusitis resolves, and the headache persists and requires evaluation, whether the headache should be reported and coded would depend on the analysis of the circumstances and coding policy.
An example like this shows that the recommendations in many coding blogs should not be blindly followed. It is not always appropriate to assign a universal headache code to every case of so-called “sinus headaches.”
Excludes1 and Excludes2: A Frequently Misunderstood Part of Headache Coding
Excludes notes are important because they show how conditions are connected to one another in the classification system.
Excludes1
Generally, an Excludes1 note indicates that the condition described in the note is not represented or coded where the condition is described above the note. For example, in the note “Excludes1 condition P is not present at this site” it indicates that condition P is coded at some other site or location. The classifications and/or condition descriptions in the classifications are mutually exclusive.
Excludes2
An Excludes2 note indicates that the described condition is not related to the condition described by the code and that condition may coexist with the described code condition.
This is important to understand for assigning codes to R51.
There may be differences in the wording of Excludes notes for conditions described in older publications because the definitions for R51 were modified when R51.0 and R51.9 were created. As a result, it is recommended that the current fiscal year’s Tabular List be consulted for the latest definitions.
Don’t exclusively use exclusion notes to assist you in coding
Exclusion notes are used to classify a patient record, and do not provide a diagnosis.
Let’s say a patient has a headache. Just because the exclusion note mentions migraine, does not mean you would assign a code for migraine.
The diagnosis would be determined by information documented in the patient record and/or the health care provider.
The medical record would take precedence over the exclusion note in determining a patient’s diagnosis.
Headache Documentation That Makes Coding Easier
The best way to improve headache coding is to address the clinical documentation that serves as the basis for coding. Often, notes may not provide sufficient information to assign headache codes.
Given the information below is documented, coding could be assigned.
1. Type of headache
If a diagnosis of a particular type of headache has not been made, it is generally not appropriate to generate a diagnosis, for example, by documenting “headache of unknown cause.” In these cases, an undefined code may be appropriate. These codes include R51.9, Headache, unspecified and R52.9, Other unspecified headache.
2. Onset
Were the headaches:
Acute?
Sub-acute?
Gradual?
3. Duration of headaches
Indicate the episode duration. If the patient has had recurring headaches, describe the headache history and the prior headaches’ characteristics.
4. Frequency
Is the headache constant? Intermittent?
How many headaches does the patient have in a year?
How many headaches occur in a month?
How many headaches occur in a week?
5. Where do the patient’s headaches occur?
Do the headaches occur on both sides?
Do the headaches occur on the left side?
Do the headaches occur on the right side?
Do the headaches occur in the back of the head?
Are the headaches widespread?
Not all of the information above is necessary to code headaches. Headache coders should not make a headache diagnosis based on where a patient is experiencing a headache.
6. Associated Symptoms
Possible symptoms may include:
- Nausea
- Vomiting
- Photophobia
- Phonophobia
- Aura
- Alterations in vision
- Other neuromuscular symptoms
These symptoms assist in constructing the clinical canvas.
7. Intractability
Intractable means the headache is unrelenting.
It is important to indicate if the headache is intractable for the type of headache documented.
Coders will not determine if the headache is intractable from the history of the headache.
8. Status Migrainosus
Migrainosus means the headache is unremitting.
If the headache is of the migraine type, and is of this nature, then status migrainosus should be documented.
9. Position or Postural Headache
If headache is position or postural and this feature is clinically salient, this should be documented.
This may impact the selection of R51.0.
10. Relationship to injury or other condition
If the headache is determined to be of a traumatic nature, or is caused by other conditions, the relationship should be explained.
Coding Scenarios From Everyday Practice
Rules become easier to remember when they’re attached to a chart.
Scenario 1: Unspecified headache at an initial visit
Documentation:
The patient reports headaches for the past two days. No headache syndrome has been determined.
Coding Direction:
Headache, unspecified (R51.9) may be appropriate since headache has been documented, but no syndrome has been determined.
Common Mistake:
Coding migraine when migraine has not been diagnosed. Coding migraine may occur when other symptoms of migraine are documented (e.g. visual changes), but there has not been a confirmatory diagnostic statement.
Scenario 2: Orthostatic headache
Documentation:
“Positional headache. Symptoms are position dependent and more severe when in an upright position and improve when in a recumbent position. Headache of orthostatic origin, NEC.”
Coding direction:
References made to R51.0 should be reviewed.
Common mistake:
Selecting R51.9 in the absence of documentation that distinguishes R51.0.
Scenario 3: Migraine without aura
Documentation:
“Migraine without aura, not intractable, without status migrainosus.”
Coding direction:
code to G43.009
Common mistake:
Coders will report R51.9 because the phrase “headache” is found elsewhere in the note.
Scenario 4: Migraine with aura
Documentation:
“Migraine with aura, not intractable, without status migrainosus”
Coding Direction:
Report with code G43.109.
Common Mistake:
Reporting a migraine-without-aura code or an unspecified code for headache.
Scenario 5: Symptoms sound like migraine but diagnosis doesn’t say migraine
Documentation:
“Throbbing unilateral headache, nausea and light app. headache”
Coding Direction:
Do not code a diagnosis of migraine. Code to the documented assessment and request, if applicable, migration headache within your organizational rules.
Lesson Learned:
Just because there are clinical indicators of a particular condition does not mean the coder is allowed to make that diagnosis.
Scenario 6: Cervicogenic headache
Documentation:
Cervicogenic headache
Coding direction:
See G44.86
Common error:
Selecting R51.9 as the code concluded the encounter because the reason for the visit was “headache.”
Scenario 7: Post-traumatic headache
Documentation:
Post-traumatic headache secondary to head injury
Coding direction:
Refer to G44.3- and related family, and assign the most specific code that is supported by the record.
Common mistake:
Assigning R51.9, thus losing the relationship to the trauma.
Scenario 8: Headache associated with another diagnosed condition
Documentation:
Patient reports headache and facial pressure. Provider diagnoses acute sinusitis.
Directions to coding staff:
When sinusitis is documented, code the sinusitis and do not create a code for “sinus headache” or similar.
Most common error:
Thinking that selecting a code for headache means that a code for headache is always appropriate, simply because a patient presented to clinic with a headache.
Common Headache ICD-10 Coding Mistakes
1.Using R51.9 for all headaches
R51.9 is a good code to use in the absence of an established diagnosis. It should not be used to code all headaches, as there may be cases in which a diagnosis has already been made. When a diagnosis has been made, that diagnosis should be used.
2.Using R51.9 Based on Symptoms
A coder sees the symptoms of migraine and codes it accordingly.
This is “diagnosing” based on symptoms and should not be done. The diagnosis should always be made by the provider.
3.Using R51.9 as Final Code
Older references in general still reference R51.0 and R51.9 as one in the same.
This is no longer the case. Verify which code is appropriate for the fiscal year.
4.Misconceptions About Category Codes
There are a lot of subcategories in G43 and G44.
Writing “G43” to describe “migraine” is permissible; however, coding rules state that each diagnosis must be fully documented to be coded, therefore, the complete code and documentation must be reviewed.
5.Incidence of Intractable migraine
The word “severe” does not equate to “intractable.”
6.Status Migrainosus
A coder may not assume that a prolonged headache is a migraine that has status.
7.Post Traumatic Headaches
Headaches that occur after a traumatic event do not always mean that the headaches are post-traumatic in nature.
8.Medical Necessity
Just because a diagnosis is coded correctly, that does not necessarily mean other associated procedures will be covered. There are numerous factors, outside of coding, that impact medical necessity.
Headache Claims: Why Denials Actually Happen
It’s common to see “R51.9 causes denials” in notes and discussions. There’s certainly truth to that, but stating it this way oversimplifies the situation.
The presence of R51.9 in a claim does not preclude payment. On the other hand, including a different diagnosis in a claim does not automatically justify the service billed as medically necessary.
Headache claims in particular run into problems for various reasons such as:
- Diagnosis/procedure mismatch
- Lack of sufficient documentation
- Inadequate prior authorization
- Incorrect/vague coding
- Limited coverage
- Eligibility issues
- Modifier errors
- Bundling edits
- Lack of supporting documents
Medical necessity based on payer guidelines
The philosophy should not be to “Avoid R51.9 at any cost.”
The philosophy should be to ensure that all services billed are warranted and supported by documentation and other relevant records. In addition, the code assigned should be the most precise code supported by the documentation.
Medical Necessity and Headache Imaging
headache-related office visits may require the use of diagnostic imaging (CT or MRI).
Accurate diagnosis coding is only one aspect of medical necessity. The reviewer should refer to the referring and/or evaluating physician’s documentation to determine the medical reason for the request. The reviewer should take into account the patient’s headache history including:
- Duration
- Neurological symptoms/findings
- Any trauma
- Recent changes in the patient’s headache pattern/symptoms
- Other associated symptoms
If the requesting/referring physician believes that an MRI is medically necessary, he/she should document the rationale to explain the request.
Imaging service coverage is determined by the payer, as well as the member’s eligibility and the service delivered.
It is inappropriate to lead the member to believe that a particular diagnosis code for a headache will result in authorization for an MRI. When coverage is denied, the coding clinic letter should not reflect an attempt at guidance or justification for the coverage denial.
CPT and ICD-10-CM Serve Different Purposes
There is an ongoing confusion regarding the use of CPT and ICD-10-CM coding systems. A common belief is that if one system is understood, the other will be straightforward to use as well. This is not true.
ICD-10-CM is the coding system that describes the reason for the patient’s visit and the patient’s condition to the payer.
CPT/HCPCS codes describe the nature of the service or procedure, test, drug or supply that is reported.
A claim may involve several components. For example, an encounter for a patient with a headache may involve an evaluation and management service, a diagnostic imaging study or a headache procedure. The condition for which the service was rendered and the imaging study or procedure may be different. It is important that the diagnosis code used by the report reflects the condition for which the service was provided. The CPT/HCPCS code for the service reports the nature of the service.
Together, the various components of a claim provide the payer the reason for the service and the nature of the service.
Don’t Choose an E/M Level From the Headache Diagnosis
An official migraine diagnosis doesn’t always elevate your E/M code from R51.9. For example, an unspecified headache isn’t always equivalent to a low-level code.
E/M code selection is dependent on a number of variables. Medical decision making must be properly documented in order to justify a level 4 or 5 E/M code. Likewise, E/M code selection may depend on the total time spent on the patient on the given day.
Your documentation must also support your level selection.
Sometimes articles on billing may give the false impression that using a more specific code, or a code that better defines the patient’s condition, may increase the E/M level. This is not the case.
Just because a patient is coded as L4 or L5, does not mean that an equivalent level of care was provided.
Modifier 25 and Headache Procedures
There are certain headache encounters that comprise an E/M service and a procedure on the same date.
In such situations, if a physician or qualified health care professional also provides a significant, distinct E/M service on the same day as the procedure or another service, then modifier 25 may be appropriate.
It is inappropriate to append modifier 25 to a procedure when an E/M service has also been performed on the same date and supports the procedure.
In such cases, it may be necessary to review the payers’ and coders’ guidelines to determine the documentation requirements for the E/M service.
Payer Rules Still Matter
While ICD-10-CM standardizes diagnoses codes, it does not modify payer coverage policies.
Prior to billing for expensive head and neck diagnostic or interventional procedures, various factors must be confirmed. These include but are not limited to:
- The patient’s eligibility
- The patient’s benefits
- The patient’s network status
- Whether the referring provider obtained the necessary referral
- Whether the payer has approved the referred service
- The payer’s medical necessity policy
- The payer’s coverage policies
These policies help determine whether the payer will cover advanced diagnostic or interventional head and neck services.
The code assigned to a particular diagnosis should not be altered to bypass a payer edit.
A Better Workflow for Headache Claims
A practical coding workflow looks like this:
Step 1: Read the Provider’s Assessment
Identify the correct diagnosis documented by the provider.
Step 2: Is it a Symptom or Headache Disorder?
The term “headache” may direct you to Z91. Other named headache disorders (e.g. migraine, tension type headache, cluster headache, cervicalogenic headache, etc.) will lead you to other diagnoses.
Step 3: If applicable, provide additional details.
Some of the details you should look for are:
- – Aura
- Intractability
- Status migrainosus
- Chronicity
- Episodic/Chronic
- Orthostatic
- Traumatic
Step 4: Start with Alphabetic Index
The documentation may provide some direction and help determine the correct code.
Step 5: Use the Tabular List
The index provides a general description of the code and may provide inclusion and exclusion criteria. There may also be instances of “code also” and “use additional code” to provide other options for describing a case. Other elements may also be included to provide clarity and further direction.
Step 6: Further Assess and Clarify as Necessary
Prioritize documentation of a query request over speculation.
Step 7: Verify Date of Service
The effective date of an update to ICD-10-CM determines the date a code may be used.
Codes from the most recent version of ICD-10-CM may be used to describe conditions from a previous period.
Step 8: Review Claim
Certain payers may define medical necessity of a service as a particular code, CPT/HCPCS code-level linkage, authorization, and/or modifier usage. Payer rules and edited values may restrict what is allowable on a claim.
2026 and 2027 ICD-10-CM Update: Which Version Applies?
IC D-10 CM code sets are published according to the U.S. federal fiscal year.
For services provided during the period September 1, 2025 through September 30, 2026, the ICD-10-CM code set published for September 30, 2025, should be used.
The publication for October 1, 2026 through September 30, 2027, will be effective from that date.
Prior to and after the change, articles published in professional and trade journals should review and identify the ICD-10-CM codes, if any, that are in current use.
Did R51.9 disappear for FY 2027?
Do not automatically update codes with the release of a new fiscal year’s codes. Ensure codes are coded to R51.9, R51.0, or other specific code sets provided on the claim with the FY 2027 Tabular List, for services rendered on or after October 1, 2026.
During the coding process, you should use the following as the most reliable resources for coding:
- The CDC/NCHS ICD-10-CM files and browser
- CMS’s ICD-10 resources
- Current ICD-10-CM Official Guidelines for Coding and Reporting
The other coding resources published by AHIMA and AAPC may also be used for coding; however, the official guidelines and classifications should always be used for coding.
Date of Service Beats Article Publication Date
This is an important detail that is often times overlooked.
Let’s say you are updating an old claim from August 2026 which you are processing in November 2026.
You cannot utilize the most up to date FY 2027 code set to process this claim.
The code sets that were current at the time of the service provide the basis for code validity.
Thus, coding teams should have access to the code sets current at the time of service when performing retrospective review of old claims and accounts receivable.
Quick Decision Guide for Headache Coding
Use this sequence:
1. Does the record provide a specific headache diagnosis?
No: If no diagnosis is given, refer to R51.9 or similar symptom code.
Yes: Continue.
2. Is an orthostatic/positional headache documented and not reported elsewhere?
Yes: Consider R51.0.
3. Is migraine documented?
Yes: Consider the type of migraine (e.g. with aura), the presence of intractability and/or status migrainosus. Consider G43.-
4. Is headache of tension-type documented?
Yes: Consider G44.2- and the supported code.
5. Is cluster headache documented?
Yes: Consider G44.0-
6. Is the headache post-traumatic, cervicogenic, drug-induced or other?
Consider other codes in branch G44.
7. Is the documentation inadequate for definite code assignment?
If the documentation is unclear or vague about the reason for the symptoms, contact the medical professional for clarification.
Coding Audit Checklist for Headache Claims
Prior to submission of the claim, a review may include the following:
- Is the documentation/coding in line with the provider’s assessment?
- Was a more specific diagnosis given, as opposed to R51.9?
- Were any ambiguous statements given by the provider, and coding clarity and specificity added?
- Was the documentation given for a migraine, including the aura and intractability?
- Is the migraine status documentation given?
- Is R51.0 given with documented orthostatic/positional component?
- Is a category I code mistakenly reported, instead of a complete code?
- Were statements in the Tabular List/Index, and Excludes/Other Notes, reviewed?
- Is the stated documentation in line with the date of service?
- Is the level of documentation sufficient, given the nature of the procedures?
- Was the reported procedure code/s approved, prior to service?
- Are the reported codes supported by modifiers?
- Is the claim comprehensive and does it support the documentation given in the record?
Prior review of the claim may identify oversights, which prove to be time consuming and frustrating to correct after the claim has been adjudicated.
Headache ICD-10 Coding by Practice Type
Primary Care
Practices in primary care are often the first to identify symptoms of various neurological conditions, including headaches. Because of this, the ICD-10-CM code R51.9, (other unspecified neurological symptoms) may be appropriate in some cases for initial presentation. However, a more specific neurological diagnosis should be assigned and coded if and when it is available.
Neurology
A review of neurology notes often will reveal sufficient information to support a more specific code in the category G43-G44 (other disorders of the nervous system). Template coding should allow the neurologist to make an accurate selection based on his or her expertise.
Pain Management
Patients with migraines, cervicogenic headaches, and other neurological conditions requiring further workup and/or interventions may be seen by pain management practices. Complete documentation is essential to justify each of the services provided, including the evaluation and/or intervention. Pain management billing services may assist practices with medical necessity, coding, and/or reimbursement. It is imperative that pain management practices which utilize billing services have complete and comprehensive records in order to validate that the services documented and billed are congruent.
Emergency Care
Patients seeking emergency care for acute neurological conditions may present with headache as the primary symptom. Coding for these conditions should be based on the condition for which the patient was evaluated and diagnosed, not on the presumed condition for which the patient was seeking care.
The Role of Provider Queries
A query shouldn’t be used to try and push a claim to a better-paying code.
A query should be used to request more information when there is incomplete, conflicting, ambiguous information in the record that prevents the coder from assigning an appropriate code.
Examples of when an appropriate query may be used to request specific information are as follows:
- There are conflicting assessments and plans.
- There are conflicting statements that lead to ambiguity in assigning a code for a migraine.
- There is a statement in the record that indicates a possible migraine, but there is no documentation to support a migraine.
- There is a statement that suggests a possible injury, however the record is not clear as to how and/or when the injury occurred.
- There is insufficient information to support a statement that a possible trauma is still causing the headache.
- There is information documented that does not fully support the diagnosis.
- There are inconsistencies in the record.
- There is a general statement that is not sufficiently clear and requires additional detail to support the coding decision.
Queries should not influence the response and be in compliance with the organizational policies.
Headache ICD 10 FAQs
What is the ICD-10-CM code for headache?
R51.9 is the ICD-10-CM code for headache, unspecified. Use it when the provider documents headache without establishing a more specific headache diagnosis. If migraine, tension-type headache or another specific syndrome is diagnosed, review the appropriate code family instead.
What’s the difference between R51.9 and R51.0?
R51.9 represents an unspecified headache. R51.0 represents a headache with an orthostatic or positional component, not elsewhere classified. The documentation must support the positional characteristic before R51.0 is selected.
Is R51.9 still valid in 2026?
Yes. R51.9 is used for unspecified headache under the applicable ICD-10-CM classification. For claims on or after October 1, 2026, verify codes against the FY 2027 ICD-10-CM release because code validity is date-of-service dependent.
Should R51.9 be used for migraine?
Not when the provider establishes migraine and a more appropriate G43 code is supported. Migraine coding can distinguish aura, intractability, status migrainosus and other characteristics.
Can R51.9 and a migraine code be reported together?
Don’t automatically report R51.9 merely because headache is a symptom of a documented migraine. Review the current ICD-10-CM Tabular instructions and the circumstances of the encounter. An Excludes2 note does not itself mean both codes should always be assigned.
Which ICD-10 code should be used for chronic headaches?
There isn’t one universal code for every “chronic headache.” Code the condition the provider documents. A diagnosed chronic migraine, chronic tension-type headache, post-traumatic headache and an unspecified headache may lead to different code families.
Final Coding Takeaway
The ICD-10-CM code for an unspecified headache is R51.9. Headache with orthostatic or positional component, not elsewhere classified, is coded as R51.0. When the provider has diagnosed or ruled out other possible conditions, like migraines or a tension-type headache, etc., then code according to the condition.
To improve your coding skills and accuracy, you must develop three habits:
Coding a diagnosis as documented requires coding specificity. Verification of the correctness of the code is a must. The Tabular List is a good resource to verify codes.
Coders in practices with a large volume of headache and/or neurology/pain management cases should be commended for seeking out audits and doing case studies to identify and correct billing errors.





