Overview
Tip: First Time Users - It is recommended that you visit MU: Introduction to Determining Medicaid Volume using the OP Software for a step-by-step process to determine how to best configure your Meaningful Use Volume to match the State Group SQL selections in the table below. |
The State Group SQL table provides you with a list of States and the associated attestation links to SQL reports that you can run to obtain provider attestation results.
Note: There is only one level of security in Database Viewer. That level of security is permission access. A staff member who has access to the Database Viewer can theoretically run any report that contains any data. This includes data concerning medications, diagnoses, lab results, and other sensitive areas of a patient's chart. Therefore, your practice should limit Database Viewer/SQL access only to individuals at your practice who would normally have access to this information. You will need to have the proper access to utilize your OP Database Viewer in order to utilize the SQL codes in this library. See Providing Access in OP Database Viewer Basics for more information. |
For brief instructions and an animated image on how to quickly clip and save SQL code, click here.
Note: The Database Viewer accesses the same database as the OP software. If you run a query that filters a lot of data, your database could become sluggish and affect your users. It is recommended to run queries during hours when users are not running the OP software. The Database Viewer is a powerful tool for aggregating data into a single file, which can prove to be a double-edged sword if placed in the wrong hands. This is even more relevant if your practice does not follow other best practices. For example, a practice may store unencrypted credit card numbers in the Patient Register. That is an ill-advised risk. The reason it is a risk is because the Database Viewer makes it very easy to download all of those credit card numbers into a single Excel file if using the proper SQL code. So, please only grant individuals at your practice the use of this powerful tool if they would normally have access to that sensitive information. |
State Group SQL Table
Please visit State Assumptions to find the logic behind each grouping. It is each practice’s responsibility to confirm with your state’s Medicaid agency that the assumptions made are current for the reporting year as of the date of the practice’s attestation. Export, save, and print all results for audit purposes at the time you run them for actual volume validation.
Note: To quickly find the form you want in this table:
Java must be enabled in order to use the search and sort capability. Otherwise, just scroll through the table to find your state. |
Group | State | SQL Code Attestation Type | Variable Note |
Depends on county and provider type | |||
Depends on county and provider type | |||
Depends on county and provider type | |||
2.52% | |||
2.52% | |||
2.52% | |||
Look up in attestation tool | |||
Look up in attestation tool | |||
Look up in attestation tool | |||
Different for each attesting NPI | |||
Different for each attesting NPI | |||
Different for each attesting NPI | |||
Depends on county | |||
Depends on county | |||
Depends on county | |||
4.40% | |||
4.40% | |||
4.40% | |||
5% | |||
5% | |||
5% | |||
Changes annually | |||
Changes annually | |||
Changes annually | |||
Group 5 | Montana | See Note in next column | Please contact your state Medicaid office to determine its rules. Also, if you can share your findings with us,we can help you find the correct attestation report(s). |
Group 5 | Virginia | See Note in next column | Please contact your state Medicaid office to determine its rules. Also, if you can share your findings with us,we can help you find the correct attestation report(s). |