ICD code R00.0 – Tachycardia, unspecified

Key takeaways

R00.0 (Tachycardia, unspecified) is billable when the record documents a fast heart rate without a confirmed arrhythmia.

R00.0 carries three Excludes1 notes: paroxysmal tachycardia (I47.-), inappropriate sinus tachycardia, so stated (I47.11), and neonatal tachycardia (P29.11).

Sinus tachycardia NOS and sinoauricular tachycardia NOS are inclusion terms under R00.0, so only a physician-named rhythm moves the claim off it.

Pabau’s claims management software sends US claims through the Claim.MD clearinghouse and posts ERA remittances back to the patient record.

ICD-10 code R00.0: Definition and official descriptor

ICD-10 code R00.0 is the billable ICD-10-CM code for tachycardia, unspecified, used when the record shows a fast heart rate without a named arrhythmia.

The FY2027 ICD-10-CM tabular list publishes it under category R00 (Abnormalities of heart beat), in block R00-R09. It is valid as written, with no seventh character or further subdivision.

The CDC/NCHS ICD-10-CM web tool lists R00.0 with no Use additional code or Code first note. It can therefore stand alone as a primary or secondary diagnosis. “Unspecified” means the physician recorded tachycardia as a finding. The note names no mechanism, or the workup has not confirmed one yet.

What R00.0 covers: Inclusions and clinical scope

R00.0 is the correct code when the documentation shows an elevated heart rate without an identified arrhythmia subtype. The tabular list names three inclusion terms under it, and common clinical wording maps to the same code.

• Tachycardia NOS: The physician documents “tachycardia” without further qualification.
• Sinus tachycardia NOS: “Sinus [sinusal] tachycardia NOS” is an inclusion term at R00.0, so an unqualified “sinus tachycardia” stays here.
• Sinoauricular tachycardia NOS: Also an inclusion term at R00.0, so it does not point to another category.
• Rapid heart beat: A heart rate above 100 bpm on exam, recorded without a named mechanism.
• Elevated rate on monitoring: A fast rate noted on a Holter or event monitor, where the interpretation confirms no arrhythmia.
• Tachycardia as a presenting symptom: The patient arrives with palpitations and a measured fast rate, and the assessment lists “tachycardia” pending workup.

What every scenario above shares is the missing specification. Once the physician writes “paroxysmal SVT” or “inappropriate sinus tachycardia,” the code path changes. When the note names a cause, as in “sinus tachycardia due to dehydration,” the cause is coded first. R00.0 is a legitimate choice while the workup is still open.

What R00.0 does not cover: Excludes1 and Excludes2 notes

R00.0 carries three Excludes1 notes in the ICD-10-CM tabular list. An Excludes1 code is never reported alongside R00.0, because each one names a confirmed diagnosis rather than an unspecified finding.

Category R00 also carries an Excludes2 note for specified arrhythmias (I47-I49), and it applies to R00.0. Excludes2 means the arrhythmia is not part of R00, though a patient can have both.

For I47 codes, the Excludes1 note at R00.0 is stricter and governs. For I48 and I49 rhythms, Section I.B.5 of the ICD-10-CM guidelines still applies: a sign routinely associated with a disease is not coded separately.

Taken in order, these exclusions form a short decision path for any note that mentions tachycardia.

R00.0 vs. similar tachycardia codes: How to choose the right code

Most coding errors with ICD-10 code R00.0 come from one of two directions. Coders pick it when a more specific code is available, or they pick an arrhythmia code when the documentation only supports a symptom. This table maps each related code to its clinical trigger.

Sinus tachycardia: When to use R00.0 and when to use a specific code

Sinus tachycardia NOS is an inclusion term under R00.0, so it has no separate code. If the physician writes only “sinus tachycardia” without a cause or subtype, R00.0 is correct. If the note names the cause, as in “sinus tachycardia due to anemia,” code the underlying condition first.

Add R00.0 only when the tachycardia is not a routine part of that condition, per guideline Section I.B.6. Stated inappropriate sinus tachycardia is the exception: it has its own code, I47.11, and never takes R00.0.

SVT and VT: Why R00.0 must yield to the I47 codes

When an ECG or the physician’s assessment confirms supraventricular tachycardia, the code is I47.10 or I47.19, not R00.0. Ventricular tachycardia follows the same logic with I47.20 or I47.29. In the current code set, I47.1 and I47.2 are subcategories rather than billable codes, so the claim needs the fifth character.

Assigning R00.0 when SVT or VT is documented is undercoding. A cardioversion billed with 92960, or an electrophysiology study, tells a payer reviewer that the arrhythmia was specific. IV amiodarone billed under J0282 sends the same signal. That mismatch can trigger an audit.

Documentation that supports an R00.0 claim

Payers reviewing R00.0 claims look for documentation that justifies the “unspecified” qualifier. The chart must show that tachycardia was identified but that no specific arrhythmia was confirmed at the time of the encounter.

• Measured heart rate: A documented reading above 100 bpm, the standard adult threshold, in the vital signs or exam note.
• No arrhythmia named: The assessment and plan must not name a specific arrhythmia. In the outpatient setting, a “rule out SVT” diagnosis is not coded. The tachycardia itself is reported, and the physician is queried for the final diagnosis.
• Diagnostic workup referenced: ECG, rhythm strip or Holter results cited in the note, even non-diagnostic ones, show that the provider investigated the finding.
• Medical necessity language: The note says why the tachycardia mattered at this encounter, such as symptoms, a need for monitoring, or a change in treatment.
• Provider attestation: The treating provider signs and dates the note. Unsigned documentation is a common medical necessity denial trigger for symptom codes.

A clinical record can timestamp vital signs, tie the ECG billed under 93000 to the encounter, and capture the signature. Kept in one place, those answer the audit questions early. Recording them at the point of care is far easier than rebuilding them before the claim goes out.

Principal or secondary: Where R00.0 sits on the claim

R00.0 can be sequenced as the principal (first-listed) diagnosis when tachycardia is the reason for the encounter and no underlying condition is confirmed. A patient who arrives at urgent care with a symptomatic fast heart rate and a non-diagnostic workup leaves with R00.0 as the principal code.

R00.0 becomes a secondary code when the encounter is driven by a confirmed condition. If a patient is admitted for sepsis and the tachycardia needs its own monitoring, sepsis is the principal diagnosis. Tachycardia is a routine sign of hyperthyroidism, though, so a patient admitted for hyperthyroidism usually gets no R00.0 at all.

Why R00.0 claims get denied, and how to prevent it

R00.0 denials cluster around four failure patterns. Each one can be caught by an edit before the claim leaves the practice.

Routing cardiac claims through a clearinghouse that validates diagnosis-procedure pairings catches Excludes1 and specificity conflicts before they reach the payer. Practices that submit through the Claim.MD clearinghouse can run claim edits against thousands of US payers, flagging code conflicts before a denial occurs.

Tracking remittance denial codes by diagnosis then shows whether R00.0 denials follow a pattern across the billing cycle. Our guide to denial management workflows covers how to work them back.

Medicare and payer rules for R00.0

CMS publishes no National Coverage Determination (NCD) specific to tachycardia diagnosis codes. R00.0 encounters fall under the rules for the services billed, such as E/M visits and cardiac monitoring under 93224 or 93228.

Local Coverage Determinations (LCDs) govern much of that monitoring. A payer then asks whether the services were medically necessary for the documented scenario.

• Medicare: Accepts R00.0 as a standalone diagnosis for E/M encounters where tachycardia is the presenting problem. Cardiac monitoring needs documented symptoms or risk factors behind it, and a bare R00.0 may not support extended monitoring.
• Medicare Advantage: Plans vary. Some require a specified arrhythmia code before authorizing cardiac event monitoring, so check the plan’s coverage policy before submitting.
• Commercial payers: Most accept R00.0 for initial evaluation encounters. Repeat visits for the same unresolved tachycardia may draw scrutiny if no diagnostic progress is documented.
• Medicaid: Rules vary by state. Some state programs require prior authorization for extended cardiac monitoring even when R00.0 drives the order.

The CMS ICD-10 codes page carries the current code files and the ICD-10-CM Official Guidelines for Coding and Reporting.

Review Section I.C.18, the Chapter 18 guidance on symptoms and signs, each October when the guidelines update. Strong clean claim submission habits for cardiac encounters then cut payer touchpoints on R00.0 claims.

Where R00.0 sits in the R00 category

The R00 category covers all abnormalities of heart beat. Coders who see cardiac encounters often should know its full structure, so the most specific code is always in reach.

The AAPC Codify ICD-10-CM lookup shows the full R00 block for checking descriptors and hierarchy. The WHO ICD-10 browser shows the international base classification that ICD-10-CM builds on. R00.9 is the catch-all, so coders should rule out R00.0, R00.1 and R00.2 before defaulting to it.

Picking the most specific code the record supports is one of the medical billing fundamentals every coder works from.

How claims management software keeps R00.0 claims clean

Many R00.0 problems start before the claim exists. The vitals sit in one system and the ECG in another, so the coder works from a summary instead of the note.

Pabau, the practice management platform we build, keeps the encounter note, vitals and uploaded ECG results on the patient’s record. Its integrated claims management software sends CMS-1500 and 837P claims through the Claim.MD clearinghouse. Eligibility checks run before the visit, so coverage questions surface early.

When the payer responds, the electronic remittance advice (ERA) posts back against the same patient record. A denied R00.0 claim then shows up next to the note that supports it, so the fix starts from the documentation.

Cleaner cardiac claims from note to payment

Pabau keeps the encounter note, vitals and ECG results with the claim. US claims go out through the Claim.MD clearinghouse, with eligibility checks and ERA posting.

Book a demo

Conclusion

R00.0 is a holding code. It is right while the record describes a fast heart rate and nothing more, and wrong once the physician names a rhythm. A newborn, a stated IST diagnosis or a confirmed paroxysmal tachycardia each moves the claim to its own code.

So check those three exclusions on every tachycardia claim, and query the physician when the note sits between a symptom and a diagnosis. Book a demo to see how Pabau keeps the cardiac note, the ECG and the claim on one patient record.

Continue your research

Need a refresher on what happens after a claim is submitted? What is revenue cycle management explains the full claim lifecycle from encounter to payment posting.

Getting unfamiliar remittance codes on R00.0 denials? Electronic remittance advice breaks down ERA files, CARC codes, and how to read denial reason codes.

Want to understand how the clearinghouse validates your claims before they reach the payer? Medical claims clearinghouse covers how clearinghouse edits work and what they catch.

Frequently asked questions