Guidance for DV Standard 1

Please refer to DV Manual 5.2.3. Guidance for Interpreting Standards and Making a Findings Determination from Review of the EES.

Implementation Guidance

(Sub-Standards 1.a -1.g)

Determine if the SO’s source documents, like programming code, spreadsheet formulas, analysis plans, saved data queries, file layouts, and process flows, correctly capture the data fields needed for each reporting section under review and are documented with the necessary detail and information to create data file sets and other outputs.

Make sure that all source documentation is legible, descriptive, and understandable, including each of the following:

• Standard Operating Procedures (SOPs) include detailed workflows and processes related to managing, producing, and tracking source documents
• Title and footnotes SOs used in programs and the reported output is legible and correspond to HPMS reports and tables
• If used, SOs properly document macros
• SOPs, file-naming conventions, dates of source documents, and output reports show application of version control
• SOs reference data file locations correctly within source code; for instance, these files can be located using the references that exist within the source code
• Dated HPMS entries match the source documents to create the data entered in the HPMS
• Verify that SOs selected data at the proper level, such as either the contract or the PBP level
• Check date ranges, demographic information, and eligibility information to examine proper data filtering
• Make sure that the DVC uses the current documentation, and it’s about the time period of the RR.