Closed codycrossley closed 4 weeks ago
The V1.1 validator is not being supported or maintained because it was based on a set of voluntary instructions that ultimately were not finalized by CMS through rulemaking. Because V1.1 does not meet the current requirements, we will not be adopting this option.
See here for the required JSON schemas or CSV templates and refer to their associated data dictionary.
Problem
The only valid choices for the
cms-hpt-validator
CLI script are currentlyv2.0
andv2.0.0
. However, there already exists av1.1
validator for earlier versions, but it is cannot currently be used due to the current choices constraint within themain()
method ofindex.ts
:.addArgument(new Argument("<version>").choices(["v2.0", "v2.0.0"]))
It was removed in this PR.
Solution
Added "v1.1" to the index.ts file, containing valid choices for the
cms-hpt-validator
script:.addArgument(new Argument("<version>").choices(["v1.1", "v2.0", "v2.0.0"]))
Result
The script will now successfully run the v1.1 validators from the
hpt-validator
repo ifv1.1
is passed as an argument theversion
parameter.Test Plan
CSV
The following command was run:
cms-hpt-validator "/<redacted>/eisenhower_standardcharges-20240628.csv" "v1.1" --format csv --error-limit 1000
And the following output was received:
JSON
Similarly, a JSON file was validated using "v1.1":
cms-hpt-validator "/<redacted>/472654841_cornerstone-specialty-hospitals-tucson_standardcharges.json" "v1.1" --format json --error-limit 1000