ICD 10 Palpitations: R00.2 Coding and Billing Guide
The ICD-10-CM code for palpitations is R00.2. It is used to code palpitations when a provider documents this symptom but a related, definitive diagnosis is not documented. An ICD 10 palpitations code differentiates the sensation described by a patient from the findings of an abnormal heart rate or a cardiac rhythm disorder.
This code is rather self-explanatory. A chart, however, can be rather unclear. For example, a patient says he/she has palpitations and the description of the examination records a regular heart rhythm and the assessment mentions possible supraventricular tachycardia. These do not all have the same level of coding importance.
This resource outlines the significant distinctions that change code assignment, the documentation that clarifies uncertainty, and the code checks that affect reimbursement. It identifies the claim the earliest to avoid coding a symptom as a diagnosis.
ICD 10 palpitations code R00.2, at a glance
R00.2 is an ICD-10 code that is used to identify palpitations in the chapter of ICD-10-CM that describes the symptoms and signs. The official name of the code is Palpitations, and the associated term that if used, will retract the code is Awareness of heart beat.
R00.2 is a complete code, which means it is not necessary to include additional characters to identify the nature of the code, extent of the condition, etc. The broader category, R00, can not be used as a substitute for this code on an insurance claim.
A code is considered “complete” when it is detailed enough to be assigned and sufficient for reimbursement. Payment still depends on the specific case, guideline, benefit, and payer.
Patient language and the provider’s assessment
Patients usually describe palpitations as rapid, fluttering or pounding. These may be helpful in describing the complaint but do not in and of themselves prove atrial fibrillation or other arrhythmias.
The Cleveland Clinic and Mayo Clinic say palpitations may be caused by emotional responses or stimulants, or may be related to certain cardiac disorders or medications. For this reason it is not valid to assume a cause based on the description of the symptom.
Review the assessment and related interpretation. A nurse’s triage, an automated ECG or a wearable alert may give context to the case but the diagnosis must still be based on the rules and laws that govern the record and setting.
Palpitations, tachycardia, bradycardia, and arrhythmia codes
The palpitations ICD 10 code describes a sensation. Neighboring codes describe different documented findings. A “more specific” choice is useful only when it is more accurate for the condition documented.
| Code | Description | Appropriate distinction | Selection caution |
|---|---|---|---|
| R00.2 | Palpitations | The provider documents awareness of the heartbeat without a related established cause. | A sensation of racing or skipping doesn’t establish a named arrhythmia. |
| R00.0 | Tachycardia, unspecified | Tachycardia is documented without a more specific applicable diagnosis; sinus tachycardia NOS is included. | Don’t diagnose tachycardia solely from a patient’s wording or an isolated pulse value. |
| R00.1 | Bradycardia, unspecified | The provider documents bradycardia without a more specific applicable condition. | Review documented conduction disease and drug effects rather than assuming every slow pulse belongs here. |
| R00.8 | Other abnormalities of heart beat | The documented heartbeat abnormality indexes here and isn’t classified more specifically elsewhere. | “Other” isn’t a stronger version of R00.2. Verify the actual indexed term. |
| R00.9 | Unspecified abnormalities of heart beat | An abnormality is documented without enough description to choose a more specific R00 code. | Don’t replace clearly documented palpitations with this less descriptive code. |
| I49.1 | Atrial premature depolarization | A documented diagnosis supports premature atrial contractions or the corresponding indexed terminology. | A patient’s report of an extra beat doesn’t identify its origin. |
| I49.3 | Ventricular premature depolarization | A documented diagnosis supports premature ventricular contractions. | Fluttering alone doesn’t establish ventricular ectopy. |
| I49.9 | Cardiac arrhythmia, unspecified | Cardiac arrhythmia is documented but its type isn’t specified. | Uncertainty about the cause of palpitations doesn’t itself establish arrhythmia. |
I49.x is shorthand for a code family, not a reportable diagnosis. Choose the complete code supported by the record and verify its instructions.
Receive assistance with tough coding decisions
Resilient MBS is there to assist your team in reviewing diagnosis coding, coding omissions, and claims edits for cardiology services.
When to use R00.2 and when to pick another code
Use R00.2 for a known symptom with an unknown cause
R00.2 can be used to code a documented palpitation that is still under evaluation. It is not necessary for an ECG to be abnormal to consider the symptom as real, and a normal ECG does not mean it is psychological.
Typical situations include:
- Palpitations are assessed by the provider and additional evaluation is requested.
- A diagnostic study does not answer the question about the complaint.
- The assessment considers an arrhythmia but is unable to confirm it in an outpatient setting.
- Recurrent episodes remain an unresolved problem that is being evaluated, even if the patient is not currently experiencing the episodes.
A symptom code is not required to perform a complete and exhaustive evaluation to rule out the other conditions. The assessment and diagnostic studies must be related to the clinical question, and not for the sole purpose of answering a different question to obtain a different diagnosis code.
Use another code when the documentation supports a different condition
A different code is required when the provider has evaluated and established a different condition that explains the symptom. Consider if the palpitation is a symptom of the condition, and therefore required, before adding R00.2.
R00.2 is also not required to code a documented abnormality of the heart rate, an unspecified arrhythmia, or an unrelated historical condition.
Just because a condition is documented on the problem list does not mean every palpitation complaint is related to that condition. This is also true with anxiety, thyroid disease, and medication. Evaluate the relationship and determine if there is ambiguity.
Coding of Symptoms, Definitive Diagnoses, and Exclusions
A definitive diagnosis captures findings, and symptoms are generally not coded separately. Classification instructions indicate exceptions to this.
Atrial fibrillation, documented by the provider, captures the diagnosis of atrial fibrillation and, therefore, supports the assignment of the code for atrial fibrillation, and a code for palpitations would not be assigned.
Documented atrial fibrillion is not the same as palpitations, and an evaluation of the patient would indicate whether an arrhythmia was the cause of the palpitations. Separate discussion in the documentation does not mean an integral symptom is reportable.
Excludes 1 vs. Excludes 2
For category R00, Excludes 1 concerns perinatal period abnormalities classified to P29.1. Determine the condition’s origin and reviewed instructions; the patient’s age does not resolve this.
Excludes 2 concerns specific arrhythmias in categories I47-I49. This allows reporting both conditions. This does not change rules concerning symptoms integral to a definitive diagnosis.
It’s critical to understand these rules. “Both are allowed” does not mean both are supported in this encounter.
Encounter types and diagnostic interpretations
Emergency medical services and outpatient visits
In outpatient cases, those diagnoses that are suspected, probable, possible, or “rule out” cannot be coded as confirmed. Code the highest level of certainty that is documented, like symptom, finding, or reason for the outpatient visit. Accurate Medical Billing and Coding Services rely on maintaining the relationship between the condition and the provider’s assessment.
“Palpitations, possible SVT” would not justify coding an SVT diagnosis alone. In most cases, emergency department services and observation services are considered as outpatient services, but if the patient is admitted as an inpatient, then it may not be the case.
The first-listed diagnosis code is selected based on the condition for which the outpatient service was performed, depending upon the coding guidelines. It is not always necessary to code R00.2 as the first-listed code because of the chief complaint.
Inpatient facility reporting
There are different rules for qualifying uncertain discharge diagnoses and for determining the principal diagnosis in inpatient facility coding. A rule that is applicable to inpatient facility coding should not be applied automatically to professional coding.
Determine the claim type before applying a sequencing rule. “The patient was in the hospital” is not a sufficient basis for determining the type of claim.
Diagnostic test interpretations
In an outpatient diagnostic test setting, if a definitive diagnosis is documented by a physicians’ interpretation of the test, that interpretation controls the diagnosis reported for that diagnostic test encounter. An automated device finding is not a definitive diagnosis.
Ensure your documentation for the diagnosis supporting the completed diagnostic service and the reason for the order are distinguishable. If the interpretation points to a diagnosis, assess its relevance to the service and comply with the diagnostic-testing guidelines. Don’t blindly re-write a separately supported office visit if the record also contains a different diagnosis.
Rhythm diagnoses requiring discrimination
I47.1 Supraventricular tachycardia
I47.1 is a parent category, and therefore, is not a complete code. Examples of complete codes would be I47.10 for unspecified supraventricular tachycardia, I47.11 for inappropriate sinus tachycardia, if stated, and I47.19 for other supraventricular tachycardia.
If the diagnosis does not support the distinction, the interpretation may not have explained the reason for the order, and therefore, the distinction does not need to be made. Ordinary sinus tachycardia does not become inappropriate sinus tachycardia because the patient’s symptoms are bothersome. A diagnosis of SVT can not be made because the patient has a history of “racing heartbeat” and the documentation does not rule out other causes of a rapid heart rate.
Atrial fibrillation and atrial flutter
I48.91 is for unspecified atrial fibrillation, and I48.92 is for unspecified atrial flutter. Although both codes belong to category I48, they are different diagnoses.
Use a more specific code for atrial fibrillation or atrial flutter if the documentation supports it. Don’t assume the subtype of AF or flutter based on other information such as a medication list, cardioversion history, or a lone statement without reviewing the entire record.
Premature contractions and ectopic beats
Premature atrial contractions (PACs) and premature ventricular contractions (PVCs) are coded differently. A vague reference to ectopic beats may not be specific enough to chose between the two.
Reconcile the interpretation with the reason for the order. If the distinction has to be made for reporting and the reason for the order is still not explained, then it would be appropriate to query.
Symptoms and conditions, associated with the cases
Some associated symptoms for palpitations may include dizziness, fainting, syncope and shortness of breath. Report these symptoms when they are required and are not related to other established conditions or if they are not excluded by other instructions.
Some of these symptoms may include R07.9 for unspecified chest pain, R42 for dizziness and giddiness, R55 for syncope and collapse, and R06.02 for shortness of breath. This is a non-exhaustive list, and the presence of these symptoms, if present, does not warrant assignment of these codes to every palpitation case.
Anxiety, Metabolic conditions and Medications
If the palpitation complaint was attributed to anxiety, this does not make the complaint psychiatric. Similarly, if abnormal thyroid or electrolyte results were found, the coder should not diagnose the cause. If a relevant relationship exists, the provider would have established this.
Code the nature of the reaction for a medication if the adverse effect was due to properly administered and prescribed medication. A reaction to a poisoning is coded differently, and there should not be a “rule out” approach to an underlying cause, symptom of palpitations.
Pregnancy and perinatal conditions
Any maternal palpitation needs a relevant Chapter 15 obstetric code as well as any other codes that identify the associated condition or symptom. Usually, such codes have precedence in sequencing when pregnancy impacts the visit. It is incorrect to select an obstetric code only on the grounds of pregnancy. In case the provider indicates that the pregnancy is coincidental, one needs to follow the related instructions. It is especially critical in the case of reviewing diagnosis sequencing by Gynecology Billing Services.
The conditions of the fetal heartbeat need to be coded under the related perinatal chapter classification, like P29.1, and not under the automatic code R00.2. Not every infant’s condition can be coded as every pediatric condition. One needs to consider the patient’s age, the onset of the condition, and its diagnosis.
Documentation that assists coders in making a defensible decision
Pointers can help if they include the symptom, the assessment and the rationale for the service. Long copied histories can still leave those three points ambiguous.
Look for:
- The assessed complaint: e.g. palpitations, tachycardia, bradycardia or named rhythm condition.
- The episode pattern: When and how often they occur, what triggers them, and what circumstances describe the patient.
- Associated findings: Chest pain, syncope, dyspnea, and relevant physical exam findings.
- The Interpretation: A signed clinical interpretation documenting the established rhythm diagnosis.
- Diagnostic Certainty: Establishing a distinction from the differential diagnosis.
- Clinical Relationships: Whether a known condition explains the patient’s complaint.
- The service justification: The reason why the ordered test was warranted.
A query should resolve a coding ambiguity. It should not suggest a diagnosis based on what a payer may cover.
For example: “The assessment documented the patient as having palpitations and the signed interpretation documented the patient as having atrial premature depolarizations. Please clarify what the finding was in relation to and if it explained the patient’s symptom.” Use your organization’s query process and include relevant clinical information.
Wearable Alerts and Inactive Problem-List Items
A patient’s smartwatch alert may help explain why a patient is seeking an evaluation. It may not, by itself, diagnose Atrial Fibrillation for coding purposes. The same is true for a reviewed AECG that is automated.
The descriptions on problem lists don’t always tell the whole story. Something on a provider’s list for “history of palpitations” may not be something that is currently bothering the patient. Determine what the provider was assessing. A symptom doesn’t have to be occurring to be reported. A historical problem may be resolved, but shouldn’t be reported as an active symptom.
Practical Coding Examples
The following are hypothetical examples. Actual reporting is dependent upon the complete record and pertinent coding instructions.
An unresolved Symptom with Normal ECG
The patient complains of fluttering. The clinician assesses palpitations, interprets the ECG as normal, and plans more testing. No cause is established.
R00.2 supports the symptom. The normal ECG doesn’t eliminate the complaint or make anxiety the cause of the complaint.
Documented Rhythm Disorder Explains the Complaint
The clinician assesses palpitations and interprets the ECG as showing ventricular premature depolarizations (VPDs). The complaint of palpitations is attributed to the VPDs.
I49.3 represents the condition. Review the integral symptom rule and not carry R00.2 along for the ride, just because it appeared first on the order. The claim should represent the condition that is related to the service being coded.
Racing Sensations without Documented Tachycardia
The patient states “my heart races.” The clinician assesses palpitations and interprets the ECG as normal. No assessment or interpretation establishes the presence of a tachycardia or a rhythm disorder.
R00.2 is the correct code. R00.0 cannot not be justified with the patient’s adjective describing the heart. An automated suggestion based on that wording would require human review against the clinician’s documentation.
Known AF with unexplained complaint
The patient is documented to have atrial fibrillation (AF), but the provider does not explain this on the complaint. It is documented that the patient has complained of palpitations and this is also captured separately. Both conditions impact the encounter.
Review whether the documented conditions satisfy reporting requirements. In this case, Excludes2 does allow for appropriate combined reporting; this doesn’t allow for automatic combined coding. A generic entry of AF on the problem list doesn’t explain this case.
Billing checks beyond diagnostic code selection
Medical necessity guidelines could change between payers and from one particular service to another. Code R00.2 could cover a diagnosis and a monitor service, but diagnosis alone will not warrant all cardiac services. Palpitations are considered an important symptom in relation to some ambulatory ECG services by CMS, whereas others might have different local coverage determination guidelines. Medical Coding Services team evaluates the procedure, its indication, documentation, authorization, and billing entity before submitting the claim.
Multiple services could be performed during a palpitations evaluation process; however, each service should be individually reviewed for the purpose of being covered and reimbursed. Just because the service is used during the process of evaluation, does not automatically mean that it could be paid. Reviewing the policy of the particular payer and aligning the medical necessity with the service is the key to avoid denials.
Procedure codes define the service performed
A routine ECG is considered a completed service and should be coded as 93000. Alternatively, codes 93005 and 93010 describe the service as tracing and interpretation respectively. Report the service the billing entity actually performed.
Monitoring services have their own code definitions and component rules. It’s inappropriate to apply modifier 26 to a code that represents a professional component. Accurate diagnosis will not adjust or change the underlying reason for global billing. It cannot justify an unsupported procedure.
Match the diagnosis pointer and reason for the service
An accurate diagnosis can still fail to justify a service line if its pointer is incorrect. Determine if there is a valid reason for the service and if there is a link to the documented condition.
Prior to adjusting anything on a denied claim, understand the payer’s reason for the denial. This will help distinguish between a data error, an unsupported service, a lack of authorization and a coding disagreement. A corrected claim and a request for reconsideration address different issues.
If R00.2 accurately describes the record, replacing it with an unsubstantiated arrhythmia to justify payment would result in an unsupported diagnosis. Where the service is supported and meets coverage requirements, an appeal should provide the support and the rationale using the applicable evidence and documentation.
Examples of common mistakes made when coding assessments
Using “irregular heartbeat” as a universal code. The ICD-10 choice for “irregular heartbeat” depends on the description provided in the assessment. Is it a description of a feeling? Is it a description of an abnormality in the heartbeat? Is it a description of an established arrhythmia?
- Using a parent category on a claim. R00, I47.1, and I49.x are NOT complete reportable codes.
- Using a differential diagnosis and coding it as a confirmed diagnosis. An outpatient “rule out AF” assessment does not establish AF.
- Coding every symptom listed. Symptoms do have to meet reporting requirements and integral symptom rules.
- Using R00.2 and R20.2 interchangeably. R20.2 describes paresthesia of the skin. An alert could flag the mismatch for review and NOT automatically change the diagnosis.
- Using a valid code as a code guaranteed to be covered by payer. The diagnosis, the service provided, and the payer all have to be supported.
- Using non-U.S. code conventions. U.S. claims use ICD-10-CM; supplementary indicators from another national system DO NOT automatically transfer.
A review of a claim edit identifies a question for review. It does NOT create a diagnosis, establish causation, or replace the judgment of the provider.
Related codes for further reading
Related coding topics may provide answers to other conditions documented in the assessment.
- Coding Tachycardia: R00.0, I47.x
- Coding Bradycardia: R00.1, other documented conduction disorders
- Coding Premature Contractions: I49.1, I49.3
- Coding Atrial Fibrillation and Flutter: I48.x
- Coding Associated symptoms: R07.9, R42, R55, R06.02
Resolve repetitive claims questions in cardiology
Collaborate with Resilient MBS for an extensive coding and billing review in cardiology, starting from selecting the symptoms to contacting the payers.
Frequently asked questions
What is the ICD-10-CM code for palpitations?
R00.2 is the ICD-10-CM code for palpitations. Its inclusion term is awareness of heart beat. It can describe the documented symptom when a related definitive diagnosis hasn’t been established.
Can R00.2 be the first-listed diagnosis?
Yes. R00.2 may be first-listed for an outpatient encounter chiefly addressing documented palpitations without an established related diagnosis. The reason for the service and applicable sequencing instructions determine its position.
Are palpitations and tachycardia coded the same way?
No. Palpitations describe awareness of the heartbeat; tachycardia describes an increased heart rate. R00.2 and R00.0 represent different documented conditions. A patient’s report that the heart feels fast doesn’t independently establish tachycardia.
Can R00.2 be reported with an arrhythmia code?
Sometimes. Excludes2 permits appropriate combined reporting, but a symptom routinely associated with a confirmed diagnosis generally isn’t separately coded. Review the documented relationship, the reason for the service, and applicable reporting rules.
Does R00.2 guarantee payment for an ECG or heart monitor?
No. R00.2 can support the documented reason for evaluation, but payment depends on the actual service, medical necessity, documentation, benefits, and applicable payer requirements. A valid diagnosis code does not guarantee coverage.
A more defensible basis for coding and billing review
A defensible palpitation claim connects the provider’s assessment, the diagnosis supported by that assessment and the service rendered. Often documentation supports the coding team in connecting the rhythm to a diagnosis, as otherwise they could be picking a diagnosis purely to satisfy a payer edit.
