Blogs

Medicare
Industry analysis

-- min read

Turquoise Is Now A CMS Qualified Entity

Which means CMS certified us to work with Medicare claims data

August 18, 2026
Turquoise Is Now A CMS Qualified Entity

Turquoise has just been certified as a Qualified Entity (QE) under the Centers for Medicare & Medicaid Services' Qualified Entity Certification Program.

It's not every day the federal government certifies we know how to handle America's most sensitive healthcare data. For those who don’t know, that means CMS reviewed how we ingest, secure, manage, and report on protected health information and claims data, and decided we're trustworthy enough to work with Medicare's data. Earned only by proving your data pipeline unimpeachable and your data practices of the highest order, the QE designation is an honor, and we're even more excited to dig into the new data now available to us as a QE.

Medicare claims data under Parts A, B, and D is heading to Turquoise soon

As a QE, in the coming months, we'll be able to access and report on Medicare claims data under Parts A, B, and D. 

That means we’ll soon have:

  • Actual utilization and payment data
  • Care settings price transparency data doesn’t currently touch (like skilled nursing facilities, home health, hospice, DME, and physician office claims) 
  • Part D prescription drug event data (pharmacy benefit, fill-level detail)
  • Diagnoses and clinical context
  • Longitudinal patient journeys
  • Payment adjudication detail

How is this different from the commercial claims data we already coupled with price transparency data? Well, commercial claims data is licensed from an aggregator, originally submitted by entities that choose to share it. That data is good but not reliably robust (hence why it acts as a great accompaniment to price transparency data!). Since almost every provider in the country submits claims to Medicare, Medicare data doesn’t suffer from the same gaps as commercial claims. Even a sample of Medicare data is universal in a way commercial claims isn't—there's no market segment Medicare misses, because there's no provider it doesn't touch. Alongside the commercial payer focus of MRF payer rates, this data set is focused on a different population (since Medicare data skews older and sometimes sicker than a commercially insured population) and a different level of granularity.

Basically, as a QE, we can now work directly with charge, payment, and utilization data alongside negotiated rate data. In addition to this new data, as a QE, we’re now required to report on CMS-approved provider performance measures. More on that soon!

It’s not just more data, it’s another piece of the complexity puzzle

This new data sharpens the resolution of Clear Rates—the foundational model of the rates, rules, and relationships underlying how U.S. healthcare gets paid and the foundation of the Turquoise platform. That directly strengthens our ability to simplify the financial complexity of healthcare. Once the data is in hand, we’ll be able to continue to evolve the PATIENT Framework’s Standard Service Packages (SSPs), our open-source, patient-first grouping methodology that collapses the revenue cycle to a single encounter-level price, reducing administrative overhead and enabling guaranteed upfront costs for patients. 

Take a knee replacement, for example. Does that SSP look identical for a commercially insured patient and a Medicare patient, or does it diverge in ways the aggregated data can't show? Right now that's a real question we’re unable to answer. With claims-level Medicare data, it's one we can actually go answer and use to confirm existing SSPs or build new ones specific to that population. 

More to come soon

Once the claims data starts flowing, it's a field day for us healthcare data enthusiasts. Look out for future reporting on the scintillating insights we find.

Your morning brief on the CMS CY 2026 proposed rule
CY 2026 OPPS Final Rule
7/16/25

Your morning brief on the CMS CY 2026 proposed rule

CMS proposes new percentile allowed amounts, a CMP reduction, doubles down on patient utility, and for the first time, looks to add utilization to hospital MRFs.

Providers
True transparency requires prescription drug rates
Prescription Drug Machine-Readable File
7/2/25

True transparency requires prescription drug rates

Read our thoughts, peruse our ideas, and get all the info on the once indefinitely delayed prescription drug file’s new RFI

Life Sciences
Turquoise Health submits public comment on the health technology ecosystem request for information
Price transparency regulations
6/17/25

Turquoise Health submits public comment on the health technology ecosystem request for information

The RFI includes specific questions focused on price transparency and binding cost estimates for pre-defined periods

Providers
As the government plots the next phase of price transparency, so do we
Price transparency regulations
5/23/25

As the government plots the next phase of price transparency, so do we

Phase 1 Price Transparency → Phase 2 Transaction Efficiency

All
Price transparency's first EO comes due with new guidance
Price transparency regulations
5/22/25

Price transparency's first EO comes due with new guidance

TL; DR: Guidance, RFIs, and FAQs walk into a bar

Payers
The most-favored-nation gets another EO on drugs
Most favored nation (MFN)
5/14/25

The most-favored-nation gets another EO on drugs

And what that means for pharmaceutical manufacturers, and providers, and payers, oh my.

Life Sciences
Not just smart—thoughtful: AI that frees the contracting SME
AI
5/13/25

Not just smart—thoughtful: AI that frees the contracting SME

Hold on to your hats, and also, those FTEs

Providers
New executive order on drug prices
Drug pricing policy
4/24/25

New executive order on drug prices

A Brief Legislative Brief

Life Sciences
What actuaries actually need to overcome data overload
Industry analysis
4/4/25

What actuaries actually need to overcome data overload

From your friendly neighborhood actuary

Payers

No results found

There are no results with this criteria. Try changing your search.