What Is the ICD-10 Code for Palpitations?

The ICD-10-CM code for palpitations is R00.2. It sits in category R00, Abnormalities of heart beat, inside the R00–R09 block that covers symptoms and signs involving the circulatory and respiratory systems part of Chapter 18 of ICD-10-CM, the chapter reserved for symptoms, signs and abnormal findings that haven't (yet) been tied to a definitive disease code elsewhere. R00.2 is billable on its own; no additional character is required.

Palpitations is a symptom, not a diagnosis. It describes what the patient reports feeling a heartbeat that seems too fast, too forceful, irregular, fluttering, or like it "skipped" rather than a confirmed underlying condition. That distinction matters more in cardiology coding than almost anywhere else, because so many patients present with exactly this complaint before any testing has pinned down a cause.

R00 groups five closely related codes that coders mix up constantly, so it helps to see R00.2 next to its siblings before going further.

R00 itself is a non-billable header a claim built around R00 alone rejects. Every encounter needs to drill to R00.0 through R00.9 and which one applies depends entirely on what the provider actually wrote.

Detailed Description of R00.2: What the Code Represents (and What It Doesn't)

R00.2 describes an unpleasant sensation of irregular or forceful heartbeat a rapid or irregular heartbeat the patient can feel, whether or not it corresponds to anything abnormal on a monitor. That last part is worth sitting with. Palpitations is a subjective report. A patient can have completely normal sinus rhythm on a 24-hour Holter and still have documented palpitations, because the code describes the complaint, not the tracing.

Two coding notes attach to this category and both matter in practice:

• Excludes1: abnormalities originating in the perinatal period (P29.1-). This is a pure exclusion the two codes are never reported together. It rarely comes up outside neonatal and pediatric cardiology, since it applies to cardiac rhythm disturbances first identified in a newborn.
• Excludes2: specified arrhythmias (I47-I49). This is a "not included here, but can coexist" note, not an absolute bar. Structurally, R00.2 and a code from I47-I49 can appear on the same claim when both are clinically distinct and separately documented. In practice, this is where a lot of coders get tripped up see the next section.

What R00.2 does not mean: it isn't shorthand for atrial fibrillation, isn't a stand-in for anxiety and isn't a synonym for tachycardia. It means the provider documented the symptom and as of that encounter nothing more specific has been established as its cause.

When to Use R00.2

R00.2 is the right code when the documentation supports the symptom on its own merits:

• The patient reports palpitations as the reason for the visit and no confirmed arrhythmia or other explanatory diagnosis has been documented yet.
• A new or established patient is being worked up for palpitations an ECG, ambulatory monitor, or echocardiogram has been ordered and the reason for the encounter is the symptom itself.
• Testing has come back inconclusive; the palpitations remain unexplained and the provider's assessment still says palpitations rather than a named rhythm disorder.
• The note documents "palpitations" plainly, without further qualifying language pointing to a specific confirmed cause.

In all of these, the common thread is the same: the symptom is doing the work in the documentation because nothing more specific has replaced it yet.

When Not to Use R00.2

R00.2 stops being the right choice the moment the record supports something more specific or when the palpitations are simply the expected experience of a condition already being managed at that same visit.

• A specific arrhythmia has been confirmed and documented. If the assessment names atrial fibrillation, supraventricular tachycardia, premature ventricular contractions, or another rhythm disorder as the explanation, code that diagnosis instead (our atrial fibrillation ICD-10-CM guide walks through how that category works). Adding R00.2 on top of it, for the same unexplained sensation, usually isn't supported once the cause is known.
• Tachycardia or bradycardia is the documented finding, not palpitations. A rapid or slow heart rate confirmed on exam or monitoring, without the patient's own report of a felt sensation, points to R00.0 or R00.1, not R00.2.
• A non-cardiac diagnosis is documented as the established cause, such as hyperthyroidism, an anxiety disorder, or a medication effect and the palpitations aren't being separately evaluated as an unresolved finding.
• The workup has concluded and a definitive diagnosis is now driving management. Continuing to bill R00.2 at every follow-up after the cause is known is one of the more common and more avoidable coding errors in this category.
• A payer's coverage policy requires a more specific diagnosis to support medical necessity for a given test or procedure. R00.2 is a valid symptom code, but it doesn't automatically satisfy every payer's covered-diagnosis list for advanced cardiac testing.

Palpitations vs Arrhythmia vs Tachycardia: Symptom vs Diagnosis

These three terms get used almost interchangeably in casual conversation and almost never should be in coding. Each sits at a different level of clinical certainty.

A useful way to keep these straight: palpitations is what the patient feels, tachycardia is what a monitor or provider measures and arrhythmia is what a clinician ultimately names. A single course of care can move through all three stages the patient reports palpitations, testing reveals a tachycardia and further evaluation confirms it's supraventricular tachycardia and the diagnosis code should track that progression, not freeze at whichever term came up first in the chart.

ICD-10 Code for Palpitations Unspecified: Handling Ambiguous Documentation

Unlike categories such as atrial fibrillation, where "unspecified" is its own billable code (I48.91) sitting alongside more specific subtype codes, palpitations doesn't work that way. R00.2 already is the specific code for the symptom there's no separate "palpitations, unspecified" code layered on top of it.

Where ambiguity actually shows up is one level higher, at the R00 category. If a note is vague enough that it's genuinely unclear whether the finding was palpitations, tachycardia, or bradycardia which is rare, but happens with poorly templated documentation the fallback is R00.9, Unspecified abnormalities of heart beat. That's a different situation from a note that clearly says "palpitations," which supports R00.2 directly and shouldn't be downgraded to R00.9 out of excess caution. Coders sometimes default to the more generic code when they're unsure, but if the word "palpitations" is sitting right there in the assessment, R00.2 is the supported code reaching for R00.9 instead is undercoding, not conservative coding.

How Cardiologists Should Document Palpitations for Accurate Coding

Coders can only code what's on the page. Documentation that supports clean R00.2 claims and makes the eventual transition to a confirmed diagnosis easy to code correctly tends to include:

• The patient's own description of the sensation (pounding, racing, fluttering, skipping, irregular), not just the word "palpitations" dropped into a problem list.
• Duration, frequency and any known triggers, since these often drive the choice of monitoring test.
• Associated symptoms dizziness, presyncope, syncope, chest discomfort, shortness of breath documented as distinct findings when present, since some carry their own codes and their own medical necessity weight for testing (our chest pain ICD-10-CM guide covers that symptom in similar depth).
• What testing was ordered and why, tying the diagnostic workup back to the documented symptom.
• Once a cause is identified, an explicit, named diagnosis in the assessment "paroxysmal supraventricular tachycardia," not just "cardiac issue" or "abnormal rhythm noted."
• Avoiding vague catch-all phrasing like "cardiac symptoms" or "heart issue," which gives a coder nothing specific to work from and usually ends up defaulting to a less precise code than the visit deserves.

Common Coding Mistakes with R00.2

Common Denials and Audit Risks Tied to Palpitations Coding

A handful of patterns account for most of the friction around R00.2 claims. The first is a straightforward diagnosis-to-procedure mismatch: a Holter, event monitor, or echocardiogram gets billed with R00.2 as the supporting diagnosis and the payer's medical policy for that specific test doesn't list R00.2 among its covered diagnoses for that CPT code. The claim denies for medical necessity even though the coding itself wasn't technically wrong the diagnosis just didn't line up with that payer's specific coverage rule for that service.

The second pattern is a stalled workup that never gets reflected in the coding. A patient billed with R00.2 across several visits over a year, with no progression toward a definitive diagnosis and no documentation explaining why, is exactly the kind of pattern that draws attention in a payer audit or internal chart review. It's not automatically wrong, but it invites a question the documentation should already be answering: why hasn't this symptom been resolved to a diagnosis and is the ongoing testing still medically necessary?

The third is thin documentation that doesn't clearly establish medical necessity for the level of testing ordered palpitations noted in passing on a problem list, without enough detail in the assessment to justify, say, a 30-day event monitor rather than a routine ECG.

Medicare Considerations for Palpitations Coding

Medicare expects diagnosis codes reported to the highest level of specificity the documentation supports, consistent with the ICD-10-CM Official Guidelines that CMS and the National Center for Health Statistics publish each fiscal year. For palpitations, that means using R00.2 when it's supported and moving to a specific diagnosis promptly once one is confirmed, rather than carrying the symptom code forward out of habit.

Beyond code selection, coverage for cardiac diagnostic testing tied to a palpitations diagnosis runs through National Coverage Determinations and Local Coverage Determinations and LCD content is set at the Medicare Administrative Contractor level which means the list of diagnoses that support coverage for a Holter monitor or ambulatory event recorder in one MAC jurisdiction isn't guaranteed to match another. National Correct Coding Initiative edits also govern how procedure codes for cardiac monitoring can be billed together. In an inpatient context, R00.2 groups under MS-DRG 308–310 (cardiac arrhythmia and conduction disorders), though the overwhelming majority of palpitations coding happens in the outpatient cardiology setting, where LCD-level diagnosis requirements are the more common concern. Verify the specific MAC's current LCD for whatever monitoring or imaging service is being billed rather than assuming a national rule applies uniformly.

Commercial Insurance Considerations

Commercial payers aren't bound to Medicare's coverage framework and their policies for palpitations-related testing frequently diverge from it. A plan may maintain its own covered-diagnosis list for ambulatory monitoring, require prior authorization for extended event monitoring or certain imaging studies that Medicare doesn't require, or apply different documentation standards for medical necessity review. A claim built to satisfy a Medicare LCD can still be denied by a commercial plan with a stricter or simply different policy, even when the R00.2 code itself is entirely correct. Confirming the individual payer's specific requirements rather than assuming one payer's rules carry over to another heads off a meaningful share of avoidable denials.

Correct Coding Examples: R00.2 vs. Alternatives

• Patient presents with a new complaint of a racing, fluttering heartbeat; no prior cardiac history; ECG ordered. R00.2 is supported.
• Same patient returns after a Holter monitor confirms paroxysmal atrial fibrillation. I48.0 (paroxysmal atrial fibrillation) replaces R00.2 going forward.
• Established patient with known, well-controlled AFib calls in reporting a new, different sensation a single hard "thump" unlike their usual AFib symptoms documented as a distinct, unexplained event. R00.2 alongside the existing I48.x code may be supported, given documentation that clearly separates the two.
• A chart shows an elevated heart rate on exam, but the note never documents the patient reporting a felt sensation. R00.0, not R00.2, matches what was actually documented.
• Palpitations are ultimately attributed to hyperthyroidism and the assessment names that diagnosis as the explanation. The endocrine diagnosis takes precedence; R00.2 isn't layered on top absent a separate, unresolved cardiac finding.

Real Cardiology Practice Scenarios

The scenarios below are illustrative teaching examples, not real patient cases.

New patient, palpitations as chief complaint. A patient presents to a general cardiology practice reporting several weeks of intermittent racing heartbeat. The provider documents the complaint, performs an in-office ECG showing normal sinus rhythm and orders a 14-day ambulatory monitor. Code: R00.2. The workup hasn't produced a diagnosis yet and the symptom itself is the reason for the visit.

Established patient follow-up, testing still pending. The same patient returns two weeks later; the monitor hasn't been read yet. The visit note still documents palpitations as the active concern. Code: R00.2 remains appropriate until results come back and change the picture.

Palpitations with associated chest symptoms. A patient reports palpitations along with mild chest tightness during episodes. Both symptoms are documented distinctly in the assessment and the chest discomfort is being evaluated as its own finding rather than assumed to be caused by the palpitations. Code: R00.2 for the palpitations, plus the appropriate chest pain code if that symptom is separately assessed and billed.

Palpitations evaluated with ambulatory monitoring, results confirm PVCs. The 14-day monitor from the first scenario comes back showing frequent premature ventricular contractions correlating with the patient's symptom diary. The follow-up note documents this finding explicitly. Code: I49.3 (ventricular premature depolarization) replaces R00.2 for this and subsequent related visits.

Palpitations resolved after workup, no cause identified. A different patient completes a full monitoring workup that shows no arrhythmia during multiple symptomatic episodes logged in a diary. The provider documents that the workup was unremarkable and the symptom has since resolved. Code: R00.2 remains the appropriate code for the encounters during which it was being actively evaluated; no arrhythmia code is added since none was ever confirmed.

Coding Tips for Better Accuracy

• Code from the assessment, not the device printout. A monitor result is clinical information the provider interprets it isn't itself a diagnosis until the note says so.
• Re-check the billed diagnosis at every follow-up. A symptom code from the first visit shouldn't still be riding along on a claim three visits after a diagnosis was confirmed.
• When documentation is ambiguous about whether a subtype or specific arrhythmia applies, a provider query is the compliant path not an inference from history or test results.
• Cross-check R00.2 against the specific payer's covered-diagnosis policy before submitting claims for higher-cost testing like extended event monitoring.
• Keep an eye on how palpitations documentation interacts with related symptoms like chest pain, dyspnea, or syncope each may carry its own code and its own medical necessity implications and lumping them together as "cardiac symptoms" loses that specificity.

Compliance Checklist for Palpitations Coding

• Documentation names the specific sensation the patient reported, not just a generic label.
• The billed diagnosis matches the current, most recent assessment not an earlier visit's unresolved symptom.
• R00.2 is used only when no more specific, confirmed diagnosis explains the sensation at that encounter.
• Diagnostic tests billed alongside R00.2 are supported by documentation tying the test to the symptom and, where applicable, checked against the payer's coverage policy.
• Confirmed arrhythmias are coded by type once documented, rather than continuing to default to a symptom code.
• Coders query the provider when documentation is ambiguous rather than inferring specificity from history or monitoring data.
• Diagnosis codes are verified against the current ICD-10-CM fiscal-year file rather than a saved favorites list or a prior year's reference.

How Professional Cardiology Billing Services Support Accurate Palpitations Coding

Palpitations is one of those diagnoses that looks simple until it isn't a single code, but a documentation trail that has to evolve correctly as a workup moves from symptom to finding to confirmed diagnosis. Practices that see repeat denials on monitoring or echo claims tied to R00.2, or that notice the billed diagnosis quietly falling out of sync with the chart over several visits, are usually dealing with a documentation-to-code drift problem rather than a one-off billing mistake.

That's the kind of pattern that dedicated cardiology medical coding services are built to catch before a claim goes out checking that the code selected actually matches the current assessment, that header codes and unsupported subtypes never make it to a claim and that testing is tied to a diagnosis the payer will actually recognize. It connects directly to the rest of the revenue cycle: accurate diagnosis coding feeds clean claims submission and tracking, reduces the volume of avoidable denial management work downstream and supports the kind of documentation trail that holds up if a payer ever asks for records. For practices doing a high volume of rhythm workups Holter and event monitor orders, echo referrals, EP consults that level of review typically sits inside broader cardiology medical billing or full revenue cycle management support, where diagnosis accuracy, claims and follow-up are handled as one connected process rather than separate handoffs. Practices whose palpitations workups regularly escalate to formal rhythm studies also lean on specialized electrophysiology billing support once a diagnosis moves past the symptom stage. None of that guarantees payment coverage still rests on documentation and payer policy but it closes off the coding-side errors that are entirely within a practice's control.

What's Changing for 2026–2027: The FY2027 ICD-10-CM Update and Palpitations Coding

The code information in this guide reflects the FY2026 ICD-10-CM code set, valid for encounters from October 1, 2025 through September 30, 2026. That window is closing soon. CMS and the CDC's National Center for Health Statistics released the FY2027 ICD-10-CM update in June 2026, adding roughly 190 new billable codes along with a handful of revisions and deletions, effective for encounters on and after October 1, 2026.

Public summaries of the FY2027 update don't list changes to the R00 category, which suggests R00.2 and its siblings are likely to carry forward into FY2027 unchanged but "likely" isn't the same as "confirmed," and this guide isn't the place to treat that as settled. Practices should verify the R00 family against the actual CMS FY2027 tabular file once it's fully in effect, rather than assuming continuity and should check that EHR favorites lists, superbills and coding templates don't carry forward any code the FY2027 update deletes or revises elsewhere in a practice's commonly used diagnosis set. The October 1 cutover is a good annual checkpoint for palpitations coding specifically, since it's exactly the kind of symptom code that tends to sit unreviewed in templates for years at a time.

Frequently Asked Questions

What is the ICD-10 code for palpitations? R00.2, used when the provider documents palpitations as the symptom and no more specific cardiac diagnosis has been confirmed for that encounter.

Is R00.2 the correct code for heart palpitations? Yes, whenever the palpitations themselves are the documented finding and no confirmed arrhythmia or other diagnosis has replaced the symptom in the assessment.

What is the ICD-10 code for palpitations, unspecified? There isn't a separate "unspecified" palpitations code. R00.2 already is the specific code for the symptom. R00.9 (unspecified abnormalities of heart beat) applies only when the documentation is genuinely too vague to tell whether the finding was palpitations, tachycardia, or bradycardia.

When should palpitations not be coded as R00.2? When a specific arrhythmia, confirmed tachycardia or bradycardia, or another established diagnosis (such as thyroid disease) already explains the sensation and the palpitations aren't being evaluated as a separate, unresolved finding.

Can palpitations be coded together with an arrhythmia diagnosis? Structurally, yes the Excludes2 note allows it when both conditions are clinically distinct and separately documented. In practice, this mainly applies when a patient with a known arrhythmia reports a new, separate episode that hasn't yet been attributed to that condition.

Is palpitations a symptom or a diagnosis? A symptom. It's the patient's own report of an abnormal-feeling heartbeat, not a confirmed disease or rhythm disorder.

What documentation supports an R00.2 diagnosis? An assessment that names palpitations as the finding, ideally with the patient's description of the sensation, without a documented confirmed arrhythmia explaining it.

What's the difference between palpitations and tachycardia coding? Palpitations (R00.2) describes what the patient feels. Tachycardia (R00.0, or a specific arrhythmia code once confirmed) describes an objectively measured fast heart rate. They can occur together or separately and the code should match what was actually documented.

Do payers treat symptom codes like R00.2 differently for medical necessity? Often, yes. Medicare LCDs and commercial medical policies each maintain their own covered-diagnosis lists for tests like ambulatory monitoring and echocardiography and R00.2 isn't automatically on every payer's list for every test.

When should a practice update the billed diagnosis after testing? As soon as a workup ECG, Holter, event monitor, echo, or EP study establishes a specific cause, the assessment and the billed code for that and subsequent related visits should reflect the confirmed diagnosis rather than the original symptom.

Can R00.2 be billed at a follow-up visit after an arrhythmia has already been diagnosed? Generally no, if the palpitations are attributable to the now-confirmed arrhythmia. R00.2 can still apply if a genuinely new, separate episode is being evaluated on its own.

Does R00.2 apply to pediatric patients? It can, with one exception: the Excludes1 note bars its use for abnormalities originating in the perinatal period, which are coded under P29.1- instead.

What tests are commonly ordered when palpitations is the diagnosis? ECG, ambulatory Holter or event monitoring and echocardiography are common, though medical necessity for any specific test still depends on the payer's own policy rather than the diagnosis code alone.

Does an R00.2 diagnosis guarantee a test will be covered? No. Medical necessity and coverage are determined during claim adjudication based on documentation and the payer's policy. A valid, well-supported diagnosis code is necessary for a payable claim, but it doesn't guarantee payment on its own.

Conclusion

R00.2 is a straightforward code on paper and a surprisingly easy one to get wrong in practice, mostly because it sits at the front end of a workup that's supposed to keep moving. The discipline that keeps it clean is consistent: code what the provider actually documented, update the diagnosis the moment a specific cause is confirmed and check the payer's own rules before assuming a symptom code will carry a claim for advanced testing. Get that sequence right and palpitations coding stops being a recurring source of denials and starts doing what a symptom code is supposed to do describe exactly where the patient's care stood at that visit, no more and no less.