ArticleAmerican health & drug benefits2019
Comparing the Medicaid Prospective Drug Utilization Review Program Cost-Savings Methods Used by State Agencies in 2015 and 2016.
Article in American health & drug benefits, 2019. The graph could read no effect estimate from its abstract, so it casts no vote on the map. Cited by 1 paper.
What it found
Each row is one number read from the abstract, on the scale the paper reported it, with its interval. Left of the dashed line favours the treatment, right favours the comparator. Under each row is the sentence it came from. New to these charts? A ten-minute tutorial.
The abstract states no effect estimate the extractor could read, or names no intervention and outcome on the map, so this paper lights no cell and moves no belief. It is still indexed, cited and linked below.
The trial behind it
Trials whose registry record cites this paper, or whose number appears in the abstract. A trial that started after this paper was published is citing it as background, not reporting it.
Neither the registry nor the abstract names a trial number. If this is a trial report, that itself is worth knowing.
Who cites it
1 citing paper in PubMed, 6 citations in OpenAlex.
Corrections and comments
PubMed lists nothing against this paper. Absence here is not a guarantee, only a check that was made.
Authors and funding
2 authors at 1 institution in 1 country.
Funding
No grant is acknowledged in the PubMed record.
Abstract
backgroundThe Medicaid Drug Utilization Review (DUR) program is a 2-phase process conducted by Medicaid state agencies. The first phase is a prospective DUR process and involves electronically monitoring prescription drug claims to identify prescription-related problems, such as therapeutic duplication, contraindications, incorrect dosage, or duration of treatment. The second phase is a retrospective DUR involving ongoing, periodic examinations of claims data to identify patterns of fraud, abuse, underutilization, drug-drug interaction, and medically unnecessary care, and implement corrective actions when needed. The Centers for Medicare & Medicaid Services requires each state to measure the prescription drug cost-savings generated from its DUR programs annually, but it provides no methodology for doing so. An earlier article compared the methodologies used by states to measure cost-savings in their retrospective DUR program in fiscal years 2014 and 2015.
objectiveTo describe and synthesize the methodologies used by states to measure cost-savings using their Medicaid prospective DUR program in federal fiscal years 2015 and 2016.
methodsFor each state, we downloaded from Medicaid's website the cost-savings methodologies included in the Medicaid DUR 2015 and 2016 reports. We then reviewed and synthesized the reports. Methods described by the states were classified into a unique group based on the methodology used, except for Arkansas and Connecticut, which were classified in more than 1 category for the same period.
resultsCurrently, 3 different methodologies are being used by states. In 2015 and 2016, the most common methodology used (by 18 states) was the calculation of total claim rejections and subtracting claim resubmissions at the amount actually paid. The comparisons of DUR program cost-savings among states are unreliable, because the states lack a common methodology in the way they measure their performance.
conclusionsConsidering the lack of methodologic consistency among states in measuring the savings in the Medicaid DUR program shown in this analysis, the federal government must lead an effort to define a unique methodology to measure cost-savings in its entire DUR program. This will help to improve the measure of savings among states and understand how this program is performing in that matter.
Indexed as
Identifiers
30972148PMC6404806W3005918319What OpenQuestion holds
Registered trials
Read under generation 80e0d062 · epoch 390. Bibliography from PubMed, PubMed Central and OpenAlex; grants from NIH RePORTER; trial links from ClinicalTrials.gov; estimates, votes and beliefs from the OpenQuestion graph.