iRhythm Holdings, Inc.: research and development expense

What this measure means

Research and development costs recognized as expense. Capitalization policies and acquired projects can make this differ from total cash invested in development.

Exact concept: us-gaap:ResearchAndDevelopmentExpense. Each value covers an annual-duration reporting interval, shown with both start and end dates. Different units remain separate; no currency conversion or interpolation is applied.

Coverage of this history

Selected reporting periods run from 2014-01-01 to 2023-12-31. The SEC response was captured on 2026-09-20.

This selected history ends more than two years before capture. Do not treat its final value as a current balance or current annual result. More recent filings may use another accounting tag; inspect the filings before drawing conclusions about the company.

Selected filing history

Related financial histories

• iRhythm Holdings, Inc.: total assets
• iRhythm Holdings, Inc.: total liabilities
• iRhythm Holdings, Inc.: stockholders equity
• iRhythm Holdings, Inc.: cash and cash equivalents
• iRhythm Holdings, Inc.: net income or loss
• iRhythm Holdings, Inc.: operating cash flow
• iRhythm Holdings, Inc.: capital expenditure payments
• iRhythm Holdings, Inc.: contract revenue excluding tax
• iRhythm Holdings, Inc.: financing cash flow
• iRhythm Holdings, Inc.: investing cash flow
• iRhythm Holdings, Inc.: retained earnings or deficit
• iRhythm Holdings, Inc.: basic weighted-average shares
• iRhythm Holdings, Inc.: diluted weighted-average shares
• iRhythm Holdings, Inc.: basic earnings per share
• iRhythm Holdings, Inc.: diluted earnings per share
• iRhythm Holdings, Inc.: income tax expense or benefit
• iRhythm Holdings, Inc.: net property, plant and equipment
• iRhythm Holdings, Inc.: share-based compensation expense
• iRhythm Holdings, Inc.: operating income or loss
• iRhythm Holdings, Inc.: current assets
• iRhythm Holdings, Inc.: interest expense
• iRhythm Holdings, Inc.: current liabilities
• iRhythm Holdings, Inc.: current accounts payable
• iRhythm Holdings, Inc.: net current accounts receivable
• iRhythm Holdings, Inc.: common-stock repurchase payments
• iRhythm Holdings, Inc.: operating expenses
• iRhythm Holdings, Inc.: net inventory
• iRhythm Holdings, Inc.: gross profit
• iRhythm Holdings, Inc.: cost of revenue
• iRhythm Holdings, Inc.: selling, general and administrative expense

Inspect the source

Entity

iRhythm Holdings, Inc. / CIK 0001388658

Captured

2026-09-20T07:59:09.531Z

SEC response SHA-256

9fcf8dff597ddbc9b6799ee4a8b1691d44250fb745115d02093b36b9660e8563

Current SEC company facts · Download the original response snapshot (gzip) · Download the selected JSON

Latest-filed annual-report facts per unit and reporting period at capture time. Duration facts cover 300 to 400 days. This selection can include restatements and is not a point-in-time backtest dataset. Missing concepts are omitted, never zero-filled. Values retain original units and are not currency converted. Extended concepts require compatible unit shapes and at least three reporting ends with changing values within one unit. Constant or incompatible added histories are omitted.

Public company accounting reference, not market prices, returns, an investment recommendation, or ALPHAC performance. Validate a separately constructed return series with the validation API; accounting values are not returns.

Use this in research

A financial period ends before its results become public. Use the filing date as a minimum availability boundary, inspect amendments, and retain the original filing vintage when testing historical signals. This latest-filed selection can contain information unavailable at the time.

These pages do not supply prices, total-return histories, corporate-action adjustments or a tradable universe. Build those inputs separately before evaluating a strategy. A profitable backtest can still reflect selection bias or costs that were left out.

Research methodology · Execution and cost assumptions · Check backtest overfitting

Build with the open-source tools

Use these accounting records as inspectable inputs. When you have constructed a return series, the validation tools can help test its statistical evidence and preserve the result with its limitations.

• Get an API key and run your first validation
• Connect the MCP server to your coding assistant
• Inspect the ALPHAC engine on GitHub
• Read the MCP server source and integration examples

import json
from urllib.request import urlopen

with urlopen("https://canlicapital.com/company-data/0001388658.json") as response:
    record = json.load(response)
print(record["fetched_at"])
print(record["policy"])
for concept in record["concepts"]:
    print(concept["tag"], next(iter(concept["observations"])))