Two implementation problems, not one policy
Two different policies often appeared in the same briefings because both were being implemented at the same time. One changed how Medicare pays for clinical laboratory tests through Medicare payment systems. It replaced an aging fee schedule with rates based on the amounts private payers actually pay. The other created a payment transparency system that requires manufacturers to report payments made to physicians and teaching hospitals.
The policies addressed different subjects. The laboratory reform concerned the information used to calculate Medicare payment rates. The transparency system concerned payments from manufacturers to medical professionals and institutions. Their implementation problems had a common feature: both depended on private parties reporting information that had not previously been collected in the required form.
The delay occurred between adopting the policy and obtaining data that could be used. A reporting requirement can exist before participants have clear definitions, consistent procedures, or complete records. Until those matters are settled, the information may not be suitable for the purpose the policy assigns to it.
Why laboratory payment reform slipped
The laboratory reform depended on private-market pricing data. Medicare could not set rates based on actual private-payer payments until laboratories provided a reliable view of prices across the market. This was part of rewriting how Medicare pays for lab tests.
That collection process required decisions about which entities had to report and which payment arrangements fell within the reporting rules. It also required a method for treating discounts and bundled contracts. Comparing one reported price with another can be difficult when a contract covers several services or includes a discount.
The definitions took several rounds to settle, as reflected in HHS documents in the Federal Register. Each open question delayed the collection period because the data could not be considered ready while the reporting rules were still changing. The problem was not just the volume of information. The information also had to be defined and organized in a consistent way so it could support a rate methodology.
This made delay difficult to avoid. A rate methodology based on data cannot be completed until the underlying data has been collected. If the process is still determining who must report, what counts as a reportable amount, or how contract terms should be handled, rate setting remains tied to unfinished collection work.
The reporting burden also affected laboratories and other entities expected to provide the information. They had to identify payment arrangements that fell within the rules and gather pricing data for a purpose that had not previously required the same process. The reform therefore depended on more than the policy decision itself. It also required new reporting practices across the market.
Why payment transparency faced a similar problem
Payment transparency involved the same type of implementation problem in a different setting. Manufacturers had to report payments made to physicians and teaching hospitals. Before the new reporting process, the parties involved had not assembled all of that information in the required form.
The task involved more than deciding which payments should be disclosed. Manufacturers also needed a process for finding the relevant payments, arranging the information, and submitting reports. Until they could collect the information consistently, the transparency system could not produce usable disclosures.
This helps explain why implementation can take longer than the basic policy requirement suggests. The reporting duty may be clear in general terms while practical questions remain open. The organizations supplying the information still have to decide what belongs in a report and how to gather the necessary records.
The two policies should not be treated as one system. The laboratory reform uses private-payer pricing information to help set Medicare payment rates for clinical laboratory tests. The transparency system uses manufacturer payment information to disclose payments made to physicians and teaching hospitals. One concerns the price of a service. The other concerns the reporting of payments.
Their shared problem was the reporting infrastructure. The laboratory policy required market participants to provide pricing information. The transparency policy required manufacturers to provide payment information. In each case, much of the schedule was taken up by the gap between passing a policy and obtaining data that could actually be used.
Data scope determines policy usefulness
The limits of each data system continue to matter after implementation. Private-payer price data can help inform Medicare rates for clinical laboratory tests, but it does not necessarily answer the cost question for someone who pays cash for a newer drug. Cash transactions fall outside claims data, so information from insured transactions usually does not capture what the direct-pay market charges.
That is a limitation of scope, not evidence that the laboratory data has no value. The data can support the narrower purpose for which it was collected while failing to describe another market. Someone seeking a cash price needs information from the direct-pay market, rather than information drawn only from insured transactions.
The same distinction applies to payment transparency. Reports of payments made to physicians and teaching hospitals can make those payments easier to see, but they do not provide a direct-pay price. A reporting system cannot supply information that it was never designed to collect.
For the question of what cash transactions currently cost, see the direct-pay cost guide.