DV Standards Format
After highlighting the artifacts and notes for the DVCs, the table then lists the various validation standards and the criteria related to that standard. These sets of DV standards are the same for all Part C and Part D reporting sections. For example, Standard 1 has the general and specific criteria for validating source documentation that the SO gives to the DVC, and its related criteria appear below.
- Database management and structure: A review of source documents like programming code, spreadsheet formulas, analysis plans, saved data queries, file layouts, and process flows, shows that all source documents correctly capture required data fields, and the SO properly documents them.
Criteria for Validating Source Documents:- SOs properly secure source documents and output and reference data file locations correctly so that DVCs can retrieve source documents at any time to confirm the information submitted to CMS via CMS systems.
- SOs clearly and adequately document source documents.
- SOs correctly capture required data fields, including all data fields for RR in source documents. All data fields have meaningful, consistent labels; for example, the label field for patient ID is Patient ID rather than Field 1 and maintains the same field name across data sets.
- Source documents are error-free; for example, programming code and spreadsheet formulas have no messages or warnings indicating errors.
- SOs appropriately apply version control of source documents.
- SOs capture the appropriate date ranges for the reporting periods. SOs report data based on the required reporting period of 1/1 - 12/31.
- SOs assign data at the applicable level, for example, plan benefit package (PBP) or contract level.