Download:
pdf |
pdfCY 2023 DV
Validation
Standard /
Sub-Standard
CY 2023 DV FDCF (Appendix J)
CY 2024 DV
Validation
Standard /
Sub-Standard
Note:
All validation standards and sub-standards have been made
uniform across all Part C & D reporting sections.
N/A
Note:
Reporting section criterion (RSCs) were removed from both
the EES and DV Manual.
N/A
1
A review of source documents (e.g., programming code,
spreadsheet formulas, analysis plans, saved data queries,
file layouts, process flows) indicates that all source
documents accurately capture required data fields and are
properly documented.
1
Type of
Change
Reason for
Change
Burden
Change
N/A
Update
Consistent with
current technical
guidance
None
N/A
Update
Consistent with
current technical
guidance
None
Database management and structure: A review of source
documents (for example, programming code, spreadsheet
formulas, analysis plans, saved data queries, file layouts,
process flows) shows that all source documents accurately
capture required data fields and the SO has properly
documented them.
Update
Consistent with
current technical
guidance
None
Update
Consistent with
current technical
guidance
None
CY 2024 DV EES (Appendix B)
1.a
Source documents are properly secured so that source
documents can be retrieved at any time to validate the
information submitted to CMS via HPMS.
1.a
SOs properly secured source documents and output, and have
referenced data file locations correctly so that DVCs can
retrieve source documents at any time to validate the
information submitted to CMS via CMS systems.
1.g
Source documents are clearly and adequately documented.
1.b
SOs clearly and adequately documented source documents.
Addition
Renumbering
None
1.c
SOs accurately captured required data fields including all data
fields for RR in source documents. All data fields have
meaningful, consistent labels (for example, label field for
patient ID as Patient ID, rather than Field1 and maintain the
same field name across data sets).
Update
Consistent with
current technical
guidance
None
1.c
SOs accurately captured required data fields including all data
fields for RR in source documents. All data fields have
meaningful, consistent labels (for example, label field for
patient ID as Patient ID, rather than Field1 and maintain the
same field name across data sets).
Update
Consistent with
current technical
guidance
None
1.b
Source documents create all required data fields for
reporting requirements.
1.d
All data fields have meaningful, consistent labels (e.g., label
field for patient ID as Patient ID, rather than Field1 and
maintain the same field name across data sets).
CY 2023 DV
Validation
Standard /
Sub-Standard
CY 2023 DV FDCF (Appendix J)
CY 2024 DV
Validation
Standard /
Sub-Standard
CY 2024 DV EES (Appendix B)
Type of
Change
Reason for
Change
Burden
Change
1.c
Source documents are error-free (e.g., programming code
and spreadsheet formulas have no messages or warnings
indicating errors, use correct fields, have appropriate data
selection, etc.).
1.d
Source documents are error-free (for example, programming
code and spreadsheet formulas have no messages or warnings
indicating errors).
Update
Consistent with
current technical
guidance
None
1.i
Version control of source documents is appropriately
applied.
1.e
SOs appropriately applied version control of source documents.
Update
Renumbering
None
Update
Consistent with
current technical
guidance
None
SOs captured the appropriate date range(s) for the reporting
period(s).
2.a
The appropriate date range(s) for the reporting period(s) is
captured.
1.f
1.f
If used, macros are properly documented.
N/A
N/A
Deletion
Consistent with
current technical
guidance
None
2.b
Data are assigned at the applicable level (e.g., plan benefit
package or contract level).
1.g
SOs assigned data at the applicable level (for example, plan
benefit package (PBP) or contract level).
Update
Consistent with
current technical
guidance
None
1.h
Titles and footnotes on reports and tables are accurate.
N/A
N/A
Deletion
Consistent with
current technical
guidance
None
1.i
Version control of source documents is appropriately
applied.
N/A
N/A
Deletion
Consistent with
current technical
guidance
None
SO reports data based on the required reporting period of 1/1 12/31.
CY 2023 DV
Validation
Standard /
Sub-Standard
CY 2024 DV
Validation
Standard /
Sub-Standard
CY 2024 DV EES (Appendix B)
Type of
Change
Reason for
Change
Burden
Change
2
A review of source documents (e.g., programming code,
spreadsheet formulas, analysis plans, saved data queries,
file layouts, process flows) and census or sample data,
whichever is applicable, indicates that data elements for
each reporting section are accurately identified, processed,
and calculated.
2
Database Extraction Function: Review of source data,
preliminary data sets, and interim data sets (for example,
programming code, spreadsheet formulas, analysis plans,
saved data queries, file layouts, process flows) indicates the
following: SOs accurately identify, process, and verify the
population for each reporting section (including calculations for
the number of members, claims, grievances, procedures, etc.).
They apply QA checks/thresholds to detect outlier or erroneous
data.
Update
Consistent with
current technical
guidance
None
2.a
The appropriate date range(s) for the reporting period(s) is
captured.
N/A
N/A
Deletion
Consistent with
current technical
guidance
None
2.b
Data are assigned at the applicable level (e.g., plan benefit
package or contract level).
N/A
N/A
Deletion
Consistent with
current technical
guidance
None
2.c
Appropriate deadlines are met for reporting data (e.g.,
quarterly).
N/A
N/A
Deletion
Consistent with
current technical
guidance
None
2.d
Terms used are properly defined per CMS regulations,
guidance, Reporting Requirements and Technical
Specifications.
N/A
N/A
Deletion
Consistent with
current technical
guidance
None
CY 2023 DV FDCF (Appendix J)
CY 2023 DV
Validation
Standard /
Sub-Standard
CY 2023 DV FDCF (Appendix J)
CY 2024 DV
Validation
Standard /
Sub-Standard
2.e
The number of expected counts (e.g., number of members,
claims, grievances, procedures) are verified; ranges of data
fields are verified; all calculations (e.g., derived data fields)
are verified; missing data has been properly addressed;
reporting output matches corresponding source documents
(e.g., programming code, saved queries, analysis plans);
version control of reported data elements is appropriately
applied; QA checks/thresholds are applied to detect outlier
or erroneous data prior to data submission.
N/A
2.e
The number of expected counts (e.g., number of members,
claims, grievances, procedures) are verified; ranges of data
fields are verified; all calculations (e.g., derived data fields)
are verified; missing data has been properly addressed;
reporting output matches corresponding source documents
(e.g., programming code, saved queries, analysis plans);
version control of reported data elements is appropriately
applied; QA checks/thresholds are applied to detect outlier
or erroneous data prior to data submission.
2.a
Type of
Change
Reason for
Change
Burden
Change
N/A
Deletion
Consistent with
current technical
guidance
None
SOs accurately identify, process, and verify the population for
each reporting section (including calculations for the number of
members, claims, grievances, procedures, etc.). They apply QA
checks/thresholds to detect outlier or erroneous data.
Update
Consistent with
current technical
guidance
None
CY 2024 DV EES (Appendix B)
CY 2023 DV
Validation
Standard /
Sub-Standard
CY 2023 DV FDCF (Appendix J)
CY 2024 DV
Validation
Standard /
Sub-Standard
CY 2024 DV EES (Appendix B)
Type of
Change
Reason for
Change
Burden
Change
Update
Consistent with
current technical
guidance
None
Update
Consistent with
current technical
guidance
None
Organization implements policies and procedures in their final
stage data sets for submission into HPMS, including the
following:
2.e
The number of expected counts (e.g., number of members,
claims, grievances, procedures) are verified; ranges of data
fields are verified; all calculations (e.g., derived data fields)
are verified; missing data has been properly addressed;
reporting output matches corresponding source documents
(e.g., programming code, saved queries, analysis plans);
version control of reported data elements is appropriately
applied; QA checks/thresholds are applied to detect outlier
or erroneous data prior to data submission.
3
a. Expected counts - Data elements are valid, complete, and
accurate according to the source document that SOs use to
upload/enter data into the HPMS; ranges of data fields are
verified; all calculations (for example, derived data fields) are
verified; they properly address missing data; reporting output
matches corresponding source documents (for example,
programming code, saved queries, analysis plans); they
appropriately apply version control of reported data elements.
b. Organization accurately captures data by applying data
integrity/logical checks; they apply QA checks/thresholds to
detect outlier or erroneous data.
Organization implements policies and procedures in their final
stage data sets for submission into HPMS, including the
following:
3.a
Data elements are accurately entered/uploaded into HPMS
and entries match corresponding source documents.
3
a. Expected counts - Data elements are valid, complete, and
accurate according to the source document that SOs use to
upload/enter data into the HPMS; ranges of data fields are
verified; all calculations (for example, derived data fields) are
verified; they properly address missing data; reporting output
matches corresponding source documents (for example,
programming code, saved queries, analysis plans); they
appropriately apply version control of reported data elements.
b. Organization accurately captures data by applying data
integrity/logical checks; they apply QA checks/thresholds to
detect outlier or erroneous data.
CY 2023 DV
Validation
Standard /
Sub-Standard
CY 2023 DV FDCF (Appendix J)
CY 2024 DV
Validation
Standard /
Sub-Standard
CY 2024 DV EES (Appendix B)
Type of
Change
Reason for
Change
Burden
Change
Organization implements policies and procedures for data
submission, including the following:
3
a. Data elements are accurately entered/uploaded into
HPMS and entries match corresponding source documents.
[Subsection #1, Data Elements A – G, Subsection #2, Data
Elements I – L, Subsection #3, Data Elements A – G,
Subsection #4, Data Elements I – L, Subsection #5, Data
Elements A – B, E – O]
N/A
N/A
Deletion
Consistent with
current technical
guidance
None
Update
Renumbering
None
b. All source, intermediate, and final stage data sets and
other outputs relied upon to enter data into HPMS are
archived.
3.a
Data elements are accurately entered/uploaded into HPMS
and entries match corresponding source documents.
3.a
Expected counts - Data elements are valid, complete, and
accurate according to the source document that SOs use to
upload/enter data into the HPMS; ranges of data fields are
verified; all calculations (for example, derived data fields) are
verified; they properly address missing data; reporting output
matches corresponding source documents (for example,
programming code, saved queries, analysis plans); they
appropriately apply version control of reported data elements.
2.e
The number of expected counts (e.g., number of members,
claims, grievances, procedures) are verified; ranges of data
fields are verified; all calculations (e.g., derived data fields)
are verified; missing data has been properly addressed;
reporting output matches corresponding source documents
(e.g., programming code, saved queries, analysis plans);
version control of reported data elements is appropriately
applied; QA checks/thresholds are applied to detect outlier
or erroneous data prior to data submission.
3.b
Organization accurately captures data by applying data
integrity/logical checks; they apply QA checks/thresholds to
detect outlier or erroneous data.
Update
Consistent with
current technical
guidance
None
3.b
All source, intermediate, and final stage data sets and other
outputs relied upon to enter data into HPMS are archived.
4
All source, intermediate, and final stage data sets and other
outputs relied upon to enter data into CMS systems are
archived.
Update
Renumbering
None
CY 2023 DV
Validation
Standard /
Sub-Standard
CY 2023 DV FDCF (Appendix J)
CY 2024 DV
Validation
Standard /
Sub-Standard
CY 2024 DV EES (Appendix B)
Type of
Change
Reason for
Change
Burden
Change
Update
Consistent with
current technical
guidance
None
Update
Consistent with
current technical
guidance
None
Update
Consistent with
current technical
guidance
None
Organization implements policies and procedures for the
following:
4
Organization implements policies and procedures for
periodic data system updates (e.g., changes in enrollment,
provider/pharmacy status, and claims adjustments).
5
i. Periodic data system updates (for example, changes in
enrollment, provider/pharmacy status, and claims adjustments).
ii. Restoring data in each data system (for example, disaster
recovery plan).
Organization implements policies and procedures for the
following:
5
Organization implements policies and procedures for
archiving and restoring data in each data system (e.g.,
disaster recovery plan).
5
i. Periodic data system updates (for example, changes in
enrollment, provider/pharmacy status, and claims adjustments).
ii. Restoring data in each data system (for example, disaster
recovery plan).
6
If organization’s data systems underwent any changes
during the reporting period (e.g., because of a merger,
acquisition, or upgrade): Organization provided
documentation on the data system changes and, upon
review, there were no issues that adversely impacted data
reported.
6
If organization’s data systems underwent any changes during
the reporting period for example, because of a merger,
acquisition, vendor change or upgrade: Organization provided
documentation on the data system changes and, upon review,
changes were implemented correctly and did not adversely
impact the reported data.
CY 2023 DV Appendix E
CY 2024 DV Appendix E
Location: Table 1, Step 4, Timeline
Location: Table 1, Step 4, Timeline
Early April (allow for up to 1 week)
Early April
Location: Table 5
Coverage Determinations and Redeterminations
Type of
Change
Reason for Change
Burden
Change
Update
Consistent with current technical
guidance
None
Update
Consistent with current technical
guidance
None
Location: Table 5
Coverage Determinations, Redeterminations,
(including At-Risk Redeterminations Under a Drug
Management Program), and Reopenings
CY 2023 DV Manual
CY 2024 DV Manual
Type of
Change
2.1. Part C and Part D Reporting Sections Requiring
Data Validation in 2023
2.1. Parts C and D Reporting Sections Requiring DV
Update
2.2. Reporting Requirements Excluded from the
Validation Requirement
2.2. Reporting Sections Excluded from the DV Requirement
Update
3.2.2.1.
3.2.2.1. Process for Obtaining HPMS Access for SOs and
DVCs
Update
None
3.2.2.2. Process for SOs
Addition
None
3.2.2.3.1. HPMS PRDVM Access
Addition
None
3.2.2.3.2. Instructions for Requesting Plan Access via EFI
Addition
None
3.2.2.3.3. Existing CMS Enterprise User Administration (EUA)
User IDs and HPMS Access
Addition
None
3.2.2.3.4. Submission of Findings to CMS: Annual DV Review
Addition
3.4.1. Introduction to the Data Validation Standards
3.4.1. Introduction to the EES
Update
3.4.2. Data Validation Standards and Reporting
Section Criteria
3.4.2. EES (Appendix B)
Update
3.4.3. Reporting Section Criteria
Deleted
Deletion
4.4. Conduct On-Site or Virtual Visit
4.4. Conduct Site Visit
Update
4.4.4. Extract Census or Sample Data
Deleted
Deletion
Reason for Change
Consistent with
current technical
guidance
Consistent with
current technical
guidance
Consistent with
current technical
guidance
Consistent with
current technical
guidance
Consistent with
current technical
guidance
Consistent with
current technical
guidance
Consistent with
current technical
guidance
Consistent with
current technical
guidance
Consistent with
current technical
guidance
Consistent with
current technical
guidance
Consistent with
current technical
guidance
Consistent with
current technical
guidance
Consistent with
current technical
guidance
Burden
Change
None
None
None
None
None
None
None
None
None
None
None
None
None
CY 2023 DV Manual
4.4.5. Conduct Exit Conference
5.1 Determine Compliance with Data Validation
Standards and Record Findings in the Findings Data
Collection Form (FDCF) (Appendix J) to Upload into
the HPMS PRDVM
CY 2024 DV Manual
4.4.4. Conduct Exit Conference
5.1. Reporting DV Results: How to Determine Scoring
Type of
Change
Update
Update
5.1.1. Reporting Findings for Standards Using Binary
Scale
Deleted
Deletion
5.1.2. Reporting Findings for Standards Using Likert
Scale
Deleted
Deletion
5.1.3. Review of the Findings Data Collection Form
Deleted
Deletion
5.1.4. Guidance for Interpreting Standards and Making
a Findings Determination
Deleted
Deletion
5.2. Provide Draft Findings to Sponsoring Organization 5.2. The EES
Update
None
5.2.1. Reporting Findings for Standards Using Binary Scale
Addition
None
Addition
None
5.2.2. Reporting Findings for Standards Using Likert Scale
5.2.3. Guidance for Interpreting Standards and Making a
Findings Determination from Review of the EES
None
5.2.3.1. Standard 1
Addition
Addition
Reason for Change
Burden
Change
Renumbering due to
deletion
None
Consistent with
current technical
guidance
None
Consistent with
current technical
guidance
Consistent with
current technical
guidance
Consistent with
current technical
guidance
Consistent with
current technical
guidance
Consistent with
current technical
guidance
Renumbering due to
deletion
Renumbering due to
deletion
Renumbering due to
deletion
Consistent with
current technical
guidance
None
5.2.3.2. Standard 2
Addition
None
5.2.3.3. Standard 3
Addition
Consistent with
current technical
guidance
Consistent with
current technical
guidance
Addition
Consistent with
current technical
guidance
None
5.2.3.4. Standards 4-7
None
None
None
None
None
None
None
None
None
None
None
None
CY 2023 DV Manual
CY 2024 DV Manual
Type of
Change
5.3. Review Draft Findings with Sponsoring
Organization and Obtain Additional Documentation
Necessary to Resolve Issues
5.3. Submit DV Review Findings via HPMS PRDVM
Update
None
5.3.1. Review Draft Findings with Sponsoring Organization
Addition
None
5.3.2. Submit DV Review Findings via HPMS PRSVM
Addition
5.4. Submit Data Validation Review Findings via
HPMS PRDVM
Deleted
Deletion
Reason for Change
Burden
Change
Renumbering due to
deletion
None
Renumbering due to
deletion
Renumbering due to
deletion
Consistent with
current technical
guidance
5.4.1. Data Validation Contractor’s Submission of
Findings
Deleted
Deletion
5.4.2. Sponsoring Organization Disagreement with
Findings
Deleted
Deletion
Consistent with
current technical
guidance
Consistent with
current technical
guidance
Consistent with
current technical
guidance
6.2. Receive Pass or Not Pass Threshold Level and
Assess Pass or Not Pass Determination based on
Final Scores
6.3. Sponsoring Organization Appeal of Data
Validation
6.2. Review Final DV Results
Update
6.2.3. SO Appeal of DV Determination
Update
None
Glossary of Terms
Addition
None
EXHIBIT 4. PART C AND PART D REPORTING SECTIONS
EXCLUDED FROM DV
Addition
EXHIBIT 5. PART C AND PART D REPORTING
SECTIONS EXCLUDED FROM DATA VALIDATION
EXHIBIT 5. STANDARD 1: REQUIRED DATA FIELDS ARE
ACCURATELY CAPTURED AND PROPERLY
DOCUMENTED
EXHIBIT 6. GENERAL INSTRUCTIONS FOR DATA
VALIDATION STANDARDS
EXHIBIT 6. EXAMPLES OF CALCULATIONS TO
DETERMINE MINIMUM THRESHOLD OF CORRECT
SAMPLE/CENSUS RECORDS FOR “YES” FINDING
EXHIBIT 7. STANDARD 1: REQUIRED DATA FIELDS EXHIBIT 7. EXAMPLE OF HOW TO DETERMINE MINIMUM
ARE ACCURATELY CAPTURED AND PROPERLY
THRESHOLD OF IMPLEMENTED POLICIES OR
DOCUMENTED
PROCEDURES FOR “YES” FINDING
Update
Addition
Addition
Renumbering due to
deletion
Consistent with
current technical
guidance
Consistent with
current technical
guidance
None
None
None
None
None
None
None
None
None
Consistent with
current technical
guidance
None
Consistent with
current technical
guidance
None
Consistent with
current technical
guidance
None
CY 2023 DV Manual
CY 2024 DV Manual
EXHIBIT 8. STANDARD 2: DATA ELEMENTS ARE
ACCURATELY IDENTIFIED, PROCESSED, AND
CALCULATED
EXHIBIT 8. EXAMPLE OF HOW TO DETERMINE MINIMUM
THRESHOLD OF IMPLEMENTED POLICIES OR
PROCEDURES FOR FINDINGS USING BINARY AND
LIKERT SCORE.
EXHIBIT 9. STANDARD 3: DATA SUBMISSION
EXHIBIT 9. EXAMPLE ROWS FROM EES (APPENDIX B)
AND GUIDANCE FOR STANDARD 1
EXHIBIT 10. STANDARDS 4 AND 5: DATA SYSTEM
UPDATES AND ARCHIVE/RESTORATION
EXHIBIT 10. EXAMPLE OF THE EES (APPENDIX B) AND
GUIDANCE FOR STANDARD 2, SUB-STANDARDS 2.a.
EXHIBIT 11. STANDARDS 6 AND 7: DATA SYSTEM
CHANGES AND OVERSIGHT OF DELEGATED
ENTITY REPORTING
EXHIBIT 11. EXAMPLE ROWS FROM EES (APPENDIX B)
FOR STANDARD 3
EXHIBIT 12. REPORTING SECTION CRITERIA FOR
APPROPRIATE REPORTING PERIOD, REPORTING
LEVEL, AND REPORTING DEADLINE IN PART C
SPECIAL NEEDS PLANS (SNPs) CARE
EXHIBIT 12. EXAMPLE ROWS FROM EES (APPENDIX B)
MANAGEMENT
FOR STANDARDS 4 THROUGH 7
EXHIBIT 13. REPORTING SECTION CRITERION
FOR DEFINING KEY TERMS IN PART D
COVERRAGE DETERMINATIONS AND
REDETERMINATIONS SECTION
EXHIBIT 13. MINIMUM DOCUMENTATION REQUIRED FOR
DV ARCHIVE
EXHIBIT 14. REPORTING SECTION CRITERIA FOR
SELECTED PART C GRIEVANCES DATA
ELEMENTS
Deleted
EXHIBIT 15. EXAMPLES OF CALCULATIONS TO
DETERMINE MINIMUM THRESHOLD OF CORRECT
SAMPLE/CENSUS RECORDS FOR “YES” FINDING Deleted
EXHIBIT 16. EXAMPLE OF HOW TO DETERMINE
MINIMUM THRESHOLD OF IMPLEMENTED
POLICIES OR PROCEDURES FOR “YES” FINDING
Deleted
Type of
Change
Addition
Addition
Addition
Addition
Reason for Change
Burden
Change
Consistent with
current technical
guidance
None
Consistent with
current technical
guidance
None
Consistent with
current technical
guidance
None
Consistent with
current technical
guidance
None
Consistent with
current technical
guidance
None
Consistent with
current technical
guidance
None
Consistent with
current technical
guidance
Reduce
burden
Consistent with
current technical
guidance
Reduce
burden
Consistent with
current technical
guidance
Reduce
burden
Addition
Addition
Deletion
Deletion
Deletion
CY 2023 DV Manual
EXHIBIT 17. EXAMPLE OF HOW TO DETERMINE
MINIMUM THRESHOLD OF IMPLEMENTED
POLICIES OR PROCEDURES FOR FINDINGS
USING BINARY AND LIKERT SCORE.
EXHIBIT 18. EXAMPLE ROWS FROM FDCF
(APPENDIX J) FOR STANDARD 1
CY 2024 DV Manual
Deleted
Deleted
EXHIBIT 19. EXAMPLE OF THE FDCF (APPENDIX J)
FOR STANDARD 2, SUB-STANDARDS 2.A - 2.D.
FOR THE PART D GRIEVANCES REPORTING
Deleted
SECTION
EXHIBIT 20. EXAMPLE ROWS FROM FDCF
(APPENDIX J) FOR STANDARD 2, SUB-STANDARD
2.E RSC-5 FOR PART D GRIEVANCES REPORTING
SECTION
Deleted
EXHIBIT 21. EXAMPLE ROWS FROM FDCF
(APPENDIX J) FOR STANDARD 3 FOR PART D
GRIEVANCES REPORTING SECTION
EXHIBIT 22. EXAMPLE ROWS FROM FDCF
(APPENDIX J) FOR STANDARDS 4 THROUGH 7
EXHIBIT 23. GUIDANCE FOR DATA VALIDATION
STANDARD 1
EXHIBIT 24. GUIDANCE FOR DATA VALIDATION
STANDARD 2
EXHIBIT 25. GUIDANCE FOR DATA VALIDATION
STANDARD 3
EXHIBIT 26. GUIDANCE FOR DATA VALIDATION
STANDARD 4
EXHIBIT 27. GUIDANCE FOR DATA VALIDATION
STANDARD 5
Deleted
Deleted
Deleted
Deleted
Deleted
Deleted
Deleted
Type of
Change
Deletion
Deletion
Deletion
Deletion
Deletion
Reason for Change
Burden
Change
Consistent with
current technical
guidance
Reduce
burden
Consistent with
current technical
guidance
Reduce
burden
Consistent with
current technical
guidance
Reduce
burden
Consistent with
current technical
guidance
Reduce
burden
Consistent with
current technical
guidance
Reduce
burden
Deletion
Consistent with
current technical
guidance
Consistent with
current technical
guidance
Deletion
Consistent with
current technical
guidance
Deletion
Deletion
Consistent with
current technical
guidance
Consistent with
current technical
guidance
Deletion
Consistent with
current technical
guidance
Deletion
Reduce
burden
Reduce
burden
Reduce
burden
Reduce
burden
Reduce
burden
Reduce
burden
CY 2023 DV Manual
EXHIBIT 28. GUIDANCE FOR DATA VALIDATION
STANDARD 6
EXHIBIT 29. GUIDANCE FOR DATA VALIDATION
STANDARD 7
EXHIBIT 30. MINIMUM DOCUMENTATION
REQUIRED FOR DATA VALIDATION ARCHIVE
CY 2024 DV Manual
Deleted
Deleted
Deleted
Type of
Change
Deletion
Deletion
Deletion
Reason for Change
Consistent with
current technical
guidance
Consistent with
current technical
guidance
Consistent with
current technical
guidance
Burden
Change
Reduce
burden
Reduce
burden
Reduce
burden
| File Type | application/pdf |
| Author | Apoorva Srivastava |
| File Modified | 2023-07-26 |
| File Created | 2023-07-26 |