> For the complete documentation index, see [llms.txt](https://docs.dataplex-consulting.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dataplex-consulting.com/data-catalog/cms-data-feeds-dataset/cms-data-feeds-catalog/medicare-telehealth-trends.md). # Medicare Telehealth Trends Part of the [CMS Data Feeds Dataset](/data-catalog/cms-data-feeds-dataset/cms-data-feeds-catalog.md) › Medicare Dataplex delivers this CMS feed as the analysis-ready table `DWV.MEDICARE_TELEHEALTH_TRENDS` on Snowflake and Databricks — coverage from 2022 to 2025 in a single aligned schema, refreshed automatically whenever CMS publishes a new file. Every row carries lineage back to the exact CMS source file that produced it. ## Key facts | | | | ------------------ | ------------------------------------------------------ | | **Snowflake** | `DWV.MEDICARE_TELEHEALTH_TRENDS` | | **Databricks** | `cms_dwv.medicare_telehealth_trends` | | **Coverage** | Oct 2022 – Dec 2025 | | **Rows** | 333,508 (total across all reporting periods) | | **Cadence** | Quarterly | | **Update pattern** | Time-partitioned — each file adds one reporting period | | **CMS published** | 2026-06-18 | | **Loaded** | 2026-06-18 | | **Columns** | 13 data + 6 lineage | | **File versions** | 13 | | **License** | CMS public data — U.S. Government work | | **Platforms** | Snowflake Marketplace · Databricks Delta Sharing | Included in the CMS Data Feeds Dataset — [start a free trial on Snowflake Marketplace](https://app.snowflake.com/marketplace/listing/GZT1Z125KDH/dataplex-consulting-data-products-cms-data-feeds-dataset). {% hint style="success" %} **Current** — CMS last published this feed on 2026-06-18. Coverage runs through 2025-12-31. Next CMS release expected \~Sep 2026. {% endhint %} {% hint style="info" %} **Time-partitioned feed** — each file version covers one reporting period, so history is additive. Query the full table for all periods; filter on `YEAR` for a single period. Do **not** filter to the latest file only — that would return just the 2025 reporting period. {% endhint %} ## Sample queries {% tabs %} {% tab title="Snowflake" %} ```sql -- Each file version covers one reporting period (2022, 2023, 2024, 2025) — history is additive SELECT * FROM DWV.MEDICARE_TELEHEALTH_TRENDS LIMIT 100; ``` {% endtab %} {% tab title="Databricks" %} ```sql -- Each file version covers one reporting period (2022, 2023, 2024, 2025) — history is additive SELECT * FROM cms_dwv.medicare_telehealth_trends LIMIT 100; ``` {% endtab %} {% endtabs %} ## About this feed > The Medicare Telehealth Trends dataset provides information about people with Medicare who used telehealth services between January 1, 2020 and December 31, 2025. The data were used to generate the Medicare Telehealth Trends Report. > > — *Source: CMS feed metadata* **Keywords:** Medicare **Theme:** Medicare ## Coverage timeline 2022 🟩 · 2023 🟩 · 2024 🟩 · 2025 🟩 4 of 4 years covered — no gaps. ## Release history | Reporting period | CMS published | Loaded | Latest file | | ----------------------- | ------------- | ---------- | ----------- | | 2025-10-01 – 2025-12-31 | 2026-06-18 | 2026-06-18 | ✓ | | 2025-07-01 – 2025-09-30 | 2026-03-19 | 2026-03-19 | | | 2025-04-01 – 2025-06-30 | 2025-12-18 | 2025-12-18 | | | 2025-01-01 – 2025-03-31 | 2025-09-18 | 2025-09-18 | | | 2024-10-01 – 2024-12-31 | 2025-06-20 | 2025-06-20 | | | 2024-07-01 – 2024-09-30 | 2025-03-20 | 2025-03-20 | | | 2024-04-01 – 2024-06-30 | 2024-12-12 | 2024-12-12 | | | 2024-01-01 – 2024-03-31 | 2024-09-12 | 2024-09-12 | | | 2023-10-01 – 2023-12-31 | 2024-06-13 | 2024-06-13 | | | 2023-07-01 – 2023-09-30 | 2024-03-21 | 2024-03-21 | |
Show 3 earlier file versions | Reporting period | CMS published | Loaded | Latest file | | ----------------------- | ------------- | ---------- | ----------- | | 2023-04-01 – 2023-06-30 | 2023-12-14 | 2023-12-14 | | | 2023-01-01 – 2023-03-31 | 2023-09-15 | 2023-09-15 | | | 2022-10-01 – 2022-12-31 | 2023-06-15 | 2023-08-29 | |
## Data dictionary
📋 13 data columns + 6 lineage columns Column-level definitions are maintained by CMS in the official [Medicare Telehealth Trends data dictionary](https://data.cms.gov/resources/medicare-telehealth-trends-data-dictionary). **Data columns** | Column | Type | | -------------------------- | ------ | | `YEAR` | NUMBER | | `QUARTER` | TEXT | | `BENE_GEO_DESC` | TEXT | | `BENE_MDCD_MDCR_ENRL_STUS` | TEXT | | `BENE_RACE_DESC` | TEXT | | `BENE_SEX_DESC` | TEXT | | `BENE_MDCR_ENTLMT_STUS` | TEXT | | `BENE_AGE_DESC` | TEXT | | `BENE_RUCA_DESC` | TEXT | | `TOTAL_BENE_TH_ELIG` | NUMBER | | `TOTAL_PARTB_ENRL` | NUMBER | | `TOTAL_BENE_TELEHEALTH` | NUMBER | | `PCT_TELEHEALTH` | NUMBER | **Lineage columns** (present on every feed table) | Column | Type | Description | | -------------- | -------------- | -------------------------------------------- | | `ROW_ID` | TEXT | Unique row ID for this table (PK) | | `FILE_ID` | TEXT | Source file — joins to `FEEDS_FILES.ID` (FK) | | `FILE_FEED_ID` | TEXT | Parent feed — joins to `FEEDS.ID` (FK) | | `FILE_NAME` | TEXT | Source file name as published by CMS | | `ROWNUM` | NUMBER | Row number within the source file | | `CREATED_AT` | TIMESTAMP\_NTZ | Timestamp when the record was loaded |
## Row-level lineage Every row in this table traces to the exact CMS source file that produced it. The `FILE_ID` column joins to the `FEEDS_FILES` catalog table, and `FILE_FEED_ID` joins to the `FEEDS` master table: ```mermaid erDiagram FEEDS ||--o{ FEEDS_FILES : "ID = FEED_ID" FEEDS ||--o{ MEDICARE_TELEHEALTH_TRENDS : "ID = FILE_FEED_ID" FEEDS_FILES ||--o{ MEDICARE_TELEHEALTH_TRENDS : "ID = FILE_ID" FEEDS { text ID PK text TITLE text VIEW_NAME text ACCURAL_PERIODICITY } FEEDS_FILES { text ID PK text FEED_ID FK date TEMPORAL_START date TEMPORAL_END date CMS_FEED_MODIFIED number IS_LATEST } MEDICARE_TELEHEALTH_TRENDS { text ROW_ID PK text FILE_ID FK text FILE_FEED_ID FK number YEAR text QUARTER text BENE_GEO_DESC text BENE_MDCD_MDCR_ENRL_STUS number remaining_9_data_columns } ``` Trace any row back to its source file and reporting period: ```sql SELECT d.YEAR, d.QUARTER, d.BENE_GEO_DESC, ff.TEMPORAL_START, ff.TEMPORAL_END, ff.CMS_FEED_MODIFIED FROM DWV.MEDICARE_TELEHEALTH_TRENDS d JOIN DWV.FEEDS_FILES ff ON d.FILE_ID = ff.ID; ``` ## Source & provenance Published by the **Centers for Medicare & Medicaid Services** (bureau 009:38). * [Official CMS data dictionary](https://data.cms.gov/resources/medicare-telehealth-trends-data-dictionary) * [Medicare Telehealth Trends Methodology](https://data.cms.gov/resources/medicare-telehealth-trends-methodology) ## Frequently asked questions ### How often is Medicare Telehealth Trends updated? Quarterly. CMS last published this feed on 2026-06-18, and Dataplex loaded it to the warehouse the same day. New releases are added automatically when CMS publishes them. ### What years does Medicare Telehealth Trends cover? 2022 through 2025. ### How many records are in Medicare Telehealth Trends? 333,508 rows across all 13 reporting periods. Because this feed is time-partitioned, the full table total is the meaningful count — no deduplication needed. ### How do I get Medicare Telehealth Trends data? It's included in the CMS Data Feeds Dataset on the [Snowflake Marketplace](https://app.snowflake.com/marketplace/listing/GZT1Z125KDH/dataplex-consulting-data-products-cms-data-feeds-dataset) (free trial available) and via [Databricks Delta Sharing](https://checkout.dataplex-consulting.com/b/3cIdR2e1J59Sh2w7pWbQY00). Once mounted, query `DWV.MEDICARE_TELEHEALTH_TRENDS` directly — no pipeline setup required. ## Related feeds {% content-ref url="/pages/ChHxmMUbXaxxDkjmq4Zy" %} [Medicare Durable Medical Equipment, Devices & Supplies - by Referring Provider](/data-catalog/cms-data-feeds-dataset/cms-data-feeds-catalog/medicare-durable-medical-equipment-devices-supplies-by-referring-provider.md) {% endcontent-ref %} {% content-ref url="/pages/23JlPDLh1VfZ3bT6688R" %} [Veterans Health Administration Provider Level Data](/data-catalog/cms-data-feeds-dataset/cms-data-feeds-catalog/veterans-health-administration-provider-level-data.md) {% endcontent-ref %} {% content-ref url="/pages/T0lp3P86YVksKba4SwKw" %} [Quarterly Prescription Drug Plan Formulary, Pharmacy Network, and Pricing Information - beneficiary\_cost](/data-catalog/cms-data-feeds-dataset/cms-data-feeds-catalog/quarterly-prescription-drug-plan-formulary-pharmacy-network-and-pricing-information-beneficiary_cost.md) {% endcontent-ref %} {% content-ref url="/pages/LPXLpHOzrZUWgwINtB64" %} [Quarterly Prescription Drug Plan Formulary, Pharmacy Network, and Pricing Information - plan\_data](/data-catalog/cms-data-feeds-dataset/cms-data-feeds-catalog/quarterly-prescription-drug-plan-formulary-pharmacy-network-and-pricing-information-plan_data.md) {% endcontent-ref %} {% content-ref url="/pages/9Z27PdJ4ihvCLfUBV74T" %} [Hospital Value-Based Purchasing (HVBP) - Person and Community Engagement Domain Scores (HCAHPS)](/data-catalog/cms-data-feeds-dataset/cms-data-feeds-catalog/hospital-value-based-purchasing-hvbp-person-and-community-engagement-domain-scores-hcahps.md) {% endcontent-ref %} ## Get this feed 1. [Start a free trial on Snowflake Marketplace](https://app.snowflake.com/marketplace/listing/GZT1Z125KDH/dataplex-consulting-data-products-cms-data-feeds-dataset) or purchase via [Databricks](https://checkout.dataplex-consulting.com/b/3cIdR2e1J59Sh2w7pWbQY00) 2. Mount the share — the database and `DWV` schema appear in your account immediately 3. Run the [sample query](#sample-queries) above — no ETL, no pipeline maintenance Questions about this feed? Contact us at . *** Part of the [CMS Data Feeds Dataset](/data-catalog/cms-data-feeds-dataset.md) — 280+ feeds · 245B+ records · updated daily. [Back to the full catalog →](/data-catalog/cms-data-feeds-dataset/cms-data-feeds-catalog.md#medicare-telehealth-trends) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.dataplex-consulting.com/data-catalog/cms-data-feeds-dataset/cms-data-feeds-catalog/medicare-telehealth-trends.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.