v8.5.0

📏 Measure & MVP Updates

• QPPA-9539: Initial CQM measures update for PY25 @ckawell-sb (#858)
• QPPA-9727: PY25 Updates to COST and PI measures @john-manack (#859)

v8.4.0

📏 Measure & MVP Updates

• QPPA-9690: Fix cqm zip links for PY24 @ckawell-sb (#853)
• QPPA-9682, QPPA-9683: remove mips and app1 from IA_MVP for PYs 24 and 25 @ckawell-sb (#851)
• QPPA-9666: update ingestion mapping @chetanmunegowda (#849)
• QPPA-9664: Remove weight for IA 2025 @ckawell-sb (#848)
• QPPA-9665: update schema and initialization script @chetanmunegowda (#847)

🐛 Bug Fixes

• QPPA-9690: Fix cqm zip links for PY24 @ckawell-sb (#853)
• QPPA-0000: fix lodash dependency level @ckawell-sb (#850)

🧰 Maintenance

• QPPA-0000; Move pre-commit to dev dependencies. @ckawell-sb (#854)

v8.3.1

🐛 Bug Fixes

• QPPA-9648: remove space from spec links @ckawell-sb (#845)

v8.3.0

📏 Measure & MVP Updates

• QPPA-9634: Update PY24 418 description @ckawell-sb (#843)
• QPPA-9220: update PY25 IA measures @ckawell-sb (#841)

📍 Benchmark Updates

• QPPA-9550: Add mock cost benchmarks @ckawell-sb (#842)

🧰 Maintenance

• [Snyk] Upgrade yaml from 2.5.0 to 2.5.1 @beekoticf (#833)

v8.2.0

📏 Measure & MVP Updates

• QPPA-9615, QPPA-9619: Update ABFM13 metric type @ckawell-sb (#839)
• QPPA-9538: Update Measure Spec Link for Quality Measures 497 & 503 to include addendums @ckawell-sb (#838)
• QPPA-9606: remove eMeasureUuid /eMeasureUuids for PY25 @chetanmunegowda (#837)
• QPPA-9589: PY24 Load ICD10 Updates (truncated measures) @chetanmunegowda (#835)

🐛 Bug Fixes

• QPPA-9605: update initialize-measures-data script @chetanmunegowda (#836)

v8.1.1

🐛 Bug Fixes

• QPPA-0000: revert package main change @ckawell-sb (#834)

v8.1.0

📏 Measure & MVP Updates

• QPPA-9535: Update 2024 Cost Spec Urls with v2 @ckawell-sb (#832)

v8.0.1

🐛 Bug Fixes

• Fixes an issue with 8.0.0 where the dist directory was not being generated, causing errors. (#831)

v8.0.0

This update adds strongly-typed return values to our package functions. This will impact TypeScript users who reference the qpp-measures-repo getter functions. This will not impact JavaScript users or anyone who bypasses the getter functions by referencing the package JSON files directly (not recommended).

We recommend updating as soon as possible, since future data changes will be in later versions building off of these updates. Actual function return data formatting is not changing, but the addition of strict typing will likely require some changes to your code to support it.

🔴 BREAKING CHANGES 🔴

This update adds typed return values to our package functions, which means your code will start erroring if it is expecting differently-formatted responses than our new types. We recommend looking through the following table for the functions your code references and refactoring to use our new types in your code.

Return Type Format Table

Function Name	Return Object/Value	Return Type Interface
getValidPerformanceYears	number[]	number[]
getProgramNames	{ "mips": "mips", "cpcPlus": "cpcPlus", "pcf": "pcf", "app1": "app1", "DEFAULT": "mips", "G0053": "G0053", "G0054": "G0054", "G0055": "G0055", "G0056": "G0056", "G0057": "G0057", "G0058": "G0058", "G0059": "G0059", "M0001": "M0001", "M0005": "M0005", "M0002": "M0002", "M0003": "M0003", "M0004": "M0004", "M1366": "M1366", "M1367": "M1367", "M1368": "M1368", "M1369": "M1369", "M1370": "M1370" } Note: The ProgramNames interface, features key-value pairs for all possible programs names. Depending on how your specific TS application is using this interface, it is possible you'll need to use the keyof operator to enforce strict typing. See documentation on keyof operator here.	ProgramNames
getBenchmarksData	{ [year: number]: { measureId: string; benchmarkYear: number; performanceYear: number; submissionMethod: string; isToppedOut?: boolean; isHighPriority?: boolean; isInverse?: boolean; metricType?: string; isToppedOutByProgram?: boolean; percentiles?: { "1": number; "10": number; "20": number; "30": number; "40": number; "50": number; "60": number; "70": number; "80": number; "90": number; "99": number; }; deciles?: number[]; averagePerformanceRate?: number; }[]; }	BenchmarksData
getBenchmarksYears	number[]	number[]
getBenchmarksExclusionReasons	{ measureId: string; submissionMethod: string; performanceYear: number; benchmarkYear: number; reasonCodes: string[]; reasonDescriptions: string[]; }[]	BenchmarksExclusionReasons[]
getBenchmarksNationalAverages	{ measureId: string; performanceYear: number; benchmarkYear: number; groupNationalAverage: number; individualNationalAverage: number; }[]	CostNationalAverage
getMeasuresData	The data type is to large and branching to document here, the link included shows the entire type structure. We also expose the individual measure types to use throughout your code: https://github.com/CMSgov/qpp-measures-data/blob/develop/util/interfaces/measure.ts	Measure
getClinicalClusterData	{ measureId: string; submissionMethod: string; firstPerformanceYear: number; lastPerformanceYear: number | null; specialtySets?: { name: string; measureIds: string[]; }; clinicalClusters?: { name: string; measureIds: string[]; }; }[]	ClinicalCluster
getMVPData	{ mvpId: string; clinicalTopic: string; title: string; description: string; specialtiesMostApplicableTo: string[]; clinicalTopics: string; hasCahps: boolean; hasOutcomeAdminClaims: boolean; qualityMeasures: QualityMeasure[]; iaMeasures: IAMeasure[]; costMeasures: AggregateCostMeasure[]; foundationPiMeasures: PIMeasure[]; foundationQualityMeasures: QualityMeasure[]; administrativeClaimsMeasures: QualityMeasure[]; }[]	MVPData
getMVPDataSlim	{ mvpId: string; clinicalTopic: string; title: string; description: string; specialtiesMostApplicableTo: string[]; clinicalTopics: string; hasCahps: boolean; hasOutcomeAdminClaims: boolean; qualityMeasures: string[]; iaMeasures: string[]; costMeasures: string[]; foundationPiMeasures: string[]; foundationQualityMeasures: string[]; administrativeClaimsMeasures: string[]; }[]	MVPDataSlim

Using the Types/Interfaces in Your Code

We use interfaces to define the return values. To access the new interfaces, you can use the following import path.

// to get specific interfaces.
import { ProgramNames, IAMeasure } from 'qpp-measures-data/util/interfaces/index';
// to get all interfaces.
import * as MeasuresRepoInterfaces from 'qpp-measures-data/util/interfaces/index';

📏 Measure & MVP Updates

• QPPA-9221: update mvps py2025 @ckawell-sb (#823)

🚀 Features

• QPPA-9423: Adds strong typing to index.ts @john-manack (#827)

🐛 Bug Fixes

• QPPA-0000: Remove /dist from filepath @john-manack (#830)

🧰 Maintenance

• QPPA-9423: fix benchmark type @ckawell-sb (#829)
• QPPA-9422: refactor mvp helper functions @chetanmunegowda (#826)
• [Snyk] Upgrade yaml from 2.4.5 to 2.5.0 @beekoticf (#824)

v7.7.2

🐛 Bug Fixes

• QPPA-0000: add npm ignore file @ckawell-sb (#822) (This was not applied in v7.7.1)